Whole Team Approach To Quality 2013 PDF

A Whole Team Approach to Quality
Were All in This Together
www.rallydev.com
1
2013 Rally So5ware Development, Inc.
Why Agile?
37% Faster to Market (Rally Teams 50%)1 16% More ProducIve (Rally Teams 25%)1 the Expected Defect Rate1
1) QSMA and Cutter Consortium ROI study on Agile teams, 2008.
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.
www.rallydev.com
2
The En.re Agile Team is Accountable for Quality

Tradi.onal Agile
Dev and QA Separate QA integrated with Team QA as the Quality Police, Team Accountability & Expected to test in quality Commitment to Quality QA has the keys to QA has a criIcal seat at the producIon/veto card table throughout the process
www.rallydev.com
3
The En.re Agile Team is Accountable for Quality

Tradi.onal
Moving Sticks Not My Job
Agile
Were All in This Together
s.
www.rallydev.com
4
The Essence of Agile is Itera.ve Development

Agile projects build so5ware incrementally, typically using short iteraIons 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 tesIng during the end game
Agile adapts to frequent feedback by delivering working, fully tested code every 1-4 week iteraIon
www.rallydev.com
5
The Agile Team has a shared goal of A High Quality Product that Drives Business Value
The team commits to delivering value in the form of potentially shippable product 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
www.rallydev.com
6
The Team Must Test to Deliver Value

Teams agree to a Definition of Done that represents potentially shippable code at the User Story, Iteration and Sample Team Done List: Release Levels.
with a Story all code is checked in all unit tests passing all acceptance tests running and passing help text written accepted by the Product Owner could be delivered to users with an iteration story criteria + product backup complete performance testing all defects closed or postponed 80%+ test code coverage
with a release iteration criteria+ stress testing performance tuning security pass validated disaster recovery plan tested
7
www.rallydev.com
Without Test, There is No Value Delivered

If its not tested, its not accepted If its not accepted, theres no value delivered The enIre team commits and is accountable Its impossible to run out of Ime for tesIng If test tasks are not complete, the team stops and everyone tests. Programmers cant get ahead of testers.
www.rallydev.com
8
The Role of the Tester

The nature of the tester's role changes in iteraIve projects. We are no longer the high-prole vicIms, we are no longer the lonely advocates of quality, we are merely (!) competent service providers, collaboraIng with a group that wants to achieve high quality.
- Cem Kaner
www.rallydev.com
9
Tes.ng - Just Another Role on the Team

Testers are co-located and fully integrated into the team Help the business stakeholders dene acceptance criteria and examples for user stories during iteraIon planning EsImate test tasks as part of user story work breakdown Automate acceptance tests Perform exploratory tesIng Perform non-funcIonal tesIng (e.g., performance/security) or interface with specialty teams Report to SQA, sharing learning within their skill center
www.rallydev.com
10
The Collabora.on Model Changes, Tester Skillsets Do Not

Acceptance Test Exploratory Test Context-Based Approaches Model Driven Risk Based TesIng Non-FuncIonal TesIng Performance Security Threat Modeling Etc
www.rallydev.com
11
Agile Team RolesDierent Skills One Goal

A High Quality Product that Drives Business Value
Developers embrace automated unit tesIng. Since no work is accepted without being tested, design for testability is encouraged.
The Product Owner drives the product from a business perspecIve. Feedback is provided every 1 to 4 weeks, so requirements mistakes are caught immediately. The ScrumMaster facilitates the team. Blocks like poor testability and failing builds are made visible and the ScrumMaster makes sure the team addresses them.
www.rallydev.com
12
How do we t Test within a 1-4 Week Itera.on?

Agile teams deliver fully tested , working code every 1-4 week iteraIon. New teams o5en wonder how tesIng can be squeezed into that Imeframe.
A Lead in For Our Next PresentaIon
How TesIng ts within an IteraIon

and yes Agile teams do it all the Ime.
www.rallydev.com
13
Summary
Agile teams are jointly commiied and 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 producIve and have the expected defects of their peers
www.rallydev.com
14

Whole Team Approach To Quality 2013 PDF

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Whole Team Approach To Quality 2013 PDF

Uploaded by

Copyright:

Available Formats

A Whole Team Approach to Quality

Were All in This Together

The En.re Agile Team is Accountable for Quality

The En.re Agile Team is Accountable for Quality

The Essence of Agile is Itera.ve Development

The Team Must Test to Deliver Value

Without Test, There is No Value Delivered

The Role of the Tester

Tes.ng - Just Another Role on the Team

The Collabora.on Model Changes, Tester Skillsets Do Not

Agile Team RolesDierent Skills One Goal

How do we t Test within a 1-4 Week Itera.on?

A Lead in For Our Next PresentaIon

How TesIng ts within an IteraIon

You might also like