agile games night

Global Business Services, GBS

Agile Games Night

Copenhagen

2013, April 4th


2 Agile Games Night

Søren Weiss Agile Coach IBM

Finn Leander Agile Coach Danske Bank


Unik mulighed for at netværke.

Udfordring: udvid dit netværk med mindst en person, som du normalt ikke ville have skabt netværk til.

Tip: 90% af ansvaret for enhver relation ligger hos dig selv.

3 Agile Games Night

”Tak til BestBrains”


Agenda

4 Agile Games Night

17:00 - 17:15 • Agenda

17:15 - 17:30 • Agile games

17:30 - 17:45 • Kanban

17:45 - 20:45 • Kanban Software Game (inkl. pause)

20:45 - 21:00 • Wrap up


Ideen med Agile Games Night “Legestue” for ligesindede nysgerrige agilister

Skabe netværk i DK

Ønsker selv at lære flere spil at kende

Løbende arrangementer

Input til blog

5 Agile Games Night


Udsagn om agile games

6 Agile Games Night


Eksempler på spil

7 Agile Games Night


8

Agile Framework

Agile is a conceptual framework for undertaking software engineering projects

Extreme

Programming

(XP)

Unified Process

Crystal Feature Driven

Development Adaptive

SCRUM

Dynamic

Systems

Development

Method (DSDM)

(Coming this

spring/summer)

Kanban

8 Agile Games Night


Kanban origin Kanban is a Japanese word that means “visual card” or “signal card”.

Used in production systems to reduce stock and ensure flow.

The kanbans tie together the production system at Toyota.

9 Agile Games Night


What is Kanban in software development? From “Lean thinking” and “Theory of contraints” models David Anderson evolved “kanban system for software development”, 2001-2004

Focus on flow rather than utilisation of resources

In software we can think of the kanban card as a ”virtual work permit”

Simple with few rules

More tool than methodology

Agile Games Night


Kanban practices

Visualise Work

Limit Work In Progress

Explicit Policies

Measurement and Manage

Flow

Continuous collaborative improvement

11 Agile Games Night


Visualise Work flow

1. Analyse existing work flow (doing states + waiting states)

2. Represent work flow on board (columns and rows)

3. Break down work into manageable pieces

4. Write each work item on a card

5. Put on the wall

Backlog Task description

Ready for dev

Development Ready for prod

Production QA

Done

Flow of work

Agile Games Night


Limit Work-In-Progress

1. Decide the amount of concurrent work.

2. Assign WIP limits to 1) columns, 2) rows, 3) resources.

3. Continuosly strive to reducing the WIP limits.



(2)

Ready for dev (1)

Development

(3)

Ready for prod (3)

Production QA (3)

Done

Flow of work


Make process policies explicit

1. Decide on your process rules

2. Document your process rules

3. Visualise your process rules


(2)

Ready for dev (1)

Development

(3)

Ready for prod (3)

Production QA (3)

Done

Flow of work

Agile Games Night 14


Measure and Manage Flow

1. Focus on flow and not utilisation

2. Measure to provide facts. Use facts to decide on improvements.

Backlog Task

description (2)

Ready for dev (1)

Development

(3)

Ready for prod (3)

Production QA (3)

Done

Flow of work



Continuous collaborative improvement

1. Improve flow

2. Fast feedback on process deficiencies

3. Visibility and measurement enables improvement


(2)

Ready for dev (1)

Development

(3)

Ready for prod (3)

Production QA (3)

Done

Flow of work



17

Kanban - benefits of Kanban? • Bottlenecks become clearly visible in real-time. This leads people to collaborate to optimize the whole value chain rather than just their part. • Provides a more gradual evolution path from waterfall to agile software development, thereby helping companies that previously have been unable or unwilling to try agile methods. • Provides a way to do agile software development without necessarily having to use time-boxed fixed-commitment iterations such as Scrum sprints. Useful for situations where sprints don’t make much sense, such as operations and support teams with a high rate of uncertainty and variability. •Tends to naturally spread throughout the organization to other departments such as HR and sales, thereby increasing visibility of everything that is going on at the company.


One day in kanban land - 1

From: ”Lean from the trenches” by H. Kniberg



One day in kanban land - 2

From: ”Lean from the trenches” by H. Kniberg



The Kanban Software Game

Backlog Planned Analysis Development Test Deploy Done

Doing Done Doing Done Doing Done

Based on Software development Kanban © 2009-2010 Christina Skaskiw 20 Agile Games Night

http://www.skaskiw.biz/resources.html


The goal of the game is to deliver

the highest amount of

business value!



Policy: Planned round is

filled

Policy: Done round and score

field is filled

Blue

Kanban board layout

Backlog Planned Analysis Development Test Deploy Done

Doing Done Doing Done Doing Done

Orange Green Purple

Assign standard cards and fixed date cards to the

backlog

Policy: Analysis round is

filled



Story types Regular story (white cards):

4 rounds (cycle time = 3) = 100% business value

5 rounds (cycle time = 4) = 75 % business value



> 7 rounds (cycle time >6) = 0 business value

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

Fixed date story (yellow cards): • Must complete before or on a deadline

• Only value when delivered on time

• Lead and cycle time is irrelevant for gaining business value

Notice

Minimum number of rounds to complete a story is 4

(round 1 + round 2 + round 3 + round 4).

When you calculate cycle time, you will get the cycle time of 3

cycles (round 4 – round 1).

Flow measurements

Lead time = Completed – Planned

Cycle time = Completed – Started



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.



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.



Self organising

Before starting the game consider how to – decide the priority of the backlog / planned work

– do the daily meetings

– do retrospective meeting



Round flow 1.

Do a daily coordination meeting to decide on strategy

2. Move stories from backlog into

planned to decide what is queued to work on

3. Update board (moving stories)

to reflect status on progress

4. Redistribute dice to decide on

ressource allocation

5. Roll dice to produce progress

6. Update story card values and

move story cards

7. Update measurement chart



User story examples

Story #1

Business value: 40

Planned in round: Started in round: Completed in round: Score:

Analyse: 10 Develop: 12 Test: 11 Deploy: 4

Fixed date story #1

Deadline round 8

Business value: 42

Planned in round: Started in round: Completed in round: Score:

Analyse: 5 Develop: 13 Test: 7 Deploy: 4



Round 1 1.

Decide on strategy and select 5 stories and assign to planned. Fill out ”planned in round” field on each

card.

2. Move X cards from planned to

”Analysis -> Doing” state. Fill out ”started in round” field on these

cards.

3. Prioritise cards in ”Analysis -> Doing

” state

4. Roll dice and assign dice to stories

in priority order

5. Update measurements



Kanban adoption strategy tips

Start with what you do now

Agree to pursue incremental, evolutionary change

Respect the current proces, roles, responsibilites and titles

Adopt as you go!



Lessons learned


Continue doing

Stop doing

Start doing


Remember to connect!


Søren Weiss dk.linkedin.com/in/sorenweiss

twitter.com/sorenweiss

Finn Leander dk.linkedin.com/pub/finn-leander/0/775/725

agile games night

Technology

global business services

development ready

cycle time

roll dice

kanban land

cards

work

story