Iteration
What is an Iteration?
An iteration is a short, fixed-length cycle, typically one to four weeks, in which a team plans, builds, tests and reviews a slice of working output. Scrum calls it a sprint; scope flexes to fit, the end date does not.
Updated November 2026 · 3 min read
An iteration is a fixed, short period, usually one to four weeks, in which a team plans a set of work, builds and tests it, and reviews the result before starting the next period. Each iteration produces working output that can be inspected, and what the team learns from it shapes the plan for the next one. In Scrum, an iteration is called a sprint.
Iterations replace one long plan with many short planning cycles. Instead of committing to a year of work based on what is known on day one, a team commits to a few weeks at a time and adjusts as customers, data and technical discoveries show what matters. Because each iteration is timeboxed, the end date never moves; if work does not fit, scope changes instead.
What happens in an iteration
| Stage | Purpose | Scrum equivalent |
|---|---|---|
| Planning | Choose the goal and the work that fits the team's capacity | Sprint planning |
| Execution | Design, build, test and integrate the work | The sprint itself, with a daily standup |
| Review | Show the result to stakeholders and gather feedback | Sprint review |
| Reflection | Improve how the team works | Sprint retrospective |
Iteration vs. increment vs. release
- Iteration is a unit of time: the cycle in which work is done.
- Increment is a unit of output: the working, tested product change produced, which must meet the team's definition of done.
- Release is a business decision to put one or more increments in front of users. A team may release several times within an iteration, or only after several iterations.
Confusing these causes problems. A team that treats each iteration's end as a mandatory release date may hold back finished work; a team that never releases may produce increments nobody uses.
Choosing an iteration length
- One week gives very fast feedback but leaves little room for larger items and makes planning overhead a bigger share of the time.
- Two weeks is the most common choice; it balances feedback speed with enough time to finish meaningful work.
- Three to four weeks suits teams with heavy integration or hardware dependencies, at the cost of slower learning. The Scrum Guide caps sprints at one month.
Whatever the length, keeping it consistent matters. A steady rhythm, or cadence, makes velocity meaningful and planning routine.
Planning an iteration: A hypothetical example
Consider a hypothetical team of five developers working two-week iterations of 10 working days, giving 5 × 10 = 50 developer-days. In the coming iteration one developer has 3 days of leave, leaving 47 developer-days, or 94% of normal capacity. The team's average velocity of 30 points was measured over iterations with close to full attendance, so it scales the target to 30 × 47 ÷ 50 = 28.2, or about 28 points, and agrees a single iteration goal: "Customers can export invoices as PDF." At the review, a customer points out that accountants need CSV as well, and the team adds that to the backlog for the next iteration.
Common pitfalls
- Mini-waterfalls. Designing in week one, building in week two and testing in the next iteration defeats the purpose. Each iteration should finish tested work.
- Changing the length often. Stretching an iteration to fit unfinished work hides the planning problem and makes forecasts unreliable.
- No goal. An iteration that is just a list of tickets gives the team nothing to trade off against when surprises arrive.
- Skipping the review. Without stakeholder feedback, iterations become a scheduling device rather than a learning loop.
Iterations are the basic building block of the iterative process and of Scrum. Over many iterations, the team's sprint velocity gives a reliable basis for forecasting larger plans.
Frequently asked questions
What is the difference between an iteration, an increment and a release?
An iteration is a unit of time, the cycle in which work gets done. An increment is a unit of output: the working, tested change produced, meeting the definition of done. A release is a business decision to put increments in front of users, which can happen several times within an iteration or only after several.
How long should an iteration be?
Two weeks is the most common iteration length because it balances fast feedback with enough time to finish meaningful work. One week speeds learning but raises planning overhead, while three to four weeks suits teams with heavy integration or hardware dependencies. The Scrum Guide caps sprints at one month. Keeping the length consistent matters more than the exact choice.
How do you adjust iteration planning when team members are on leave?
Scale the team's usual velocity by available capacity. For example, five developers on a ten-day iteration have 50 developer-days; if one takes three days off, 47 remain, or 94%. A team averaging 30 points at full attendance would plan about 28 points and still agree a single iteration goal.
Related terms
Timebox
A hard time limit for an activity, with scope adjusted to fit.
Sprint Planning
The meeting that starts each Sprint by setting a goal and a plan.
Daily Standup
A short daily team meeting to check progress and surface blockers.
Sprint Retrospective
The end-of-Sprint meeting where the team agrees how to work better.