Useful stepping stones in growth towards Agile testing by Kees Blokland
Download as PPTX, PDF0 likes68 views
The document outlines a strategy for transitioning to agile testing, emphasizing a stepwise approach and identifying key areas for improvement. It introduces the concept of 'stepping stones' to navigate the transition and highlights the importance of stakeholder commitment, planning, and team dynamics. The goal is to achieve effective testing and better project predictability through an iterative process that adapts to the agile methodology.
Useful stepping stones in growth towards Agile testing by Kees Blokland
- 1. Useful stepping stones in growth towards Agile testing. Kees Blokland kees.blokland@polteq.com https://improvement.polteq.com/ti4agile
- 2. 2© 2015 Transition to Agile • Many follow a stepwise approach • Cross the river using stepping stones (and keep going)
- 3. 3© 2015 Approach for transition to Agile (testing focus) • How to outline a route towards Agile (testing)? • How to stimulate / motivate and prevent stagnation? • Recipe: – Start form an industry standard test improvement approach – Identify ‘Agile’ and ‘Scrum’ ingredients – Mix these with a lot of field experience • Result: TI4Agile
- 4. 4© 2015 Agile testing maturity levels Forming Norming PerformingAgiletestinglevels Set the basis and the first steps towards working in an Agile manner Adopt a process that facilitates the Agile view on working Continuously improve the way you work by living the Agile way
- 5. 5© 2015 Key areas and checkpoints Key area Forming Norming Performing 1 Stakeholder commitment 1 2 3 4 1 2 3 4 1 2 3 2 Planning & Estimation 1 2 3 4 1 2 3 4 1 2 3 4 3 People 1 2 3 4 1 2 3 4 1 2 3 4 Interaction 1 2 3 4 1 2 3 4 1 2 3 4 5 Teamwork 1 2 3 1 2 3 4 1 2 3 4 6 Test process 1 2 3 1 2 3 4 1 2 3 7 Test management 1 2 3 4 1 2 3 1 2 3 8 Test profession 1 2 3 4 1 2 3 4 1 2 3 9 Test automation 1 2 3 1 2 3 4 1 2 3 4 10 Regression & E2E testing 1 2 3 4 1 2 3 1 2 3 4 11 Defect management 1 2 3 1 2 3 4 1 2 3 12 Test environment 1 2 3 1 2 3 1 2 3 4 Checkpoint description on https://improvement.polteq.com/ti4agile
- 6. 6© 2015 How to outline a route to Agile testing? • Make a picture of the current situation using the model • Identify ‘gaps’ • Decide on what to do first and what to do next – Quick wins, what can be done now – Short term and mid term – Logical sequence as suggested by the model – What is on the horizon? Where to aim for? • Implement!
- 7. 7© 2015 How to stimulate and motivate? • What is in it for everyone? • ‘Agile’ is not the goal, it is the benefits of Agile • What are benefits of important steps underway? • When do we get such benefits? • Mark the route with stepping stones!
- 8. 8© 2015 Just good testing!
- 9. 9© 2015 product risk analysis exploratory testing testing techniques @ sprint planning done well Just good testing! As testers we need to make choices What to test and what not to test What to test thoroughly, what to test superficially What to test first, what to test later What to test once, what to test each software build What to test by senior testers, what by others What to test scripted, what to test exploratory, … just to name a few
- 10. 10© 2015 Just good testing! http://www.stickyminds.com/interview/things-really-matter-testing-today-and-tomorrow-interview-bj-rollison
- 11. 11© 2015 Just good testing! Getting the best testing in the time available - Most serious bugs found - Fit for purpose Benefits
- 12. 12© 2015 Cross functional team in one location Practice example
- 13. Cross functional team in one location Agileprinciples
- 14. 14© 2015 Cross functional team in one location Scrummaster ProductOwner Testlead Dev.lead SOS India One location China One location Collaboration Cooperation Communication USA Practice example
- 15. 15© 2015 Cross functional team in one location Scrummaster ProductOwner Testlead Dev.lead SOS India One location China One location Collaboration Cooperation Communication USA
- 16. 16© 2015 Cross functional team in one location Enables Agile - Teamwork - Interaction - Lean documentation Increases team velocity Benefits
- 17. 17© 2015 Simplified process - 1 Practice example
- 18. 18© 2015 Simplified process - 1 sprints
- 19. 19© 2015 Simplified process Increases predictability of project results - Better scope control - Less delays - Easier to deal with changes Benefits
- 20. 20© 2015 Simplified process - 2 bugs bugs bugs bugs late feedback Practice example
- 21. 21© 2015 Simplified process - 2 Tea m tester dev dev user Practice example
- 22. 22© 2015 Simplified process - 2 Reduces ‘waterfall-ish’ behaviour Enables lean documentation Increase project predictability Benefits
- 23. 23© 2015 Finish testing within the iteration bugs bugs bugs bugs rework Practice example
- 24. 24© 2015 Finish testing within the iteration stop dev stories<1 day
- 25. 25© 2015 Finish testing within the iteration Creates flow in the team Potentially shippable product at the end of the sprint Benefits
- 26. 26© 2015 Agile (testing) transition • Stepping stones help crossing the river • Use them and keep on moving • Like antibiotic therapy: you need to complete it Conclusion https://groengeloven.files.wordpress.com/2014/04/ijsbeer-springt.jpg
- 27. 27© 2015 Agile (testing) transition • Stepping stones help crossing the river • Use them and keep on moving • Like antibiotic therapy: you need to complete it • Recognize stepping stone benefits and motivate people based on it • Experience shows: it’s worth it! Conclusion The best testing in the time available Increased predictability Increased productivity
- 28. Useful stepping-stones in growth towards Agile testing. Kees Blokland kees.blokland@polteq.com https://improvement.polteq.com/ti4agile
Editor's Notes
- #3: In many organizations agile is introduced. This is done in various ways. In certain environments enhtusiastic people just start applying aome agile practces, mostly from scrum methodology and find out what works and what doesn’t Others just pick up succesful practices In other organzations people where people just feel comfortable with a sequential way of working a change program needs to get people going IN both of thses examples it is recommended to follow a stepwise approach In the first case: to check that we do not forget to implement important practices and miss benefits In the second example to get things going TO make it easier for people to buy in to agile I will share with you en number of stepping stones that show that you already get benefits underway
- #6: Discuss the concepts of: Key areas Maturity levels Checkpoints
- #8: Using real life experiences of projects we did