Kanban Software Game

BestBrains

29. oktober

2013

Søren Weiss
Agile Coach
@sorenweiss
 Agile Games
¤  The gamification trend
¤  Conferences
¤  Boot camps
¤  Certification programs
¤  Agile Games Nights

¤  Game types and complexity

¤  "Tell me, I'll forget. Show me,

I'll remember. Involve me, I'll
understand”

¤  And It’s fun J

2
 Gaming examples

3
 What is Kanban?

Agile Framework
Manifesto – principles - values

Agile is a conceptual framework for undertaking software engineering projects

Dynamic
Extreme
Systems
Programming Unified Process SCRUM
Development
(XP)
Method (DSDM)

Feature Driven
Crystal Adaptive Kanban
Development

Source: IBM

4
 Kanban practices

Measurement Continuous
Visualise Limit Work In Explicit
and Manage collaborative
Work Progress Policies
Flow improvement

5
 Kanban software game

Goal: To deliver the highest amount of business value

6
 Kanban board layout

WIP limit WIP limit WIP limit

3 3 4

Backlog   Planned   Analysis   Development   Test   Deploy   Done  

Doing   Done   Doing   Done   Doing   Done  

Policy Policy Policy

”Planned in ”Started in ”Completed in
Round” is round” is round” and
filled filled Score field is
filled

7
 Story types
Regular story (white cards): Notice
4 rounds (cycle time = 3) = 100% business value
5 rounds (cycle time = 4) = 75 % business value Minimum number of rounds to
6 rounds (cycle time = 5) = 50 % business value complete a story is 4
7 rounds (cycle time = 6) = 25 % business value (round 1 + round 2 + round 3 + round 4).
> 7 rounds (cycle time >6) = 0 business value
When you calculate cycle time, you
will get the cycle time of 3 cycles
Fixed date story (yellow cards): (round 4 – round 1).
•  Must complete before or on a deadline
•  Only value when delivered on time
•  Lead and cycle time is irrelevant for gaining Flow measurements
business value
Lead time = Completed – Planned
Cycle time = Completed – Started
Expedite story (red cards):
•  Must complete in 4 rounds
•  Can break WIP limits
•  Only value when on time
•  Must be done even if no value

8
 Dice and flow
1.  Daily meeting (start of each round) decides
¤  Placement of dice
¤  What to work on

2.  When rolling dice you roll for one column at a time.

3.  Dice can be moved from (home) column to another column. Dice score is reduced to half
the score if dice is moved from home column to another column. Hence a dice roll of value 1
or 2 = value 1, a value 3 or 4 = value 2 and value 5 or 6 = value 3.

4.  When counting dice score, count each dice by themselves. Do not add all dices together
and then divide, it will give the wrong result when many dices are moved.

5.  Unused dice score is lost.

6.  In one round you can only work a story in one column (state). Hence a story cannot be
worked on in several columns in the same round.

7.  Place stories at the bottom of the a column if team decides not to complete it (e.g. if the
team thinks that it is not possible to gain business value). This is not possible for expedite stories.

9
 Measurements
¤  Lead time
¤  is calculated as = Done round – Planned round

¤  Cycle time

¤  is calculated as = Done round – Analysis round

¤  Accumulated Earned Business value

¤  is calculated based on cycle time.

¤  Cumulative flow diagram

¤  Is calculated by counting number of story cards per state.

10
 Round flow 1.
Do a daily coordination
meeting to decide on
strategy

2.
7. Move stories from backlog
Update measurement chart into planned to decide
what is queued to work on

3.
6.
Update board (moving
Update story card values stories) to reflect status on
and move story cards
progress

5. 4.
Roll dice to produce Redistribute dice to decide
progress on ressource allocation

11