Skip to content
PMPCAPM

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.

Share:

Know it well enough for the exam? Questions on Increment are scenario-based, not definitional.

Practice it free

Explanation

An Increment is the sum of all Product Backlog items completed during a Sprint, plus the value of all previous Increments. The Increment must be usable and meet the Definition of Done. If a Product Backlog item does not meet the Definition of Done, it cannot be released or presented at the Sprint Review.

Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value.

The Increment is the tangible output that demonstrates progress. In Scrum, delivering a usable Increment at the end of every Sprint is non-negotiable, as it provides the transparency needed for meaningful inspection and adaptation.

Key Points

  • •Each Increment is additive to all prior Increments
  • •Must meet the Definition of Done to be considered complete
  • •Multiple Increments can be created within a single Sprint
  • •The Increment can be released at any point, not just at the Sprint Review

Exam Tip

An Increment must be usable and meet the Definition of Done. If a question asks about incomplete work, it is NOT part of the Increment.

Frequently Asked Questions

Related Topics

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

Study full domain →

Practice Increment

Scenario-based questions with a full explanation on every answer — including why the distractors are wrong.