Certified ScrumMaster (CSM) Scrum Artifacts and Transparency Syllabus

Scrum Artifacts and Transparency syllabus — full chapter and topic list

Expand any chapter to see its topics and sub-topics. This is the whole examinable outline for Scrum Artifacts and Transparency in Certified ScrumMaster (CSM), not a summary of it.

1. 1

   Product Backlog

   4 topics

   • Nature of the Product Backlog
     • Single source of work for the team
     • Emergent and ordered list
   • Product Backlog Refinement
     • Adding detail, estimates, and order
     • Ongoing collaborative activity
   • Commitment: The Product Goal
     • Long-term objective for the team
     • Relationship to the Product Backlog
   • Writing Effective Backlog Items
     • User stories and the INVEST criteria
     • Acceptance criteria
2. 2

   Sprint Backlog

   3 topics

   • Composition of the Sprint Backlog
     • Sprint Goal, selected items, and plan
     • Highly visible real-time picture
   • Commitment: The Sprint Goal
     • Single objective for the Sprint
     • Providing coherence and flexibility
   • Owned by the Developers
     • Updating the Sprint Backlog throughout the Sprint
3. 3

   Increment

   3 topics

   • Definition of an Increment
     • Concrete stepping stone toward the Product Goal
     • Additive to prior Increments
   • Commitment: The Definition of Done
     • Quality measures for the Increment
     • Shared understanding of complete
     • Organizational versus team-defined standards
   • Multiple Increments in a Sprint
     • Delivering value before the Sprint ends
4. 4

   Transparency and Artifact Integrity

   3 topics

   • Importance of Transparency
     • Decisions based on perceived artifact state
     • Risks of low transparency
   • Reducing Incomplete Transparency
     • Scrum Master's role in fostering transparency
     • Making work visible with information radiators
   • Artifacts and the Empirical Pillars
     • How each artifact enables inspection
     • Commitments reinforcing transparency

Scrum Artifacts and Transparency flashcards for Certified ScrumMaster (CSM)

18 of 50 cards from the Scrum Artifacts and Transparency deck — real questions with worked answers.

1. What is the Product Backlog in Scrum?

   An emergent, ordered list of everything that is known to be needed to improve the product. It is the single source of work undertaken by the Scrum Team.

2. Who is accountable for the Product Backlog?

   The Product Owner is accountable for the Product Backlog, including its content, availability, and ordering.

3. Why is the Product Backlog described as 'emergent' and 'never complete'?

   Because it constantly changes to reflect new knowledge, market conditions, and product evolution; it is dynamic and continuously refined rather than fully defined up front.

4. What is Product Backlog Refinement?

   The ongoing act of breaking down and further defining Product Backlog items into smaller, more precise items, and adding details such as description, order, and size.

5. Who performs Product Backlog refinement?

   It is a collaborative effort: the Developers do the sizing/breakdown work, while the Product Owner may influence by helping understand and select trade-offs. There is no separate refinement event.

6. Roughly how much of a Sprint's time is typically spent on refinement?

   As a guideline, refinement usually consumes no more than about 10% of the Developers' capacity, though Scrum prescribes no fixed amount.

7. Which Scrum artifact contains the commitment 'Product Goal'?

   The Product Backlog contains the Product Goal as its commitment.

8. What is the Product Goal?

   A future state of the product that serves as a long-term objective for the Scrum Team; it describes the 'why' and target the team plans toward.

9. How does the Product Goal relate to the Product Backlog?

   The Product Goal is the target the team plans against; the Product Backlog emerges to define 'what' will fulfill the Product Goal. The Product Goal is in the Product Backlog.

10. Can a Scrum Team work toward more than one Product Goal at a time?

    No. A Scrum Team must fulfill (or abandon) one Product Goal before taking on the next.

11. What attributes do Product Backlog items often include?

    A description, order (priority), size (estimate), and value. Sometimes a 'test' or acceptance criteria as well.

12. What is a common format for writing backlog items as user stories?

    As a [role/user], I want [goal/feature], so that [benefit/reason].

13. What does the INVEST acronym describe for effective backlog items?

    Independent, Negotiable, Valuable, Estimable, Small, and Testable — qualities of a well-formed Product Backlog item / user story.

14. Why should backlog items near the top of the Product Backlog be smaller and clearer than lower ones?

    Higher-ordered items are worked on sooner, so they must be refined enough ('ready') to be selected and completed within a Sprint; lower items can remain larger and vaguer.

15. What does it mean for a backlog item to be 'Ready'?

    It is refined to the point that the Developers consider it clear and small enough to reasonably be 'Done' within one Sprint (Definition of Ready is optional and team-defined).

16. What is the Sprint Backlog?

    The set of Product Backlog items selected for the Sprint (what), plus a plan for delivering the Increment (how), and the Sprint Goal (why).

17. What are the three components of the Sprint Backlog?

    The Sprint Goal (why), the set of Product Backlog items selected for the Sprint (what), and an actionable plan for delivering the Increment (how).

18. Who owns the Sprint Backlog?

    The Developers own the Sprint Backlog. It is created by and for the Developers.

See more Scrum Artifacts and Transparency flashcards →

Planning Scrum Artifacts and Transparency for Certified ScrumMaster (CSM)

Scrum Artifacts and Transparency (Certified ScrumMaster (CSM)) FAQ