Testing alongside development.
WHAT CHANGES FROM SEQUENTIAL APPROACHES
Testing happens continuously, not at the end Testers are part of the team Requirements emerge and change Releases are frequent
WHAT TESTERS DO EARLY
Review requirements for testability Identify cases during planning Ask what happens when
WHY THAT IS THE HIGHEST-VALUE CONTRIBUTION
Questions asked before building prevent defects entirely.
WHAT THREE-AMIGO CONVERSATIONS ARE
Business, development and testing agreeing what a piece of work means before it starts.
WHAT THEY PRODUCE
Shared understanding, and examples that become tests.
WHAT DEFINITION OF DONE SHOULD INCLUDE
Tests written and passing Code reviewed Acceptance criteria verified No known defects of agreed severity
WHY IT MATTERS
Without it, done means different things to different people.
WHAT REGRESSION REQUIRES IN FREQUENT RELEASES
Automation, since manual regression cannot keep pace.
WHAT TO AUTOMATE FIRST
The paths that must never break.
WHAT TO AVOID
Testing squeezed into the end of an iteration A separate testing phase after development Testers receiving work with no time remaining
WHAT TO MEASURE
Defects escaping to production, not defects found.
