scrum with kanban; small adjustments, big improvements

Post on 31-Oct-2014

1.242 Views

Category:

Technology

1 Downloads

Preview:

Click to see full reader

DESCRIPTION

Scrum with Kanban; small adjustments, big improvements.Kanban and Scrum are not orthogonal to each other; in fact they can be quite complementary! Join us and learn the insights for improving the delivery of SW projects based on the Scrum framework via Kanban add-ons.

TRANSCRIPT

Johann Arispe Business Analyst

jarispe@thoughtworks.com

Scrum with Kanban;Small adjustments,

big improvements

Paulo Caroli Agile Coach

pcaroli@thoughtworks.comTwitter: @paulocaroli

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

Image available at www.mountaingoatsoftware.com/scrum

Image available at www.mountaingoatsoftware.com/scrum

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

Workflow

A workflow is a sequence of steps

and activities of work performed by

a person or a team to achieve a

specific goal.

Stage 1 Stage 2 Stage

N

Final Goal

(Done)

Workflow examples

On Agile projects,

we typically work with

User Stories…

Overall project

requirement

For each User Story…

The SW development workflow…

Analysis Design Code Test Deploy

Visible Workflow

The workflow stages

The workflow stages

the work

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

Pushing the work

10

5

9

3117

21

4

12

JohnSuzy

Paul

Amy

Dan

Sprint Backlog Engineers

10

5

9

31

17

21

4

12 John

Suzy

Paul

Amy

Dan

Sprint Backlog Engineers

Pulling the work

10

5

9

3117

21

4

12

JohnSuzy

Paul

Amy

Dan

Sprint Backlog Engineers

10

5

9 3118

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev In QCBacklog

7

Ready for

Sign off

31

10

5

9

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

9

In QC

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

A Sprint example…

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

Another team…

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

What about that Sprint review

meeting on Monday?

Common Kanban terms…

Doing DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

Doing DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Doing DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

Lead Time

10 10Day 1Day 6

Doing DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

Day 1Day 1

Cycle time

Day 2

Day 3Day 3

Kanban mechanics

DoingDoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

ThroughputDemand

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

ThroughputDemand

Balance demand against throughput

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Lead Time

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Lead Time

increased lead time => poorer quality

Doing

(Limit) DoneTo Do

10

5

9

3118

17

21

4

75

112

John

Suzy

Paul

Amy

WIP

Lead Time

# WIP is proportional to average lead time

Before and After

example

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev In QCBacklog

7

Ready for

Sign off

31

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

Any problem?

9

10

5

18

17

21

4

5 1

12

John Suzy

Paul Amy

Dan

In Dev Backlog

7

Ready for

Sign off

31

In QC

Stop starting

and start finishing!

WIP Limit

9

10

5

18

17

21

4

7

5 1

12

John Suzy

Paul Amy

Dan

31

In Dev

(2)

Backlog Ready for

Sign offIn QC

(3)

Visible Workflow,

Pull System and WIP Limit

9

10

5

17

21

4

7

5

12

John Suzy

Paul Amy

Dan

31

In Dev

(2)

Backlog

18

1

Ready for

Sign offIn QC

(3)

Dev Complete for Card #9

9

10

5

17

21

4

7

5

12

John Suzy

Paul Amy

Dan

31

In Dev

(2)

In QC

(3)

Backlog

18

1

Ready for

Sign off

9

10

5

17

21

4

7

5

12

John Suzy

Paul

Dan

31Amy

Amy

In Dev

(2)

Backlog

18

1

Ready for

Sign offIn QC

(3)

9

10

5

17

21

4

7

5

12

John Suzy

Paul

Dan

31

Amy

In Dev

(2)

Backlog

18

1

Ready for

Sign offIn QC

(3)

9

10

5

17

21

4

7

5

12

John Suzy

Paul

Dan

31

Amy

In Dev

(2)

Backlog

18

1

Ready for

Sign off

5

In QC

(3)

9

10

5

17

21

4

7

12

John Suzy

Paul

Dan

31

Amy

In Dev

(2)

Backlog

18

1

Ready for

Sign off

5

In QC

(3)

9

10

5

17

21

4

7

12

John Suzy

Paul

Dan

31

Amy

7

In Dev

(2)

Backlog

18

1

Ready for

Sign off

5

In QC

(3)

7

9

10

5

17

21

4

12

John Suzy

Paul

Dan

31

Amy

In Dev

(2)

Backlog

18

1

Ready for

Sign off

5

In QC

(3)

9

10

5

17

21

4

12

John Suzy

Paul 31

7

Amy

In Dev

(2)

Backlog

DanAmy

18

1

Ready for

Sign off

5

In QC

(3)

9

10

5

17

21

4

12

John Suzy

Paul 31

7

Amy

In Dev

(2)

Backlog

