Execution & delivery · Delivery framework
Scrum
Help a small cross-functional team learn toward a valuable product goal through short, inspectable cycles.
- Plan
- Build
- Inspect
- Adapt
Start here · 5-minute visual lesson
A small team pursues one Product Goal by creating usable increments, inspecting evidence, and adapting in short fixed cycles.
Think of it like this: A repeated scientific loop for product delivery: make a useful slice, observe reality, change the plan.
- 1Choose a Sprint Goal
- 2Build a usable increment
- 3Inspect with stakeholders
- 4Improve the system
Work is sliced into ceremonies, handoffs, and status reports; nothing usable appears until many Sprints later.
One coherent Sprint Goal guides trade-offs and ends with a usable slice and an evidence-based next decision.
Learn by deciding
A Sprint is not a two-week project plan
A fraud team selects eight unrelated tickets. What is missing?
A Sprint Goal that explains why this set belongs together and what outcome the Increment enables.
The code is merged but cannot be used safely. Is it an Increment?
No. It must meet the Definition of Done and be usable in its intended environment.
Who adapts the daily plan?
The Developers doing the work—not a manager collecting status in the Daily Scrum.
01 · Understand
In plain English
Scrum is a lightweight framework of accountabilities, events, artifacts, and commitments grounded in transparency, inspection, and adaptation.
Origin and context
Ken Schwaber and Jeff Sutherland developed Scrum in the 1990s and maintain the Scrum Guide. The 2020 Guide describes a framework, not a complete engineering process.
The problem it solves
Complex product work cannot be fully predicted upfront. Scrum creates a cadence for producing a usable increment, inspecting evidence, and adapting the plan.
The concepts, explained
Learn the vocabulary first. Each concept changes a decision you will make when using the framework.
Scrum Team accountabilities
The Product Owner maximizes value, the Scrum Master improves Scrum effectiveness, and Developers create a usable Increment together.
Sprint and Product Goal
The Product Goal gives longer-term direction; each Sprint creates a short learning cycle with one coherent Sprint Goal.
Backlogs and Increment
The Product Backlog holds evolving options, the Sprint Backlog holds the current plan, and the Increment is the usable result.
Three commitments
Product Goal, Sprint Goal, and Definition of Done give each artifact a clear purpose and a standard for inspection.
Empiricism and Scrum values
Transparency makes the work visible, inspection tests reality, and adaptation changes the plan. The values shape how the team does this together.
02 · Deep dive
Go beyond the definition
Follow the reasoning inside Scrum, then challenge it before you use it.
1 of 4mental model
The mental model
What changes in the way you see the problem
Product Owner, Scrum Master, Developers
Use this concept to examine the problem from a distinct Scrum perspective.
Sprint and Product Goal
Use this concept to examine the problem from a distinct Scrum perspective.
Product Backlog / Sprint Backlog / Increment
Use this concept to examine the problem from a distinct Scrum perspective.
Commitments: Product Goal, Sprint Goal, Definition of Done
Use this concept to examine the problem from a distinct Scrum perspective.
Empiricism and Scrum values
Use this concept to examine the problem from a distinct Scrum perspective.
Reasoning trace
Watch each step earn the next one
A fraud-prevention team sets a Product Goal to cut false-positive card blocks. In a two-week Sprint it chooses a Sprint Goal: “let support safely release low-risk blocks.” It ships a narrow reviewed flow behind permissions, watches release accuracy and handle time, reviews evidence with support, and adapts thresholds next Sprint.
- 01Frame
Establish one Product Goal and an ordered Product Backlog.
Decision question: What decision will the next Increment make possible? - 02Interrogate
Form a small, cross-functional, self-managing Scrum Team.
Decision question: Which event has become theater rather than inspection? - 03Interrogate
In Sprint Planning, choose why, what, and how for the Sprint.
Decision question: What decision will the next Increment make possible? - 04Interrogate
Build a usable Increment while updating the plan daily.
Decision question: Which event has become theater rather than inspection? - 05Interrogate
Hold the Daily Scrum for Developers to adapt toward the Sprint Goal.
Decision question: What decision will the next Increment make possible? - 06Interrogate
Inspect the outcome with stakeholders in the Sprint Review.
Decision question: Which event has become theater rather than inspection? - 07Interrogate
Improve the team system in the Retrospective.
Decision question: What decision will the next Increment make possible? - 08Decide
Begin the next Sprint immediately; do not insert a mini-waterfall.
Decision question: Which event has become theater rather than inspection?
Failure-mode lab
Which mistake is most likely on your team?
Choose one to turn it into a control for your next workshop.
Context adaptation
The canonical version is only a starting point
Startups may use one product team with lightweight artifacts; enterprises should preserve team autonomy and avoid multiplying coordination layers. Scrumban may fit mixed planned and interrupt work.
Signals it fits
- Work is complex and benefits from frequent feedback
- A stable cross-functional team can own an outcome
- A usable increment can be inspected regularly
Signals to switch tools
- The work is a simple queue with no coherent Sprint Goal
- People are allocated fractionally across many teams
- Events are used as status control rather than adaptation
Now use the framework. The workbench below turns your own context into a first decision draft.
Work my problem03 · Apply
How to use Scrum
- 01
Establish one Product Goal and an ordered Product Backlog.
- 02
Form a small, cross-functional, self-managing Scrum Team.
- 03
In Sprint Planning, choose why, what, and how for the Sprint.
- 04
Build a usable Increment while updating the plan daily.
- 05
Hold the Daily Scrum for Developers to adapt toward the Sprint Goal.
- 06
Inspect the outcome with stakeholders in the Sprint Review.
- 07
Improve the team system in the Retrospective.
- 08
Begin the next Sprint immediately; do not insert a mini-waterfall.
04 · See it work
A worked example
A fraud-prevention team sets a Product Goal to cut false-positive card blocks. In a two-week Sprint it chooses a Sprint Goal: “let support safely release low-risk blocks.” It ships a narrow reviewed flow behind permissions, watches release accuracy and handle time, reviews evidence with support, and adapts thresholds next Sprint.
Business case study
Illustrative fictional scenario
A regulated fintech team uses Scrum with invented data and retains independent security review. The scenario shows that Scrum can host necessary controls; it does not make compliance disappear.
Across company types
Startups may use one product team with lightweight artifacts; enterprises should preserve team autonomy and avoid multiplying coordination layers. Scrumban may fit mixed planned and interrupt work.
05 · Work your problem
Turn the framework into a result
Explore the mechanics
Copy the working template
Product Goal: Sprint Goal: Selected outcomes / backlog items: Definition of Done: Daily risks: Increment evidence: Review learning: Retrospective improvement:
06 · Use judgment
Where it helps—and where it breaks
Use when
- Work is complex and benefits from frequent feedback
- A stable cross-functional team can own an outcome
- A usable increment can be inspected regularly
Do not use when
- The work is a simple queue with no coherent Sprint Goal
- People are allocated fractionally across many teams
- Events are used as status control rather than adaptation
Advantages
- Clear learning cadence
- Shared goal and transparency
- Makes process improvement routine
Limitations & criticisms
- Does not supply product discovery or technical practices
- Can become ceremony theater
- Sprint boundaries may not match interrupt-driven work
Common failure modes
- Calling the Daily Scrum a manager status meeting
- Using velocity as performance
- Shipping only at the end of many Sprints
Often confused with
Kanban optimizes flow through an explicit workflow and does not require Sprints; Scrum uses a bounded Sprint and defined accountabilities/events.
Practical checklist
Reflection questions
- What decision will the next Increment make possible?
- Which event has become theater rather than inspection?
07 · Check
Five-question knowledge check
Key takeaways
- Help a small cross-functional team learn toward a valuable product goal through short, inspectable cycles.
- Clear learning cadence
- Does not supply product discovery or technical practices
08 · Go deeper
Sources and further reading
- The Scrum GuideKen Schwaber and Jeff Sutherland · Scrum Guides · 2020
Scrum accountabilities, events, artifacts, commitments, and empiricism.
- What is Scrum?Scrum.org · Scrum.org
Complementary beginner explanation of Scrum teams, feedback loops, empiricism, and incremental value.