Intro to Git — Snapshots, Branches & Sharing
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
Scrum training for teams: run a two-week Sprint hands-on. Order the backlog, plan to a Sprint Goal, make the Daily Scrum calls, decide what's Done.

WorkshopyOfficial
78 lessons · used by 2 teachers
Sign in to copy it to your workspace. It’s free.
10 steps · 2 quizzes · open any step, or read it here
This Scrum training for teams walks through one Sprint from start to finish: who does what, which events happen when, and how the work moves. Scrum is a lightweight framework in which a small team delivers value in short, fixed-length cycles called Sprints, inspecting the result and adapting as it goes.
Our example all through the lesson is a team that builds the tool a company's support agents use to answer customer tickets. Press Play the Sprint to watch the rest of a two-week Sprint.
Interactive · A two-week Sprint, from planning to retrospective — try it in the lesson
The board above is a common way to make the team's work visible. Scrum doesn't require a board, columns or any particular tool; we use one because it shows the Sprint moving.
In this lesson you'll:
It takes about 75 minutes.
Takeaway: a Sprint is a short, fixed cycle: plan, work and check every day, then show the result and improve how you work.
Scrum is built on empiricism: knowledge comes from experience, and decisions are made on what is observed. In complex work, what customers need, what the technology allows and what the team learns all change while the work is going on. A plan made once at the start is out of date long before the end.
Empiricism rests on three pillars:
A Sprint is one month or less, so the team gets an inspection point at least once a month, and usually every one or two weeks. The timeline below has three moments (illustrative) when what the support agents need changes.
Try it: pick how often the team inspects and adapts. Watch the red bands, the weeks of work built on needs that had already changed.
Interactive · How often the team inspects, and how long it builds on old assumptions — try it in the lesson
Inspecting more often isn't free: each inspection takes time. That is why Scrum gives each event a timebox and caps the Sprint at one month.
Takeaway: short cycles limit how long a team can work on wrong assumptions; every Sprint is a chance to inspect and adapt.
A Scrum Team is small, typically 10 or fewer people: one Product Owner, one Scrum Master and the Developers. There are no sub-teams and no hierarchy inside it. The team is cross-functional (it has the skills to create value each Sprint) and self-managing (it decides who does what, when and how).
People search for "Scrum roles", but the 2020 Scrum Guide calls them accountabilities: what each one answers for.
The team works by five values: commitment, focus, openness, respect and courage.
Try it: sort the nine cards. A wrong pick tells you why.
Interactive · Who does what in the Scrum Team — try it in the lesson
Takeaway: the Product Owner owns what and in which order, the Developers own how, the Scrum Master owns how well Scrum works.
The Sprint is the heartbeat of Scrum: a fixed length of one month or less. A new Sprint starts right after the previous one ends. All the work happens inside Sprints, and so do the other four events:
| Event | Purpose | Timebox for a one-month Sprint |
|---|---|---|
| Sprint Planning | Why this Sprint is valuable, what can be Done, how | 8 hours at most |
| Daily Scrum | Inspect progress toward the Sprint Goal, adapt the plan | 15 minutes, every working day |
| Sprint Review | Inspect the outcome with stakeholders, decide what's next | 4 hours at most |
| Sprint Retrospective | Plan ways to improve quality and effectiveness | 3 hours at most |
For shorter Sprints, the Guide says the events are usually shorter. It gives no formula; the Daily Scrum is 15 minutes whatever the Sprint's length.
During the Sprint, no changes are made that would put the Sprint Goal at risk, quality doesn't go down, the Product Backlog is refined as needed, and scope can be clarified and renegotiated with the Product Owner as the team learns more. Only the Product Owner can cancel a Sprint, when its goal no longer makes sense.
Backlog refinement is not an event: it is ongoing work, done whenever it helps, in which Product Backlog items are split, described and sized.
Try it: change the Sprint length and turn on refinement. Look at the share of time the events take.
Interactive · Lay out a Sprint and its events — try it in the lesson
Takeaway: a Sprint never runs longer than a month, and its events are short and timeboxed, so most of the time goes to the work.
Scrum has three artifacts, and each comes with a commitment that says what it is for:
| Artifact | Commitment |
|---|---|
| Product Backlog | Product Goal |
| Sprint Backlog | Sprint Goal |
| Increment | Definition of Done |
The Product Backlog is one ordered list of what is needed to improve the product, and the single source of work for the Scrum Team. The Product Goal is its long-term objective: the team works toward one Product Goal at a time, fulfilling or abandoning it before taking on the next.
The Product Owner orders the list. Items near the top are small and clear enough to be Done in one Sprint; items lower down can stay rough until refinement makes them ready. Requests that don't serve the Product Goal aren't deleted on the spot, but they move down.
Try it: you are the Product Owner. Order the backlog toward the Product Goal, and refine the big item first.
Interactive · Order the Product Backlog toward the Product Goal — try it in the lesson
Takeaway: the Product Backlog is one list in one order, set by the Product Owner and pointed at the Product Goal.
Sprint Planning starts the Sprint. The whole Scrum Team plans together, around three topics:
The Sprint Goal, the selected items and the plan together form the Sprint Backlog, which belongs to the Developers. The Sprint Goal is their commitment: if the work turns out different from the plan, they renegotiate the scope with the Product Owner, without dropping the goal.
Scrum doesn't say how to estimate. Our team estimates in days of work; others use other units, or none.
Try it: plan the Sprint. Pick a goal, then fill the Sprint with work that serves it, within the forecast.
Interactive · Sprint Planning: a goal, then the work that serves it — try it in the lesson
Takeaway: a Sprint starts with a goal, and the Developers take on only the work that serves it and fits.
Question 1. A stakeholder wants a new feature added to the Product Backlog. Who decides whether and where it goes?
Question 2. Which of these is a Scrum event?
Question 3. What is the longest a Sprint can be?
Question 4. In Sprint Planning, who selects which Product Backlog items go into the Sprint?
The Daily Scrum is a 15-minute event for the Developers, at the same time and place every working day. They inspect progress toward the Sprint Goal and change the Sprint Backlog when they need to. The format is theirs: there is no required list of questions. If the Product Owner or the Scrum Master is working on items in the Sprint Backlog, they take part as Developers.
It isn't the only moment the plan can change; it is the moment it is checked every day. Problems that block the work are raised there, and solved as soon as possible, often right after.
Three kinds of surprise come up in almost every Sprint:
Try it: run the team's two-week Sprint day by day, and make the call each time something happens.
Interactive · Run a two-week Sprint and make the calls — try it in the lesson
Takeaway: the Sprint Goal stays fixed; the plan to reach it changes every day, at the Daily Scrum.
An Increment is a concrete step toward the Product Goal. It adds to all the Increments before it, and it must be usable. A Sprint can produce several Increments, and the team can release one before the Sprint ends: the Sprint Review is never a gate to releasing value.
The Definition of Done is the Increment's commitment: a formal description of the quality the work must have. An item that meets it becomes part of the Increment. An item that doesn't can't be released or shown as Done at the Sprint Review; it goes back to the Product Backlog. If the organisation has a Definition of Done, the team follows it at least; if not, the team creates one.
Try it: switch rules of the team's Definition of Done off and on. Watch what joins the Increment, and what goes quietly missing.
Interactive · The Definition of Done decides what is in the Increment — try it in the lesson
Takeaway: Done means the Definition of Done is met, and only that work is in the Increment.
A Sprint ends with two inspections.
The Sprint Review inspects the product. The Scrum Team shows the results of the Sprint to key stakeholders, and together they discuss progress toward the Product Goal and what to do next. The Product Backlog may change as a result. It is a working session, not a presentation, and lasts at most 4 hours for a one-month Sprint.
The Sprint Retrospective inspects how the team works: people, interactions, processes, tools and the Definition of Done. The team names what went well, what problems it met and how they were (or weren't) solved, and picks the most helpful changes, which can go into the next Sprint Backlog. It lasts at most 3 hours for a one-month Sprint, and it closes the Sprint.
Try it: sort the topics from the end of the team's Sprint into the event where each belongs.
Interactive · Sprint Review or Sprint Retrospective? — try it in the lesson
Takeaway: the Review looks at what was built and what's next; the Retrospective looks at how the team builds it.
Answer each one in hours or minutes, as asked. All the numbers are the Scrum Guide's maximum timeboxes for a one-month Sprint.
Question 1. Halfway through the Sprint, the team learns that the work for one item is bigger than planned. What should happen?
Question 2. The company's director emails a developer: "Drop everything and build this report this week." It doesn't serve the Sprint Goal. What should the developer do?
Question 3. The Daily Scrum has turned into a 40-minute status report to the Scrum Master. What is the best way to get back to Scrum?
Question 4. An item is coded and works on the developer's laptop, but its tests haven't run, which the Definition of Done requires. Can the team show it as Done at the Sprint Review?
Question 5. A market change makes the Sprint Goal pointless in week one. Who can cancel the Sprint?
Question 6. Which of these are true of Scrum as the 2020 Scrum Guide defines it? (pick all that apply)
Workshopy shares this lesson under CC BY 4.0. Anyone may use and change it, with credit to you. Anyone can learn it here, free. A copy in your workspace is yours to change and run live; your students never need an account.
Version 1Current
· First published
Copies are made from the current version. A copy you already have doesn’t change.
WorkshopyOfficial10 stepsQuiz9 interactiveDiagram
gitversion controlbeginners
WorkshopyOfficial16 steps2 quizzes15 interactiveDiagram
workshopyproduct touronboarding
WorkshopyOfficial10 steps2 quizzes10 interactive
data-literacystatisticsmean and median
WorkshopyOfficial10 steps2 quizzes9 interactive
managementokrgoal setting
WorkshopyOfficial10 steps2 quizzes9 interactive
managementproject managementcritical path
WorkshopyOfficial10 steps2 quizzes9 interactive
managementtime managementeisenhower matrix
Comments
No comments yet. Be the first to say how it went.