Introduction to kanban lean ghm_02022010

Introduction to KANBAN & LEAN

Mads Troels Hansen

BestBrains, February 2nd 2010

• Inspiration, theory, examples

Kanban

VisualMgt.

Lean Agile

Kaizen

Your expectations?

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.

Scrum extended with Kanban

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”

• Kanban and kanban

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

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

• Lean (TPS) and Kanban

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

Kanban

Scrum vs. Kanban

PullScrum vs. K

ScrumPush from business/product mgt.

KanbanDownstream pull from upstream

Task board game

ToDo In Prog Review Done

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

Scrum vs. Kanban

Task board game

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

X New request from a customer

Scrum vs. Kanban

Task board game

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

Scrum vs. Kanban

Task board game

Queue (3)

In Prog (2)

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

Scrum vs. Kanban

Task board game

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

Scrum vs. Kanban

Task board game

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

Scrum vs. Kanban

Task board game

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

Problem with test server

Queue full

Scrum vs. Kanban

Task board game

Queue (3)

In Prog

Review (2)

Que (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

Fixing the test server

Scrum vs. Kanban

Task board game

Queue (3)

In Prog

Review (2)

Queue (2)

Test Doc Deploy

Test Queue (2)

Doc Queue (2)

Deploy

New bug reportedY

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

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

• 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

• Virtual Kanban board (Custom solution against TFS)

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 youmth@bestbrains.dk

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

- Peter Scholtes

@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

Introduction to kanban lean ghm_02022010

Technology

Transcript of Introduction to kanban lean ghm_02022010

Lean Management and Kanban System

Kanban Iceberg, Lean Kanban North America 2015 conference

Key Note - Lean Kanban France 2013 - Kanban Evolutionary Management

Agil scrum lean kanban Infografía

Lean Software Development - Net Objectives · with, Lean-Kanban University kanban Kanban LKU Kanban ... Kanban as a Team Development Process Often reducing batch size is all it takes

Week12 JIT TPS Kanban Lean

Discovery Kanban - Lean Kanban UK 2014

Lean Kanban Practitioner

Jit (us), kanban, lean

An Introduction to Kanban and Lean Software Development · Kanban is a transparent, work-limited, pull system. [2] Kanban is the result of practitioners applying lean principles to

Lean Kanban France2013 : kanban for managers

Lean / Kanban

Lean Kanban to Lean Business

Lean kanban benelux 2016 - Lean Startup simulation

IIT Academy: Lean & Kanban 102

Lean , Pull System & Kanban |iZenBridge

Lean out your backlog - Lean and Kanban Belgium 2010

Kanban, Lean, and Scrum

Go Lean IT with Kanban

Lean Kanban - ESIC Business & Marketing School · WORKSHOP Lean & Kanban Auto-organización con Kanban. Controlar el trabajo en curso (WIP). Realización de métricas. Optimización