Agile Testing in unified teams
Suppose a team is developing a feature for call center software that allows a customer representative to provide detailed notes about a call to their supervisor for review each week. The software developer on that team’s project writes the code for that feature during the current iteration, while the QA team is happily testing the features the development team had completed last week.
The development team finishes the feature and in the next iteration, they move on to another feature and hand the call notes feature over to QA to test. Well, it just so happens that when the QA team starts testing the feature, the customer who is going to use the software tries it out as well and discovers that they actually want the feature implemented in a completely different way.
Obviously, at this point it doesn’t make sense for QA to continue testing the feature, so they stop. But now, the developers are already working on something else, so they either have to stop what they are doing and start working on the call notes feature again, or they have to put off the changes to the feature for the next iteration. Even if they manage to complete the requested changes to the feature in their current iteration, it will be a whole other iteration before the feature is tested. Not very Agile.
DOWNLOAD the entire document to keep learning how to become Agile by creating a unified team environment between developers and QA analysts