Easier to read with cream paper, a tint, more contrast or larger text? Choose your colours and text, once, for every page.

Preview

DS 2.2: Scrum and Kanban for support teams

This is the first page of the lesson. Read it and have a go at the activities. The rest is in the full lesson.

60 minutes

Twelve jobs and three people

A help desk has twelve jobs on Monday morning. Three technicians start all twelve at once. By Friday, nothing is finished.

Two ways of working fix this in different ways. One works in short bursts. The other limits how much is started.

Key words

WordWhat it means
Agilea way of working in small steps, with feedback after each step
Scruman agile method that works in short bursts called sprints
Sprinta short, fixed period of work, often two weeks
Product ownerthe person who decides what is most important
Scrum masterthe person who helps the team follow Scrum
Backlogthe list of work still to do
Kanbanan agile method that shows work on a board
Bottlenecka step where work piles up and waits
WIP limitthe most cards allowed in a column at once
Capacityhow much work a team can do

The cells students fill in are left blank in this preview.

By the end of this lesson

Note

I can describe how Scrum and Kanban organise work, and what a daily scrum, a bottleneck and a WIP limit are.

Starter

Have a go

Starter

3 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

Scrum: roles and rules

Scrum has three roles. The Scrum Guide calls them accountabilities. The product owner says what matters most. The scrum master helps the team follow the rules and removes blockers. The developers do the work. In support, they are the technicians.

Scrum has fixed rules. Work is done in sprints. A sprint has a set length of one month or less, and a goal.

Events and artefacts

NameKindWhat it is
Sprint planningEventThe team picks work for the sprint
Daily scrumEventA 15 minute meeting to plan the next day of work. Many teams share what they did, what they will do and what blocks them
Sprint reviewEventThe team shows the finished work
RetrospectiveEventThe team talks about how to work better
Product backlogArtefactAll the work wanted, in order of importance
Sprint backlogArtefactThe work chosen for this sprint
IncrementArtefactThe finished, working result of the sprint

The cells students fill in are left blank in this preview.

Check: Scrum

Have a go

Check: Scrum

4 questions
Have a go: your answers are marked here and then forgotten. Sign in if you would like your score kept, and to pick up where you left off.Sign in to keep your score

Your answers are marked here and are not kept. A college account keeps every student’s marks.

The lesson goes on

7 more parts of this lesson are in the full curriculum, with the tasks, the final check and the labs. A college account gives your students all of it.