Picture a college fest team with six weeks to go. If they make one giant plan and meet again on fest day, chaos is guaranteed. A smart team does something else: they fix a goal for the week ("sponsors confirmed and stage booked"), meet for fifteen minutes every evening to sync up, show the faculty coordinator what is actually done at the end of the week, discuss what went badly, and then plan the next week with what they learned.
That rhythm of short goal, daily sync, show real results, reflect, repeat is essentially Scrum, the most widely used way of putting the ideas from Agile Methodology into practice.
Scrum is a lightweight framework that helps people, teams and organizations generate value through adaptive solutions for complex problems. Work is done in fixed-length iterations called Sprints, by a small Scrum Team consisting of a Product Owner, a Scrum Master and Developers, using a defined set of events and artifacts.
Scrum was created by Ken Schwaber and Jeff Sutherland, who first presented it in 1995. Its official definition is The Scrum Guide, a short document they maintain. Everything in this chapter follows the 2020 Scrum Guide, which is still the current official version as of late 2026. (In 2025 a separately authored "Scrum Guide Expansion Pack" was published as an optional companion; it does not replace the 2020 Guide.)
One important idea before we start: Scrum is deliberately incomplete. It defines the minimum structure (who, which meetings, which artifacts) and leaves the actual techniques (how to write requirements, how to estimate, how to test) to the team.
Scrum at a Glance
The whole framework fits in one table. Learn it by heart; almost every Scrum question is answered from it.
Category | Items |
|---|---|
Theory | Empiricism and lean thinking |
3 pillars | Transparency, Inspection, Adaptation |
5 values | Commitment, Focus, Openness, Respect, Courage |
3 accountabilities | Product Owner, Scrum Master, Developers |
5 events | The Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective |
3 artifacts (each with a commitment) | Product Backlog (Product Goal), Sprint Backlog (Sprint Goal), Increment (Definition of Done) |
Product Backlog Sprint Planning Sprint (1 month or less)
(ordered list, ---> Why? What? How? ---> +---------------------------+
Product Goal) produces Sprint | Daily Scrum, 15 min, |
^ Backlog + Sprint Goal | every working day |
| | Developers build the |
| refinement (ongoing) | Increment (meets DoD) |
| +---------------------------+
| |
| v
+---------- adaptations --------- Sprint Review <-- Increment(s)
|
v
Sprint Retrospective
|
v
next Sprint starts immediatelyScrum Theory: Empiricism and Lean Thinking
Empiricism means knowledge comes from experience and decisions are based on what is observed, not on predictions made months earlier. Lean thinking means reducing waste and focusing on essentials. Scrum applies both with an iterative, incremental approach.
Empiricism rests on three pillars:
Transparency: the work and the process must be visible to those doing the work and those receiving it. You cannot inspect what you cannot see. The artifacts are the main tool of transparency.
Inspection: the artifacts and progress toward goals must be inspected frequently and diligently to detect problems. Each event is an inspection point.
Adaptation: if anything has drifted outside acceptable limits, the process or product must be adjusted as soon as possible.
The three depend on each other: inspection without transparency is misleading, and inspection without adaptation is pointless.
The Five Values
Value | In a Scrum Team, this looks like... |
|---|---|
Commitment | Committing to achieving the team's goals and to supporting each other. |
Focus | Concentrating on the work of the Sprint to make the best progress toward the goals. |
Openness | Being open about the work and the challenges, including bad news. |
Respect | Respecting each other as capable, independent people. |
Courage | Having the courage to do the right thing and to work on tough problems. |
The Scrum Team
The fundamental unit of Scrum is a small team: one Scrum Master, one Product Owner, and Developers. Key properties from the Guide:
No sub-teams and no hierarchies. It is one cohesive unit focused on one objective at a time: the Product Goal.
Cross-functional: the members together have all the skills needed to create value each Sprint.
Self-managing: they decide internally who does what, when and how.
Small: typically 10 or fewer people. Larger teams communicate less well. If a team becomes too large, it should reorganize into multiple Scrum Teams focused on the same product, sharing the same Product Goal, Product Backlog and Product Owner.
The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint.
Note the word accountabilities. The 2020 Guide deliberately avoids calling these "roles" or "job titles". A person is accountable for something; a job title is an HR matter.
Developers
"Developers" means anyone in the Scrum Team who creates any part of the usable Increment each Sprint: programmers, testers, designers, analysts and so on. Developers are accountable for:
Creating a plan for the Sprint, the Sprint Backlog.
Instilling quality by adhering to the Definition of Done.
Adapting their plan each day toward the Sprint Goal.
Holding each other accountable as professionals.
Product Owner
The Product Owner is accountable for maximizing the value of the product resulting from the team's work, and for effective Product Backlog management, which includes:
Developing and explicitly communicating the Product Goal.
Creating and clearly communicating Product Backlog items.
Ordering Product Backlog items.
Ensuring the Product Backlog is transparent, visible and understood.
The Product Owner is one person, not a committee. They may delegate some of this work to others, but they remain accountable. Their decisions are visible in the content and order of the Product Backlog, and the organization must respect those decisions. Anyone wanting to change the Product Backlog does so by convincing the Product Owner.
Scrum Master
The Scrum Master is accountable for establishing Scrum as defined in the Scrum Guide and for the Scrum Team's effectiveness. The Guide describes Scrum Masters as true leaders who serve the Scrum Team and the larger organization. They serve:
The Scrum Team: coaching self-management and cross-functionality, helping focus on high-value Increments that meet the Definition of Done, causing the removal of impediments, and ensuring all events take place, are positive and productive, and stay within their timebox.
The Product Owner: helping find techniques for defining the Product Goal and managing the Product Backlog, helping establish empirical product planning, and facilitating stakeholder collaboration.
The organization: leading, training and coaching the organization in its Scrum adoption, and removing barriers between stakeholders and Scrum Teams.
A Scrum Master is not a project manager. They do not assign tasks or command the team. The Developers decide how to do the work.
Question | Product Owner | Scrum Master | Developers |
|---|---|---|---|
Accountable for | Maximizing product value | Team's effectiveness; Scrum as defined | Creating the usable Increment |
Owns | Product Backlog (and Product Goal) | (no artifact) | Sprint Backlog |
Decides | What is most valuable and its order | How to help the team use Scrum well | How to turn backlog items into an Increment; how much work to select |
The Five Scrum Events
Each event is a formal opportunity to inspect and adapt. Events are held at the same time and place where possible to reduce complexity. Each has a maximum duration, a timebox.
Event | Timebox (for a one-month Sprint) | Purpose | Attendees |
|---|---|---|---|
Sprint | Fixed length, one month or less | Container for all other events; turns ideas into value | Scrum Team |
Sprint Planning | Maximum 8 hours | Lay out the work for the Sprint | Scrum Team (may invite others for advice) |
Daily Scrum | 15 minutes (every working day, same for any Sprint length) | Inspect progress toward the Sprint Goal; adapt the Sprint Backlog | Developers |
Sprint Review | Maximum 4 hours | Inspect the outcome and decide future adaptations | Scrum Team and key stakeholders |
Sprint Retrospective | Maximum 3 hours | Plan ways to increase quality and effectiveness | Scrum Team |
For shorter Sprints, Sprint Planning, Review and Retrospective are usually shorter. The Guide does not give a formula; many teams simply scale them (for example, about 4 hours of planning for a two-week Sprint), but that is a common practice, not a rule.
1. The Sprint
Sprints are the heartbeat of Scrum. A new Sprint starts immediately after the previous one ends. All the work, including Sprint Planning, Daily Scrums, the Review and the Retrospective, happens inside Sprints. During a Sprint:
No changes are made that would endanger the Sprint Goal.
Quality does not decrease.
The Product Backlog is refined as needed.
Scope may be clarified and renegotiated with the Product Owner as more is learned.
Why at most one month? Longer Sprints let the Sprint Goal become invalid, increase complexity and increase risk. Short Sprints limit risk of cost and effort to a small time frame.
Cancelling a Sprint: a Sprint can be cancelled if the Sprint Goal becomes obsolete, and only the Product Owner has the authority to cancel it.
2. Sprint Planning
It answers three topics:
Why is this Sprint valuable? The Product Owner proposes how the product could increase its value; the whole Scrum Team then defines a Sprint Goal. The Sprint Goal must be finalized before the end of Sprint Planning.
What can be done this Sprint? The Developers, through discussion with the Product Owner, select items from the Product Backlog. Their past performance, upcoming capacity and Definition of Done help them forecast how much they can do.
How will the chosen work get done? The Developers plan the work, often by decomposing items into smaller work items of one day or less. How this is done is decided solely by the Developers.
Sprint Goal + selected items + delivery plan = the Sprint Backlog.
3. Daily Scrum
A 15-minute event for the Developers to inspect progress toward the Sprint Goal and adapt the Sprint Backlog, at the same time and place every working day. The Developers can choose any structure and techniques. If the Product Owner or Scrum Master are actively working on items in the Sprint Backlog, they participate as Developers.
Note: the 2017 Guide suggested three questions (What did I do yesterday? What will I do today? Any impediments?). The 2020 Guide removed them. Many teams still use them, but they are not required.
The Daily Scrum is not the only time Developers may talk. They often meet throughout the day for detailed discussions and re-planning.
4. Sprint Review
The Scrum Team presents the results of its work to key stakeholders, and progress toward the Product Goal is discussed. Together they review what changed in the environment and decide what to do next; the Product Backlog may be adjusted. The Guide stresses that it is a working session, and the team should avoid limiting it to a presentation.
5. Sprint Retrospective
The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools and the Definition of Done. They discuss what went well, what problems occurred and how they were (or were not) solved, and identify the most helpful changes to improve effectiveness. The most impactful improvements are addressed as soon as possible and may even be added to the next Sprint Backlog. The Retrospective concludes the Sprint.
Product Backlog Refinement (not an event)
Refinement is the act of breaking down and further defining Product Backlog items into smaller, more precise items: adding descriptions, order and size. It is an ongoing activity, not one of the five events. The Developers who will be doing the work are responsible for sizing; the Product Owner may influence them by helping them understand and select trade-offs.
The Three Artifacts and Their Commitments
Artifacts represent work or value and are designed to maximize transparency. Each artifact has a commitment that gives a clear target to measure progress against.
Artifact | What it is | Commitment | Who is accountable |
|---|---|---|---|
Product Backlog | An emergent, ordered list of what is needed to improve the product; the single source of work for the Scrum Team | Product Goal: the long-term objective; the team must fulfil (or abandon) one goal before taking on the next | Product Owner |
Sprint Backlog | Sprint Goal (why) + selected Product Backlog items (what) + an actionable plan for delivering the Increment (how); a plan by and for the Developers, updated throughout the Sprint | Sprint Goal: the single objective for the Sprint; gives flexibility on the exact work needed to achieve it | Developers |
Increment | A concrete stepping stone toward the Product Goal; additive to all prior Increments, verified, and usable | Definition of Done: a formal description of the state of the Increment when it meets the required quality measures | Developers (whole team for value) |
The Definition of Done (DoD)
The moment a Product Backlog item meets the Definition of Done, an Increment is born. Important rules:
Work that does not meet the DoD cannot be released or even presented at the Sprint Review. It returns to the Product Backlog for future consideration.
If the organization has a standard DoD, all Scrum Teams must follow it as a minimum; otherwise the Scrum Team creates one appropriate for the product.
Multiple Increments may be created within a Sprint, and an Increment may be delivered to stakeholders before the Sprint ends. The Sprint Review should never be considered a gate to releasing value.
An example DoD for a web team might be: code reviewed by one peer; unit tests written and passing; integrated into the main branch with the build green; acceptance criteria verified; no new critical security warnings; deployed to the staging environment.
Worked Example: One Two-Week Sprint
A team building a college placement portal has 5 Developers. Sprint length: 2 weeks (10 working days).
Step 1: Estimate capacity (a common practice, not part of the Guide)
The team assumes about 1 day of the Sprint goes to Planning, Review, Retrospective and refinement, leaving 9 days. Each Developer has about 6 focused hours a day. One Developer is on leave for 2 days.
Capacity = 5 developers × 9 days × 6 hours − (2 days × 6 hours of leave)
= 270 − 12
= 258 hoursStep 2: Sprint Planning
Why: the Product Owner explains that placement season opens next month and students cannot yet apply. Sprint Goal: "A student can upload a resume and apply to a company drive."
What: the Developers pick the top items (resume upload, list of open drives, apply button, confirmation email), forecasting 30 story points, which is in line with their recent Sprints and fits the 258-hour capacity once broken into tasks.
How: the items are split into tasks (database table for applications, upload API, file-size validation, UI form, tests...), most of a day or less.
Step 3: Daily Scrums and a burndown
Many teams track remaining work with a burndown chart. (The Guide does not require burndowns, story points or velocity; they are optional practices.) Here is a simple script that prints a burndown table for this Sprint and flags days when the team is behind the ideal line.
# Sprint burndown: remaining story points at the end of each day
committed = 30
done_per_day = [0, 3, 5, 0, 8, 2, 5, 3, 4, 0] # 10-day Sprint
remaining = committed
ideal_step = committed / len(done_per_day)
print("Day Ideal Actual")
print(f"{0:>3} {committed:>5.1f} {remaining:>6}")
for day, done in enumerate(done_per_day, start=1):
remaining -= done
ideal = committed - ideal_step * day
flag = " <- behind" if remaining > ideal else ""
print(f"{day:>3} {ideal:>5.1f} {remaining:>6}{flag}")
print("Sum done:", sum(done_per_day))Output:
Day Ideal Actual
0 30.0 30
1 27.0 30 <- behind
2 24.0 27 <- behind
3 21.0 22 <- behind
4 18.0 22 <- behind
5 15.0 14
6 12.0 12
7 9.0 7
8 6.0 4
9 3.0 0
10 0.0 0
Sum done: 30What the Daily Scrums would have seen: on Day 4 the remaining work did not move (22 → 22) because the upload API was blocked by a storage permission issue. The Scrum Master helped get the impediment removed, and on Day 5 the team completed 8 points, crossing below the ideal line. By Day 9 all 30 points met the Definition of Done. The last line, Sum done: 30, confirms that the daily numbers add up to the commitment.
Step 4: Review and Retrospective
Sprint Review: the placement officer tries the feature live and asks for a "withdraw application" option. The Product Owner adds it to the Product Backlog and moves it near the top.
Sprint Retrospective: the team notices the Day 4 blockage came from late access requests. Improvement for next Sprint: request environment access during refinement, before the Sprint starts.
What Changed in the 2020 Guide
Before (2017 Guide) | 2020 Guide |
|---|---|
"Development Team" inside the Scrum Team | "Developers"; one Scrum Team with no sub-team |
Roles | Accountabilities |
Self-organizing | Self-managing |
No Product Goal | Product Goal introduced as the Product Backlog's commitment |
Two Sprint Planning topics (what, how) | Three topics (why, what, how) |
Three suggested Daily Scrum questions | Removed; Developers choose the structure |
Scrum Master as "servant-leader" | "True leaders who serve" |
Team size 3–9 Developers | Whole Scrum Team typically 10 or fewer |
More software-specific wording | Less prescriptive, less IT-specific language |
What Scrum Does NOT Prescribe
These are popular, but they are not part of the Scrum Guide. Exams and interviews love this trap.
User stories (any format of Product Backlog item is allowed).
Story points, planning poker, velocity.
Burndown or burnup charts.
The three Daily Scrum questions (removed in 2020).
A "Sprint 0" or "hardening Sprint".
Specific engineering practices such as pair programming or test-driven development (those come from XP; see Kanban & Extreme Programming).
Scrum vs Waterfall
Aspect | Waterfall | Scrum |
|---|---|---|
Planning | Once, in detail, at the start | Every Sprint (and refined continuously) |
Delivery | At the end | At least one usable Increment every Sprint |
Change during development | Controlled, costly | Welcomed through the Product Backlog; Sprint Goal protected within a Sprint |
Who decides priorities | Fixed in the requirements document | The Product Owner, by ordering the Product Backlog |
Who decides how work is done | Project manager plans and assigns | Self-managing Developers |
Process improvement | Post-project lessons learned | Every Sprint, in the Retrospective |
Common Mistakes
Calling the Scrum Master the team's manager or project manager. The Scrum Master coaches and removes impediments; the Developers manage their own work.
Saying the Scrum Master can cancel a Sprint. Only the Product Owner can.
Counting refinement as an event. There are exactly five events; refinement is an ongoing activity.
Thinking Sprint Planning, Review and Retrospective happen "between" Sprints. They happen inside the Sprint; the next Sprint starts immediately after the previous one ends.
Presenting unfinished work at the Sprint Review. Work not meeting the Definition of Done is not part of the Increment and goes back to the Product Backlog.
Having a committee of Product Owners. The Product Owner is one person.
Using the Daily Scrum as a status report to a manager. It is for the Developers to plan their next 24 hours toward the Sprint Goal.
Treating the Sprint Review as a release gate. Increments can be released whenever they are done, even mid-Sprint.
GATE and Interview Questions
Name the three accountabilities, five events and three artifacts of Scrum.
Accountabilities: Product Owner, Scrum Master, Developers. Events: the Sprint, Sprint Planning, Daily Scrum, Sprint Review, Sprint Retrospective. Artifacts: Product Backlog, Sprint Backlog, Increment.
What are the commitments attached to each Scrum artifact?
Product Backlog → Product Goal; Sprint Backlog → Sprint Goal; Increment → Definition of Done.
What is the maximum length of a Sprint, and what is the timebox of the Daily Scrum?
A Sprint is one month or less. The Daily Scrum is 15 minutes, regardless of Sprint length.
Who owns the Sprint Backlog and who orders the Product Backlog?
The Developers own the Sprint Backlog (it is their plan). The Product Owner is accountable for ordering the Product Backlog.
Who can cancel a Sprint, and when?
Only the Product Owner, when the Sprint Goal becomes obsolete (for example, a business change makes the goal meaningless).
What happens to a Product Backlog item that does not meet the Definition of Done at the end of a Sprint?
It is not part of the Increment, cannot be released or presented at the Sprint Review, and returns to the Product Backlog for the Product Owner to reconsider.
What are the three pillars of Scrum's empiricism?
Transparency, inspection and adaptation.
Are story points and burndown charts mandatory in Scrum?
No. They are common complementary practices, but the Scrum Guide does not prescribe them. Teams may use any technique to forecast and track progress.
A team has 6 Developers in a 2-week Sprint. Assume 8 working days of build time, 5 focused hours per day, and one Developer away for 3 days. What is the capacity in hours?
6 × 8 × 5 = 240 hours, minus 3 × 5 = 15 hours for the absence, giving 225 hours. (Capacity planning is a team practice, not part of the Scrum Guide.)
Summary
Scrum is a lightweight framework for complex work, defined by the 2020 Scrum Guide (still current), based on empiricism and lean thinking.
Pillars: transparency, inspection, adaptation. Values: commitment, focus, openness, respect, courage.
Scrum Team (typically 10 or fewer, no sub-teams): Product Owner (value, Product Backlog), Scrum Master (team effectiveness, Scrum as defined), Developers (Sprint Backlog, quality, Increment).
Events: Sprint (≤ 1 month), Sprint Planning (≤ 8 h; why/what/how), Daily Scrum (15 min), Sprint Review (≤ 4 h), Sprint Retrospective (≤ 3 h).
Artifacts → commitments: Product Backlog → Product Goal, Sprint Backlog → Sprint Goal, Increment → Definition of Done.
Only the Product Owner can cancel a Sprint; refinement is an ongoing activity, not an event; undone work goes back to the Product Backlog.
Story points, velocity, burndowns and user stories are optional practices, not Scrum rules.
Scrum organizes work into fixed Sprints. Some teams, such as support and operations teams, prefer a continuous flow of work instead, and many teams want stronger engineering discipline inside each iteration. The next chapter, Kanban & Extreme Programming, covers both.