Examius

🇺🇸 Certified ScrumMaster (CSM) · subject

Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle Syllabus

The Scrum Events and the Sprint Cycle syllabus for Certified ScrumMaster (CSM) in full: 5 chapters, 16 topics and 32 sub-topics, every one listed below, plus 50 Scrum Events and the Sprint Cycle flashcards with answers.

5Chapters
16Topics
32Sub-topics
50Flashcards

Scrum Events and the Sprint Cycle syllabus: all 5 chapters

Expand any chapter to see its topics and sub-topics.

  1. The Sprint as a Container

     3 topics
    • Sprint Purpose and Length
      • Fixed-length cadence of one month or less
      • Consistency of Sprint duration
    • Sprint Rules and Constraints
      • No changes that endanger the Sprint Goal
      • Scope clarification and renegotiation
      • Quality does not decrease
    • Cancelling a Sprint
      • When a Sprint Goal becomes obsolete
      • Authority of the Product Owner to cancel

  2. Sprint Planning

     4 topics
    • Why Is This Sprint Valuable
      • Crafting the Sprint Goal
    • What Can Be Done This Sprint
      • Selecting Product Backlog items
      • Forecasting based on capacity and past performance
    • How Will the Work Get Done
      • Decomposing items into actionable work
      • Developers planning the how
    • Timebox and Attendees
      • Eight-hour maximum for a one-month Sprint

  3. Daily Scrum

     3 topics
    • Purpose of the Daily Scrum
      • Inspecting progress toward the Sprint Goal
      • Adapting the Sprint Backlog
    • Format and Timebox
      • Fifteen-minute timebox
      • Same time and place each day
      • Developers as primary participants
    • Common Anti-Patterns
      • Status report to the Scrum Master
      • Problem-solving overrunning the timebox

  4. Sprint Review

     3 topics
    • Inspecting the Increment
      • Demonstrating completed work
      • Collaborating with stakeholders
    • Adapting the Product Backlog
      • Discussing what to do next
      • Reviewing market and progress changes
    • Working Session Versus Presentation
      • Avoiding the demo-only trap

  5. Sprint Retrospective

     3 topics
    • Purpose of the Retrospective
      • Inspecting people, interactions, process, and tools
      • Identifying improvements
    • Creating Actionable Improvements
      • Selecting the most impactful changes
      • Adding improvements to the next Sprint Backlog
    • Retrospective Facilitation Techniques
      • Start-Stop-Continue
      • Sailboat and other structures
      • Creating psychological safety

Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle flashcards — 50 questions with answers

  1. What is the purpose of a Sprint in Scrum?

    A Sprint is a fixed-length event during which a usable, potentially releasable product Increment is created. It is the container for all other Scrum events and turns ideas into value.

  2. What is the maximum length of a Sprint?

    One month (four weeks) or less. Sprints are time-boxed to no more than one calendar month.

  3. Why are Sprints kept short (one month or less)?

    Short Sprints limit risk and cost to one calendar month, generate more frequent feedback and inspection points, and keep the cost of any single Sprint's failed effort low.

  4. In Scrum, when does a new Sprint start relative to the previous one?

    A new Sprint starts immediately after the conclusion of the previous Sprint; there is no gap between Sprints.

  5. Which rules/constraints must hold during a Sprint to ensure quality and predictability?

    No changes are made that endanger the Sprint Goal, quality does not decrease, the Product Backlog is refined as needed, and scope may be clarified and renegotiated with the Product Owner as more is learned.

  6. Can the Sprint Goal change during a Sprint?

    No. The Sprint Goal must not change during the Sprint, though the scope of work to achieve it may be clarified and renegotiated between the Developers and Product Owner.

  7. Who has the sole authority to cancel a Sprint?

    Only the Product Owner has the authority to cancel a Sprint, though they may do so under influence from stakeholders, Developers, or the Scrum Master.

  8. When should a Sprint be cancelled?

    A Sprint should be cancelled if the Sprint Goal becomes obsolete — for example, if the company changes direction or market/technology conditions change so the goal no longer makes sense.

  9. What happens to completed and incomplete Product Backlog items when a Sprint is cancelled?

    Completed and 'Done' items are reviewed; if part of the work is potentially releasable, the Product Owner typically accepts it. All incomplete items are re-estimated and put back on the Product Backlog.

  10. Why are Sprint cancellations described as rare and traumatic?

    Cancellations consume resources, disrupt the team, and are unusual because the short Sprint length already limits how often a goal can become obsolete mid-Sprint.

  11. What is Sprint Planning and what does it initiate?

    Sprint Planning is the event that initiates the Sprint by laying out the work to be performed; it is a collaboration of the entire Scrum Team that produces the Sprint Goal and the initial Sprint Backlog.

  12. What is the maximum time-box for Sprint Planning?

    Eight hours for a one-month Sprint, and usually shorter for shorter Sprints.

  13. Sprint Planning addresses which three topics?

    (1) Why is this Sprint valuable? (2) What can be done this Sprint? (3) How will the chosen work get done?

  14. In Sprint Planning, who proposes how the product could increase value and who crafts the Sprint Goal?

    The Product Owner proposes how the product could increase value/utility in the current Sprint; the whole Scrum Team then collaborates to define a Sprint Goal that communicates why the Sprint is valuable to stakeholders.

  15. What is the Sprint Goal?

    The single objective for the Sprint. It provides a coherent purpose, creates focus and flexibility around the work, and is the commitment associated with the Sprint Backlog.

  16. In the 'What can be done this Sprint?' topic, who selects the items for the Sprint Backlog?

    The Developers select the items from the Product Backlog to include in the current Sprint, collaborating with the Product Owner to refine and clarify them.

  17. What helps Developers gauge how much work they can complete in a Sprint?

    Their past performance (velocity/history), their upcoming capacity for this Sprint, and their Definition of Done. The more they know, the more confident they are in their forecast.

  18. In the 'How will the work get done?' topic, what do Developers do for each selected item?

    For each selected Product Backlog item, the Developers plan the work needed to create an Increment that meets the Definition of Done, often by decomposing items into smaller work items of one day or less.

  19. What three things make up 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).

  20. What is the purpose of the Daily Scrum?

    To inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. It improves communication, identifies impediments, and promotes quick decision-making.

