Product backlog, sprint backlog, increment, and their commitments. Four shared sources of truth that make a team's work visible — and a window into its health.
▸ Try the interactive toolScrum has exactly four artifacts, and together they make a team's work visible and transparent. An artifact, in Scrum, is a shared document or system everyone can see and trust as a source of truth. Each has a single owner and a single clear purpose — and the health of those artifacts is a reliable window into the health of the whole team.
The Product Backlog is the ordered list of everything that might be built (owned by the PO). The Sprint Backlog is what the team committed to this sprint plus the plan to deliver it (owned by the Developers). The Increment is the working, done output of the sprint. Modern Scrum pairs each with a commitment: the Product Goal, the Sprint Goal, and the Definition of Done — the things that give each artifact direction and meaning.
Product Backlog (→ Product Goal) — ordered list of all potential work
Sprint Backlog (→ Sprint Goal) — this sprint's commitment + plan
Increment (→ Definition of Done) — the working, done output
Transparency is the point: everyone sees the same truth.
When artifacts are neglected — a stale backlog, no Sprint Goal, a fuzzy Definition of Done — the team loses its shared source of truth, and dysfunction follows quietly.
| The shortcut | What it costs | What it gives you instead |
|---|---|---|
| Stale product backlog | An un-groomed, unordered backlog gives the team no clear next work. | A maintained, ordered backlog is a trustworthy source of truth. |
| No Sprint Goal | A sprint that's just a list of tasks lacks coherent purpose. | The Sprint Goal gives the sprint a single, meaningful aim. |
| Fuzzy Definition of Done | ‘Done’ means different things to different people; quality varies. | A shared DoD makes ‘done’ unambiguous and the increment trustworthy. |
| Hidden work | Work that isn't in an artifact is invisible and unmanaged. | Artifacts make all the work visible and transparent. |
Keep it groomed and prioritised so the top is always the most valuable next work. A neglected backlog is the most common artifact failure — and a clear health signal.
Each sprint should have a single coherent objective the Sprint Backlog serves. The goal is what lets the team make trade-offs mid-sprint without losing the point.
The Developers own the sprint backlog and its plan. It's their commitment and their working document — not something imposed from outside.
Agree a clear Definition of Done so the Increment is genuinely complete and trustworthy. Without it, ‘done’ drifts and quality becomes unpredictable (see Tool 07).
A stale backlog, a missing Sprint Goal, an ignored DoD — each signals a deeper problem. Use artifact health to diagnose team health.
A team's sprints felt chaotic and unfocused, and no one could quite say why. Looking at their artifacts told the story instantly: the product backlog was a disordered dumping ground, sprints had no goal beyond ‘finish these tickets,’ and ‘done’ meant whatever each developer decided.
The artifacts weren't just neglected paperwork — their state was the dysfunction. Restoring them fixed the team: an ordered backlog gave clear priorities, a real Sprint Goal gave each sprint coherence and a basis for trade-offs, and an explicit Definition of Done made the increment trustworthy. The chaos resolved not through a new process but through repairing the four shared sources of truth.
The deliverable is four well-maintained artifacts — each with its owner, commitment, and a transparency the whole team trusts.
| Artifact | Owner | Commitment | Health signal |
|---|---|---|---|
| Product Backlog | Product Owner | Product Goal | Ordered & groomed? |
| Sprint Backlog | Developers | Sprint Goal | Coherent goal, not just tasks? |
| Increment | Developers | Definition of Done | Genuinely, consistently done? |
The four artifacts exist to create transparency — a shared truth everyone can see and trust. And because they're shared and visible, their condition doubles as the most reliable diagnostic of a team's underlying health.
The diagnostic angle is the underused one. Teams tend to treat artifacts as administrative overhead, but a stale backlog, a goal-less sprint, or a fuzzy Definition of Done aren't just sloppy bookkeeping — they're symptoms. A disordered backlog means prioritisation has broken down; a missing Sprint Goal means the team is working without coherent purpose; an ignored DoD means quality is unmanaged. So when a team feels chaotic but no one can name why, reading the artifacts is often the fastest route to the cause — and repairing them is frequently the cure, because restoring the shared source of truth restores the clarity that was quietly lost.
A stale, unordered backlog is the most common failure — and a sign of broken prioritisation. Keep it groomed.
A task list isn't a Sprint Goal. Give each sprint a coherent purpose.
Without a shared DoD, quality drifts. Define done explicitly.
They're the team's shared truth and health signal, not paperwork to minimise.
Each artifact maps to a role (Tool 04) — the PO owns the product backlog, Developers own the sprint backlog.
The Increment's commitment is the DoD, covered alongside the DoR in Tool 07.
The events (Tool 06) are when artifacts get created, refined, and inspected.
The product backlog is the delivery-side sibling of Module 3's discovery backlog (Tool 24).
For a team you know, assess each artifact: is the product backlog ordered and groomed? Do sprints have real goals? Is ‘done’ defined and consistent?
Whichever artifact is weakest — what team dysfunction might its neglect be both causing and revealing?
If a chaotic-feeling team also has a stale backlog and no Sprint Goals, you've found that the artifacts aren't just neglected — their state is the dysfunction made visible.