Your SlideShare is downloading. ×
© 2009 Rally Software Development, Inc.<br />1<br />A Whole TeamApproach to Quality<br />We’re All in<br />This Together<b...
Why Agile?<br />37% Faster to Market(Rally Teams 50%)1<br />16% More Productive(Rally Teams 25%)1<br />¼ the Expected Defe...
The Entire Agile Team is Accountable for Quality<br />Traditional<br />Agile<br />Dev and QA Separate<br />QA as the Quali...
The Entire Agile Team is Accountable for Quality<br />Traditional<br />Agile<br />© 2009 Rally Software Development, Inc.<...
© 2009 Rally Software Development, Inc.<br />5<br />The Essence of Agile is Iterative Development<br />Agile projects buil...
The Agile Team has a shared goal ofA High Quality Product that Drives Business Value<br />© 2009 Rally Software Developmen...
© 2009 Rally Software Development, Inc.<br />7<br />The Team Must Test to Deliver Value<br />Teams agree to a “Definition ...
 all unit tests passing
 all acceptance tests running and passing
 help text written
 accepted by theProduct Owner
 could be delivered to users</li></ul>…with an iteration<br /><ul><li>story criteria +
 product backup complete
 performance testing
Upcoming SlideShare
Loading in...5
×

Whole Team Approach to Quality

2,404

Published on

Agile teams are cross-functional and share a common goal of delivering a high quality product that drives business value.

Learn how developers, testers, product owners and managers work together towards this common goal.

Published in: Technology, Sports
0 Comments
7 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total Views
2,404
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
0
Likes
7
Embeds 0
No embeds

No notes for slide

