{"id":31054,"date":"2024-06-17T13:54:50","date_gmt":"2024-06-17T11:54:50","guid":{"rendered":"https:\/\/scrum-master.org\/scrum-artifacts-complete-guide\/"},"modified":"2024-06-17T15:12:07","modified_gmt":"2024-06-17T13:12:07","slug":"scrum-artifacts-complete-guide","status":"publish","type":"post","link":"https:\/\/scrum-master.org\/en\/scrum-artifacts-complete-guide\/","title":{"rendered":"Scrum Artifacts: Complete Guide"},"content":{"rendered":"\t\t
\n\t\t\t\t
\n\t\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

As part of the Scrum methodology, artifacts play a crucial role in ensuring transparency, inspection and adaptation. They provide essential information on work in progress, actions to be taken and progress achieved.<\/p>\n

This article aims to explain in detail the three main Scrum artifacts: the Product Backlog, the Sprint Backlog and the Increment, as well as their associated commitments<\/strong>.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Diagram\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

What is a Scrum Artifact?<\/h2>\n

A Scrum artifact is a tool used by Scrum teams to represent work or value. It provides important information about the product under development, the actions required to achieve the objectives, and the measures taken during the life of the product.<\/p>\n

Artifacts are designed to maximize the transparency of key information, enabling the Scrum team and stakeholders to inspect and adapt their work accordingly. There are three main Scrum artifacts: the Product Backlog, the Sprint Backlog and the Increment.<\/strong><\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Scrum\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Product Backlog<\/strong><\/h2>

Description<\/h3>

The Product Backlog<\/strong> is an ordered list of everything needed to improve the product. It is the one and only working reference for the Scrum team. Product Backlog items are continuously refined and can include user stories, features, business requirements, enhancements and bug fixes. Click here to read our full article on the Product Backlog <\/strong><\/a>to find out more.<\/p>

The Product Owner’s role<\/h3>

The Product Owner<\/a> is responsible for managing and prioritizing the Product Backlog<\/strong>. He must ensure that the Product Backlog is transparent, prioritized, visible and understood by all. The Product Owner is also responsible for developing and clearly communicating the Product Goal.<\/p>

Typical content<\/h3>

The Product Backlog contains elements such as user stories, features<\/a> and all the tasks required to achieve the Product Goal. These elements are prioritized according to their added value and impact on the product.<\/p>

Associated Commitment – Product Goal<\/h3>

The Product Goal<\/strong> is a long-term objective for the Scrum team, describing a desired future state of the product. It guides the evolution of the Product Backlog and gives a clear direction to the Scrum team. This goal is enshrined in the Product Backlog, and all the elements of this backlog are organized and prioritized to help achieve this goal. The Product Goal helps the team maintain focus on long-term results and ensure that each product increment brings significant value in that direction.<\/p>\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Product\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Sprint Backlog<\/strong><\/h2>\n

Description<\/h3>\n

The Sprint Backlog<\/strong> is a set of Product Backlog items selected for completion during the next sprint. It also includes an action plan for delivering the increment and reaching the Sprint Goal. The Sprint Backlog is created during theSprint<\/a> Planning meeting and updated daily during the Daily Scrum. <\/span>.<\/p>\n

Creation<\/h3>\n

The Sprint Backlog is drawn up during Sprint Planning. The development team selects the items in the Product Backlog and defines a detailed plan for implementing them during the sprint. Developers break down user stories and tasks into smaller, achievable elements over the course of a Sprint. The Sprint Backlog is constantly revised and adapted to reflect new information and progress.<\/p>\n

Contents<\/h3>\n

The Sprint Backlog contains specific tasks to be completed during the sprint, including user stories, features and bug fixes. These tasks are detailed and scheduled to ensure that they are completed within the allotted time of the sprint. It also includes the Sprint Goal, which guides the team and ensures the consistency of their efforts.<\/p>\n

Associated commitment – Sprint Goal<\/h3>\n

The Sprint Goal<\/strong> is the single objective of the sprint. It provides a clear direction and focus for the Scrum team during the sprint. The Sprint Goal is defined during Sprint Planning and added to the Sprint Backlog. It guides the team through tasks and helps maintain consistency and direction. The Sprint Goal helps the team focus on essential tasks and avoid distractions <\/span>.<\/p>\n

Follow-up and adaptation<\/h3>\n

The Sprint Backlog is a living document that is updated daily during the Daily Scrum. This meeting enables the team to monitor progress and adapt the plan according to new learnings and challenges encountered. Developers can add, delete or reorganize tasks in the Sprint Backlog to ensure they reach the Sprint Goal.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"Sprint\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

Increment<\/strong><\/h2>\n

Description<\/h3>\n

An increment<\/strong> is a set of functionalities or new features added to the product during each sprint. These are parts of the product that are complete and potentially deliverable at the end of the sprint. Each increment must be usable, even if not all of them are put into production immediately.<\/p>\n

In simple terms, in each sprint, the Scrum team develops and adds a new feature or enhancement to the product, making gradual progress towards the final product objective (Product Goal).<\/p>\n

Quality criteria – Definition of Done<\/h3>\n

The Definition of Done is a set of criteria that the increment must meet to be considered complete. It guarantees that the product meets the required quality standards and ensures consistency and clarity within the team. Definition of Done is crucial to maintaining the transparency and quality of delivered increments. <\/span>.<\/p>\n

Engagement Associ\u00e9 – Definition of Done<\/h3>\n

The commitment associated with the increment is the Definition of Done<\/strong>. This commitment ensures that the work is completed to the required quality standards before it is considered complete. Once the Product Backlog items comply with the Definition of Done, they can be integrated into the increment. This creates transparency and a shared understanding of what constitutes a finished job. We explored Definition of Done in detail in this article: Definition of Done (DoD): Everything you need to know<\/a>.<\/p>\n

Delivery and Feedback<\/h3>\n

The delivery and feedback process is essential for continuous product improvement. At the end of each sprint, the increment is presented at the Sprint Review<\/a>. This review enables the team and stakeholders to inspect the increment and provide feedback. This feedback is used by the Product Owner to adjust the Product Backlog and plan the next sprints, ensuring that the product evolves iteratively and incrementally to better meet user needs.<\/p>\n\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t

\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t\"definition\t\t\t\t\t\t\t\t\t\t\t\t\t\t\t<\/div>\n\t\t\t\t<\/div>\n\t\t\t\t
\n\t\t\t\t
\n\t\t\t\t\t\t\t\t\t

To sum up<\/h2>\n

Scrum artifacts are essential to guarantee transparency, inspection and adaptation within a Scrum team. The Product Backlog<\/b>, Sprint Backlog<\/b> andIncrement<\/b> each play a key role in organizing and managing work.<\/p>\n