Skip to content
Tutorials Center
My learning

Topics

Lesson 5 of 29 ยท The Scrum Framework

Scrum at a Glance

A clear overview of Scrum: empirical process control, transparency, inspection and adaptation, the Sprint loop, roles, events, artifacts and the Scrum Guide.

Scrum is a lightweight framework for solving complex problems by delivering value in small steps. It does not tell you how to write code, design a database or run a marketing campaign. It only sets a few roles, events and artifacts that create a regular rhythm of planning, doing, showing and improving. Everything else is up to the team. Scrum is defined in a short document called the Scrum Guide, maintained by Ken Schwaber and Jeff Sutherland, who created it. The current version dates from 2020.

This lesson is the map for the whole chapter. You will learn the idea behind Scrum (empiricism), the three pillars and five values, how one Sprint flows, and how the guide is organized. The following lessons look closer at roles, events and artifacts. If you have not read it yet, What Is Agile? gives the background.

Empiricism: learn from what happens

Scrum is built on empirical process control, or empiricism: knowledge comes from experience, and decisions are based on what is observed. This is the opposite of trying to predict everything up front. It is the right approach when work is complex, meaning that cause and effect are only clear in hindsight, which describes most product development.

Empiricism rests on three pillars:

  • Transparency: the significant aspects of the work are visible to the people responsible for the outcome, using shared definitions. Hidden problems cannot be solved. If one person's "done" differs from another's, you do not have transparency.
  • Inspection: the team and stakeholders frequently check progress toward goals and look for unwanted variances. Inspection must be frequent enough to be useful, but not so frequent that it gets in the way of the work.
  • Adaptation: if inspection shows that something has drifted outside acceptable limits, the process or the product is adjusted as soon as possible to limit further deviation.

You can think of the three as a loop: make things visible, look at them, and change something. Every Scrum event exists to give that loop a place to happen.

Three pillars

Transparency Everyone sees the real state of the work.
Inspection Check progress and results often.
Adaptation Adjust quickly when things drift.

Without transparency, inspection is blind and adaptation is guessing.

1 / 2

The Scrum Team

A Scrum Team is one small, cross-functional group. It has no sub-teams and no hierarchy inside it. It normally has ten or fewer people and contains three accountabilities:

  • The Product Owner is accountable for maximizing the value of the product and for managing the Product Backlog.
  • The Scrum Master is accountable for the team's effectiveness and for establishing Scrum as described in the guide.
  • The Developers are the people who create any aspect of a usable Increment each Sprint.

The word "Developers" means everyone doing the work (programmers, designers, testers, analysts), not only programmers. Roles get their own lesson: Scrum Roles.

The Sprint loop

The Sprint is the container for everything else. It is a fixed length of one month or less, and a new Sprint starts immediately after the previous one ends. Inside a Sprint, four other events happen:

  1. Sprint Planning starts the Sprint. The team decides why the Sprint is valuable (the Sprint Goal), what can be done, and how the chosen work will get done.
  2. Daily Scrum is a 15-minute event for Developers to inspect progress toward the Sprint Goal and adapt the plan for the next day.
  3. Sprint Review closes the work: the team and stakeholders inspect the outcome and talk about what to do next.
  4. Sprint Retrospective ends the Sprint: the team inspects how it worked and plans improvements.
flowchart LR
  PB["Product Backlog"] --> SP["Sprint Planning"]
  SP --> SB["Sprint Backlog"]
  SB --> DS["Daily Scrum<br/>(every day)"]
  DS --> INC["Increment"]
  INC --> SR["Sprint Review"]
  SR --> RE["Retrospective"]
  RE --> SP

One Sprint: plan from the backlog, work and sync daily, show the Increment, improve, then start the next Sprint.

During the Sprint, no changes are made that would endanger the Sprint Goal, quality does not decrease, and the Product Backlog is refined as needed. Scope can be clarified and renegotiated with the Product Owner as more is learned.

The three artifacts and their commitments

Scrum has three artifacts, each with a commitment that gives it focus:

