Agile och Kanban på driftavdelningen - Tomas Bjorkholm

Post on 23-Jan-2015

790 views 2 download

Tags:

description

 

Transcript of Agile och Kanban på driftavdelningen - Tomas Bjorkholm

123-04-10

Who am I?

Tomas BjörkholmScrum, Agile & Lean coach/mentorContact:

0708-251632Tomas.bjorkholm@crisp.se

Agile/Kanban på driftavdelningenAgile/Kanban på driftavdelningen

2Tomas Björkholm 2

Scrum characteristics

Transparency – exposes problems early and builds trustStrict prioritization – the fundamental for focusEmpirical (invent/implement) & adaptive

Short feedback loopContinuous improvement (Kaizen)Frequent & regular delivery of working softwarePlans are needed, but they are always wrong

Cross-functional self-organizing teamPull scheduling – team chooses how much work to commit toTimeboxingFace-to-face communicationSimple tools

But, operation can’t commit, we don’t know how much support there is

Limit work-in-progress

Balance demand to

capacity

3

Kanban characteristics

Wanted elementsClear priorityFocus (reduce work-in-progress)Limit demand after capacityTransparency

Key metrics is cycle time rather than velocity

Tomas Björkholm 3

Cycle time = Capacity

Work in progress

6

Kanban basic

Tomas Björkholm 6

Kanban limit of 3

A Kanban = new feature, bug or change request

12

3

Product Owner

Team

7

Kanban board for non cross-functional teams

Tomas Björkholm 7

DeployDevDBDesignReq

Prod

Proj

PerfBuild

DeployDingo

Fix

Dingo

Dingo

Dingo

Product backlog

Capacity orDemand limitation

Empty slotUsed slot

Work in progress

Waiting for a free kanban in Req’s column.

Places on prio order

Dingo

Dingo

Dingo

Next

8

Kanban board – Scrum look-a-like- Used for improvement projects within operation teams -

Tomas Björkholm 8

DoneTo do

ProdProd

bmx

BuildBuild

Limit, max2 tasks per memb.

Working on

qdb

sö dh

bmx

erkjhf

erwoi

gi

sfs

arajkh

hdtes

SAÖFSDJ

SAÖFSDJ A-LRJA-LRJ

SAJSAJ

Prio

Urgent

Dailyduty

2

jfh

wer

Capacity orDemand limitation

On planning meetingbreak down and fill

empty slots

bmxPerfPerf qdb

sö dh

sfsjfh

wer

1

9

Kanban board – A typical scenario

Tomas Björkholm 9

DoneTo do

ProdProd

BuildBuild

Working on

qdb

bmx

kjhf

woi

gi

sfs

arajkh

hdtes

SAÖFSDJ

SAÖFSDJ A-LRJA-LRJ

SAJSAJ

Prio

Urgent

Dailyduty

2

wer

On planning meetingbreak down and fill

empty slots

bmxPerfPerf qdb

sö dh

sfsjfh

wer

1

hdteshd

3

10

Kanban board – For small stories (< 1w) - Add a buffer -

Tomas Björkholm 10

Prepared Backlog

InstallInstall

ConfigConfig

bmxer

kjhf

bmxer

kjhf

SAÖFSDJ

SAÖFSDJ A-LRJA-LRJ

SAJSAJ

On planning meetingbreak down and fill

empty slots in prepared queue.

Team pulls from Prepared queue whenever there is a empty slot.

DoneTo do

ProdProd

bmx

BuildBuild

Working on

qdbsö

dh

bmx

erkjhf

erwoi

gi

sfs

arajkh

hdtes

Prio

Urgent

Dailyduty

2

jfh

wer

bmxPerfPerf qdb

sö dh

sfsjfh

wer

1

11

Kanban process

Week 1 Week 2 Week 3

Timeline

Sprint-planning

Review andRetrospective

ProduktBacklog

Daily Scrum

Daily meeting

Tomas Björkholm

release1.3.0

Sprint-planning

Releases can still be

periodic

Week 4

Very important to

improve

12

Result

Tomas Björkholm 12

Timeline

Timespent

Unplanned

Daily dutiesDaily duties

Pre-emptive work

13

That’s it! Questions?