Skip to content 
Key Highlights of Scrum Artifacts
- Understand what are Scrum artifacts and why they matter.
- Explore the three Scrum artifacts and their commitments.
- Learn Product Backlog, Sprint Backlog, and Increment explained.
- Understand Scrum artifacts and commitments with practical examples.
- Know the Definition of Done Scrum artifact commitment.
- Clarify artifact accountabilities, Sprint changes, and exam essentials.
Scrum artifacts sound simple until you sit for a certification exam, join a real Scrum Team, or have to explain the difference between a Product Backlog and a Sprint Backlog. That is where small terminology mistakes can create big confusion.
Scrum officially defines only three artifacts: the Product Backlog, Sprint Backlog, and Increment. Each has a specific commitment, the Product Goal, Sprint Goal, and Definition of Done. It gives the work its direction and meaning.
After working with Agile and Scrum concepts across training and content, I’ve found that most confusion comes from mixing official Scrum elements with commonly used practices such as burndown charts, velocity, roadmaps, and user stories.
This blog breaks that down without unnecessary theory. You’ll see what each artifact contains, who is accountable for it, what can change during a Sprint, and how the three artifacts connect from product planning to a usable Increment.
What Are Scrum Artifacts?
Scrum artifacts are work or value representations that make important information transparent to the Scrum Team and stakeholders. Scrum has three official artifacts: the Product Backlog, Sprint Backlog, and Increment. Each has a commitment that provides focus and supports inspection and adaptation.
What is an Artifact in Scrum?
An artifact in Scrum represents work or value and helps everyone understand the current state of the product and Sprint.
- Product Backlog: Ordered list of work needed to improve the product.
- Sprint Backlog: Selected Product Backlog items and the plan for delivering them.
- Increment: A usable, valuable result that meets the Definition of Done.
How Scrum Artifacts Create Transparency
Scrum artifacts make work visible and create a shared understanding of progress. The Product Backlog shows what may be needed, the Sprint Backlog shows what the team is working on, and the Increment shows completed, usable value.
This transparency supports effective inspection and adaptation. Scrum practices can also contribute to broader enterprise digital transformation by improving visibility, collaboration, and iterative delivery across teams.
What Are the 3 Scrum Artifacts?
The three artifacts provide transparency into the work and value created during Scrum. Each commitment gives the corresponding artifact a clear purpose and focus.
| Scrum Artifact | Commitment | Primary Accountability |
| Product Backlog | Product Goal | Product Owner |
| Sprint Backlog | Sprint Goal | Developers |
| Increment | Definition of Done | Developers |
If you’re considering a Scrum career, understanding whether Scrum Master Certification is worth it can help you evaluate the skills, career opportunities, and certification path involved.
Scrum Artifacts and Their Commitments
Each Scrum artifact has a corresponding commitment that provides focus and supports transparency. The three commitments are the Product Goal, Sprint Goal, and Definition of Done.
Product Backlog and Product Goal
The Product Goal describes a future state of the product and provides a long-term objective for the Scrum Team. It is the commitment to the Product Backlog and gives the team a clear direction for product development.
Effective Product Backlog management is also an important part of Agile Product Management, where product priorities are continuously aligned with customer and business needs.
Sprint Backlog and Sprint Goal
The Sprint Goal is the single objective for the Sprint. It is the commitment for the Sprint Backlog and gives Developers flexibility in adjusting their plan while keeping the Sprint focused on a specific outcome.
Increment and Definition of Done
The Definition of Done is the formal description of the quality state required for an Increment to be considered complete. It is the commitment to the Increment and ensures that completed work meets the required quality standards.
Product Backlog vs Sprint Backlog
The Product Backlog contains the ordered work needed to improve the product, while the Sprint Backlog contains the work selected for the current Sprint and the plan for delivering it.
| Aspect | Product Backlog | Sprint Backlog |
| Purpose | Defines potential product work | Defines work for the current Sprint |
| Scope | Product-wide | Sprint-specific |
| Commitment | Product Goal | Sprint Goal |
| Accountability | Product Owner | Developers |
| Changes | Continuously updated | Updated as more is learned during the Sprint |
If you’re comparing certification paths, understanding SAFe vs CSM can help clarify how their frameworks, roles, and learning objectives differ.
Who owns the Scrum Artifacts?
Scrum assigns specific accountabilities rather than treating all artifacts as personally owned. The Product Owner, Developers, and Scrum Team have different responsibilities for the artifacts and their commitments.
Who is Accountable for the Product Backlog?
The Product Owner is accountable for effective Product Backlog management, including communicating with the Product Goal and ensuring the backlog is ordered and clear.
Who Owns the Sprint Backlog?
The Developers are accountable for creating the Sprint Backlog, including the Sprint Goal, selected Product Backlog items, and delivery plan. They update it throughout the Sprint as they learn more.
The Daily Scrum provides Developers an opportunity to inspect progress toward the Sprint Goal and adapt their plan, which is why understanding what a Daily Scrum meeting is is important.
Who is Responsible for the Definition of Done?
The Definition of Done is the commitment to the Increment. If an organization has a quality standard, all Scrum Teams must follow it as a minimum. Otherwise, the Scrum Team creates an appropriate Definition of Done for the product.
What Are Not Scrum Artifacts?
Scrum officially defines only three artifacts: the Product Backlog, Sprint Backlog, and Increment. Other tools and techniques may support Scrum but are not official Scrum artifacts.
It is also useful to understand Daily Scrum vs Standup, since the terms are often used interchangeably even though Scrum defines the Daily Scrum as a specific event.
Is a Burndown Chart a Scrum Artifact?
No. A burndown chart is a common progress-tracking tool, but it is not one of Scrum’s three official artifacts.
Is Velocity a Scrum Artifact?
No. Velocity is a metric that some teams use to understand their historical work rate. It is not defined as a Scrum artifact.
Is a Product Roadmap a Scrum Artifact?
No. A product roadmap can communicate product direction and planned outcomes, but Scrum does not define it as an official artifact.
Are User Stories Scrum Artifacts?
No. User stories are a technique for describing work or customer needs. They can be used as Product Backlog items, but Scrum does not require user stories specifically.
What Can Change During a Sprint?
The Sprint Goal remains fixed, but the Sprint Backlog can be updated as Developers learn more. Scope can also be clarified and renegotiated with the Product Owner without affecting the Sprint Goal. If the Sprint Goal becomes obsolete, the Product Owner can cancel the Sprint.
Scrum Masters can also use relevant Agile metrics for Scrum Master practices to understand progress without turning metrics into rigid performance targets.
Scrum Artifacts and PSM Exam Questions
For Scrum certification exams such as PSM, remember the three artifacts and their commitments:
- Product Backlog to Product Goal
- Sprint Backlog to Sprint Goal
- Increment to Definition of Done
Also remember that the Product Owner is accountable for the Product Backlog, while Developers are accountable for the Sprint Backlog and creating a usable Increment that meets the Definition of Done.
Scrum Artifacts Example: From Product Backlog to Increment
Consider a team developing an online learning platform:
- Product Backlog: The backlog includes features such as course search, user registration, and personalized recommendations.
- Product Goal: The team aims to improve how users discover relevant courses.
- Sprint Backlog: Developers select relevant backlog items and create a plan for the Sprint.
- Sprint Goal: The Sprint focuses on improving course discovery.
- Increment: By the end of the Sprint, the completed work forms a usable Increment that meets the Definition of Done.
This flow shows how the three artifacts and their commitments connect from product direction to usable value.
Conclusion
Scrum has three official artifacts: the Product Backlog, Sprint Backlog, and Increment. Each has a clear commitment, the Product Goal, Sprint Goal, and Definition of Done. Together, they create transparency around product work, Sprint progress, and delivered value.
Knowing their purpose, accountabilities, and differences also helps avoid confusion with practices like velocity, burndown charts, roadmaps, and user stories.
For both Scrum Teams and certification candidates, understanding this 3+3 structure makes Scrum easier to apply and remember.
Frequently Asked Questions
1.What are the 3 artifacts in Scrum?
The three Scrum artifacts are the Product Backlog, Sprint Backlog, and Increment.
2.What is the commitment for the Product Backlog?
The commitment for the Product Backlog is the Product Goal, which describes the future state the Scrum Team aims to achieve.
3.What is the difference between Product Backlog and Sprint Backlog?
The Product Backlog contains the work needed for the product, while the Sprint Backlog contains the work selected for the current Sprint and the plan to deliver it.
4.Can the Product Owner change the Sprint Backlog?
No. The Developers manage the Sprint Backlog. They can negotiate scope changes with the Product Owner as long as the Sprint Goal remains unchanged.
5.Is a burndown chart a Scrum artifact?
No. Scrum officially defines only the Product Backlog, Sprint Backlog, and Increment as artifacts.
6.What is the Definition of Done in Scrum?
The Definition of Done is the commitment for the Increment. It describes the quality standard an Increment must meet to be considered complete.
