Weitere ähnliche Inhalte Mehr von Rally Software (14) Kürzlich hochgeladen (20) Whole Team Approach to Quality1. © 2009 Rally Software Development, Inc. 1 A Whole TeamApproach to Quality We’re All in This Together 2. Why Agile? 37% Faster to Market(Rally Teams 50%)1 16% More Productive(Rally Teams 25%)1 ¼ the Expected Defect Rate1 © 2009 Rally Software Development, Inc. 2 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. 1) QSMA and Cutter Consortium ROI study on Agile teams, 2008. 3. The Entire Agile Team is Accountable for Quality Traditional Agile Dev and QA Separate QA as the Quality Police,Expected to “test in” quality QA has the keys to production/veto card QA integrated with Team Team Accountability & Commitment to Quality QA has a critical seat at the table throughout the process © 2009 Rally Software Development, Inc. 3 4. The Entire Agile Team is Accountable for Quality Traditional Agile © 2009 Rally Software Development, Inc. 4 “We’re All in This Together” “Moving Sticks – Not My Job” s. 5. © 2009 Rally Software Development, Inc. 5 The Essence of Agile is Iterative Development Agile projects build software incrementally, typically using short iterations of 1-4 weeks, to keep development aligned with changing business needs So, instead of a single pass, 6-18 month release that predicts all requirements up-front and squeezes testing during the end game… Agile adapts to frequent feedback by delivering working,fully tested code every 1-4 week iteration 6. The Agile Team has a shared goal ofA High Quality Product that Drives Business Value © 2009 Rally Software Development, Inc. 6 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 “As a buyer, I want to have my shipping information confirmed so I get a chance to correct any errors” 21. The Role of the Tester © 2009 Rally Software Development, Inc. 9 “The nature of the tester'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.” - Cem Kaner 23. Help the business stakeholders define acceptance criteriaand examples for user stories during iteration planning 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. 40. Summary and Next Steps Summary Agile teams are jointly committedand accountable to Quality Testers are one role on a team delivering a quality product that drives business value The results are in. Agile teams using Rally are 50% faster to market, 25% more productive and have ¼ the expected defects of their peers Next Steps © 2009 Rally Software Development, Inc. 14 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. Explore the Implementing Agile Teams, Agile Test & Engineering Practices, and Rally JumpStart Service Offerings Request a free 30-day Rally Enterprise Edition trial.