Go back to:

Scrum Artifacts: the building blocks of transparency and value

A key principle of Scrum is that everyone on the team knows exactly what they are working on and why. Scrum Artifacts make this possible: they provide transparency regarding progress, priorities, and results already achieved. At Spark Academy, we've observed that teams effectively utilizing these artifacts experience less miscommunication and maintain a clearer view of the value they deliver.

Overview of Scrum Artifacts

In Scrum, there are three core artifacts: the Product Backlog, the Sprint Backlog and the Increment. Each artifact serves a specific purpose:

  • Product Backlog: a prioritized list of everything needed to improve the product or service.
  • Sprint Backlog: the selection from the Product Backlog for the current sprint, plus the plan to realize the work.
  • Increment: the sum of all completed items that meet the ‘Definition of Done’, ready for inspection and, ideally, use or release.

By clearly maintaining these artifacts, everyone within the team (and beyond) can see what the priorities are, where progress has already been made, and where there might still be work to be done.

Role of the Scrum Master

Although the Product Owner and Development Team are responsible for the content management and execution of these artifacts, the Scrum Master plays an indispensable role in safeguarding transparency and the process surrounding the artifacts. This includes facilitating inspection and adaptation moments, ensuring that the definitions of ‘Done’ and the quality of the items are respected, and helping to resolve any misunderstandings or obstacles.

The Scrum Master ensures that:

  • Sufficient clarity and discipline are maintained when updating the Product and Sprint Backlogs.
  • Continuous inspection and adaptation takes place, for example, during Sprint Reviews and Retrospectives.
  • Transparency is maintained, so that the Increment is visible and understandable to everyone.

Why are artifacts so important?

Through these artifacts, you create a shared understanding of what's happening in the sprint, how far along you are with delivering value, and where adjustments are still needed. This not only creates clarity within the team but also for stakeholders. This way, you prevent unrealistic expectations and collaborate more effectively towards a valuable end result.