Skip to content
Tutorials Center
My learning

Topics

Lesson 26 of 50 ยท Agile and Teamwork

Scrum in Practice

Learn how Scrum works in practice: the three roles, five events, three artifacts, the definition of done, and the arithmetic behind sprint planning and burndown.

Scrum is the most widely used way of putting agile ideas into practice. It is a small framework, not a full methodology: it tells a team who does what, when the team meets, and what it keeps track of, and leaves almost everything else (how to write code, how to test, which tools to use) to the team itself. The official Scrum Guide is only a few pages long on purpose.

Scrum itself is a way of organizing people, so there is nothing to install or run. The code in this lesson is plain JavaScript stand-ins with invented numbers. They show the arithmetic of sprint planning and the shape of a burndown chart; they are not a real project-management tool such as Jira.

If you have not read the values behind this, start with agile principles.

The idea: short cycles with a fixed rhythm

A Scrum team works in sprints: fixed-length periods, usually one to four weeks (one month is the maximum), that follow each other with no gap. At the end of every sprint the team has a usable increment of the product. Because the length never changes, the team learns how much it can really do in one sprint, and stakeholders get a regular chance to look at real software and change direction.

Scrum in one slide

Three roles Product Owner, Scrum Master, Developers.
Five events Sprint, planning, daily, review, retrospective.
Three artifacts Product Backlog, Sprint Backlog, Increment.

Each artifact has a commitment that keeps it honest.

1 / 2

The roles

Scrum calls the whole group the Scrum Team. It is deliberately flat: there are no sub-teams and no hierarchy inside it.

  • Product Owner is accountable for the value of the product. The Product Owner decides what goes into the Product Backlog and in what order. This is one person, not a committee, so the Developers always know whom to ask.
  • Developers are everyone who builds the increment: programmers, testers, designers, whoever the work needs. They own the how and the sprint plan. "Developers" is a role name, not a job title.
  • Scrum Master is accountable for the team using Scrum well. That means coaching, removing obstacles, protecting the team from constant interruptions, and helping the organization understand the framework. A Scrum Master is a servant leader, not a project manager who assigns tasks.

A typical team has about ten people or fewer in total. Larger groups usually split into several teams.

The events

All events are time-boxed: they have a maximum length and end when the time is up.

Event Purpose Typical length for a 2-week sprint
Sprint Container for all other events 2 weeks
Sprint Planning Agree on the Sprint Goal and select work up to 4 hours
Daily Scrum Inspect progress toward the goal, adjust the plan 15 minutes
Sprint Review Show the increment, collect feedback, adapt the backlog up to 2 hours
Sprint Retrospective Improve people, process and tools up to 1.5 hours

Sprint Planning answers three questions: Why is this sprint valuable (the Sprint Goal)? What can be done? How will the chosen work get done? The Daily Scrum is for the Developers, and it is not a status report to a manager. The Sprint Review is a working session with stakeholders, not a slide show. The Retrospective looks at how the team worked together and picks one or two concrete changes to try next sprint.

The artifacts and their commitments

  1. Product Backlog: an ordered list of everything the product might need. Its commitment is the Product Goal, the long-term objective the backlog serves. Items near the top are small and well understood; items near the bottom are vague on purpose.
  2. Sprint Backlog: the Sprint Goal, the selected Product Backlog items, and the Developers' plan for delivering them. It belongs to the Developers and is updated throughout the sprint.
  3. Increment: a concrete, usable step toward the Product Goal. Its commitment is the Definition of Done.

The Definition of Done

The Definition of Done (DoD) is a shared, written checklist of what "finished" means. For example: code reviewed, automated tests passing, documentation updated, deployed to a staging environment. Work that does not meet the DoD is not part of the increment, even if it is 95% finished, and goes back to the Product Backlog. This rule prevents the slow slide into "done, except for testing".

Keep the Definition of Done short and checkable. If nobody can answer "yes or no" for an item, it will not be applied consistently. Compare it with the per-story acceptance criteria: acceptance criteria say what this story must do, the DoD says what is true of every story.

Sprint planning math

Planning has to answer "how much work fits?" Two common approaches, which teams often combine:

  • Capacity-based: add up the focused hours available. Person-days (minus holidays and leave) times the hours per day that are really spent on sprint work. Four people with 36 person-days in total and 5 focus hours per day have 180 hours. A focus factor below the 8-hour day accounts for meetings, email, and support.
  • Velocity-based: use the story points the team completed in recent sprints (see estimation and planning) and select roughly that many points.

The stand-in below uses capacity. It takes items from the top of the backlog in priority order and stops at the first one that does not fit. The hour estimates are invented.

JS Sprint capacity and selection

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

No output.

Notice that the team does not fill the last 12 hours with a smaller item from lower in the backlog. Skipping ahead would break the Product Owner's ordering. A real team might instead split "Avatar upload" so a first slice fits, which is a conversation, not a calculation.

Tracking progress: the burndown chart

A burndown chart plots the work remaining against the days of the sprint. The ideal line runs straight from the committed amount down to zero. The actual line zigzags around it. If the actual line stays above the ideal line, the team is behind; below it, ahead. The point is to start a conversation early, not to judge people.

JS Text burndown chart

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

No output.

Look at days 2 and 3: nothing was finished on day 3 and the line went above the ideal. That is normal. Work arrives in chunks, and a flat day often means a story is nearly done. A burndown that is always perfectly on the ideal line usually means that people are reporting hours to look good.

Burndown charts also hide scope changes: if new work is added mid-sprint, the line goes up and looks like slow progress. This is one reason the Sprint Goal matters more than the chart. The team can drop or renegotiate items as long as the goal is still reachable.

Common mistakes

  • Scrum-but: adopting the events and ignoring the rest, for example no Definition of Done or a Product Owner who cannot decide.
  • Changing the sprint scope constantly. A sprint is a protected period. Only the Product Owner can cancel it, and that is rare.
  • Treating the Daily Scrum as a status meeting for a manager.
  • Skipping the Retrospective when the team is busy, which removes the only mechanism for improving.
  • Calling the velocity a performance target. Once velocity is used to compare teams or reward people, estimates inflate and the number becomes useless.

Check your understanding

Quick check ยท 4 questions

of 4 answered You scored / 4 ยท perfect!

  1. 1. Who is accountable for ordering the Product Backlog?

    The Product Owner is one person accountable for the value of the product and the order of the Product Backlog. Others can advise, but the decision is theirs.
  2. 2. What happens to a story that is 95% finished when the sprint ends?

    Only work that meets the Definition of Done is part of the increment. Sprints never get longer to fit unfinished work.
  3. 3. Four people have 40 person-days in the sprint and spend 5 focus hours per day on sprint work. What is the capacity?

    Capacity is person-days times focus hours: 40 x 5 = 200 hours. The 160 comes from 4 x 40 and ignores the focus factor and the real number of days.
  4. 4. Which statement about the Daily Scrum is correct?

    The Daily Scrum is time-boxed to 15 minutes and is owned by the Developers. It is for planning the next day of work, not for reporting to a manager.

Summary

  • Scrum is a lightweight framework: three roles (Product Owner, Developers, Scrum Master), five events, three artifacts.
  • Sprints are fixed-length, back to back, and end with a usable increment.
  • The Definition of Done is the commitment of the increment: unfinished work does not count.
  • Planning uses capacity (person-days times focus hours) or velocity; the Sprint Goal matters more than any single item.
  • A burndown chart starts conversations; it does not prove the team is good or bad.

Next: Kanban, Extreme Programming and Lean.