4.5 Increment Artifact & Definition of Done Commitment

4.5 Increment Artifact & Definition of Done Commitment

The ultimate purpose of every Sprint is to produce value. In Scrum, value is realized through the creation of an Increment. The 2020 Scrum Guide defines the Increment as a concrete stepping stone toward the Product Goal. To ensure transparency and quality, the Increment is paired with a mandatory commitment: the Definition of Done.

On the PSM I exam, candidates are evaluated on their knowledge of what constitutes an Increment, when an Increment is born, how incomplete work is handled, and the timing of releases.

---

Definition and Core Attributes of the Increment

Scrum Guide Definition: "An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable."

Key Attributes of the Increment

1. Additive Nature: An Increment does not exist in isolation. It integrates seamlessly with all previously delivered Increments, forming a cumulative, working version of the product.
2. Mandatory Usability: An Increment MUST be usable, regardless of whether the Product Owner decides to release it immediately to end users.
3. Thorough Verification: An Increment must meet all quality criteria established by the Definition of Done.
4. Multiple Increments per Sprint: A Scrum Team is not restricted to producing a single Increment at the very end of a Sprint. Multiple Increments may be created and deployed throughout the Sprint.

---

The Definition of Done as the Artifact Commitment

To prevent ambiguity regarding whether work is finished, Scrum requires a shared understanding of quality:

Scrum Guide Commitment: "The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born."

• Quality Standard: The Definition of Done creates transparency by providing everyone a shared understanding of what work was completed as part of the Increment (e.g., code written, unit tested, integrated, security scanned, documented).
• Birth of the Increment: A PBI remains a PBI until it fully satisfies the Definition of Done. Only upon meeting the DoD does it transition into part of the Increment.

+-----------------------------------------------------------------------------------+
|                         PBI TO INCREMENT TRANSITION PROTOCOL                      |
+-----------------------------------------------------------------------------------+
| Product Backlog Item ---> [ Meets Definition of Done? ] ---> YES: Becomes INCREMENT|
|                                     |                                             |
|                                     NO                                            |
|                                     v                                             |
|               Remains PBI; Returns to Product Backlog; NO RELEASE              |
+-----------------------------------------------------------------------------------+

---

Protocol for Non-Conforming ("Undone") Work

What happens when work on a Product Backlog item is 90% or 99% complete at the end of the Sprint, but fails one aspect of the Definition of Done (e.g., pending integration testing)?

Strict PSM I exam rules apply:

1. No Partial Credit: The item cannot be declared Done, cannot be presented as part of an Increment at the Sprint Review, and cannot be counted toward velocity.
2. Return to Product Backlog: The item returns immediately to the Product Backlog.
3. Re-Evaluation: The Product Owner re-evaluates the item's order and value. The PO may choose to prioritize it for the next Sprint or deprioritize it if business needs changed.
4. No Demo of Undone Work: Demonstrating incomplete work at the Sprint Review creates false transparency and undermines empirical decision-making.

---

Release Timing and the Sprint Review

A persistent misconception among candidates is that an Increment can only be released after it is inspected at the Sprint Review. The Scrum Guide clarifies:

• Release Anytime: An Increment may be delivered to stakeholders and released into production at any time during the Sprint, prior to the end of the Sprint.
• Sprint Review Role: The Sprint Review is an inspection and adaptation working session—not a release gate or approval milestone. Releasing early and often accelerates feedback loops.

---

Done Increment vs. Undone Work Comparison

---

Real-World PSM I Exam Traps

• Exam Trap 1: Work that is 95% finished can be demonstrated at Sprint Review as long as Developers promise to complete it tomorrow. False! If an item does not meet the DoD, it cannot be presented at the Sprint Review.
• Exam Trap 2: Increments can only be released to production after the Product Owner approves them during the Sprint Review. False! Increments can be released anytime during the Sprint as soon as they meet the DoD.
• Exam Trap 3: The Scrum Master decides whether an Increment is Done. False! Compliance with the Definition of Done is assessed by the Developers who create the Increment.
• Exam Trap 4: Unfinished items automatically roll over into the next Sprint Backlog. False! Unfinished work returns to the Product Backlog, where the PO decides its future order.