What are Scrum Artifacts?

Scrum Artifacts are an essential part of the Scrum Framework. There are three, the Product Backlog, the Sprint Backlog and the Increment. Scrum Artifacts are an Agile form of documentation. They are the output of the Scrum Teams that contain all the information and documentation to ensure that it is clear to all what is being delivered and to what standards they adhere to.

The Product Backlog

The Product Backlog functions as a customers wishlist, the Product Owner drafts it after talking to the stakeholders and discussing the wishes for the Product and the priority for each work item. In Scrum these work items are usually divided into Epics, features and user stories. The Product Backlog is dynamic and should be constantly updated and refined.

When the Epics and features get broken down into smaller work items, called User Stories they end up on the Product Backlog. As the Scrum Team delivers these User Stories, new ones are created and broken down into smaller pieces of work so they can be selected for the upcoming Sprint.

The Sprint Backlog

The Sprint Backlog is like a shopping cart for the current Sprint. It’s a subset of items from the Product Backlog that your team commits to delivering during the Sprint. The Development Team is responsible for selecting these items based on their capacity and the Sprint Goal. Ensuring self-organisation and continuous improvement.

The difference between the Product Backlog and the Sprint Backlog is that the Product Backlog belongs to the Product Owner and the Sprint Backlog belongs to the Development Team. Both are structured based on priority.

Increment

The increment in Scrum is everything that is delivered at the end of the Sprint plus all Increments from previous Sprints. Its the accumulation of all completed User Stories that were selected from the Product Backlog and put on the Sprint Backlog for creation and delivery. The Goal of a Sprint is to create at least one valuable and potentially releasable Increment.

To sum up

Scrum artifacts provide Clarity and Transparency, they keep everyone informed and aligned with the project goals. The Product Backlog is a living document, constantly evolving as new insights and priorities emerge, this is why it’s at the foundation of implementing continuous improvement within Scrum. Whereas the Sprint Backlog keeps everyone focused on the value delivery to be done at the end of the Sprint. They also contain the requirements and “Definition of Done” so the Development Team knows when a work item is considered as done.

What are the 3 Pillars within Scrum?

Scrum contains many concepts, including 5 values, 3 pillars, 5 events, and 3 artifacts. This might sound like a lot, and perhaps even unnecessary, but nothing could be further from the truth! They all play an important role. The 3 pillars help to understand the principles on which Scrum is based.

Where do the 3 Scrum Pillars come from?

Scrum is based on Empiricism. Just like Scrum, Empiricism has 3 pillars, which Scrum has adopted. The 3 pillars can be seen as an ancient Greek temple. The temple has a roof, Empiricism, and 3 pillars, each representing one value: Transparency, Inspection, and Adaptation. Finally, there is a foundation necessary to support the 3 pillars, which is trust.

Empiricism

You may have heard the term “empirically determined.” This means something has been established based on practice. The expression “trial and error” is similar because you try something and see if it works or not. In Empirical working, we learn from practice, and this forms the basis for Scrum. However, we want to work in a structured manner, not just try everything. To do this, according to the Scrum framework, we need the other 3 pillars, as well as the foundation of trust.

Trust

As mentioned earlier, the foundation for the pillars in Scrum is trust. Trust makes it possible to have the other pillars. For example, transparency is not possible without trust. Why would someone be transparent if the organization doesn’t trust them to make mistakes? A mutual trust between team members and the organization is crucial in Scrum, as it enables empirical working.

Transparency

Transparency is one of the core principles and 3 pillars within Scrum, ensuring that all aspects of the process are visible to everyone. This includes the work being done, the progress being made, and any obstacles that may arise. Through transparency, Scrum teams can make informed decisions, adapt to changes, and continuously improve. Key elements such as the Product Backlog, Sprint Backlog, and Burndown charts are made visible to everyone, allowing for clear communication and shared understanding. Transparency fosters trust among team members, stakeholders, and ensures alignment on goals, priorities, and expectations, contributing to successful outcomes.

Inspection

Inspection is an essential element and part of the 3 pillars within Scrum, where teams regularly assess progress toward goals and the quality of work. This process ensures that the team identifies problems, obstacles, or deviations early, allowing for timely adjustments. Scrum events such as the Daily Scrum, Sprint Review, and Sprint Retrospective promote continuous inspection of work and processes. Inspection is closely related to transparency, as it depends on clear, visible information about progress, challenges, and results. By inspecting regularly, the team can maintain an accurate view of the situation and make informed decisions to stay aligned with project goals—this is not possible without transparency.

Adaptation

Adaptation in Scrum refers to the team’s ability to adjust their approach based on insights gained through regular inspection. When the team identifies problems, inefficiencies, or changes in priorities, they adjust their plan, processes, or goals to stay on track. This flexibility ensures continuous improvement and alignment with project objectives. Adaptation is closely linked to transparency, as it relies on clear, accessible data about progress and challenges. When information is transparent, the team can make informed adjustments quickly, enabling them to respond effectively to emerging needs and remain aligned with both stakeholders and the broader vision.

Conclusion

The three pillars of Scrum—transparency, inspection, and adaptation—work together to create a framework that promotes continuous improvement and ensures teams can respond effectively to challenges. Transparency provides clarity and shared understanding, inspection allows teams to assess progress, and adaptation enables necessary changes to stay on track. When these pillars are embraced, Scrum teams are empowered to deliver high-quality results, adapt to changes, and achieve greater success in their projects.