Scrum Framework Explained: Roles, Events and Artifacts

The Scrum Framework provides a simple structure for teams to work together, inspect their progress, and adapt their approach while creating value.

To understand Scrum properly, it helps to look at four connected areas:

  • Scrum Team accountabilities
  • Scrum Events
  • Scrum Artifacts
  • Commitments

1. Scrum Team Accountabilities

A Scrum Team consists of three accountabilities:

  • Product Owner — maximizes product value and manages the Product Backlog.
  • Scrum Master — helps establish Scrum, supports the team, and helps remove impediments.
  • Developers — create the usable Increment during each Sprint.

2. Scrum Events

Scrum defines five events that create opportunities for inspection and adaptation.

  • Sprint — the container for all other Scrum events.
  • Sprint Planning — the team plans the work for the Sprint.
  • Daily Scrum — Developers inspect progress toward the Sprint Goal and adapt their plan.
  • Sprint Review — the team and stakeholders inspect the outcome and discuss what to do next.
  • Sprint Retrospective — the Scrum Team identifies ways to improve.

3. Scrum Artifacts

Scrum has three artifacts that provide important information about the work and product.

  • Product Backlog — the ordered list of everything needed to improve the product.
  • Sprint Backlog — the Sprint Goal, selected Product Backlog items, and the plan for delivering them.
  • Increment — a usable, valuable step toward the Product Goal.

4. Scrum Commitments

Each Scrum artifact has a corresponding commitment.

Artifact
Commitment
Product Backlog
Product Goal
Sprint Backlog
Sprint Goal
Increment
Definition of Done

How Everything Fits Together

The Product Backlog contains the work needed to improve the product. During Sprint Planning, the Scrum Team selects work and creates a Sprint Goal.

Developers then work during the Sprint and create an Increment that meets the Definition of Done.

The Sprint Review provides an opportunity to inspect the result, while the Sprint Retrospective focuses on improving how the team works.

Simple way to remember Scrum:

People + Events + Artifacts + Commitments work together to help a Scrum Team create value and continuously improve.

The Accountabilities in Depth: What Each Does and Does Not Do

Most confusion in new Scrum Teams comes from unclear accountabilities. The table below summarises what each one is responsible for and what it is not.

AccountabilityIs accountable forDoes not
Product OwnerMaximizing the value of the product; developing and communicating the Product Goal; creating and ordering Product Backlog items; making the backlog transparentTell Developers how to build; act as a project manager; need to write every backlog item personally (the work can be delegated, accountability stays)
Scrum MasterEstablishing Scrum; the Scrum Team's effectiveness; coaching, facilitating and removing impediments; helping the organization adopt ScrumAssign tasks; approve work; act as the team's manager or secretary
DevelopersCreating a plan for the Sprint (the Sprint Backlog); instilling quality through the Definition of Done; adapting the plan daily; holding each other accountableWait to be told what to do; leave quality to a separate team

Read Scrum Team Explained and Scrum Master Role and Responsibilities for fuller descriptions.

The Events in Depth

Sprint Planning

The whole Scrum Team plans the Sprint by addressing three topics. Why is this Sprint valuable? The Product Owner proposes how the product could increase its value, and the team agrees on a Sprint Goal. What can be done? Developers select Product Backlog items that fit the goal, using their experience and recent performance to judge how much they can do. How will the work get done? Developers plan the work needed to turn the selected items into an Increment. The plan, the goal and the selected items together form the Sprint Backlog. See Sprint Planning Explained.

Daily Scrum

A 15-minute event for the Developers, held at the same time and place each day to reduce complexity. The structure is up to the Developers, so long as it focuses on progress toward the Sprint Goal and produces an actionable plan for the next day. The Scrum Master ensures it takes place and stays within the timebox. The well-known "three questions" are a common technique, not a Scrum requirement.

Sprint Review

A working session in which the Scrum Team presents the results of the Sprint to key stakeholders and discusses progress toward the Product Goal. It is not a formal sign-off or a one-way demo: attendees collaborate on what to do next, and the Product Backlog may be adjusted as a result. See Sprint Review Explained.

