Iteration
An Iteration is a fixed-length timebox during which an agile team develops and delivers a working increment of the product, with each iteration building on the previous one.
Know it well enough for the exam? Questions on Iteration are scenario-based, not definitional.
Practice it freeExplanation
Iteration is the generic agile term for a development cycle, with Sprint being the Scrum-specific equivalent. Each iteration typically lasts one to four weeks and includes planning, development, testing, and delivery activities. At the end of each iteration, the team delivers a working increment that can be demonstrated and potentially released.
Iterative development allows teams to get feedback early and often, reducing the risk of building the wrong thing. Each iteration provides a learning opportunity: the team can adjust direction based on stakeholder feedback, changing requirements, or new technical insights. This is fundamentally different from a waterfall approach where feedback comes only at the end.
In frameworks like SAFe, iterations are organized into Program Increments (PIs), which are larger timeboxes that coordinate multiple teams. The iteration remains the basic unit of planning and delivery, even at scale.
Key Points
- •Fixed-length timebox, typically one to four weeks
- •Each iteration produces a working, demonstrable increment
- •Enables early and frequent feedback from stakeholders
- •Sprint is the Scrum-specific name for an iteration
Exam Tip
Iteration is the generic term; Sprint is the Scrum-specific term. They refer to the same concept: a fixed-length development cycle.
Frequently Asked Questions
Related Topics
Sprint
A Sprint is a fixed-length timebox of one month or less in Scrum during which the team creates a usable, potentially releasable product Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Increment
An Increment is a concrete stepping stone toward the Product Goal, where each Increment is additive to all prior Increments and must meet the Definition of Done to be considered complete.
Release Planning
Release Planning is an agile practice where the team and Product Owner determine the scope, timing, and goals for the next product release by mapping backlog items across future iterations based on team velocity.
Most-studied PMP concepts
High-yield topics our learners drill most before exam day.
Burndown Chart
A burndown chart plots the work remaining (usually in story points) against time in a sprint or release, alongside an ideal line to zero, so the team can see each day whether it is on track to finish.
Burn-Up Chart
A burn-up chart plots completed work rising over time against a separate total-scope line, so progress and scope changes are visible independently; the work is finished when the two lines meet.
Weighted Shortest Job First (WSJF)
Weighted Shortest Job First (WSJF) is a prioritization model, popularized by SAFe, that ranks work by cost of delay divided by job duration (usually estimated as job size), so the items that lose the most value per unit of time spent waiting are done first.
Relative Estimation
Relative Estimation is an agile technique where work items are sized in comparison to each other rather than in absolute units like hours or days, providing faster and more accurate estimates.
Sprint Review
The Sprint Review is a Scrum event held at the end of the Sprint where the Scrum Team presents the Increment to stakeholders, gathers feedback, and collaborates on what to do next.
Sprint Backlog
The Sprint Backlog is the set of Product Backlog items selected for the Sprint, plus the Sprint Goal and the plan for delivering the Increment.
Timeboxing
Timeboxing is the practice of allocating a fixed, maximum amount of time for an activity, after which the activity stops regardless of whether it is complete.
Resource Leveling
Resource leveling is a resource optimization technique that adjusts activity start and finish dates so that demand for a resource never exceeds its availability, accepting a longer schedule and a changed critical path if necessary.
Deliverables
A deliverable is any unique and verifiable product, result, or capability to perform a service that must be produced to complete a process, phase, or project, such as a software release, an audit report, or a trained support team.
Part of
Agile & Hybrid
Practice Iteration
Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.