Iterative development
Iterative development is a way to build a product through repeated cycles of design, testing and revision. Each cycle uses lessons from the previous version to improve the next, rather than treating the first design as final.
How it works
An iteration can produce a prototype, an internal build or a customer-facing update. It does not have to end with a public release. What matters is testing an assumption and changing the work in response to evidence.
Finding an onboarding problem before spending the whole budget
A startup budgets 120 engineering hours for onboarding, split into three 40-hour cycles. Each version is tested with 10 new users. These results are hypothetical.
| Cycle | Version tested | Users finishing without help |
|---|---|---|
| 1 | Initial flow | 4 of 10 |
| 2 | Fewer required fields | 7 of 10 |
| 3 | Clearer instructions | 9 of 10 |
Total effort is 3 × 40 = 120 hours. The first test exposes friction after 40 hours, leaving 80 hours for revision.
For the founder, the benefit is earlier evidence about where to spend limited engineering time. Better completion in this small test does not prove market demand.
What the Scrum Guide says
The 2020 Scrum Guide states: "Scrum employs an iterative, incremental approach to optimize predictability and to control risk."
Scrum uses iteration, but iterative development does not require adopting Scrum.
Questions people ask
What is the difference between agile, iterative, and incremental development?
Agile is a set of values and principles that emphasizes feedback and responding to change. Iterative development improves successive versions; incremental development adds usable portions of a product. A team can revise existing features and add new ones in the same cycle.
What are the 5 steps of the iterative process?
There is no universal five-step standard. A common way to describe the loop is: plan, design, build, test and review. Review feeds the next plan. Teams combine or rename these stages to fit their work.
