Lean/Kanban – Going Lean/Kanban – Going beyond Scrumbeyond Scrum

Kamon Treetampinij (Korn4D)Kamon Treetampinij (Korn4D)

About myselfAbout myself

Agile coach with more than Agile coach with more than 10+ years of hands-on 10+ years of hands-on

experience in the industry experience in the industry including the rare and including the rare and

repetitive success cases of repetitive success cases of self-managed team building in self-managed team building in

both local and international both local and international enterprisesenterprises

Scrum is goodScrum is good

• We are support teamWe are support team

• We keep failing our sprintWe keep failing our sprint

• The scope is changing every dayThe scope is changing every day

• The story is longer than a sprintThe story is longer than a sprint

• We have architect teamWe have architect team

• Etc.Etc.

butbut……

ScrumScrum

into small, cross-functional, self- into small, cross-functional, self- organizing teams.organizing teams.

Split your Split your organizationorganization

ScrumScrum

into a list of small, concrete deliverables. Sort the list by priority into a list of small, concrete deliverables. Sort the list by priority and estimate the relative effort of each item.and estimate the relative effort of each item.

Split your Split your workwork

ScrumScrum

into short fixed-length iterations (usually 1 – 4 weeks),into short fixed-length iterations (usually 1 – 4 weeks), with potentially shippable code demonstrated after with potentially shippable code demonstrated after

each iteration. each iteration.

Split Split time time

ScrumScrum

and update priorities in collaboration with the customer, based on and update priorities in collaboration with the customer, based on insights gained by inspecting the release after each iteration. insights gained by inspecting the release after each iteration.

Optimize the release Optimize the release planplan

by having a retrospective after each by having a retrospective after each iteration. iteration.

Optimize the Optimize the process process

So, for ScrumSo, for Scrum

• Large groupLarge group

• Spending a long timeSpending a long time

• Building a big thingBuilding a big thing

Instead Instead ofof

We We havehave

• Small teamSmall team

• Spending a short timeSpending a short time

• Building a small thingBuilding a small thing

KanbanKanban

• Visualize the workflowVisualize the workflow

• Limit Work In Progress Limit Work In Progress (WIP)(WIP)

• Measure the lead timeMeasure the lead time

Scrum is more prescriptive Scrum is more prescriptive than Kanbanthan Kanban

Scrum prescribes rolesScrum prescribes roles

• Product OwnerProduct Owner

• TeamTeam

• Scrum MasterScrum Master

Scrum prescribes Scrum prescribes timeboxed iterationstimeboxed iterations

Single Single CadenceCadence

Kanban CadenceKanban CadenceThree Three

CadenceCadence

Event Event DrivenDriven

Kanban limits WIP per workflow Kanban limits WIP per workflow state, Scrum limits WIP per state, Scrum limits WIP per

iterationiteration

So in Scrum WIP is limited per unit of time.So in Scrum WIP is limited per unit of time.

In Kanban WIP is limited per workflow In Kanban WIP is limited per workflow state.state.

Example: Experimenting with WIP Example: Experimenting with WIP limits in Kanbanlimits in Kanban

Example: Experimenting with WIP Example: Experimenting with WIP limits in Kanbanlimits in Kanban

Example: Experimenting with WIP Example: Experimenting with WIP limits in Kanbanlimits in Kanban

Example: Experimenting with WIP Example: Experimenting with WIP limits in Kanbanlimits in Kanban

Example: Experimenting with WIP Example: Experimenting with WIP limits in Kanbanlimits in Kanban

Scrum board is reset Scrum board is reset between each iterationbetween each iteration

Scrum prescribes cross-Scrum prescribes cross-functional teamsfunctional teams

Scrum backlog items Scrum backlog items must fit in a sprintmust fit in a sprint

Scrum prescribes Scrum prescribes estimation and velocityestimation and velocity

Scrum working on Scrum working on multiple products multiple products

simultaneouslysimultaneously

Kanban working on Kanban working on multiple products multiple products

simultaneouslysimultaneously

Minor DifferencesMinor Differences

• Scrum prescribes a prioritized product backlogScrum prescribes a prioritized product backlog

• In Scrum, daily meetings are prescribedIn Scrum, daily meetings are prescribed

• In Scrum, burndown charts are prescribedIn Scrum, burndown charts are prescribed

Look at the chartsLook at the charts

One day in Kanban-LandOne day in Kanban-Land

One day in Kanban-LandOne day in Kanban-Land

One day in Kanban-LandOne day in Kanban-Land

One day in Kanban-LandOne day in Kanban-Land

ReferenceReferencehttp://www.infoq.com/minibooks/kanban- scrum-http://www.infoq.com/minibooks/kanban- scrum-

minibookminibook

http://bit.ly/http://bit.ly/kanbanbkkkanbanbkk

““There is no dumb questions.” There is no dumb questions.”

See you again atSee you again at