Sprint Retrospective

The event that closes the Sprint. The Scrum Team inspects how the last Sprint went with regard to individuals, interactions, processes, tools and its Definition of Done, identifies the most helpful changes, and addresses them as soon as possible, sometimes by adding them to the next Sprint Backlog. See Sprint Retrospective Explained.

Artifacts, Commitments and the Definition of Done

ArtifactCommitmentWhat the commitment means
Product BacklogProduct GoalThe long-term objective the team plans toward; the backlog is organised to achieve it
Sprint BacklogSprint GoalThe single objective for the Sprint; gives flexibility on the work needed to reach it
IncrementDefinition of DoneThe shared quality standard an Increment must meet to count as finished

The Definition of Done deserves special attention because it creates transparency. If the Definition of Done for a web feature includes "code reviewed, automated tests passing, documented, accepted by the Product Owner and deployed to the test environment", then a feature missing any of those is not Done, no matter how complete it looks. An item that does not meet the Definition of Done cannot be released or even presented as part of the Increment at the Sprint Review; it goes back to the Product Backlog.

A Two-Week Sprint Timeline

The Scrum Guide does not prescribe days, but this example shows how the events fit together in a two-week Sprint (ten working days). The timings are illustrative.

DayWhat happens
Day 1Sprint Planning (up to four hours for a two-week Sprint): agree the Sprint Goal and Sprint Backlog
Days 1 to 9Developers build and test; Daily Scrum each day; Product Backlog refined as needed
Day 10Sprint Review (up to two hours), then Sprint Retrospective (up to one and a half hours)
Day 11Next Sprint begins immediately with Sprint Planning

Quick Reference: Rules and Timeboxes

  • A Sprint is one month or less and a new Sprint starts immediately after the previous one ends.
  • Sprint Planning: up to 8 hours for a one-month Sprint. Sprint Review: up to 4 hours. Sprint Retrospective: up to 3 hours. Daily Scrum: 15 minutes.
  • Only the Product Owner can cancel a Sprint, and only if the Sprint Goal becomes obsolete.
  • During the Sprint, no changes are made that would endanger the Sprint Goal, quality does not decrease, and scope may be clarified and renegotiated with the Product Owner as more is learned.
  • Each Scrum Team has one Product Owner, one Scrum Master and Developers, typically ten people or fewer.

Common Mistakes When Applying the Framework

  1. Treating the Sprint Backlog as a contract. It is a plan the Developers adapt as they learn. The commitment is the Sprint Goal.
  2. Skipping the Retrospective when busy. This removes the main mechanism for improvement.
  3. Using the Daily Scrum as a status report to the Scrum Master. It is for the Developers to plan their work.
  4. Weak or missing Definition of Done. Without it, unfinished work accumulates as hidden debt.
  5. A Product Owner who is unavailable or a committee. One person must be accountable for the backlog, and the team needs timely answers.
  6. Mixing up Scrum rules and popular practices. Story points, velocity and burndown charts are optional; see Common Scrum Myths and Misconceptions. For one such practice, read Estimation and Story Points in Scrum.

When something is blocking the team, the Scrum Master helps remove it; Impediment Management shows how.

Check Your Understanding

  1. Who decides how many Product Backlog items are selected for a Sprint? The Developers, based on their capacity and the Sprint Goal.
  2. What is the commitment for the Increment? The Definition of Done.
  3. Who can cancel a Sprint? Only the Product Owner.
  4. How long is the Daily Scrum? Fifteen minutes, regardless of Sprint length.
  5. Which event ends the Sprint? The Sprint Retrospective, after the Sprint Review.
Key takeaways
  • Scrum has three accountabilities, five events and three artifacts with matching commitments.
  • The Sprint is the container for everything else, and all events are timeboxed.
  • The Definition of Done creates a shared meaning of finished work.
  • Scrum is a framework, not a complete method: teams choose the techniques that suit them.

What Comes Next?

Now that we understand the overall Scrum Framework, we will look at each part in more detail.

The next lesson focuses on the Scrum Team and its three accountabilities.