8 Agile Testing Success Factors
Download as PPTX, PDF3 likes627 views
The document discusses success factors in agile testing, emphasizing collaboration, shared ownership, and the importance of a whole-team approach to quality. It introduces practical exercises like building a Jenga tower to illustrate teamwork dynamics and highlights the need for automating processes to shorten feedback loops. It also addresses behavior-driven development to align business and development expectations with a common language.
8 Agile Testing Success Factors
- 1. (Agile) Testing Success Factors 8 Glenn Waters www.westborosystems.com @gwww https://ca.linkedin.com/in/glennwaters
- 14. Whole Team1
- 16. Whole Team1 We own quality And, we help each other achieve it!
- 17. I can break anything! 2
- 18. I can break anything! We work together to improve it!!! 2
- 19. Mindset shift I can break anything! We work together to improve it!!! 2
- 20. Jenga Exercise • The goal is to build a tower with Jenga blocks • Tower must use all 36 Jenga pieces • Tower must be at least 30 cm high (12 inches) – One block is 7.5 cm long (3 inches) 20
- 21. Jenga Exercise • Teams of 5 - 6 • Two testers on each team • This is a timed exercise • One of the testers can be the timekeeper – Not done until testers say you are done!! 21 https://commons.wikimedia.org/wiki/File:Jenga_tower_with_vertical_pieces.JPG
- 22. Automate3
- 23. Automate Automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate Automate, automate, automate, automate, automate 3
- 24. Picture from: Sam Laing and Karen Greaves book, A Coach’s Guide to Agile Testing. Original idea from Mike Cohn
- 25. Practices4
- 28. Practices4 Pairing, Mobbing Shared ownership And more… • Simple design • Shared language • Refactoring • Sustainable pace
- 35. Deepen understanding Behavior-Driven Development • Concrete, specific examples of needs • Common language across Business and Development • Language is such that it can be automated 7
- 36. Check Explore Business Business-facing expectations Risks to external quality attributes Technology Technology- facing expectations Risks to internal quality attributes Ideas from Elisabeth Henrickson, James Bach, et. al. 8
- 37. Check Explore Business Business-facing expectations Risks to external quality attributes Technology Technology- facing expectations Risks to internal quality attributes Ideas from Elisabeth Henrickson, James Bach, et. al. Don’t be a Checker8
Editor's Notes
- #18: Instead of “We are here to break the software” think “What can we do to ensure successful delivery” Move from “Quality Police” to “Collaboration to achieve positive outcome”
- #19: Instead of “We are here to break the software” think “What can we do to ensure successful delivery” Move from “Quality Police” to “Collaboration to achieve positive outcome”
- #20: Instead of “We are here to break the software” think “What can we do to ensure successful delivery” Move from “Quality Police” to “Collaboration to achieve positive outcome”
- #21: Meet with testers privately; give them 4 numbers and tell them NOT to share Round 1: build entire tower then test Round 2: build 9 blocks then test; repeat Round 3: build 1 block then test; repeat Round 4: your process 27 21 31 29 15 12 33 18 11 1 32 6 14 20 16 36
- #22: Meet with testers privately; give them 4 numbers and tell them NOT to share Round 1: build entire tower then test Round 2: build 9 blocks then test; repeat Round 3: build 1 block then test; repeat Round 4: your process 27 21 31 29 15 12 33 18 11 1 32 6 14 20 16 36
- #26: Pairing, Mobbing Simple Design Collective ownership
- #27: Pairing, Mobbing Simple Design Collective ownership
- #28: Pairing, Mobbing Simple Design Collective ownership
- #29: Pairing, Mobbing Simple Design Collective ownership