The Whole Team Approach

Roles prone to bottlenecks

-Product owner
-UX specialist

Common Challenge: Bottlenecks -1 developer/tester in the team

Limited Infrastructure

Working simultaneously on multiple projects

Collaborative testing practices that occur continuously, from inception to delivery and
Lisa Crispin & Janet Gregory
beyond, supporting frequent delivery of value for our customers. Testing activities focus on
What is Agile Testing? building quality into the product, using fast feedback loops to validate our understanding.
the practices strengthen and support the idea of whole team responsibility for quality

The focus of Agile development is producing high quality software in a time frame that
maximizes its value to the business. This is the job of the whole team, not just testers or
designated quality assurance professionals. Everyone on an Agile team gets test infected

An Agile team must possess all the skills needed to produce quality code that delivers
Shared Responsibility the features required by the organization. Any task might be completed by any team
member, or pair of team members

Team takes responsibility for all kinds of testing tasks such as automating tests and
manual exploratory testing. Also whole team constantly thinks of designing code for
testability

Share testing perspectives

Help team to see the product from a different viewpoint

Coaching Testing
Conduct workshops, talks and coach hands-on on the job

Share testing knowledge across teams

The Automation Expert

Developers
Who does Automation in the team?
The Tester

The Team

Traditional environment

What about Special situations and context? Transition to becomming Agile

Cutting edge environment