Iteration
A timeboxed cycle of development producing a working increment.
Detailed Explanation
An iteration is a timeboxed cycle of development in which a working product increment is created. In Scrum, iterations are called sprints and typically last 1-4 weeks. Each iteration follows a plan-do-check-adapt cycle.
Iterations allow teams to incorporate feedback early and adjust the product incrementally rather than delivering everything at once. Each iteration should produce something demonstrable and potentially shippable, even if it is a small slice of functionality.
The iterative approach reduces risk by validating assumptions frequently and allows stakeholders to see tangible progress. If requirements change or priorities shift, the team can adapt at the start of the next iteration rather than mid-stream.
Key Points
- Timeboxed development cycle (typically 1-4 weeks)
- Produces a working, demonstrable increment each cycle
- In Scrum, iterations are called sprints
- Follows plan-do-check-adapt cycle
- Enables early feedback and frequent course correction
- Reduces risk through frequent validation
Practical Example
A mobile app team works in 2-week iterations. Iteration 1 delivers user registration and login. Iteration 2 adds profile management. Iteration 3 adds the core feature. After each iteration, the Product Owner demos to stakeholders and collects feedback that shapes the next iteration's priorities.
Tips for Learning and Applying
Keep iterations short (2 weeks is a good default) to maintain momentum
Every iteration should produce something demonstrable to stakeholders
Use iteration retrospectives to continuously improve the process
Protect the iteration timebox — do not extend it when work is incomplete
Related Terms
Want to Master These Concepts?
Our courses cover all these terms in depth with practical examples and exercises.