What Is Scrum? A Simple Introduction for Beginners
Scrum is a lightweight framework that helps teams work on complex products and deliver value in small, manageable increments.
Scrum is commonly used with Agile ways of working. It provides a simple structure for planning, doing the work, reviewing results, and improving continuously.
How Does Scrum Work?
Scrum organizes work into short, fixed-length periods called Sprints.
During a Sprint, the Scrum Team works on selected items, creates a usable Increment, reviews the result, and identifies improvements for the next Sprint.
Basic Scrum Components
- Scrum Team — the people responsible for creating the product Increment.
- Sprint — a fixed-length period in which useful work is completed.
- Product Backlog — an ordered list of work needed to improve the product.
- Increment — a usable, valuable result produced during the Sprint.
- Scrum Events — structured opportunities for planning, inspection and adaptation.
Scrum Is Not a Detailed Process
Scrum provides a framework rather than step-by-step instructions for every situation.
Teams can use different techniques and practices within the Scrum framework depending on their product and circumstances.
Scrum provides the structure. The Scrum Team decides how best to perform the work within that structure.
Where Scrum Came From
Scrum was created in the early 1990s by Ken Schwaber and Jeff Sutherland, who were each looking for a better way to build software in situations where the old plan-everything-first approach kept failing. They presented Scrum publicly in 1995. The name comes from rugby, where a scrum is a way of restarting play in which the whole team works together to move the ball forward. The official definition of Scrum is the Scrum Guide, a short document of about thirteen pages that Schwaber and Sutherland maintain; the current edition was published in 2020.
Scrum is one way of putting Agile into practice. If the idea of Agile is still new to you, read What Is Agile? first.
The Theory Behind Scrum
Scrum is built on empiricism, which means making decisions based on what you have actually observed rather than on prediction. The Scrum Guide describes three pillars that make empiricism work:
- Transparency: the work and the process are visible to those who do the work and those who receive it, and everyone uses a shared understanding of terms such as "Done".
- Inspection: the team frequently checks its progress and its product to detect unwanted variances or problems.
- Adaptation: when inspection shows that something is off course, the team adjusts as soon as possible.
Scrum also uses lean thinking, which reduces waste and focuses on what is essential, and it is guided by five values: Commitment, Focus, Openness, Respect and Courage. See The Five Scrum Values in Real Teams for how they appear in daily work.
The Scrum Team in More Detail
A Scrum Team is small, usually ten people or fewer, and has no sub-teams or hierarchy. It has three accountabilities:
- Product Owner: accountable for maximizing the value of the product, including managing the Product Backlog and being clear about what the team is trying to achieve.
- Scrum Master: accountable for establishing Scrum as described in the Scrum Guide and for the team's effectiveness. Scrum Masters serve the team, the Product Owner and the organization.
- Developers: the people who do the work of creating a usable Increment each Sprint. The term covers anyone doing that work, such as programmers, testers, designers and analysts.
The whole team is cross-functional, meaning it has all the skills needed to create value each Sprint, and self-managing, meaning it decides internally who does what, when and how. More on each accountability in Scrum Team Explained and Scrum Master Role and Responsibilities.
The Five Scrum Events
Scrum uses short, time-boxed events that give the team regular chances to inspect and adapt. The maximum durations below apply to a one-month Sprint and are usually shorter for shorter Sprints.
| Event | Purpose | Maximum time (1-month Sprint) |
|---|---|---|
| The Sprint | A fixed-length container, one month or less, in which all other events happen and an Increment is created | 1 month |
| Sprint Planning | Decide why the Sprint is valuable, what can be done, and how the work will be done | 8 hours |
| Daily Scrum | Developers inspect progress toward the Sprint Goal and adapt the plan for the next 24 hours | 15 minutes |
| Sprint Review | Team and stakeholders inspect the outcome and decide what to do next | 4 hours |
| Sprint Retrospective | Team inspects how it worked and plans improvements | 3 hours |
A detailed look at each is in Scrum Events Explained.
Artifacts and Commitments
Scrum has three artifacts, each paired with a commitment that keeps it honest and focused:
- Product Backlog, committed to the Product Goal: an ordered list of what is needed to improve the product, and a long-term objective for the team.
- Sprint Backlog, committed to the Sprint Goal: the goal for the Sprint, the items chosen to achieve it and a plan for delivering them.
- Increment, committed to the Definition of Done: a usable step toward the Product Goal, which counts only when it meets the team's shared quality standard.
A Sprint in Practice: A Simple Example
Imagine a team building a mobile app for ordering groceries. The Product Owner has a long Product Backlog, and the top item is "customers can reorder a previous basket".
- Sprint Planning (day 1). The team agrees on a Sprint Goal: "Returning customers can reorder their last basket in under a minute." They pull the backlog items needed for that goal and break them into tasks.
- Daily Scrums (every day). In 15 minutes the Developers check progress toward the goal. One mentions a problem with the payment service; the Scrum Master helps get the right person involved the same day.
- Sprint Review (last days). The team shows the working reorder feature to a few customers and managers. Their feedback leads the Product Owner to move "saved delivery times" higher in the backlog.
- Sprint Retrospective. The team notices that testing started too late. They agree to test each item as soon as it is built and add this to the next Sprint.
The next Sprint begins immediately, using what was learned.
When Scrum Works Well, and When It Does Not
Scrum is designed for complex work, where requirements are unclear or likely to change and the team needs to learn by building. It fits product development, software and many knowledge-work teams. It is a poor fit for purely repetitive tasks that need no learning, or for organizations that will not let the team make decisions. A common alternative for continuous flow work is Kanban; Scrum vs Kanban compares them.
Common Misunderstandings About Scrum
- "The Scrum Master is the team's manager." No. The Scrum Master serves and coaches; the Developers manage their own work.
- "Scrum is a methodology with a complete set of procedures." It is deliberately incomplete; teams add techniques that suit them.
- "Story points, burndown charts and user stories are part of Scrum." They are popular practices, not requirements.
More are covered in Common Scrum Myths and Misconceptions.
Frequently Asked Questions
Is Scrum the same as Agile?
No. Agile is a set of values and principles; Scrum is a framework that implements them.
How long is a Sprint?
A Sprint is one month or less. Two weeks is the most common choice, but the team can choose what fits its context.
Who decides what goes into a Sprint?
The Product Owner orders the Product Backlog. The Developers decide how much they can take on, and the whole Scrum Team agrees on the Sprint Goal.
Where should I go next?
Continue with Scrum Framework Explained for a full tour of roles, events and artifacts.
- Scrum is a lightweight framework for complex work, created by Ken Schwaber and Jeff Sutherland and defined in the Scrum Guide.
- It rests on transparency, inspection and adaptation, and on five values.
- A Scrum Team has one Product Owner, one Scrum Master and Developers, working in Sprints of one month or less.
- Scrum is intentionally incomplete: it gives a structure, and teams choose the techniques.
Scrum and Agile
Agile is a broader approach to working and thinking. Scrum is one framework used to put Agile principles into practice.
Understanding this difference is important for anyone preparing to become a Scrum Master.
What Comes Next?
Now that we understand Scrum at a high level, the next step is to understand the Scrum Framework and how its different elements fit together.