SkarpChapter 5 of 10
Scrum Events Part 1: Sprint, Sprint Planning, and Daily Scrum
Walk through the heartbeat of Scrum—from the overarching Sprint to the daily 15‑minute inspection—and uncover the exact timeboxes, participants, and goals that exam questions will probe.
Big Picture: Scrum Events and the Sprint Container
Scrum Events Overview
Scrum (Scrum Guide 2020, still current in 2026) defines five events: the Sprint (container), Sprint Planning, Daily Scrum, Sprint Review, and Sprint Retrospective.
Focus of This Module
Here we cover the heartbeat of Scrum: the Sprint, Sprint Planning, and Daily Scrum. These are heavily tested in certification exams.
Why Exams Love Events
Expect questions on each event's purpose, exact timebox, mandatory participants, and rules. Many items try to mix them up.
Key Idea: The Sprint Container
The Sprint is a fixed timebox (usually 1–4 weeks) that contains all other Scrum events and should produce a usable, valuable Increment.
The Sprint: Definition, Duration, and Rules
What Is a Sprint?
A Sprint is a fixed-length event of one month or less in which the Scrum Team creates a usable, valuable Increment.
How Long Is a Sprint?
Commonly 2 weeks, but any length up to 1 month is allowed. The team keeps the Sprint length consistent over time.
Core Sprint Rules
No changes that endanger the Sprint Goal, quality does not decrease, and scope may be clarified and renegotiated with the Product Owner.
Outcome of a Sprint
Every Sprint must produce at least one usable Increment that meets the Definition of Done, even if it is not released.
Sprint Cancellation: When and Who Decides
Who Can Cancel a Sprint?
Only the Product Owner can cancel a Sprint. Others may advise, but they cannot formally cancel it.
When to Cancel
A Sprint may be cancelled when the Sprint Goal becomes obsolete, for example due to strategy shifts or regulatory changes.
What Happens After Cancellation
Done work is reviewed, useful work may be released, and the Product Backlog is updated and reordered for future Sprints.
Common Exam Trap
You do not cancel a Sprint just because the team is behind or a stakeholder wants new features. Obsolete Sprint Goal is the key reason.
Example: A 2‑Week Sprint in Practice
Sprint Timeline Example
A team runs a 2‑week Sprint: Day 1 Sprint Planning, Daily Scrum every weekday, and Sprint Review plus Retrospective on the last day.
Sample Sprint Goal
Sprint Goal: Enable customers to view their last 10 transactions in the mobile app to quickly check recent spending.
Renegotiating Scope
Developers find advanced filtering too complex. They and the Product Owner postpone filters but keep the Sprint Goal unchanged.
Outcome and Lesson
Users can view 10 transactions, Definition of Done is met, and the Sprint Goal is achieved even though some items moved out.
Sprint Planning: Purpose, Timebox, Attendees
Purpose of Sprint Planning
Sprint Planning answers: Why is this Sprint valuable? What can be done? How will the work get done?
Timebox
For a 1‑month Sprint, Sprint Planning is timeboxed to 8 hours. Shorter Sprints usually have proportionally shorter planning.
Who Attends
The full Scrum Team attends: Product Owner, Scrum Master, and Developers. Stakeholders may be invited but are optional.
Outputs of Sprint Planning
Outputs: a Sprint Goal, selected Product Backlog items forming the Sprint Backlog, and a plan for how to deliver them.
Interactive: Draft a Sprint Goal
Interactive: Draft a Sprint Goal
You are the Product Owner for an online learning platform. The next Sprint is 2 weeks. The top Product Backlog items are:
- Add "bookmark lesson" feature
- Improve course search speed
- Add course ratings (1–5 stars)
- Fix bug: video playback stops at 10 minutes on mobile
Task:
- Write one clear Sprint Goal in your own words that could tie several of these items together.
- Check your goal against these criteria:
- It explains why the Sprint is valuable.
- It is focused (one main theme).
- It allows some flexibility in scope.
Example reflection (do not copy, just compare):
- A weak goal: "Finish all four items above." (Too detailed, no clear value.)
- A stronger goal might focus on improving the learner experience when watching and finding courses.
Write your Sprint Goal now, then adjust it to be shorter, clearer, and value-focused.
Daily Scrum: Purpose, Timebox, and Focus
Purpose of Daily Scrum
The Daily Scrum is a 15‑minute event for Developers to inspect progress toward the Sprint Goal and adapt their plan.
Timebox and Cadence
It is timeboxed to a maximum of 15 minutes, held every working day of the Sprint at the same time and place.
Who Participates
Developers must attend. The Scrum Master ensures the event happens but does not have to lead. The Product Owner is optional.
What Happens in Practice
Developers discuss progress, changes since yesterday, next steps, and obstacles. The exact format is flexible; the 3 questions are optional.
Daily Scrum Anti‑Patterns (What Not To Do)
Status Reporting Anti‑Pattern
Treating the Daily Scrum as a status report to the Scrum Master is wrong. It is for Developers to plan their own work.
Problem‑Solving Trap
Diving into deep problem‑solving during the Daily Scrum breaks the 15‑minute timebox. Issues should be handled afterwards.
Timebox and Cadence Violations
Letting the event exceed 15 minutes or skipping days undermines transparency and fast adaptation.
Partial Participation
If only some Developers speak, planning is incomplete. All Developers should contribute to the discussion.
Quiz: Sprint and Daily Scrum Essentials
Answer this exam‑style question to check your understanding of Sprint rules and Daily Scrum purpose.
During a 2‑week Sprint, a stakeholder asks to add a new high‑priority feature. It would endanger the Sprint Goal if added now. What is the BEST action according to Scrum?
- The Scrum Master cancels the Sprint so the team can start a new Sprint with the new feature.
- The Product Owner adds the feature to the Product Backlog and may include it in a future Sprint.
- The Developers immediately add the feature to the Sprint Backlog to keep the stakeholder happy.
- The Scrum Master extends the Sprint by one week to fit in the new feature.
Show Answer
Answer: B) The Product Owner adds the feature to the Product Backlog and may include it in a future Sprint.
The Sprint Goal should remain stable and not be endangered. New work that would threaten the Sprint Goal should go to the Product Backlog for future consideration. Only the Product Owner can cancel a Sprint, and extending the Sprint timebox is not allowed.
Quiz: Daily Scrum Anti‑Patterns
Check your understanding of the Daily Scrum's purpose and common mistakes.
Which statement BEST describes a proper Daily Scrum?
- Developers meet for 15 minutes each day to report status to the Scrum Master, who then updates management.
- Developers meet every other day for 30 minutes to solve technical problems in depth.
- Developers meet for up to 15 minutes every working day to inspect progress toward the Sprint Goal and adapt their plan.
- The Scrum Master and Product Owner meet daily to review progress and assign tasks to Developers.
Show Answer
Answer: C) Developers meet for up to 15 minutes every working day to inspect progress toward the Sprint Goal and adapt their plan.
The Daily Scrum is a 15‑minute event held every working day for Developers to inspect progress toward the Sprint Goal and adapt their plan. It is not a status report, not every‑other‑day, and not a management meeting.
Key Terms Review
Flip these cards (mentally) to reinforce the core concepts from this module.
- Sprint
- A fixed‑length event of one month or less that acts as a container for all other Scrum events and should produce at least one usable, valuable Increment.
- Sprint Goal
- The single objective for the Sprint that provides focus and flexibility in scope. Scope may change, but the Sprint Goal should remain stable.
- Sprint Planning
- Event at the start of the Sprint where the Scrum Team defines why the Sprint is valuable, what can be done, and how the work will be achieved, producing a Sprint Goal and Sprint Backlog.
- Sprint Cancellation
- An action that only the Product Owner can take, and only when the Sprint Goal becomes obsolete. Done work is reviewed; remaining items are re‑estimated and reordered.
- Daily Scrum
- A 15‑minute event held every working day for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
- Daily Scrum Anti‑Pattern
- Misuse of the Daily Scrum, such as treating it as a status report to the Scrum Master, exceeding the 15‑minute timebox, or turning it into a problem‑solving session.
Key Terms
- Sprint
- A fixed‑length event of one month or less that acts as a container for all other Scrum events and results in at least one usable, valuable Increment.
- Timebox
- A fixed maximum duration for an event. The event cannot be extended beyond this limit.
- Increment
- A concrete stepping stone toward the Product Goal that is usable and meets the Definition of Done.
- Developers
- Members of the Scrum Team committed to creating any aspect of a usable Increment during a Sprint.
- Daily Scrum
- A 15‑minute daily event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours.
- Sprint Goal
- A single objective for the Sprint that guides the work of the Scrum Team. Scope can change, but the Sprint Goal should stay intact.
- Scrum Master
- Scrum accountability responsible for establishing Scrum as defined in the Scrum Guide and helping everyone understand and apply Scrum theory and practice.
- Product Owner
- Scrum accountability responsible for maximizing the value of the product resulting from the work of the Scrum Team.
- Sprint Backlog
- The set of Product Backlog items selected for the Sprint, plus a plan for delivering them. Owned by the Developers.
- Sprint Planning
- Scrum event at the start of the Sprint where the Scrum Team plans the upcoming Sprint by defining the Sprint Goal, selecting Product Backlog items, and planning how to deliver them.
- Definition of Done
- A shared understanding of what it means for work to be complete, ensuring quality and transparency.