Transcript of "Whole Team Approach to Quality"

  1. 1. © 2009 Rally Software Development, Inc.<br />1<br />A Whole TeamApproach to Quality<br />We’re All in<br />This Together<br />
  2. 2. Why Agile?<br />37% Faster to Market(Rally Teams 50%)1<br />16% More Productive(Rally Teams 25%)1<br />¼ the Expected Defect Rate1<br />© 2009 Rally Software Development, Inc.<br />2<br />QSMA Benchmarked 26 Agile development projects, against a database of 7,500 primarily traditional development projects in 500 organizations.Results – Agile teams using Rally were 50% faster to market and 25% more productive @ ¼ the expected defect rates.<br />1) QSMA and Cutter Consortium ROI study on Agile teams, 2008.<br />
  3. 3. The Entire Agile Team is Accountable for Quality<br />Traditional<br />Agile<br />Dev and QA Separate<br />QA as the Quality Police,Expected to “test in” quality<br />QA has the keys to production/veto card<br />QA integrated with Team<br />Team Accountability & Commitment to Quality<br />QA has a critical seat at the table throughout the process<br />© 2009 Rally Software Development, Inc.<br />3<br />
  4. 4. The Entire Agile Team is Accountable for Quality<br />Traditional<br />Agile<br />© 2009 Rally Software Development, Inc.<br />4<br />“We’re All in This Together”<br />“Moving Sticks – Not My Job”<br />s.<br />
  5. 5. © 2009 Rally Software Development, Inc.<br />5<br />The Essence of Agile is Iterative Development<br />Agile projects build software incrementally, typically using short iterations of <br />1-4 weeks, to keep development aligned with changing business needs<br />So, instead of a single pass, 6-18 month release that predicts all requirements up-front and squeezes testing during the end game…<br />Agile adapts to frequent feedback by delivering working,fully tested code every 1-4 week iteration<br />
  6. 6. The Agile Team has a shared goal ofA High Quality Product that Drives Business Value<br />© 2009 Rally Software Development, Inc.<br />6<br />The team commits to delivering value in the form of potentially shippableproduct every 1-4 weeks. User stories specify the value to be delivered.For stories to be accepted, the implementation must be complete and fully tested<br />“As a buyer, I want to have my shipping information confirmed so I get a chance to correct any errors”<br />
  7. 7. © 2009 Rally Software Development, Inc.<br />7<br />The Team Must Test to Deliver Value<br />Teams agree to a “Definition of Done” that representspotentially shippable code at the User Story, Iteration and Release Levels.<br />Sample Team “Done” List:<br />…with a Story<br /><ul><li> all code is checked in
  8. 8. all unit tests passing
  9. 9. all acceptance tests running and passing
  10. 10. help text written
  11. 11. accepted by theProduct Owner
  12. 12. could be delivered to users</li></ul>…with an iteration<br /><ul><li>story criteria +
  13. 13. product backup complete
  14. 14. performance testing
  15. 15. all defects closed or postponed
  16. 16. 80%+ test code coverage</li></ul>…with a release<br /><ul><li>iteration criteria+
  17. 17. stress testing
  18. 18. performance tuning
  19. 19. security pass validated
  20. 20. disaster recovery plan tested</li></li></ul><li>Without Test, There is No Value Delivered<br />If it’s not tested, it’s not accepted<br />If it’s not accepted, there’s no value delivered<br />The entire team commits and is accountable<br />It’s impossible to “run out of time” for testing<br />If test tasks are notcomplete, the teamstops and everyonetests. Programmerscan’t “get ahead” oftesters.<br />© 2009 Rally Software Development, Inc.<br />8<br />
  21. 21. The Role of the Tester<br />© 2009 Rally Software Development, Inc.<br />9<br />“The nature of the tester&apos;s role changes in iterative projects. We are no longer the high-profile victims, we are no longer the lonely advocates of quality, we are merely (!) competent service providers, collaborating with a group that wants to achieve high quality.”<br />- Cem Kaner<br />
  22. 22. Testing - “Just Another” Role on the Team<br />© 2009 Rally Software Development, Inc.<br />10<br /><ul><li>Testers are co-located and fully integrated into the team
  23. 23. Help the business stakeholders define acceptance criteriaand examples for user stories during iteration planning
  24. 24. Estimate test tasks as part of user story work breakdown
  25. 25. Automate acceptance tests
  26. 26. Perform exploratory testing
  27. 27. Perform non-functional testing(e.g., performance/security) or interfacewith specialty teams
  28. 28. Report to SQA, sharing learning withintheir skill center</li></li></ul><li>The Collaboration Model Changes, Tester Skillsets Do Not<br />© 2009 Rally Software Development, Inc.<br />11<br /><ul><li>Acceptance Test
  29. 29. Exploratory Test
  30. 30. Context-Based Approaches
  31. 31. Model Driven
  32. 32. Risk Based Testing
  33. 33. Non-Functional Testing
  34. 34. Performance
  35. 35. Security
  36. 36. Threat Modeling
  37. 37. Etc…</li></li></ul><li>© 2009 Rally Software Development, Inc.<br />12<br />Agile Team Roles…Different Skills – One Goal<br />A High Quality Product that Drives Business Value<br /><ul><li>Developers embrace automated unit testing. Since no work is accepted without being tested, design for testability is encouraged.
  38. 38. The Product Owner drives the product from a business perspective. Feedback is provided every 1 to 4 weeks, so requirements mistakes are caught immediately.
  39. 39. The ScrumMaster facilitates the team.Blocks like poor testability and failing builds are made visible and the ScrumMastermakes sure the team addresses them.</li></li></ul><li>How do we fit Test within a 1-4 Week Iteration?<br />© 2009 Rally Software Development, Inc.<br />13<br />Agile teams deliver fully tested , working code every 1-4 week iteration.New teams often wonder how testing can be squeezed into that timeframe.<br />A Lead in For Our Next Presentation…<br />“How Testing fits within an Iteration”<br />…and yes Agile teams do it all the time.<br />
  40. 40. Summary and Next Steps<br />Summary<br />Agile teams are jointly committedand accountable to Quality<br />Testers are one role on a team delivering a quality product that drives business value<br />The results are in. Agile teams using Rally are 50% faster to market, 25% more productive and have ¼ the expected defects of their peers<br />Next Steps<br />© 2009 Rally Software Development, Inc.<br />14<br />View the “How to Fit Testing in the Iteration” presentation in this series to see how testing fits in a 1-4 week time-box.<br />Explore the Implementing Agile Teams, Agile Test & Engineering Practices, and Rally JumpStart Service Offerings<br />Request a free 30-day Rally Enterprise Edition trial.<br />

×