Either way, it is a symptom that the development team is not using the whole team approach that is central to Agile...
development, and that the feedback loop is much too long. When we collaborate closely with customers from the beginning, get concrete examples from them of desired system behavior and turn those into tests that drive development, they won't have any unpleasant surprises during the iteration demo. When testers and programmers work together throughout the development of a user story, working together on the high level acceptance tests, testing and coding in tiny increments so that development stays on track, there won't be an antagonistic situation of a tester "rejecting" the delivered code. Hold frequent retrospectives – maybe even after a story is completed, just for that story – to bring the whole team together and identify the biggest impediments to successful delivery. Is testing falling behind coding? Perhaps the programmers can help with automating tests and other testing activities. Are the testers physically separate from the programmers? Move everyone so all roles of the development team sit together, or if that's not possible, use video and audio to facilitate real-time, face-to-face communication.
Changing from a phased-and-gated methodology to an Agile environment is a big cultural change. Testers, programmers and other team members need plenty of time, support and training to make this move. Managers should nurture a learning culture and make quality, not quantity or meeting deadlines, the goal. As Jurgen Appelo points out in his new book, Management 3.0, teams need to be empowered, so they can self-organize with a clear purpose and shared goal and grow appropriate structure. They need time and resources to develop competence, and team members need to be energized. Testers and programmers who never worked together before need time to experiment with the best ways to collaborate. It's not going to happen overnight, so get your team together and identify one baby step you can take today.
Dig Deeper on Agile Software Development (Agile, Scrum, Extreme)
Related Q&A from Lisa Crispin
Agile leader Lisa Crispin explains a more organic, more Agile approach to test reporting.continue reading
When it comes to Agile planning, average time over many iterations is a more important metric than individual story estimates.continue reading
Most inexperienced Scrum teams overcommit on what they will deliver, and when. Agile leader Lisa Crispin says that does more harm than good.continue reading
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.