1. What are Scrum Artifacts?

   Scrum artifacts are essential tools in the Scrum framework that represent work or value to provide transparency and opportunities for inspection and adaptation. The primary Scrum artifacts are the Product Backlog, Sprint Backlog, and Increment. These artifacts are designed to maximize transparency of key information so that everybody has the same understanding of the artifact.

2. How Do They Contribute to the Process?

   • Product Backlog: This is an ordered list of everything that is known to be needed in the product. It is dynamic, constantly evolving to identify what the product needs to be most useful and competitive. It helps teams prioritize work and focus on delivering the most valuable features first.

   • Sprint Backlog: This includes the set of Product Backlog items selected for the Sprint, along with a plan for delivering the product Increment and realizing the Sprint Goal. It provides a real-time view of work in progress and helps the team manage their tasks during the sprint.

   • Increment: This is the sum of all the Product Backlog items completed during a Sprint and the value of the increments of all previous Sprints. It ensures that work done is always in a potentially releasable state.

Key Talking Points:

• Product Backlog: Ordered list of needed work items.
• Sprint Backlog: Selected items for the Sprint and their implementation plan.
• Increment: Completed work that is potentially shippable.
• Transparency: Artifacts ensure everyone has a clear view of progress and work.
• Adaptability: They allow for adjustments based on feedback and new information.

NOTES:

Reference Table:

• Product Backlog: Like your shopping list of ingredients, it includes everything you need to create your dish (product).
• Sprint Backlog: Like selecting the ingredients and following a step-by-step recipe for your meal (sprint).
• Increment: Like the finished dish, ready to serve to customers (potentially shippable product).

Follow-Up Questions and Answers:

1. How do you ensure that the Product Backlog is effectively managed?

   • Regular grooming and prioritization sessions with stakeholders and the team.
   • Ensuring clarity and understanding of each backlog item, often with the help of user stories and acceptance criteria.

2. What happens if the Sprint Backlog is not completed within a Sprint?

   • Unfinished items return to the Product Backlog for re-prioritization.
   • The team reflects on the reasons during the Sprint Retrospective to improve future sprints.

3. How do you handle changes in the Product Backlog during a Sprint?

   • Changes are typically discouraged during a Sprint to maintain focus.
   • Urgent changes may trigger re-planning or influence future sprints.

CHAPTER: Scrum Events