5.5 Commitments Summary & Exam Traps

The Master Mapping

If you remember nothing else from this chapter, remember this table. Every artifact has exactly one commitment, the commitment lives inside the artifact, and the PSM I will test the pairing in many disguises.

There are three artifacts and three commitments — never "six things." If a question implies the commitments are additional artifacts, or that an artifact can have two commitments, it is wrong.

How Commitments Reinforce Empiricism

Commitments exist to add transparency and focus against which progress can be measured. Map each commitment to the empirical pillar it strengthens:

• The Product Goal lets the team inspect whether the evolving Product Backlog still moves toward a meaningful destination, and adapt the backlog if not.
• The Sprint Goal lets the Developers inspect daily progress at the Daily Scrum against a single, shared objective, and adapt the plan.
• The Definition of Done lets everyone inspect an Increment against an unambiguous quality bar at the Sprint Review, removing the opacity of "is it really done?"

Remove the commitments and each artifact loses the reference point that makes inspection trustworthy and adaptation purposeful — which is precisely why the 2020 Scrum Guide bound a commitment to each artifact.

High-Frequency Exam Traps

Trap 1: Commitments are not separate artifacts

The Product Goal, Sprint Goal, and Definition of Done are commitments contained within the Product Backlog, Sprint Backlog, and Increment respectively — not a second set of artifacts. Scrum still has exactly three artifacts.

Trap 2: Definition of Done vs. acceptance criteria

The Definition of Done is a product-wide quality standard applied to every Increment. Acceptance criteria are item-specific behavioral conditions for one Product Backlog item. Satisfying acceptance criteria does not guarantee an item is Done.

Trap 3: The Sprint Goal is flexible in scope, firm in objective

The Sprint Goal is committed to, yet the precise scope of work is flexible. Developers renegotiate scope with the Product Owner as they learn — the objective stays, the work list can change. Only the Product Owner may cancel a Sprint if the Sprint Goal becomes obsolete.

Trap 4: One commitment per artifact, and where things live

Do not attach the Definition of Done to the Sprint Backlog, or the Sprint Goal to the Product Backlog. Each artifact carries exactly one commitment, and the Product Goal lives inside the Product Backlog — not in a separate strategy document.

Trap 5: An Increment failing the Definition of Done cannot be released

It also cannot be presented as Done, and it returns to the Product Backlog. The Definition of Done creates transparency; without it, no one can trust that an Increment is finished.

Rapid-Fire Recall List

• Three artifacts, three commitments, each commitment inside its artifact.
• Product Owner is accountable for the Product Backlog and the Product Goal.
• Developers own the Sprint Backlog and commit to the Sprint Goal.
• The Scrum Team owns the Increment and complies with the Definition of Done.
• Undone work → back to the Product Backlog; never silently rolled forward.

Ownership and Accountability Cheat Sheet

A large share of artifact questions are really ownership questions in disguise. Lock this grid in:

If a question asks "who changes the Sprint Goal," "who orders the Product Backlog," or "who can present undone work as Done," answer from this grid, not from job titles like "manager" or "project lead" — those roles do not exist in Scrum.

Putting It Together: An Empirical Walkthrough

Follow one feature through the artifacts and commitments to see the whole machine work:

1. The Product Owner adds and orders an item in the Product Backlog, keeping it aligned to the Product Goal.
2. In Sprint Planning the Developers pull it into the Sprint Backlog, and the team crafts a Sprint Goal that the item helps achieve.
3. Each day the Developers inspect the Sprint Backlog at the Daily Scrum against the Sprint Goal, adapting their plan.
4. The moment the item meets the Definition of Done, an Increment exists; it is usable and could be released immediately.
5. At the Sprint Review, stakeholders inspect the Increment against the Definition of Done and the Product Goal, then the Product Backlog is adapted.

Every step depends on a transparent artifact measured against its commitment — which is the single biggest idea this chapter exists to cement, and the lens through which most PSM I artifact questions should be answered.