Introduction to kanban lean ghm_02022010

1

Introduction to KANBAN & LEAN

Mads Troels Hansen

BestBrains, February 2nd 2010

2February, © 2010 BestBrains, Mads Troels Hansen 2

• Inspiration, theory, examples

Kanban

VisualMgt.

Lean Agile

Kaizen

Your expectations?

3February, © 2010 BestBrains, Mads Troels Hansen

Why Kanban and Lean?


Kanban and Visual Management (1/3)

• Aligned goals



• More contribution



Bottlenecks and Quality


Mads Troels Hansen: Kanban Experience

• Agile and Lean Coach at BestBransAgile and Lean Coach, Management Consultant

• Development Director at Omada 7 different nationalities, products, projects and support, 4 teams, global clients

• Development Director, co-founder at SoftwarePeople Products, projects and hosting, 6 teamsStarted Offshore in Bangladesh, SoftwarePeople Ltd, 25+ people

• IT Director at PeopleGroup Started Offshore graphical production in Bangladesh.

• Development Manager at NetPeople15+ nationalities, 2 teamsAlso experience as developer, architect, project manager.

2010

2008

2006

2004

Scrum extended with Kanban

2003

Kanban and offshore teams

Kanban talks, training, coaching

Kanban and Visual Management

Scrum boards with offshore teams

Kanban techniques

Hyper productive offshore teams

Started Offshore production company

Agile+XP, Task Boards


Agenda•Introduction w. basic theory (20 min)• break (5 min)

•Kanban, Scrum, Scrumban (~20 min) • break: Sandwich (15 min)

•Examples of Kanban boards (20 min)• break (5 min)

•Kanban on Whiteboard (20 min)•5 steps to get started (5 min)


Kanban development

• A very simple tool

Prescriptive Adaptive

KanbanSCRUMExtreme Programming

RUPCMMI (ML 3-5)

”Whatever”

9


• Kanban and kanban

• Toyota Production System (TPS)• Taiichi Ohno ( 大野耐 )• A kan-ban

– A physical card (kan)– A signaling device (ban)


• Lean (TPS) and Kanban


FLOW


PULL


CADANCE


Release per

Feature


Systems Thinking


Value Streams


Limit Work-In-Progress


Schedule large work orders and align resources by workflow

Schedule small work orders and align resources by schedule

Schedule small work orders and align resources by workflow


Kanban, Scrum, Scrumban


Scrum and KanbanTwo process tools

Accept test

DeploymentSales Analyze Dev

Scrum

Kanban

Scrum vs. Kanban


PullScrum vs. K

anban

ScrumPush from business/product mgt.

KanbanDownstream pull from upstream


Task board game

A

ToDo In Prog Review Done

B

C

D

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

B

C

D

E

F

E

F

PBL

PBL

Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BC

E

F

X

X

X New request from a customer

PBL

PBL

D

E

F

Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

B

E

F

X

C

PBL

PBL

X

D

E

F


Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

E

F

C

XY

New bug reportedY

Y

PBL

PBL

X


Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

E

F

C

XY

Y

PBL

PBL

X

New bug reportedY


Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

E

F C

XY

Y

PBL

PBL

X

New bug reportedY


Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

C

XY

Y

PBL

PBL

X

New bug reportedY


Problem with test server

Queue full

E

F

Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog

Review (2)

Que (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

C

XY

Y

PBL

PBL

X

New bug reportedY


Fixing the test server

E

F

Scrum vs. Kanban


Task board game

A


B

C

D

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

A

BD

E

F

C

XY

Y

PBL

PBL

X

New bug reportedY


Kanban: Visualize bottlenecks fast, and enable frequent business prioritization.E

F

Scrum vs. Kanban

Scrum: Scope commitment more focus to developers.


Business prioritization

• Scrum– Don't interrupt WIP and you may only adjust our

work plan every iteration.

• Kanban– Don't interrupt WIP and you may change

prioritization any time.

Scrum vs. Kanban


Commitment and goals

• Scrum– Commit to a scope

• Kanban– Commit to deliver working features within a time

limit.– SLA: “…always deliver within 14 days…”

Scrum vs. Kanban


Planning

• Scrum– Combined planning and release cycles.

• Kanban– Planning and release can be separated.– Frequent planning with release interval related to

cost of release and business feedback.

Scrum vs. Kanban


WIP

• Scrum– Limit WIP pr. iteration

• Kanban– Limit WIP pr. workflow state

Scrum vs. Kanban


Reporting

• Scrum– Product Backlog Burndown chart– Sprint Backlog Burndown

• Kanban– Cumulative Flow Diagrams (CFD)

Scrum vs. Kanban


Quick summaryKanban Scrum (Iterations)

Change prioritization any time Iterations

No roles Roles defined (PO, SM, Team)

Commitment to deliver capacity, SLA Commitment to a scope

Seperated planning and release Combined planning and release

Limits WIP pr. Workflow state Limits WIP pr. iteration

Queues Backlog

Can use CFD Burndown charts

Break down features, no estimation Estimation and velocity

Release Cycle can be the Cadence Iteration is the Cadence

Throughput Velocity

Scrum vs. Kanban


EXAMPLES OF KANBAN BOARDS




• Traditional task boards


Just get started


• Devs, tests, technical writer, operations, support


Personal Kanban


• Traditional task board extended with limits


• Kanban board


• Kanban board


• Kanban board


• Kanban board


• Kanban board


• Virtual Kanban board (Custom solution against TFS)


Rally


Version One


Target Process


Jira Greenhopper


Kanban on Whiteboard




• Kanban – Get started

My Top 5

Use 2 minutes to create your personal list

My Top 51. Draw your end-to-end process (Value Stream)2. Map your process to a physical Task board3. Start using the board4. Limit work-in-process with WIP limits5. Measure cycle time and lead time

n. Find bottlenecks, do Kaizen and improve


• Kanban – Take Away

A Kanban system, starts to focus on flow and cycle time of delivered work and gives a way to visualize and resolve bottlenecks


Thank [email protected]

People don’t resist change, they resist being changed.

- Peter Scholtes

@MadsTH

mailto:[email protected]

http://twitter.com/madsth


Some references• Lean Software Development - An Agile Toolkit, Mary & Tom Poppendieck,

2003• Implementing Lean Software Development, Mary & Tom Poppendieck,

2007• The Enterprise and Scrum, Ken Swaper, 2007• Factory Physics, W. Hopp, 3rd edition, 2008• Agile management, David Andersson, 2004• Scrumban, Corey Ladas, 2009• Kanban vs Scrum – A practical guide, Henrik Kniberg, April 2009• Kanban intro, Karl Scotland,

http://availagility.wordpress.com/2008/10/28/kanban-flow-and-cadence/• YahooGroup: Kanbandev• Software Excellence http://www.bestbrains.dk/dansk.aspx/Rådgivning

http://availagility.wordpress.com/2008/10/28/kanban-flow-and-cadence/




http://www.bestbrains.dk/dansk.aspx/R%C3%A5dgivning

Date post:	06-May-2015
Category:	Technology
Upload:	mads-troels-hansen
View:	4,535 times
Download:	6 times

Introduction to kanban lean ghm_02022010

Technology