Quality Awareness When Practicing Agile Testing
1 like1,808 views
The document discusses the importance of quality awareness in agile testing, emphasizing the need for continuous collaboration and involvement of QA in planning and execution. It highlights the challenges faced in test planning and proposes strategies such as parallel QA sprints and the integration of QA in poker planning to improve quality outcomes. The presentation frames agile practices around delivering customer-ready products, maintaining a focus on the quality throughout each phase of the testing process.
Quality Awareness When Practicing Agile Testing
- 1. Quality Awareness When Practicing Agile Testing Ana Milutinovic Quality Assurance Engineer @ youngculture 25th of October 2014
- 2. “Quality is a value to some person, at some time” Jerry Weinberg 1. Understanding the impact of this statement 2. Going to effort of making every team member aware of this concept
- 3. How did agile come around? Deliver working software frequently… Daily whole team collaboration… Build projects around motivated individuals… Working software as the primary measure of progress… Self-organizing teams… Satisfied customers…
- 4. Go agile! How it really looked
- 5. SCRUM Framework Test management tool Defect tracking tool Product backlog Team 5 – 7 people Sprint 2 weeks First release after 1,5 year Customer-ready Product Increment Project duration: 3 years and counting…
- 6. Problems We were confused in Test Planning Sprints looked like small Waterfalls NNoo ttiimmee ttoo tteesstt BBuuggss aaccccuummuullaattiinngg QA was left out of the process.
- 7. Living in a time box
- 8. Quality in Planning Ideas to improve Test Planning: PPaarraalllleell QQAA SSpprriinntt QQAA iinn PPookkeerr PPllaannnniinngg
- 9. Quality in Planning 3 8 5 QA Poker Planning “Everyone involved with delivering code is a developer, and is part of the developer team.” Lisa Crispin and Janet Gregory
- 10. Quality in Planning Arguments for (not)involving QA into Poker Planning: Symmetry between testing and programming Testing never ends Where is the scope of ‘Done’ CD system Programming never ends Agile implies adjustments QA was included into calculation
- 11. Quality in Design Avoid presenting finished test cases to developers Create a common understanding of the user story, get the right direction and split it into smaller pieces Decision on which stories need automation
- 12. Quality in Execution IF IT CAN’T BE TESTED IT’S NOT GOING INTO SCRUM AUTOMATION IN EACH SPRINT CONTINIOUS DELIVERY TESTABLE USER STORIES QA ESTIMATED TEST AUTOMATION AGREEMENT CLEARLY ESTABLISHED TEST GOALS
- 13. Quality in Reporting and Metrics We allowed testing to be planned in fewer details Attention in reporting to whatever is specific for the current sprint
- 14. Quality in Reporting and Metrics Test Planning • Test strategy • Story board • Simple test management tool Defect Tracking Tool • Not track defect rates • Attention on fast feedback Sprint Review • Discussion whatever defect influenced the sprint in an interesting way
- 15. Agile in Fundamental Test Process Planning Control Analyses Design Test Closure Reporting Execution
- 16. Thank You! Switzerland youngculture AG Hotelstrasse - Postfach 2574 CH-8060 Zürich-Airport Tel. +41 (0)44 366 40 40 office.ch@youngculture.com Germany youngculture (Deutschland) Rottmannstrasse 11 DE-80333 Munich Tel. +49 (0)89 890 637 40 office.de@youngculture.com Austria youngculture (Österreich) GmbH Renngasse 4 AT-1010 Vienna Tel. +43 (0) 1 532 19 60 office.at@youngculture.com Serbia (Nis and Belgrade) youngculture d.o.o. Bulevar Z.@inAica 64a RS-11000 Belgrade Tel. +381 (0)11 404 99 50 offfice.rs@youngculture.com Romania youngculture (Romania) S.R.L Palas 7B-7C, UBC3 Tower RO-700032 IaFi Tel. +40 (0)33 27 10 530 offfice.ro@youngculture.com www.youngculture.com - www.youngculture-mobile.com