It is fairly hard to know what solid software testing is all about within Agile and Scrum teams. What traditional software testing practices are fine to continue, which ones need modification and what totally new approaches are necessary. Moving from traditional testing to agile testing is often a high-wire balancing act to some degree with no clear direction.
This presentation explores the critical lessons from teams that have successfully made the transition. We’ll explore the requisite team skills, how to deal with agile requirements, the right strategies for developing agile automation, how to plan and test within your agile team, effective agile test metrics, and aspects of quality for agile teams. The lessons will be shared via real stories from real agile teams who have crossed this chasm-so no hypotheticals here.
Transitioning from traditional to Agile testing means shifting from late-phase, document-heavy, sequential testing to continuous, collaborative, iterative testing that starts on day one of development. Agile testing integrates testers into the team, emphasizes rapid feedback, and adapts to change quickly.
This transition to Agile testing faces challenges that include difficulty to adapt to rapid change, lack of test automation skills, difficulty to get clear requirements early on and cultural resistance to collaboration between developers, testers and product owners.
Video Producer: https://www.eurostarconferences.com/
Further reading:
* Book “Agile Testing” by Lisa Crispin and Janet Gregory, Addison Wesley
* 4 Reasons Why Scrum Needs Testers From Day 1
* 5 Tips for Getting Software Testing Done in the Scrum Sprint