Learn to treat testing as an activity woven through the Sprint rather than a phase that follows it. Understand the testing pyramid and the different test types, and redesign Sprint Planning so quality is built in by the whole team, not inspected in afterwards.
Watch the free preview
The one-Sprint lag and why after-the-fact testing fails — free to watch, no account needed.
What you'll learn
- Explain why testing after the Sprint creates a permanent quality lag and hidden risk
- Describe the testing pyramid and how unit, integration, exploratory and acceptance tests serve different purposes at different speeds
- Integrate testing activities into Sprint Planning as whole-team work rather than a downstream handoff
- Redesign a develop-then-test workflow so that stories are truly Done within the Sprint
- Produce a one-page In-Sprint Testing Plan that assigns testing alongside development for each Sprint
Syllabus
Why Testing Belongs Inside the Sprint
The one-Sprint lag and why after-the-fact testing failsFree preview
The testing pyramid and whole-team quality
The Test Types and the Shape of the Pyramid
Unit, integration, exploratory and acceptance testing
Reading and fixing the shape of your test suite
Testing as Whole-Team Work in the Sprint
Planning testing into Sprint Planning
Case study — closing the one-Sprint testing gap
Making In-Sprint Testing Stick
Building your In-Sprint Testing Plan
Common traps and anti-patterns to avoid