QA in an agile world Tom Churchwell
Download as PPTX, PDF1 like510 views
This document discusses quality assurance in an agile development environment. Some key points: - In agile, quality is a team responsibility built into each sprint through practices like test-driven development and continuous integration. QA focuses on working software rather than documentation. - Traditional QA tested after development, but agile QA works throughout development. Automated testing and continuous integration allow for faster feedback. - The "definition of done" ensures quality standards are met before work is considered complete. This includes things like testing, documentation, and business verification of requirements. - Metrics like burn-down charts are used to track progress and quality over iterations. Visualizing progress helps the team respond quickly to changes.
QA in an agile world Tom Churchwell
- 1. QA in and Agile World Tom Churchwell TChurchwell@GMail.com
- 2. Agenda 2 Survey Exercise 1 Agile vs. Traditional Effect of Test Driving Testing Pyramid Exercise 2 Q&A
- 3. Quick Survey 3 How many QA folks are focused on testing? Who owns Quality? Who owns improvement?
- 4. What is different? 4 Old Focus No Defects ◦ By Requirements Comprehensive Testing ◦ Slow ◦ Manual Integration at the End of Dev Quality Tested In No Defects ◦ By PO Demo Fast ◦ Automated Testing ◦ Continuous Integration Clean Code ◦ Modular Quality Built In
- 5. Manifesto for Agile Software Development We are uncovering better ways of developing software by doing it and helping others do it. Through this work we have come to value: • Individuals and interactions over processes and tools • Working software over comprehensive documentation • Customer collaboration over contract negotiation • Responding to change over following a plan That is, while there is value in the items on the right, we value the items on the left more.
- 6. Working Software 6 Quality Assurance is all about working software. Quality Standards Confidence in the codebase is the key to sente; having choices, momentum, velocity, autonomy, adaptability, competitive advantage and the inherent propensity for innovation and luck.
- 7. Exercise 1 7 What does a traditional QA do that an Agile QA does not do? What skills does an agile QA need that a traditional QA does not? Report Outs…
- 8. Cultural Environmental Practical Collaborative Big & Visible Perpetual Buzz Food Thorough Courageous Adaptable Forthright FUN TDD Quality Standards Iterative Development Business Verification
- 9. Whole Team Ownership Quality as a fundamental ongoing concern for the team ◦ Not just at the end of a release ◦ Meeting quality standards has become a part of the “Definition of Done” for the whole team An Integrated Team Focus ◦ QA throughout development Elimination of QA as a sequential process ◦ Whole Team collaboration from beginning to end ◦ Teams take ownership Definition of Done Quality Standards Level of quality being produced every day Business Verification ◦ Weekly verification demo ◦ Product Owner Drives the Demo
- 10. 10
- 12. Bake Quality In… We Cannot Improve Our Recipe’s By Eating More Cookies… We Must Bake, Rather Than Try To Test Quality In!
- 13. Whole Team Ownership of Quality Historically QA has been: ◦ An event that occurs after development is done Point in time validation rather than an ongoing standard for quality Verification before production launch ◦ Held by QA Not part of “Definition of Done” for the team Not part of what every member of the team was committed to uphold. ◦ Part of a rigid sequential process At the end of development An event rather than an ongoing concern
- 14. Definition Of Done 14 Build it RIGHT -- “Done” • Quality Metrics Passed • Unit test coverage at or above 80% overall • Cyclomatic Complexity 1-3 • Fewer Than 10 Statements per Method • Integration tests created and successfully passed for each external dependency (minimum one per dependency) • Deploy scripts updated for deployment to DevInt and QA. • Functional tests pass in DevInt or preferably QA • Functional tests automated (Selenium, Fitnesse or other) • Single user execution against functional timing SLA passed for each story. • Business verified by product owner OR technical lead/architect if technical card. • Exploratory Testing Complete
- 15. Definition Of Done 15 “Production Ready” -- “Done” – Done • Performance testing executed and passed. • Production-level content successfully integrated and tested • Accessibility & Usability Tested • Full browser testing for all specified browsers and versions
- 17. Test Driving 17
- 19. Working Software Environment 19 Source Code Management
- 20. Environment 20 Source Code Management Continuous Integration
- 21. Environment 21 Pairing Stations Source Code Management Continuous Integration
- 22. Environment 22 Pairing Stations Source Code Management Continuous Integration
- 23. Building Work Software 23 Code Check Out Source Code Management
- 24. Building Work Software 24 Code Development Source Code Management
- 25. Building Work Software 25 Coding Pair Source Code Management Code Check-In Continuous Integration
- 27. Spike - End-to-End What’s needed end to end? Travel Light
- 29. • Project Concerns – Tight Schedules – Maintaining “High Quality” despite changes – Responsiveness to customer needs • Project Situations – Don’t know all of what is needed at onset of project • ONLY Commit for the “Known's” – Requirements Change During the Project • Accommodate change with later releases • Value to the Customer – Give customers regular functionality reviews – Realizing Value often rather than “big bang” Accommodates Multiple Challenges
- 30. • Project Concerns – Burn-Down Chart – Burn-Up Charts • Practices – Consistency Allows Ease of Spool Up – Allows Migration of Team Members • Tools – Consistency Allows Ease Migration of Team Members • Quality – Defects – Components Big Visible Charts
- 31. Burnup ChartsBurning Up Tasks Burnup 0 20 40 60 80 100 120 140 160 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 En d WorkingDays TaskHours Burnup Total Linear (Burnup) Linear (Total) 31
- 32. 32 1026 1013 982 951 924 913 879 847 798 742 695 16 13 31 31 27 32 34 45 16 23 34 40 43 53 62 66 90 72 61 70 93 120 53 62 62 67 90 102 138 173 189 200 223 150 160 180 190 198 198 143 150 180 184 196.5 0 50 100 150 200 250 300 350 400 450 500 550 600 650 700 750 800 850 900 950 1000 1050 1100 1150 1200 1250 1300 1350 1400 1450 2/3 2/10 2/17 2/24 3/3 3/10 3/17 3/24 3/31 4/7 4/14 4/21 4/28 5/5 5/12 5/19 5/26 6/2 6/9 6/16 6/23 6/30 7/7 7/14 7/21 7/28 TeamPoints Sprint Iteration K12 Burndown Content Verified / DONE QA Verified Complete / Business Verified Active Remaining Release 1 Release 2 & 3 BVC’s
- 33. BVC’s
- 34. BVC’s
- 35. BVC’s