choosing between scrum and kanban

Post on 02-Jul-2015

1.979 Views

Category:

Technology

0 Downloads

Preview:

Click to see full reader

DESCRIPTION

In this talk from the 2014 SQE Orlando Conference, Cory Foy details how a team can choose between Scrum and Kanban - by understanding that Kanban is a method for evolutionary change that sits inside of an existing process like Scrum or SAFe. He then details how we can use the properties of Kanban to improve our Scrum framework to resolve the pressures and forces of using it on a day to day basis. The talk was recorded by Cory and is available here: http://blog.coryfoy.com/2014/11/video-from-choosing-between-scrum-and-kanban-now-online/

TRANSCRIPT

Choosing Between Scrum and Kanban

Cory Foy | @cory_foy | foyc@coryfoy.com

Scrum

Kanban

ProcessMethod

FrameworkMethodology

System

ProcessMethod

FrameworkMethodology

System

A series of actions or steps taken in order to achieve a particular end

ProcessMethod

FrameworkMethodology

System

A particular form of procedure for

accomplishing or approaching something

ProcessMethod

FrameworkMethodology

System

A basic structure underlying a system,

concept or text

ProcessMethod

FrameworkMethodology

System

A system of methods used in a particular area of

study or activity

ProcessMethod

FrameworkMethodology

System

A set of principles or procedures according to which something is done

RefactoringTest-Driven Development

Listening to Code

Fra

mew

ork

Insp

ect

and A

dap

tKn

owle

dge

Design Patterns

Hedge TrimmerForce Resolved By

Thick Bushes

Lots of Bushes

Tall Bushes

Sharp Blade

Long Reach Arm

Seat for Operator Automated Blade

Fra

mew

ork

Insp

ect

and A

dap

tKn

owle

dge

Scrum

- Remote Team Members - Coordinate Work Across Teams - Dependencies with non-agile teams - New work during sprint - Stories overlapping sprints

Scrum Forces

–Gunther Verheyen

“As long as the methodology is being followed everyone feels safe, because they are formally covered, even in the absence of working

results. ”

http://guntherverheyen.com/2013/03/21/scrum-framework-not-methodology/

Even InThe AbsenceOf Working

Results

People

Scrum is

Scrum

MeetingsRoles

Artifacts

Scrum Master

Product Owner

Team

Burn Down

Product Backlog

Sprint Backlog

Sprint Demo

Stand Up

Sprint Planning

Scrum

MeetingsRoles

Artifacts

Process Vision

Product Vision

Delivery

Visual of Delays

Key Inventory

Goal Inventory

Fast Feedback

Rapid Comms

Focused Plan

Process Vision

Product Vision

Delivery

Visual of Delays

Key Inventory

Goal Inventory

Fast Feedback

Rapid Comms

Focused Plan

Know What We Need

Know How We Work

Work In Small

Chunks

Get Frequent Feedback

Know What We Need

Know How We Work

Work In Small

Chunks

Get Frequent Feedback

4 Immutable Attributes of Successful Projects

Scrum Master

Product Owner

Burn Down

Product Backlog

Sprint Backlog

Sprint Demo

Stand Up

Sprint Planning

Know What We Need

Know How We Work

Work In Small

Chunks

Get Frequent Feedback

Expect Well Less Well Change

What we wanted to happen What went

well

What didn’t go so well

What we want to

try

K A N B A N

A Method for Evolutionary Change Management

Visualize Workflow

Measure and Manage Flow

Limit Work-in-process

Make Process Policies Explicit

Use Models for

Improvement

5 Core Properties of Kanban

Visua

lize

Work

flow

Backlog WIP Done

Visua

lize

Work

flow

Story

Poin

ts

Days in Sprint

“The Lemming”

Visua

lize

Work

flow

Backlog Analysis Dev Testing Done

Visua

lize

Work

flow

Backlog Analysis Dev Testing Done

Visua

lize

Work

flow

7 weeks of work

40 weeks to do the 7 weeks

Lim

it W

ork

-In-P

roce

ssLittle’s Law

L = λW

Response Time = Number In System / Throughput

# In System = Time * Throughput

Lim

it W

ork

-In-P

roce

ss

Lim

it W

ork

-In-P

roce

ss

Lim

it W

ork

-In-P

roce

ss Backlog Analysis Dev Testing Done

4

Lim

it W

ork

-In-P

roce

ss Backlog Analysis Dev Testing Done

4

Lim

it W

ork

-In-P

roce

ss BL Analysis Dev Testing Done

4

Ready for Test

Lim

it W

ork

-In-P

roce

ss

Lim

it W

ork

-In-P

roce

ss BL Analysis Dev Testing Done

4

Ready for Test

Mea

sure

and M

anag

e Flo

w

Mea

sure

and M

anag

e Flo

w

Mea

sure

and M

anag

e Flo

w

BL Analysis Dev Testing Done

4

Ready for Test

Mea

sure

and M

anag

e Flo

w

BL Anal

ysis

Dev Testing Done

3

Ready for Test

Write Test

2

Expect Well Less Well Change

What we wanted to happen What went

well

What didn’t go so well

What we want to

try

Mea

sure

and M

anag

e Flo

w

Mak

e Pr

oce

ss P

olici

es E

xplici

t

Mak

e Pr

oce

ss P

olici

es E

xplici

t

Standard Scrum

Standard Process

New Process

New Process

Inspect and Adapt

Inspect and Adapt

Standard Work

Ascend

Acclimate

Use

Model

s to

Rec

ogn

ize

Impr

ove

men

t Theory of Constraints Deming

Complex Adaptive Systems

Fra

mew

ork

Insp

ect

and A

dap

tKn

owle

dge

Scru

mVisualize Workflow

Measure and Manage Flow

Limit Work-in-process

Make Process Policies Explicit

Use Models for

Improvement

Know What We Need

Know How We Work

Work In Small

Chunks

Get Frequent Feedback

Kanban

Thanks!@cory_foy | Cory Foy | foyc@coryfoy.com

http://www.coryfoy.com

top related