What are Scrum artifacts? Types and examples
Learn what Scrum artifacts are, the three official types and their commitments, with practical examples of how Scrum teams plan and deliver work.
Learn what Scrum artifacts are, the three official types and their commitments, with practical examples of how Scrum teams plan and deliver work.

A Scrum team may have dozens of tasks in progress, yet three questions still matter: What should we build next? What are we trying to accomplish this sprint? What have we completed? Scrum artifacts provide a shared reference for answering these questions by making product priorities, ongoing work, and completed outcomes visible. They help teams inspect progress, coordinate decisions, and adapt as requirements evolve. This guide explains the three official Scrum artifacts, their associated commitments, and how they work together throughout product development.
What are Scrum artifacts?
Scrum artifacts are the three formal elements of the Scrum framework that represent work or value and make essential information about product development transparent. They establish a shared understanding of what the team intends to accomplish, how the current sprint is progressing, and what has been delivered.
According to the Scrum Guide, there are three official types of Scrum artifacts:
- Product backlog: An ordered, evolving list of work needed to improve the product.
- Sprint backlog: The sprint goal, selected product backlog items, and the developers' plan for completing the work.
- Increment: A usable addition to the product that meets the definition of done and builds on previously completed work.
Each artifact has an associated commitment that gives the team a clear reference for evaluating progress. Together, they support Scrum's three pillars of transparency, inspection, and adaptation.
Scrum artifacts also work alongside Scrum events. While events such as sprint planning and sprint review create opportunities for teams to inspect and adapt, artifacts provide the information needed to make those decisions.
Why are Scrum artifacts important?
Scrum teams make decisions continuously, from ordering product requirements to adjusting sprint plans and evaluating completed functionality. Scrum artifacts ensure these decisions are informed by a consistent and current understanding of the work.
Their importance comes down to five practical benefits:
- Shared visibility: Product owners, developers, and stakeholders can examine the same information about product priorities, current work, and completed outcomes, reducing reliance on disconnected status updates.
- Better alignment: Teams can connect individual development activities with product objectives and evaluate whether their efforts contribute to the intended outcome.
- More informed planning: An ordered view of upcoming work helps developers assess priorities, dependencies, and capacity before selecting work for a sprint.
- Earlier course correction: Regular inspection helps teams recognize changing requirements, emerging constraints, and differences between planned and actual progress.
- Clearer delivery expectations: Completed functionality can be evaluated against agreed quality standards, giving stakeholders greater confidence in what is ready for use.
These benefits depend on the information remaining accurate and accessible. An outdated backlog or an incomplete sprint plan can create misunderstandings even when the team follows the prescribed Scrum events.
What are the three Scrum artifacts?
The three Scrum artifacts address different parts of product development. The product backlog establishes the work available for consideration, the sprint backlog describes the current execution plan, and the increment represents the usable results of development.
Scrum artifact | Primary purpose | Accountability | Associated commitment |
Product backlog | Organizes work needed to improve the product | Product owner | Product goal |
Sprint backlog | Makes the current sprint objective and execution plan visible | Developers | Sprint goal |
Increment | Represents completed, usable product functionality | Entire Scrum team | Definition of done |
1. Product backlog
The product backlog is the single, ordered list of work required to improve a product. It evolves as the team gains a better understanding of customer needs, technical requirements, and business priorities.
Product backlog items (PBIs) may represent new features, bug fixes, technical improvements, performance enhancements, or other changes that contribute to the product's development. Their level of detail varies depending on how soon the team expects to work on them.
Items approaching implementation generally need clearer descriptions, smaller scopes, and sufficient information for developers to understand the expected outcome. Work that may be considered several sprints later can remain less detailed until further refinement becomes useful.
The product owner is accountable for effective product backlog management, including communicating backlog items, ordering the work, and ensuring that the backlog remains visible and understood. Developers contribute technical knowledge and are responsible for sizing the work they will perform.
Backlog refinement is an ongoing activity in which items are clarified, broken into smaller pieces, and prepared for potential selection during sprint planning.
A well-maintained product backlog also helps teams connect near-term development decisions with broader product direction. For a detailed explanation of this relationship, read Product roadmap vs. backlog: What's the difference?.
2. Sprint backlog
The sprint backlog is the plan developers create and maintain for achieving the current sprint's objective. It is developed during sprint planning, when the Scrum team discusses the most important product backlog items and determines what can reasonably be accomplished.
It contains three essential components:
- Sprint goal: The objective that explains why the sprint is valuable.
- Selected product backlog items: The work developers have chosen to undertake during the sprint.
- Actionable delivery plan: The activities required to turn those items into a usable increment.
Developers are accountable for the sprint backlog and determine how the selected work will be implemented. They may break larger items into smaller tasks, identify technical dependencies, and coordinate activities according to their understanding of the work.
The sprint backlog evolves during execution. Developers may discover additional tasks, revise implementation approaches, or negotiate changes in scope with the product owner as new information becomes available. These adjustments must preserve the sprint goal.
The backlog should contain enough detail for developers to inspect their progress during the daily Scrum and make informed decisions about upcoming work.
For practical guidance on building an executable sprint plan, explore What is a sprint backlog? A complete guide for Agile teams.
3. Increment
An increment represents a usable addition to the product that has satisfied the definition of done. It builds on previous increments, with each completed addition contributing to the product's overall functionality and value.
For an item to become part of an increment, the completed work must meet the relevant quality requirements and function correctly alongside existing product capabilities.
The entire Scrum team is accountable for creating a valuable, useful increment every sprint. Developers are responsible for adhering to the definition of done as they create the work.
Several increments can be produced during a single sprint. For example, developers might complete one independently usable improvement early in the sprint and integrate another later, provided both satisfy the required standards.
An increment can also be released before the sprint ends. The decision to make completed functionality available depends on the team's product and delivery requirements.
This approach allows Scrum teams to build products through successive usable improvements while maintaining consistent quality expectations.
For a deeper explanation of incremental delivery, read What is a product increment? Definition, examples, and best practices.
What are Scrum artifact commitments?
Scrum artifacts and commitments work together to provide clarity about objectives, progress, and completion. Each official artifact has one commitment that establishes the focus or standards against which it can be inspected.
1. Product goal: Commitment to the product backlog
The product goal defines the future state the Scrum team wants to achieve for its product. It establishes a longer-term direction that guides decisions about which backlog items deserve attention and how individual development efforts contribute to a larger objective.
A product goal should describe a meaningful outcome that the team can work toward across multiple sprints. For example, a product team may aim to enable new customers to complete their initial setup independently.
The product owner communicates the product goal, while the entire Scrum team works toward achieving it. Scrum teams pursue one product goal at a time, completing or abandoning that objective before adopting another.
This gives the product backlog a consistent direction even as individual requirements and their ordering change.
2. Sprint goal: Commitment to the sprint backlog
The sprint goal establishes the single objective that developers commit to achieving during the current sprint. It gives the selected work a shared purpose and provides a reference for evaluating implementation decisions.
The Scrum team develops the sprint goal collaboratively during sprint planning. Its wording should make the expected outcome understandable while leaving developers flexibility in how they accomplish it.
When unexpected work or technical constraints arise, the sprint goal helps developers determine which adjustments are appropriate. Scope may be clarified or renegotiated with the product owner, provided the changes preserve the agreed objective.
This supports adaptability during execution while keeping the team's efforts focused.
Learn more about defining meaningful sprint objectives in What is a sprint goal? Examples and how to write one.
3. Definition of done: Commitment to the increment
The definition of done establishes the quality requirements that completed work must satisfy before becoming part of an increment.
For software development teams, these requirements may include successful automated tests, completed code reviews, integration checks, security validations, and relevant documentation updates.
The applicable definition of done must follow any organizational standards established for the product. When no such standards exist, the Scrum team creates an appropriate definition.
Developers are required to meet these standards when producing an increment. If several Scrum teams work on the same product, they must share a common definition of done.
A consistent completion standard helps everyone understand what qualifies as finished work and reduces ambiguity when evaluating delivery readiness.
For examples of practical completion criteria, explore Definition of done (DoD): Checklist examples for Agile teams.
How do Scrum artifacts work together? A practical example
Understanding individual artifacts is useful, but their relationship becomes clearer when following a feature from initial prioritization through development and stakeholder feedback.
Consider a hypothetical software team improving the onboarding experience for new workspace administrators. Its product goal is to help administrators complete their initial workspace setup independently.
The team has identified several improvements that could contribute to this objective.
Step 1. Organize requirements in the product backlog
The product owner creates and orders backlog items based on the expected customer value, current product needs, and the team's understanding of implementation dependencies.
The initial product backlog might contain:
Product backlog item | Intended outcome | Example order |
Guided project creation | Help administrators create their first project | 1 |
Teammate invitations | Make it easier to start collaborating | 2 |
Suggested project templates | Reduce repeated setup decisions | 3 |
Setup progress indicators | Help administrators identify remaining setup steps | 4 |
The team refines the guided project creation item by clarifying the expected user journey, identifying validation requirements, and discussing technical dependencies.
The product backlog now provides an ordered view of the onboarding improvements available for future development.
Step 2. Select work and create the sprint backlog
During sprint planning, the Scrum team reviews the highest-ordered backlog items and agrees on a sprint goal:
Enable new administrators to create their first project through a guided setup experience.
Developers select the guided project creation item and develop an initial implementation plan.
The plan covers interface design, project creation logic, form validation, integration, and testing. The developers also consider their available capacity and any dependencies that could affect delivery.
Other onboarding improvements remain in the product backlog for future consideration.
The sprint backlog now contains the objective, selected work, and implementation plan needed for the current sprint.
Step 3. Complete the feature and create a usable increment
During the sprint, developers implement the guided setup experience and update their plan as work progresses.
Before the completed functionality can become part of an increment, it must satisfy the team's definition of done.
For this hypothetical feature, the agreed criteria might require:
- Successful project creation through the guided setup flow.
- Correct handling of required fields and validation errors.
- Passing automated and integration tests.
- Completed code review.
- Verified compatibility with the existing project creation workflow.
Once the functionality meets these requirements and is integrated with the existing product, it forms a usable increment.
The team can make the improvement available to users when appropriate, even if the sprint is still underway.
Step 4. Inspect the outcome and adapt future work
At the sprint review, the Scrum team and stakeholders examine the completed onboarding experience and discuss how effectively it supports the product goal.
Suppose stakeholders observe that users need clearer instructions for inviting teammates after creating their first project.
The product owner can use this feedback to refine the teammate invitation item and reconsider its position in the product backlog. Developers may also contribute implementation insights that influence how the next improvement is approached.
The completed feature remains part of the product, while the newly identified needs inform future development decisions.
This example shows how Scrum artifacts connect product direction, sprint execution, and usable outcomes. Each artifact provides information that supports the next decision, allowing the team to adjust its approach as it learns more about the product and its users.
What are the other commonly used artifacts in Scrum?
Beyond the three official Scrum artifacts, Agile project management teams often use additional planning documents and visual tools to organize work, communicate direction, and evaluate delivery trends.
These are supporting practices rather than additional artifacts formally required by the Scrum Guide.
Supporting tool | What it helps teams understand | Common application |
Burndown and burnup charts | How completed or remaining work changes over time | Monitoring sprint or release progress |
Product roadmaps | How planned initiatives contribute to product direction | Communicating longer-term priorities |
Scrum boards | Where current work sits in the development workflow | Coordinating execution and identifying blockers |
Release plans | How completed capabilities will be made available | Coordinating deployment and delivery expectations |
Burndown and burnup charts are particularly useful for examining delivery trends. A burndown chart tracks remaining work, while a burnup chart shows completed work against a defined scope.
These charts can inform discussions about progress, although the team must still inspect actual outcomes to determine whether its sprint goal has been achieved.
For a closer look at progress visualization, read What is a burndown chart? How to create and interpret one.
The value of supporting tools depends on the decisions they enable. Teams should choose them according to their planning and coordination needs while maintaining the three official Scrum artifacts and their commitments.
How do you manage Scrum artifacts effectively?
Effective Scrum artifact management requires current information, clear accountability, and consistent opportunities to inspect and adapt the work. Teams can improve their practices by focusing on four areas.
1. Refine backlog items at the right level of detail
Backlog refinement should help developers understand upcoming work well enough to discuss its value, complexity, and feasibility.
Items being considered for the next sprint generally benefit from clearer outcomes, smaller scopes, and an understanding of relevant dependencies. More distant work can remain broader until the team has enough information to refine it meaningfully.
This approach helps teams invest refinement effort where it supports immediate planning decisions.
2. Keep the sprint plan visible and adaptable
The sprint backlog should reflect the developers' current understanding of the work, including progress, newly discovered tasks, and changes in the implementation approach.
During the daily Scrum, developers inspect progress toward the sprint goal and determine whether their plan needs adjustment. They may also coordinate changes throughout the working day as new information emerges.
A current plan makes it easier to identify dependencies, discuss impediments, and decide what needs attention next.
For more guidance on preparing and coordinating sprint work, read Sprint planning 101: How to run productive sprints.
3. Use Scrum events to make informed decisions
Each Scrum event creates an opportunity to inspect specific information and determine what should happen next.
During sprint planning, the team establishes its objective and develops an initial plan. The daily Scrum helps developers adapt execution, while the sprint review brings the team and stakeholders together to examine outcomes and consider future product decisions.
The sprint retrospective focuses on improving team effectiveness, including working practices that influence how artifacts are created and maintained.
The usefulness of these events depends on the quality of the information available and the decisions that follow.
4. Maintain shared visibility through project management tools
Project management tools can help teams organize work, coordinate sprint activities, and keep relevant information accessible.
In Plane, teams can organize features, bugs, improvements, and other development tasks using Work Items. Selected work can be grouped into time-boxed Cycles, helping teams manage sprint execution and inspect progress.
Plane also provides burn-down and build-up charts within Cycles, giving teams additional information for assessing delivery trends.
These capabilities support the practical organization of Scrum work. Teams remain responsible for establishing their product and sprint goals, applying the definition of done, and inspecting the actual value delivered.
What are the common mistakes to avoid when managing Scrum artifacts?
Many Scrum implementation problems arise from how teams interpret the information provided by artifacts. A backlog may be perfectly maintained, and a sprint board may show substantial progress, while the team still lacks clarity about the outcome achieved.
The following mistakes deserve particular attention.
1. Measuring sprint success only by completed tasks
A sprint can finish with every planned task marked complete while the team falls short of its intended objective.
For example, developers might complete several technical improvements without delivering the user-facing capability described in the sprint goal.
Evaluating sprint success requires inspecting the outcome against the sprint goal alongside the work completed. Task counts and progress charts can provide supporting information, but they offer only part of the delivery picture.
2. Treating the sprint review as a release approval gate
Some teams delay releasing completed functionality until the sprint review, even when an increment has already satisfied the definition of done and is ready for use.
Scrum allows usable increments to be delivered during the sprint. The sprint review provides an opportunity to inspect results, discuss stakeholder feedback, and determine future adaptations.
Teams can therefore coordinate releases according to their delivery requirements while preserving the review's purpose as an inspection and adaptation event.
3. Counting individually completed tasks as a usable increment
Development tasks may be marked complete while the associated functionality still requires integration or verification.
For example, an interface component may be finished and reviewed, but the feature cannot function correctly until its supporting services are connected and tested.
A usable increment requires completed work to meet the applicable definition of done and function alongside previous increments. Teams should evaluate the integrated product outcome before including work in the increment.
4. Maintaining disconnected product backlogs for the same product
When several teams contribute to one product, separate and independently ordered backlogs can make it difficult to understand overall product priorities.
The Scrum framework establishes one product backlog as the source of work for a product. Multiple Scrum teams working on that product share its product goal, product backlog, and product owner.
Maintaining this shared direction helps teams coordinate dependencies and make decisions based on the product's overall needs, even when execution happens across different development teams.
Final thoughts
Scrum artifacts connect product planning, sprint execution, and completed outcomes through a shared set of information. The product backlog establishes the work available for development, the sprint backlog provides a focused execution plan, and the increment makes completed product value available for inspection.
When teams maintain these artifacts accurately and use their commitments to guide decisions, they gain a clearer understanding of priorities, progress, and delivery outcomes as their products evolve.
Frequently asked questions
1. What are the three main artifacts of Scrum?
The three main Scrum artifacts are the product backlog, sprint backlog, and increment. The product backlog organizes work needed to improve the product, the sprint backlog contains the current sprint's objective and execution plan, and the increment represents completed, usable product work. These artifacts make work and value transparent throughout development.
2. Who is responsible for managing Scrum artifacts?
The product owner is accountable for effective product backlog management, while developers are accountable for creating and maintaining the sprint backlog. The entire Scrum team is accountable for producing a valuable, usable increment every sprint. The Scrum master helps the team understand and apply Scrum effectively.
3. What is the difference between Scrum artifacts and Scrum commitments?
Scrum artifacts represent work or value, while their commitments establish the objectives or quality standards used to evaluate them. The product goal is associated with the product backlog, the sprint goal with the sprint backlog, and the definition of done with the increment.
4. What is the difference between a product backlog and a sprint backlog?
The product backlog contains the ordered work needed to improve a product over time. The sprint backlog focuses on the current sprint and includes its goal, selected product backlog items, and an actionable delivery plan. The product owner is accountable for effective product backlog management, while developers are accountable for the sprint backlog.
5. Is the definition of done considered a Scrum artifact?
The definition of done is the commitment associated with the increment. It establishes the quality requirements that completed work must satisfy before becoming part of a usable increment. The Scrum Guide formally recognizes the increment as an artifact and the definition of done as its associated commitment.
Recommended for you



