Your SlideShare is downloading. ×
  • Like
  • Save
Whole Team Approach to Quality
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×

Now you can save presentations on your phone or tablet

Available for both IPhone and Android

Text the download link to your phone

Standard text messaging rates apply

Whole Team Approach to Quality

  • 2,266 views
Published

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

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
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
2,266
On SlideShare
0
From Embeds
0
Number of Embeds
0

Actions

Shares
Downloads
0
Comments
0
Likes
7

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide

Transcript

  • 1. © 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”
  • 7. © 2009 Rally Software Development, Inc.
    7
    The Team Must Test to Deliver Value
    Teams agree to a “Definition of Done” that representspotentially shippable code at the User Story, Iteration and Release Levels.
    Sample Team “Done” List:
    …with a Story
    • all code is checked in
    • 8. all unit tests passing
    • 9. all acceptance tests running and passing
    • 10. help text written
    • 11. accepted by theProduct Owner
    • 12. could be delivered to users
    …with an iteration
    • story criteria +
    • 13. product backup complete
    • 14. performance testing
    • 15. all defects closed or postponed
    • 16. 80%+ test code coverage
    …with a release
    • iteration criteria+
    • 17. stress testing
    • 18. performance tuning
    • 19. security pass validated
    • 20. disaster recovery plan tested
  • Without Test, There is No Value Delivered
    If it’s not tested, it’s not accepted
    If it’s not accepted, there’s no value delivered
    The entire team commits and is accountable
    It’s impossible to “run out of time” for testing
    If test tasks are notcomplete, the teamstops and everyonetests. Programmerscan’t “get ahead” oftesters.
    © 2009 Rally Software Development, Inc.
    8
  • 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
  • 22. Testing - “Just Another” Role on the Team
    © 2009 Rally Software Development, Inc.
    10
    • Testers are co-located and fully integrated into the team
    • 23. Help the business stakeholders define acceptance criteriaand examples for user stories during iteration planning
    • 24. Estimate test tasks as part of user story work breakdown
    • 25. Automate acceptance tests
    • 26. Perform exploratory testing
    • 27. Perform non-functional testing(e.g., performance/security) or interfacewith specialty teams
    • 28. Report to SQA, sharing learning withintheir skill center
  • The Collaboration Model Changes, Tester Skillsets Do Not
    © 2009 Rally Software Development, Inc.
    11
  • © 2009 Rally Software Development, Inc.
    12
    Agile Team Roles…Different Skills – One Goal
    A High Quality Product that Drives Business Value
    • Developers embrace automated unit testing. Since no work is accepted without being tested, design for testability is encouraged.
    • 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. The ScrumMaster facilitates the team.Blocks like poor testability and failing builds are made visible and the ScrumMastermakes sure the team addresses them.
  • How do we fit Test within a 1-4 Week Iteration?
    © 2009 Rally Software Development, Inc.
    13
    Agile teams deliver fully tested , working code every 1-4 week iteration.New teams often wonder how testing can be squeezed into that timeframe.
    A Lead in For Our Next Presentation…
    “How Testing fits within an Iteration”
    …and yes Agile teams do it all the time.
  • 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.