Simplified Scrum’s artifacts represent work or value. They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation (learning).
One could keep asking the question “is this the highest level of transparency we can provide within <artifact name>?”. If not, experiment and uncover better ways by doing and helping others do it.
(entire chapter based on the Scrum Artifacts chapter in the 2020 Scrum Guides)
The Product Backlog provides the highest level of transparency on the possible future of the product.
Only near term implementations and experimentation have a higher level of transparency and thus details available. They usually acquire this degree of transparency after refining activities (= clarification) by the Teams and their customers. Refinement is an ongoing activity to add details about a possible approach to generate impact to customers and within the market. Refinement activities do take into account the transparency given within the Product Backlog and the learnings achieved in previous Sprints.
The Product Backlog is continuously being adapted according to the learning achieved by delivering a working product into the market. Validating assumptions and hypotheses along the way.
Multiple Teams often work together on the same product. One Product Backlog is used to describe the possible future of the product. One Product Owner is accountable to maximize the product value and drive focus through that single Product Backlog.
(entire chapter based on the Product Backlog chapter in the 2020 Scrum Guides)
The Sprint Backlog provides the highest level of transparency on the ongoing work within the Sprint.
The Sprint Backlog provides transparency by and for the Team. It is a highly visible, real-time picture of the work the Team is engaged in. Being committed to provide an impactful change towards their customers and market. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that the Team can inspect, adapt and learn how to self-manage and collaborate to drive impact forward.
To reduce complexity and coordination overhead, a single Sprint Backlog is owned by a single Team. Even when multiple Teams collaborate on a single Product Backlog.
(entire chapter based on the Sprint Backlog chapter in the 2020 Scrum Guides)
A Product Increment provides the highest level of transparency on “what is” from a product perspective.
Each Product Increment is additive to all prior increments and thoroughly integrated within the product. Multiple increments may be created within a Sprint, the sum of the increments is used at the Sprint Review thus supporting empiricism. However, a Product Increment may be delivered to customers prior to the end of the Sprint. Low technical quality of a Product Increment will lead to a low level of transparency and less effective learning.
(entire chapter based on the Increment chapter in the 2020 Scrum Guides)
Use the menu on the left to navigate the Simplified Scrum Guidance or move to the next chapter.