How you work today Task 1 is done as a team on a Kanban copy of your board. Tasks 2 and 3 are done by each student in a spreadsheet and on paper. Marks are given to each student. |
1. Objectives
By the end of this practical you will be able to:
- Turn your Scrum board into a Kanban board with WIP limits and explicit policies.
- Calculate lead time, cycle time and throughput from a card log using spreadsheet formulas.
- Find a bottleneck, use Little's Law, and recommend Scrum, Kanban or a mix for your project.
2. Word bank
Word | Simple meaning | Real-world example |
|---|---|---|
WIP limit | the most cards allowed in a column | In Progress (max 3) |
policy | a written rule that everyone follows | "Done = tested and shown to the PO" |
lead time | days from card added to done | added day 1, done day 4 = 3 days |
cycle time | days from work started to done | started day 2, done day 4 = 2 days |
throughput | cards finished per day | 8 cards in 10 days = 0.8 per day |
bottleneck | the column where cards pile up | five cards waiting in Testing |
3. Background
Kanban (Lecture 06) has no sprints. Cards flow across the board, and each column has a WIP limit. You may pull a card into a column only when it has space.
Little's Law: average lead time = average WIP ÷ average throughput. With the same speed, less WIP means each card finishes sooner.
Real-world example: the bank queue A bank branch has 3 counters. If 30 people are inside, each waits a long time even though the counters work at the same speed. Letting people in only when a counter is nearly free does not make the counters faster, but each person spends less time inside. WIP limits do the same for cards. |
4. Before you start
1. In Trello, open your team board and use ... → Copy board to make SE401 - <Team> - Kanban. (Keep your Scrum board unchanged.)
2. Open Excel or Google Sheets for Task 2.
5. Time plan (50 minutes)
Time | What you do |
|---|---|
0:00-0:05 | Teacher: show a Kanban board with WIP limits in the list names |
0:05-0:15 | Parts A, B and C (on paper) |
0:15-0:23 | Task 1: Kanban board, WIP limits and policies |
0:23-0:33 | Task 2: flow metrics in a spreadsheet |
0:33-0:45 | Task 3: bottleneck, Little's Law and recommendation |
0:45-0:50 | Teacher checks; start Part E (finish at home) |
Part A: Warm-up: name the measure
A card was added on day 2, started on day 4 and done on day 9.
(a) What is its lead time?
(b) What is its cycle time?
(c) How long did it wait before work started?
Part B: Predict
Board: In Progress (max 3) has 3 cards; Testing (max 2) has 2 cards. A developer finishes coding a card.
(a) Can the card move to Testing? What should the developer do?
(b) A team has 9 cards in progress and finishes 3 per day. Average lead time? What if WIP is cut to 6 at the same throughput?
Part C: Find the flaw
Each item has ONE main problem. Name it.
(1) A 5-person team's board has no limits and 14 cards in In Progress.
(2) The team measures "cycle time" from the day a card was added to the board.
(3) Policy card: "Done = code written."
Part D: Graded tasks (10 marks)
Task | Level | What you build | Marks |
|---|---|---|---|
T1 | Easy | Build a Kanban board with WIP limits | 3 |
T2 | Medium | Calculate flow metrics | 3 |
T3 | Challenge | Find the bottleneck and recommend | 4 |
Total | 10 |
T1 Build a Kanban board with WIP limits (3 marks · Easy)
1. On the Kanban copy, rename the lists to: Backlog | Ready (max 5) | In Progress (max 3) | Testing (max 2) | Done. For a team of 4, use In Progress (max 2).
2. Move cards so that no column breaks its limit.
3. Add a Policies card at the top of Backlog with three rules: when a card is Ready, when it is Done, and the pull rule ("take a new card only when the next column has space").
Sample: Policies card Ready = story has acceptance criteria and points. Done = tested against acceptance criteria, reviewed by a teammate, shown to the PO. Pull rule = only pull a card when the next column is below its limit; if Testing is full, help test. |
T2 Calculate flow metrics (3 marks · Medium)
1. Enter this card log in a spreadsheet (columns A-D):
2. A: added 1, started 2, done 4 · B: 1, 3, 6 · C: 2, 3, 5 · D: 2, 5, 9 · E: 3, 4, 7 · F: 4, 6, 8 · G: 5, 7, 10 · H: 6, 8, 10
3. Column E Lead time with the formula =D2-B2; column F Cycle time with =D2-C2; copy down.
4. Below, calculate the average lead time and cycle time with =AVERAGE(...), and the throughput over the 10 days with =COUNT(D2:D9)/10.
5. Which card waited longest before work started?
Sample: First rows Card | Added | Started | Done | Lead | Cycle A | 1 | 2 | 4 | 3 | 2 B | 1 | 3 | 6 | 5 | 3 |
T3 Find the bottleneck and recommend (4 marks · Challenge)
1. A team counted the cards in each column at the end of five days:
2. In Progress: 3, 3, 3, 3, 3 · Testing: 1, 2, 3, 4, 5 · Done: 4, 4, 5, 5, 5
3. (a) Which column is the bottleneck? How do you know?
4. (b) Give two actions that would fix it.
5. (c) Today the team has 6 cards in progress and finishes 2 per day. Use Little's Law to find the average lead time now, and with a WIP limit of 4 (same throughput).
6. (d) Write 3-4 sentences: should your project team use Scrum, Kanban or Scrumban? Give two reasons.
Sample: Part of a good answer to (d) "We will use Scrumban: two-week sprints with a review for our teacher, plus WIP limits (In Progress max 3, Testing max 2) because last week testing piled up." |
Part E: Post-lab questions
1. Why does lowering WIP shorten lead time even if the team does not work faster?
2. Give one situation where Kanban suits better than Scrum, and one where Scrum suits better.
Marking rubric
Task | Marks | Full marks when ... |
|---|---|---|
T1 Build a Kanban board with WIP limits | 3 | 1 mark: lists with WIP limits 1 mark: no column over its limit 1 mark: Policies card with three clear rules |
T2 Calculate flow metrics | 3 | 1 mark: lead and cycle time with formulas 1 mark: correct averages 1 mark: throughput and card D identified |
T3 Find the bottleneck and recommend | 4 | 1 mark: bottleneck with evidence 1 mark: two sensible actions 1 mark: both Little's Law results 1 mark: reasoned recommendation |
Parts A, B, C and E are not marked separately; they prepare you for the tasks and the viva.
Submission
- The teacher checks your Kanban board and spreadsheet before you leave.
- Upload to the LMS by the end of the day: the Kanban board link, your flow-metrics spreadsheet and your Task 3 answers.
- Copy your WIP limits, the averages from Task 2 and your recommendation (d) into the Lab Book (Practical 06 page).