HKSM
Incremental Life Cycle
An adaptive life cycle where the deliverable is built in a sequence of planned, timeboxed iterations, each one adding new functionality. The work is considered complete only after the final iteration provides the full, sufficient capability required.
Key Points
- Work proceeds in fixed-length iterations that add distinct features or components.
- Earlier increments may be reviewed or piloted, but the deliverable is only deemed complete at the end of the last iteration.
- Scope details can evolve between iterations based on feedback and learning.
- Integration, testing, and planning recur each iteration to control risk, cost, and schedule.
Example
A team develops an internal analytics portal in four 4-week iterations: Iteration 1 delivers user authentication, Iteration 2 adds dashboards, Iteration 3 enables data exports, and Iteration 4 completes admin controls and integration testing. The portal is officially complete and released only after Iteration 4.
PMP Example Question
A project plans five 3-week cycles. Each cycle adds a new module, and the product will meet the minimum required capability for release only after the fifth cycle. What life cycle best describes this approach?
- Iterative life cycle focused on refining the same feature repeatedly
- Incremental life cycle adding functionality in timeboxed iterations with completion at the final iteration
- Predictive life cycle with a single delivery at project end
- Hybrid life cycle combining waterfall phases with agile sprints
Correct Answer: B — Incremental life cycle
Explanation: The scenario describes scheduled iterations that add features over time, with the deliverable considered complete only after the last iteration.
