Iteration

An iteration is a fixed-length development cycle-typically one to four weeks-during which a team completes a planned set of work. At the end of each iteration, the team has potentially shippable output and uses feedback from that cycle to improve planning and execution in subsequent iterations.

Why iterations matter

Iterations provide rhythm and feedback:

Regular delivery. Teams produce working output at predictable intervals rather than disappearing for months.

Frequent feedback. Short cycles enable rapid learning. Problems surface quickly; improvements compound.

Manageable planning. Planning for weeks is more accurate than planning for months.

Progress visibility. Stakeholders see regular evidence of progress rather than trusting promises.

Sustainable pace. Fixed cycles with defined scope help teams maintain consistent velocity without burnout.

Iteration structure

Most iterations follow a pattern:

Planning. Select work for the iteration based on priority and capacity. Define what "done" means for each item.

Execution. Complete the planned work. Daily coordination keeps the team aligned.

Review. Demonstrate completed work to stakeholders. Gather feedback on what was built.

Retrospective. Reflect on how the team worked. Identify improvements for future iterations.

Iteration length

Common iteration lengths:

Shorter iterations suit environments with high uncertainty or rapid change. Longer iterations suit more stable work or teams with high coordination overhead.

Iteration vs. sprint

In practice, these terms are often interchangeable. "Sprint" comes from Scrum specifically, while "iteration" is the more general term used across agile methods. The concepts are essentially the same: time-boxed development cycles with planning, execution, and review.

Iteration challenges

Scope pressure. Pressure to fit more into iterations leads to overcommitment and missed targets.

Incomplete work. Work that doesn't finish in one iteration carries over, creating coordination complexity.

Ritual fatigue. Without intentional facilitation, planning and retrospective meetings can become stale.

Long-running work. Some work genuinely doesn't fit iteration boundaries. Teams need strategies for breaking down or managing larger efforts.

Tools like Klero help connect iteration work to customer value. When teams can see which iteration items address user feedback and requests, the connection between daily work and customer impact becomes tangible.