Join my presentation on: The boundary values of your test team
Developing software requires collaboration. Between humans, between humans and computers, between humans and documentation, between humans and AI. We know for decades that requirements (specifications, models, user stories, …) are incorrect, incomplete and inconsistent by definition, and that collaboration and communication are key.
Use the voting options below to nominate this presenter for the Best Presenter Award and the Best Presentation Award.
Breaking the system, helping to rebuild it, and providing advice and guidance on how to avoid problems. That’s me in a nutshell. With over 20 years of experience in test consultancy in a variety of environments, I have seen the best (and worst) in software development. I’m chair of the ISTQB Advanced workgroup, author and international keynote speaker.
Developing software requires collaboration. Between humans, between humans and computers, between humans and documentation, between humans and AI. We know for decades that requirements (specifications, models, user stories, …) are incorrect, incomplete and inconsistent by definition, and that collaboration and communication are key.
However, collaboration and communication require some group dynamics, leaving ones comfort zone to explore new ideas and possibilities. Since less is being documented, the wellbeing of the team is even more crucial than ever.
In this talk, I’ll highlight some tell-tale signs that your team has most likely hit its boundaries. A warning light if you want, of upcoming loss of velocity, job satisfaction, retention drop and lower software quality.
