Skip to content
Tutorials Center
My learning

Topics

Lesson 29 of 41 ยท Agile and Scrum

Scrum Framework

Learn Scrum: the three accountabilities, five events, three artifacts, the Definition of Done, user stories, backlog refinement and a sprint walk-through with runnable Python.

Scrum is the most widely used agile framework. It is deliberately small: a handful of roles, events and artifacts that wrap a team in a rhythm of short cycles called sprints. Scrum does not tell you how to write code or run a marketing campaign; it tells you how to organize the work so that learning and delivery happen every few weeks. The rules are described in the Scrum Guide, which is short (about 13 pages), and it is worth reading once.

Scrum rests on three pillars: transparency (everyone sees the real state), inspection (you check often) and adaptation (you change course when needed). It values commitment, focus, openness, respect and courage.

The Scrum team

A Scrum Team is one small group (usually 10 or fewer) with three accountabilities and no sub-teams or hierarchy.

Three accountabilities

Product Owner Maximizes value; owns the Product Backlog.
Scrum Master Helps the team follow Scrum and removes obstacles.
Developers Build the increment each sprint.

Developers means everyone who does the work, not only programmers.

1 / 2
  • The Product Owner (PO) is one person, not a committee. They order the backlog, make scope trade-offs and are the voice of customers and stakeholders.
  • The Scrum Master is a true leader and coach: facilitates events, helps the PO with backlog techniques, shields the team from interruptions and helps the organization adopt Scrum. They are not the team's boss.
  • The Developers are self-managing: they decide how to turn backlog items into an increment, and they hold themselves to the Definition of Done.

The artifacts

Each artifact has a commitment that increases transparency.

Artifact Commitment What it is
Product Backlog Product Goal Ordered list of everything the product might need
Sprint Backlog Sprint Goal Items chosen for this sprint plus the plan to deliver them
Increment Definition of Done A usable, verified step toward the Product Goal

The Product Backlog is never finished: items at the top are small and clear, items at the bottom are vague. Refinement is the ongoing work of breaking items down, clarifying them and estimating them, usually taking up to 10 percent of the team's capacity.

User stories

Backlog items are often written as user stories:

TEXT
As a <type of user>, I want <goal>, so that <benefit>.

For example: "As a shopper, I want to save my cart, so that I can finish buying later." A good story passes the INVEST test: Independent, Negotiable, Valuable, Estimable, Small, Testable. Add acceptance criteria: concrete conditions that must be true when the story is done.

Python An ordered product backlog

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Value divided by effort is only one ordering aid; the PO also weighs risk, dependencies and deadlines. But it shows how ordering turns into a decision, not a guess.

The events

All events are time-boxed, and all happen inside the Sprint, a fixed length of one month or less. Sprints run back to back. A sprint does not change its goal if it endangers the sprint goal, and only the PO can cancel one.

Sprint Planning (up to 8 hours for a one-month sprint, proportionally less for shorter ones) answers three questions: why is this sprint valuable (the Sprint Goal), what can be done (items chosen from the backlog), and how will the chosen work get done (a plan). See sprint planning and burndown.

Daily Scrum (15 minutes, same time and place) is for the Developers to inspect progress toward the Sprint Goal and adjust the plan for the next 24 hours. It is not a status report to the manager. A popular format is "what moves us toward the goal today, and what blocks us?".

Sprint Review is a working session with stakeholders where the team shows the increment and everyone discusses what to do next. It is not a sign-off meeting; the PO adjusts the Product Backlog with the feedback.

Sprint Retrospective is the team inspecting itself: people, interactions, processes, tools and the Definition of Done. At least one improvement should enter the next sprint backlog.

flowchart LR
  PL["Sprint Planning"] --> SP["Sprint<br/>Daily Scrum each day"]
  SP --> RV["Sprint Review"]
  RV --> RT["Retrospective"]
  RT --> PL

One sprint feeds the next; the Product Backlog changes along the way.

Definition of Done

The Definition of Done (DoD) is a shared, written checklist for what "finished" means for any backlog item. If an item does not meet the DoD, it is not part of the increment and returns to the backlog. A simple DoD:

  • Code reviewed and merged.
  • Automated tests written and passing.
  • Acceptance criteria verified.
  • Documentation and release notes updated.
  • No known high-severity defects.

A sprint walk-through

Python Simulate a two-week sprint

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

Program input ยท what you'd type while the program runs

Type the answers before you press Run, one per line. Each time the program reads a line (with input()), it gets the next line from this box.

Common Scrum mistakes

  • Scrum-but: "we use Scrum, but we skip retrospectives". The missing parts usually hide the problems Scrum would expose.
  • A Product Owner who is a messenger, without authority to decide.
  • Scrum Master as project manager who assigns tasks.
  • Carrying unfinished work from sprint to sprint instead of learning from it.
  • Treating the sprint as a mini-waterfall: design in week 1, test in week 2, nothing integrated until the end.
  • Velocity as a performance target; velocity is a planning tool, not a goal (next lesson).

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 maximizes value and is accountable for effective Product Backlog management.
  2. 2. What is the Daily Scrum for?

    It is a 15-minute event for the Developers, to plan the next 24 hours toward the Sprint Goal.
  3. 3. A backlog item does not meet the Definition of Done at the end of the sprint. What happens?

    Undone work is not an increment; it goes back to the backlog for re-ordering.
  4. 4. Which event inspects the team's own process?

    The Retrospective is about people, process and tools; the Review inspects the product.

Summary

  • Scrum is a small framework of one team, three accountabilities, five events and three artifacts, built on transparency, inspection and adaptation.
  • The Product Owner orders the backlog, the Scrum Master serves the team and organization, Developers build the increment.
  • Each artifact has a commitment: Product Goal, Sprint Goal, Definition of Done.
  • A sprint is time-boxed (one month or less) and ends with a Review and a Retrospective.
  • Most failures come from dropping parts of Scrum or misusing roles.

Next: Sprint Planning and Burndown