Iterative Development
In Scrum, the product is built through successive, timeboxed sprints so it evolves over repeated cycles, enabling frequent feedback, lowering risk, and increasing stakeholder satisfaction.
Key Points
- Work is delivered in short, timeboxed sprints that build on prior increments.
- Each iteration produces a usable increment for review and stakeholder feedback.
- Regular inspection and adaptation reduce uncertainty and surface risks early.
- Frequent engagement improves alignment, transparency, and stakeholder satisfaction.
Example
A Scrum team delivers a basic reporting feature in Sprint 1. Users review it and request filters and export options. In Sprint 2, the team adds those enhancements, gathers more feedback, and continues refining in subsequent sprints, reducing risk and improving the product each cycle.
PMP Example Question
A team delivers a working increment every two weeks, gathers user input, reprioritizes the backlog, and refines scope before the next cycle to reduce uncertainty. Which approach are they using?
- Iterative development
- Predictive life cycle
- Fast tracking
- Crashing
Correct Answer: A — Iterative development
Explanation: The scenario describes repeated sprints with frequent feedback and adaptation, which characterizes iterative development in Scrum.