Artifact What it is Commitment
Product Backlog The ordered list of what the product may need Product Goal: the long-term objective
Sprint Backlog The Sprint Goal, the selected items and the plan Sprint Goal: the single objective for this Sprint
Increment A usable step toward the Product Goal Definition of Done: the shared quality bar

The commitments exist for transparency: they say what the team is trying to achieve and what "good enough" means. The details of each are in Scrum Artifacts and Commitments.

How the Scrum Guide is organized

The Scrum Guide is only a few pages long and worth reading in full. It is organized as:

  1. Purpose of the guide.
  2. Scrum definition and theory: empiricism and Lean thinking.
  3. Scrum values.
  4. The Scrum Team: Developers, Product Owner, Scrum Master.
  5. Scrum events: the Sprint and the four events inside it.
  6. Scrum artifacts: Product Backlog, Sprint Backlog, Increment and their commitments.

Scrum is deliberately incomplete. The guide says that Scrum is a framework, not a methodology: it does not give a recipe for every situation. You must add your own practices (such as user stories, estimation and testing techniques) on top. Changing the core pieces, for example skipping the retrospective, may hide problems that Scrum was designed to surface.

A sprint lifecycle model

Seeing the loop run is the best way to remember it. The model below creates a Product Backlog, runs Sprint Planning to pick items for a Sprint Goal, simulates five working days with a Daily Scrum, and finishes with a Review and a Retrospective. It is a stand-in: real Scrum is about people talking, not a script. What it models faithfully is the order of events and the way work moves from the Product Backlog to the Increment.

JS One Sprint from start to finish

Press Run (or Ctrl + Enter) to see the console output here.

No output.

Change capacity to 5 or days to 2 and compare. With fewer days, items that did not finish stay out of the Increment, which is exactly how Scrum keeps the Increment honest: only work that meets the Definition of Done counts. The loop is the point of Scrum, not the individual steps.

Inspect and adapt across Sprints

Empiricism is not only about Sprint events; it is about changing course using evidence. The second model runs four Sprints. After each one the team inspects how much it actually finished compared with what it forecast, and adapts its next forecast by averaging recent results. This is a simplified version of how many teams use history to plan, not a rule of Scrum.

JS Inspect and adapt the forecast

Press Run (or Ctrl + Enter) to see the console output here.

No output.

The numbers show the pillars working: the first forecast was visible (transparency), it was compared with reality (inspection), and the next forecast changed (adaptation).

Scrum has two ideas that are easy to miss. First, the Sprint Goal is the commitment for the Sprint, and the team may change the work needed to reach it. Second, nobody outside the team tells the Developers how to turn backlog items into an Increment.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. What are the three pillars of empirical process control in Scrum?

    Transparency, inspection and adaptation are the pillars of empiricism. Focus, courage and respect are among the five Scrum values, and roles, events and artifacts are the parts of the framework.
  2. 2. How long can a Sprint be?

    A Sprint is fixed in length at one month or less. Many teams choose two weeks, but that is a team choice, not a rule.
  3. 3. Which artifact has the Definition of Done as its commitment?

    The Increment's commitment is the Definition of Done. The Product Backlog's commitment is the Product Goal, and the Sprint Backlog's is the Sprint Goal.
  4. 4. Which statement about Scrum is true?

    Scrum is a framework. It sets roles, events and artifacts and leaves the techniques to the team.

Summary

  • Scrum is a lightweight framework for complex work, built on empiricism: decisions come from observation.
  • The three pillars are transparency, inspection and adaptation; the values are commitment, focus, openness, respect and courage.
  • A Scrum Team is small, with a Product Owner, a Scrum Master and Developers.
  • The Sprint (one month or less) contains Sprint Planning, the Daily Scrum, the Sprint Review and the Retrospective.
  • The three artifacts are the Product Backlog, the Sprint Backlog and the Increment, with the commitments Product Goal, Sprint Goal and Definition of Done.
  • Scrum is a framework: add your own practices, and be careful when removing parts.

Next, look at who does what in Scrum Roles.