5.1 Artifacts & the Transparency Mandate

Why Artifacts Matter on the PSM I

Scrum's empirical foundation rests on three pillars: transparency, inspection, and adaptation. Inspection and adaptation are worthless if the thing being inspected is not transparent — you cannot make a sound decision from a distorted picture. That is precisely why the 2020 Scrum Guide states that Scrum's artifacts are designed to maximize transparency of key information so that everybody inspecting them has the same basis for adaptation. The artifacts are not status reports or paperwork; they are the carriers of the information the Scrum Team and stakeholders depend on.

Expect the PSM I assessment to test whether you can (1) name all three artifacts exactly, (2) attach the correct commitment to each, (3) explain why opacity in an artifact corrupts the empirical process, and (4) recognize that the commitments are part of the artifacts rather than four-, five-, or six-item lists of separate things. Roughly a quarter of PSM I questions touch artifacts or commitments, so this chapter is high-yield.

The Three Artifacts — No More, No Fewer

There are exactly three artifacts. A burndown chart, a release plan, a Sprint board, a roadmap, or a velocity chart are not Scrum artifacts; they are optional, complementary practices a team may adopt. If an exam answer lists a fourth artifact, it is wrong. Each artifact represents work or value, which makes each one inspectable so the team can adapt:

Commitments Reinforce Empiricism

The 2020 Scrum Guide introduced a commitment for each artifact. Commitments are not bureaucratic add-ons and they are not a fourth, fifth, and sixth artifact — a very common trap. Each commitment exists inside its artifact to ensure the artifact provides information that enhances transparency and focus against which progress can be measured:

• The Product Backlog commits to the Product Goal.
• The Sprint Backlog commits to the Sprint Goal.
• The Increment commits to the Definition of Done.

Without a commitment, an artifact becomes a destination-less list. The Product Goal gives the Product Backlog a long-term direction; the Sprint Goal gives the Sprint Backlog coherence; the Definition of Done gives the Increment a shared, unambiguous quality bar. Mentally bind the commitment to its artifact so that, on the exam, you never separate the two.

Transparency Failures and the Scrum Master's Role

When an artifact is not transparent, inspection produces flawed conclusions and the resulting adaptation is wrong. The Scrum Guide is blunt: decisions made on low-transparency artifacts diminish value and increase risk. Consider concrete failure modes the exam loves to describe:

1. A Product Backlog padded with stale, duplicated, or undefined items — stakeholders cannot tell what the product will actually become.
2. A Sprint Backlog that lives only in one Developer's head — the team cannot see real-time progress toward the Sprint Goal.
3. An Increment that quietly does not meet the Definition of Done — it looks finished but is not, so release decisions are made on a lie.

The Scrum Master serves the team by helping everyone raise transparency and by coaching the organization to value it — not by policing process for its own sake. Transparency is enabled by the artifacts but ultimately depends on people inspecting honestly and acting on what they learn; it cannot be imposed.

Artifacts, Commitments, and the Empirical Cycle

It helps to see how the three artifacts plug into the transparency → inspection → adaptation cycle that runs through every Scrum event. Each artifact is inspected at specific events, and its commitment is the yardstick used during that inspection:

This is why the commitments are not optional decoration: they convert each artifact from a passive list into a measurable standard for empirical decisions. When the Daily Scrum inspects the Sprint Backlog, the team is really asking, "are we still going to hit the Sprint Goal?" When stakeholders inspect the Increment at the Sprint Review, the Definition of Done tells them whether what they are looking at is genuinely complete.

Common Misconceptions to Unlearn

Several artifact misconceptions appear again and again on the PSM I, and unlearning them early pays off across the whole assessment:

• "A Definition of Ready is required." It is not. "Definition of Ready" is an optional complementary practice, never a Scrum artifact or commitment.
• "The task board is the Sprint Backlog." A board is one representation of the Sprint Backlog; the artifact is the plan (goal + items + delivery plan), not the tooling.
• "Artifacts make work transparent automatically." Artifacts enable transparency, but a backlog full of vague items or an Increment that secretly misses the Definition of Done is opaque despite existing. People must keep the artifacts honest.
• "There are six artifacts." There are three artifacts and three commitments contained within them — a distinction the next sections reinforce repeatedly.