30
WIP: A Tragedy in 278 Parts Eric Willeke (@erwilleke) Rally Software Your pic

Eric Willeke - WIP: A Tragedy in 278 Parts

Embed Size (px)

Citation preview

Page 1: Eric Willeke - WIP: A Tragedy in 278 Parts

WIP: A Tragedy in 278 Parts

Eric Willeke (@erwilleke)Rally Software

Your pic

Page 2: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Welcome!

Goal Improve service delivery

Page 3: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Welcome!

Goal

Techniques

Improve service delivery

Optimize the right thingsAvoid the tragedy of WIPKeep your options open

Page 4: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corpwww.rallydev.com ©2013

Optimize the Right Things

Page 5: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

How Long Does it Take?

Customer lead time(Time to market)

Great Idea! I love it!

We should

get started.

Ok, all good!

Queue time(waiting)

Time in process(TIP)

Page 6: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Whew! Ship it!

How Long Does it Take?Time in Process

(TIP)

What is this

thing?I think it works.

Nope!

Now?

Yep!

Page 7: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Analysis & Design Code Test (and fix) Ship

Whew! Ship it!

How Long Does it Take?Time in Process

(TIP)

What is this

thing?I think it works.

Nope!

Now?

Yep!

Page 8: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Analysis & Design Code Test (and fix) Ship

How Long Does it Take?Time in process

(TIP)

Touch timeWait time= 18 days = 2 days

Page 9: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

How Long Does it Take?Time in process

(TIP)

Touch timeWait time= 18 days = 2 days

Touch time

Wait time + Touch timeFlow efficiency =

2d

18d + 2d= = 10% efficiency

Page 10: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

What is Your Goal?

I love it!(Wow, that was fast!)

I should get started …

(but, I’m so busy)

Flow efficiency “Resource” efficiency100% efficiency10% efficiency

Get things done Keep people busy

Page 11: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Your Goal

I love it!

I love it!

I love it!

I love it!

I love it!

I love it!

I love it!

I love it!

Keep value moving!

Page 12: Eric Willeke - WIP: A Tragedy in 278 Parts

We Have Lots of Work!

(Don’t we have both efficiencies?)

Page 13: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Image courtesy morguefile.com

Page 14: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corpwww.rallydev.com ©2013

The Tragedy of WIP

Page 15: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Work Interacts (through workers) …

Page 16: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

… and Impacts Throughput

WIP

Lead TimeTP =

You

are

her

e

Page 17: Eric Willeke - WIP: A Tragedy in 278 Parts

Let’s Juggle!

Page 18: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

How Much WIP is Bad?

?

Page 19: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Our Answer …

Between one and two work items per person - closer to one!

See: http://www.rallydev.com/agilemetrics

Page 20: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Page 21: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

But … but … how can we get there?

Only start the really important things

For every two items you finish, start one new one

For every “expedite,” pull an existing item out

Say “not yet” more

Be creative

Page 22: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corpwww.rallydev.com ©2013

Options and CommitmentBalancing expectations and flexibility

Page 23: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

When do you Commit?

Customer Lead Time(Time to market)

Queue Time(waiting…)

Time in Process(TIP)

Here?

Here?

Here?

When do your customers believe you?

Page 24: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Avoid Empty Commitments

Treat work here as optionsThese are committed

An untrusted commitment has no meaning (but lots of stress)

Changing our minds here is cheap

Changing here has a cost

Here!

Page 25: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Commit Later! (And Mean it)

Options have value

Options expire

Never commit early unless you know why

Cover image courtesy Amazon.com, used with authors’ permission

Page 26: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Limit Commitments in Progress

Com

mit

to h

ere

Not

to

here

Target Range

Page 27: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Summary: Three Simple Guidelines

1. Keep work moving 2. Do less at once3. Commit when it means something

Page 28: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Get where you need to be

Image courtesy morguefile.com

Get Where you Need to be!

Page 29: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Questions?

Page 30: Eric Willeke - WIP: A Tragedy in 278 Parts

www.rallydev.com ©2014 Rally Software Development Corp

Thanks for listening…Eric WillekeRally SoftwareFollow me @erwilleke

Your pic