Scrum Framework - Scrum Artifacts

Scrum Artifacts are the three critical information radiators in the Scrum Framework that provide transparency, enable inspection, and support adaptation. The three artifacts - Product Backlog, Sprint Backlog, and Increment - each have associated commitments that reinforce empiricism and Scrum values.

Quick Answer: The Three Scrum Artifacts

Artifact	Purpose	Commitment	Owner
Product Backlog	Emergent, ordered list of product improvements	Product Goal	Product Owner
Sprint Backlog	Sprint plan (Goal + selected items + delivery plan)	Sprint Goal	Developers
Increment	Sum of all completed work meeting quality standards	Definition of Done	Scrum Team

In this section, we explore each Scrum Artifact, its purpose, structure, and how it supports the Scrum Team's empirical approach to product development.

Product Backlog

The Product Backlog is an emergent, ordered list of everything needed to improve the product. It serves as the single source of work for the entire Scrum Team.

Key characteristics:

• Emergent: The backlog continuously evolves based on new insights from customers, stakeholders, and the marketplace
• Ordered: Items are explicitly sequenced (not categorized as high/medium/low priority)
• Living artifact: Never complete - it grows and changes throughout the product's lifetime
• Single source of truth: One Product Backlog per product, even with multiple teams

The Product Owner is accountable for the Product Backlog, including its content, ordering, and ensuring transparency to all stakeholders.

Product Goal Commitment

The Product Goal is the commitment for the Product Backlog. It describes a future state of the product that serves as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog, and the rest of the backlog emerges to define what will fulfill the Product Goal.

Role of Product Backlog in Scrum

The Product Backlog provides clarity on what work delivers maximum value:

• Strategic direction: Product Goal guides all planning decisions
• Value optimization: Ordering enables teams to work on highest-value items first
• Transparency: All stakeholders can see what's coming and why
• Sprint Planning input: Provides refined, ready items for Sprint selection
• Continuous refinement: Product Owner regularly refines items, ensuring top items are ready for upcoming Sprints

Sprint Backlog

The Sprint Backlog is composed of three elements:

1. Sprint Goal (why) - The objective for the Sprint
2. Selected Product Backlog items (what) - Items chosen for the Sprint
3. Actionable plan (how) - The team's plan for delivering the Increment

The Sprint Backlog is created during Sprint Planning and is owned entirely by the Developers. It's a highly visible, real-time picture of the work the Developers plan to accomplish during the Sprint.

Key characteristics:

• Dynamic: Updated throughout the Sprint as more is learned
• Detailed enough: Contains sufficient detail for inspection during Daily Scrum
• Flexible scope: Specific work items may change while Sprint Goal remains fixed
• Developer-owned: Only Developers can change the Sprint Backlog

Sprint Goal Commitment

The Sprint Goal is the commitment for the Sprint Backlog. It's the single objective for the Sprint that provides coherence and focus, encouraging the Scrum Team to work together rather than on separate initiatives. The Sprint Goal provides flexibility regarding the exact work needed to achieve it.

Relevance of Sprint Backlog in Scrum

The Sprint Backlog serves multiple critical functions:

• Focus: Helps Developers maintain focus on Sprint Goal work
• Transparency: Provides visible view of current Sprint plans and progress
• Adaptability: Updated daily to reflect new insights and changes
• Accountability: Holds Developers accountable for Sprint commitments
• Coordination: Enables effective collaboration during Daily Scrum

Increment

The 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.

Key characteristics:

• Cumulative: Each new Increment includes all previous Increments, integrated and tested
• Usable: Must be in a releasable state, regardless of whether Product Owner decides to release it
• Verified: Thoroughly tested and meets quality standards
• Multiple per Sprint: Teams can create multiple Increments within a single Sprint
• Done: Meets the team's Definition of Done

The Increment is the tangible outcome of the Scrum Team's work during a Sprint, presented at Sprint Review for inspection and feedback.

Definition of Done Commitment

The Definition of Done is the commitment for the Increment. It's a formal description of the state of the Increment when it meets the quality measures required for the product. Work cannot be considered part of an Increment unless it meets the Definition of Done.

Significance of Increments

Increments provide critical value to the Scrum process:

• Deliver value: Each Increment delivers new features, enhancements, or fixes to stakeholders
• Measure progress: Provides concrete evidence of progress toward Product Goal
• Enable feedback: Stakeholders can inspect working software and provide input
• Support empiricism: Regular Increments enable inspection and adaptation cycles
• Reduce risk: Frequent integration reduces the risk of late-stage integration problems
• Maintain transparency: Clear view of product's current state for all stakeholders

Why Artifacts Matter: Transparency, Inspection, Adaptation

Scrum Artifacts are designed to maximize transparency of key information, enabling the Scrum Team and stakeholders to have a shared understanding of:

What is being developed (Product Backlog with Product Goal)

• Single source of truth for all product work
• Clear strategic direction through Product Goal
• Transparent ordering based on value and risk

What is being worked on right now (Sprint Backlog with Sprint Goal)

• Visible Sprint plans and daily progress
• Coherent Sprint objective uniting the team
• Flexible execution within Sprint Goal boundaries

What has been delivered (Increment with Definition of Done)

• Concrete, working software at regular intervals
• Shared quality standards through Definition of Done
• Cumulative value delivery toward Product Goal

Each artifact and its commitment work together to support Scrum's empirical process control, enabling teams to inspect their progress and adapt their approach based on reality rather than assumptions.