110506 - scrumban - XP2011

© 2010 Proyectalis Gestión de Proyectos S.L.

Scrumban An evolutionary approach


Ángel Medinilla!


Enough for a start…


Disclaimer:


Disclaimer:

You (probably)


Disclaimer:

You (probably)

Unintended audience (but of course you are welcome )


Let’s go back in time to Scrum Era…


5thAnnual ”State of Agile Development” Survey, 2010

“One size does not fit all” but…


Monster #1:


The “you are not flexible enough” problem:


Also called…


The support team approach


Our rule:


Monster #2:


The 40 hour week fallacy:

100% (40 hours a week)

Programming (value adding tasks, focus factor, sprint dedication, project

advance…)


A more realistic approach:

50%

10%

15%

10%

10%

5%

Bugs, technical debt, stoppers, blocked tasks, rework, context switching, other forms of waste…

Reports, e-mail, internal meetings, hiring interviews, admininistrative stuff, bureaucracy…

Slack

Research, Development, training, innovation

Programming ( value adding tasks, focus factor, sprint dedication, project

advance…)

Overhead


Naked truth:

35%

10%

10%

10%

5%

30% Bugs, technical debt, stoppers, blocked tasks, rework, context switching, other forms of waste…


Slack


Programming ( value adding tasks, focus factor, sprint dedication, project

advance…)

Overhead


Naked truth:

35%

10%

10%

10%

5%

30% Bugs, technical debt, stoppers, blocked tasks, rework, context switching, other forms of waste…


Slack


Scrum (measured & known)

Overhead


Naked truth:

35% Scrum (measured & known)

65%


Some more monsters:


What’s really happening in here?

Ongoing Pending Done!


Who’s doing what?



Everyone busy = value delivered?



Do we care about delivered value?



Are these tasks or features?



Are we cross-functional enough?



What’s the lead time?



So we had a jolly family of monsters…


And we looked for some help…

2007 2008 2009 2010


2010, David J. Anderson (thanks, man!)

Although I wish I had this one a couple of years earlier…


We had to fight some myths…


“Kanban is decaf Scrum”


“Kanban opens Pandora’s box”


“WIP limits are impossible to fulfill here”


“When something gets blocked, just start with something else”


Here’s how we did it


Start mapping your value stream


Add columns accordingly

Selected Backlog Code Test Done! Design


Categorize demand

Selected Backlog Code Test Done! Design


Be sure there’s a prioritizing mechanism and a single entry point

?


Add avatars (oh, yeah!) Selected Backlog Code Test Done! Design

Tim

Lyz

Fred

Scott


Add queues (and some sense) Selected Backlog

Code Test Done!

Design

Tim

Lyz

Fred

Scott

Rdy Rdy Rdy On On On


Measure lead time, see the whole

Selected Backlog Code Test

Done! Design


120 days

~15 days

~4 days


Add WIP limits by any means Selected Backlog

Code Test - 2 Done!

Design

Rdy Rdy Rdy On -3 On On


Add uncertainty / out of focus space Selected Backlog

Code Test Done!

Design


SP

RIN

T B

UFF

ER

SPA

CE


Measure uncertainty / out of focus


Done! Design


SP

RIN

T B

UFF

ER

SPA

CE

Scrum Velocity

Buffer Capacity


Measure uncertainty / out of focus V Scrum Buffer cap

80 20

85 20

75 30

70 35

75 25

80 25

? ?

¿Your prediction?

Uuuh… Well, on average we make something like 75 scrum points per sprint. Guess we can commit on that as long as you keep the uncertainty level safe…

That means somewhere below 25 buffer points


Measure uncertainty / out of focus V Scrum Buffer cap

80 7500

85 7000

75 8000

70 8500

75 7500

80 7000

? ?

¿Your prediction?

Uuuh… Well, on average we make something like 75 scrum points per sprint. Guess we can commit on that as long as you keep the uncertainty level safe…

That means somewhere below 7500 buffer points


Add qualities of service


Done! Design

Rdy Rdy Rdy On On On S

PR

INT

FIRE!

PRIO

ASAP


Make rules explicit


Measure capacity

50l/sg

20/sg

10l/sg

100/sg

30/sg


Identify bottlenecks

50l/sg

20/sg

10l/sg

100/sg

30/sg


Don’t brute-force the system

50l/sg

22/sg

11l/sg

110/sg

33/sg

+10%!!


Adapt workload to capacity instead

50 23l/sg

23/sg

23l/sg

100l/sg

33l/sg

¡Kaizen!

Capacity surplus: - Attack

bottlenecks - R&D - Tech.Debt. - Help colleagues - Widen job title


Bonus: drop estimations!


Bonus: Flow Enhancement tools


Last thought…


Thank you, and… BLOG IT!

[email protected]


http://creativecommons.org/licenses/by-nc-nd/3.0/

This presentation is based upon the ideas and work of many people. And while I’ve tried to recognize copyrights and give credit and attribution where possible, I cannot possibly list them all, so if you feel like there’s something that should be added, changed or removed from this presentation, please drop me an e-mail at [email protected]

Special thanks to Henrik Kniberg, David J. Anderson, Mattias Skarin and Corey Ladas. You guys Rock!

110506 - scrumban - XP2011

Business

Transcript of 110506 - scrumban - XP2011