Artifacts
-
Product Backlog
- What is the Product Backlog in Scrum?
- Who is responsible for managing the Product Backlog?
- What are Product Backlog items (PBIs)?
- Why must the Product Backlog be transparent?
- How do Scrum Teams capture and document Product Backlog items?
- What are the challenges of having a long Product Backlog?
- What tools can be used to manage a Product Backlog?
- Why might a digital tool be preferred for managing a Product Backlog?
- How does the Product Backlog contribute to planning and roadmaps?
- What is a good practice for maintaining an effective Product Backlog?
- What are Product Backlog items (PBIs) and why are their attributes important?
- Why is it suggested to aim for a consistent approach when gathering PBI attributes?
- What are some common attributes of PBIs and their purposes?
- Why is it important to balance the number of attributes set for PBIs?
- How do PBI attributes aid in planning and collaboration during a Sprint?
- What is Product Backlog ordering in Scrum, and why is it important?
- What factors influence the ordering of Product Backlog items?
- What techniques can be used to order a Product Backlog?
- How does the RICE Scoring Model help in prioritising Product Backlog items?
- Why is Product Backlog ordering considered a continuous process?
- What is decomposition in the context of managing a Product Backlog in Scrum?
- What are themes in a Product Backlog, and how do they function?
- How do epics fit into the hierarchy of decomposition in a Product Backlog?
- What role do features play in the decomposition of a Product Backlog?
- How should tasks be approached in the context of Sprint Planning?
- What is the importance of slicing Product Backlog items (PBIs) in Scrum?
- How does vertical slicing benefit the development process in Scrum?
- What is the role of risk-based slicing in managing PBIs?
- How can value-based slicing enhance the delivery of a product?
- Why is it important to consider dependencies between PBIs in Scrum?
-
Sprint Backlog
- What is the Sprint Backlog in Scrum?
- How is the Sprint Backlog created and maintained?
- What does the Sprint Backlog make visible?
- How do the Developers handle new work during a Sprint?
- Who is accountable for changes to the Sprint Backlog during a Sprint?
- What happens if all the work in the Sprint Backlog is completed before the end of the Sprint?
- How does the Sprint Backlog contribute to the transparency of the Sprint?
- What role does flexibility play in the Sprint Backlog?
- How does the Sprint Backlog support short-term planning?
- Why is the Sprint Backlog considered a real-time picture of the Sprint’s work?
-
Increment
- What is the Increment in Scrum?
- When must the Increment be Done?
- What is included in the Definition of Done?
- What happens to incomplete Product Backlog items at the end of a Sprint?
- How does the Scrum Team use the Increment during the Sprint Review?
- Why is reaching Done earlier and more often beneficial?
- How does the Increment support empiricism in Scrum?
- What is the significance of the Increment for stakeholders?
- How does the Increment reflect the Scrum Team’s past work?
- What role does testing play in the Definition of Done?