Show the other 30 Scrum Events and the Sprint Cycle flashcards

  1. What is the time-box for the Daily Scrum?

    15 minutes, regardless of Sprint length.

  2. Who is required to attend and participate in the Daily Scrum?

    The Developers of the Scrum Team. If the Product Owner or Scrum Master are actively working on Sprint Backlog items, they participate as Developers.

  3. Does the Daily Scrum have to be held at the same time and place each day? Why?

    Yes. Holding it at the same time and place every working day reduces complexity and decision overhead about when and where to meet.

  4. Are the 'three questions' (what I did, what I'll do, blockers) mandated by the Scrum Guide for the Daily Scrum?

    No. The three-question format is one optional technique. Developers may use any structure or technique as long as the Daily Scrum focuses on progress toward the Sprint Goal and produces an actionable plan for the next day.

  5. Name a common Daily Scrum anti-pattern related to the Scrum Master.

    The Scrum Master running the meeting or having Developers report status to them, turning it into a status meeting for the Scrum Master rather than a planning session by and for the Developers.

  6. Why is the Daily Scrum not meant to be the only time Developers adjust their plan?

    Developers often meet throughout the day for more detailed discussions about adapting or re-planning the Sprint's work; the Daily Scrum is a key inspect-and-adapt point but not the only opportunity to do so.

  7. Give an example of a Daily Scrum anti-pattern involving problem-solving.

    Diving into deep technical problem-solving or detailed design discussions during the 15 minutes, which derails the meeting; such discussions should be taken offline immediately after.

  8. What is the purpose of the Sprint Review?

    To inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents results to stakeholders and discusses progress toward the Product Goal.

  9. What is the time-box for the Sprint Review?

    A maximum of four hours for a one-month Sprint, and typically shorter for shorter Sprints.

  10. During the Sprint Review, what is inspected and what is adapted?

    The Increment is inspected (along with progress toward the Product Goal), and the Product Backlog is adapted/adjusted based on feedback and changed conditions.

  11. Why is the Sprint Review described as a working session rather than a presentation?

    The Sprint Review is a collaborative working session where the Scrum Team and stakeholders review what was accomplished and what has changed, then collaborate on what to do next — not merely a one-way status or demo presentation.

  12. What is a risk of treating the Sprint Review only as a demo/presentation?

    It becomes one-way reporting, loses stakeholder collaboration and feedback, and fails to produce meaningful adaptation of the Product Backlog — defeating the inspect-and-adapt purpose.

  13. Who attends the Sprint Review?

    The Scrum Team and key stakeholders invited by the Product Owner collaborate on what was done and what to do next.

  14. What is the purpose of the Sprint Retrospective?

    To plan ways to increase quality and effectiveness. The Scrum Team inspects how the last Sprint went regarding individuals, interactions, processes, tools, and Definition of Done.

  15. What is the time-box for the Sprint Retrospective?

    A maximum of three hours for a one-month Sprint, and usually shorter for shorter Sprints.

  16. When does the Sprint Retrospective occur in the Sprint?

    It is the last event of the Sprint, held after the Sprint Review and before the end of the Sprint (before the next Sprint Planning).

  17. What does the Scrum Team inspect during the Retrospective?

    How the last Sprint went with regard to individuals, interactions, processes, tools, and their Definition of Done — identifying what went well, what problems were encountered, and how they were (or were not) solved.

  18. What is the key output of a Sprint Retrospective?

    The most impactful improvements identified, which the team commits to. These actionable improvements may be added to the next Sprint's Sprint Backlog to ensure they get addressed.

  19. Why should retrospective improvements be made actionable rather than vague?

    Vague intentions rarely get done. Concrete, assignable, and ideally measurable improvement actions — sometimes added to the next Sprint Backlog — increase the chance they are actually implemented and lead to real change.

  20. Name two common Sprint Retrospective facilitation techniques.

    Examples include 'Start, Stop, Continue,' the '4 Ls' (Liked, Learned, Lacked, Longed For), 'Mad/Sad/Glad,' the Sailboat exercise, and timeline/dot-voting to prioritize improvements.

  21. What is the Scrum Master's role in facilitating the Retrospective?

    To create a safe, blameless environment, encourage open and honest participation, vary techniques to keep it fresh, and ensure the team leaves with concrete improvement actions.

  22. List the five Scrum events.

    The Sprint (the container), Sprint Planning, the Daily Scrum, the Sprint Review, and the Sprint Retrospective.

  23. Compare the Sprint Review and the Sprint Retrospective in focus.

    The Sprint Review focuses on the product/Increment and Product Backlog with stakeholders (what was built). The Retrospective focuses on the team's process — people, interactions, tools, and Definition of Done (how they worked).

  24. Why is the Sprint considered the 'container' event?

    Because Sprint Planning, the Daily Scrums, the Sprint Review, and the Sprint Retrospective all occur within the Sprint; the Sprint encloses all other events and a new one begins immediately after each ends.

  25. What is the relationship between the Sprint Goal and the Sprint Backlog commitment?

    The Sprint Goal is the commitment for the Sprint Backlog. It gives the Developers flexibility in the exact work while keeping a single, coherent objective to focus on.

  26. What is the maximum time-box for each Scrum event in a one-month Sprint?

    Sprint Planning: 8 hours; Daily Scrum: 15 minutes; Sprint Review: 4 hours; Sprint Retrospective: 3 hours. Shorter Sprints generally use shorter time-boxes (except the Daily Scrum, always 15 min).

  27. Why does shortening the Daily Scrum to a strict 15 minutes matter?

    The fixed 15-minute time-box keeps it focused and efficient as a quick re-planning checkpoint, preventing it from sprawling into a status or problem-solving meeting.

  28. During Sprint Planning, what is the role of the Definition of Done?

    It informs the Developers' planning by clarifying what 'complete' means, so they can decompose work and forecast how much can be brought to a Done Increment within the Sprint.

  29. How does the Daily Scrum support adapting the Sprint Backlog?

    By inspecting progress toward the Sprint Goal daily, Developers identify whether they are on track and adjust the Sprint Backlog and next day's plan to remove impediments and stay aligned with the goal.

  30. In the Sprint Review, why is adapting the Product Backlog a collaborative activity?

    Because stakeholders provide feedback on the Increment and share changes in the market, budget, or priorities, the Scrum Team and stakeholders jointly adjust the Product Backlog to define the most valuable next work.

Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle FAQ

What is in the Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle syllabus?

Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle is split into 5 chapters: The Sprint as a Container, Sprint Planning, Daily Scrum, Sprint Review and Sprint Retrospective. Together they contain 16 topics and 32 sub-topics.

How many chapters are in Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle?

5 chapters, containing 16 topics and 32 sub-topics. The largest chapter is Sprint Planning, with 4 topics.

Are there flashcards for Certified ScrumMaster (CSM) Scrum Events and the Sprint Cycle?

Yes — a 50-card Scrum Events and the Sprint Cycle deck, printed in full in the flashcards section of this page and available in the Examius app with spaced repetition. The free plan covers one exam of your choice, including its flashcards; Examius Pro, a one-time purchase, unlocks every other exam and deck.