Dan

18

1

Ready for

Sign off

5

In QC

(3)

9

10

5

17

21

4

12

John Suzy

Paul 31

7

9

Amy

In Dev

(2)

Backlog

10

Dan

18

1

Ready for

Sign off

5

In QC

(3)

10

5

17

21

4

12

31

7

9

In Dev

(2)

Backlog

10 John Suzy

Paul

Dan

Amy

18

1

Ready for

Sign off

5

In QC

(3)

10

In Dev

(2)

Backlog

10

5

17

21

4

12

John Suzy

Paul 31

7

9

Amy

Dan

18

1

Ready for

Sign off

5

In QC

(3)

10

In Dev

(2)

Backlog

5

17

21

4

12

31

7

9

John Suzy

Paul

Dan

Amy

18

1

Ready for

Sign off

5

In QC

(3)

Back to the Sprint example…

In Dev In QC Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Signed

OffBacklog

2

4

5

3

1

M Tu W Th FToday is:

In Dev

(2)

In QC

(1)

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

A release example…

Features on the product backlog

115

Stories for Feature A

Stories for Feature B

Stories for Feature C

The Product Backlog

116

117

Fu

nct

ion

ali

ty

4

2

8

8

2

4

8

4

Total Scope: 40

If all work could be

started at the same time...

118

Product Backlog

119

Fu

nct

ion

ali

ty

time

The team has 3 pairs of engineers,

and dependent Stories

(swim lanes)

120

121

time

122

Fu

nct

ion

ali

ty

time

Now looking at Sprints

123

124

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

125

Fu

nct

ion

ali

ty

time

4

2

8

8

2

4

8

4

sp 1 sp 2 sp 3

Let’s go back in time

and compare planned and actuals

126

Planned

127

Fu

nct

ion

ali

ty

4

2

8

8

2

4

8

4Total Scope: 40`points

1 Release of 3 sprints

Expected velocity:

10 points for Sprint 1

15 points for Sprint 2 and 3

128

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

Velocity (planned)

10

15 15

129

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

Burn Up (planned)

10

25

40

Actual...

130

131

Fu

nct

ion

ali

ty

time

4

2

sp 1 sp 2 sp 3

132

Fu

nct

ion

ali

ty

time

4

2

sp 1 sp 2 sp 3

133

Fu

nct

ion

ali

ty

time

4

2

sp 1 sp 2 sp 3

Planned: 10

10

134

Fu

nct

ion

ali

ty

time

4

2

sp 1 sp 2 sp 3

Finished: 6

106

135

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

Burn Up (planned)

10

25

40

plannedactual

6

That Sprint review meeting...

136

137

Fu

nct

ion

ali

ty

time

4

2

sp 1 sp 2 sp 3

8

2

138

Fu

nct

ion

ali

ty

time

4

2

8

8

2

4

8

4

sp 1 sp 2 sp 3

10

15 15

6

18 16

139

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

Burn Up

10

25

40

6

24

plannedactual

Tracking lead time and cycle time

140

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking Story #

time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle TimeLead time

time

143

Fu

nct

ion

ali

ty

time

4

2

8

8

2

4

8

4

sp 1 sp 2 sp 3

144

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking Story #

time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

time

Lead time

147

Fu

nct

ion

ali

ty

time

sp 1 sp 2 sp 3

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking Story #

time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

S

time

Lead time

150

Fu

nct

ion

ali

ty

time

4

sp 1 sp 2 sp 3

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

16

17

18

19

20

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Story Tracking Story #

time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

S

M

L

time

Lead time

153

Fu

nct

ion

ali

ty

time

4

2

8

8

2

4

8

4

sp 1 sp 2 sp 3

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

S

M

L

S

L

M

L

M

time

Lead time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

S

M

L

S

L

M

L

M

time

Lead time

0

1

2

3

4

5

6

7

8

9

10

11

12

13

14

15

Day 1 Day 2 Day 3 Day 4 Day 5 Day 6 Day 7 Day 8 Day 9 Day 10 Day 11 Day 12 Day 13 Day 14 Day 15

Lead Time and Cycle Time

S

M

L

S

L

M

L

M

Cycle time

time

Lead time

Agenda

• The Scrum flow of work

• Visible workflow

• Pull don’t push

• Limit WIP

• Tracking lead time and cycle time

• Q&A

Scrum with Kanban;Small adjustments,

big improvements

Johann Arispe Business Analyst

jarispe@thoughtworks.com

Paulo Caroli Agile Coach

pcaroli@thoughtworks.comTwitter: @paulocaroli

Thank you!

Questions?

feedback please: @paulocaroli

Johann Arispe Business Analyst

jarispe@thoughtworks.com

Paulo Caroli Agile Coach

pcaroli@thoughtworks.comTwitter: @paulocaroli

top related