The document outlines the importance of limiting Work In Progress (WIP) to improve productivity by minimizing multitasking, reducing context switching, and establishing a sustainable pace. It emphasizes the need to focus on high-priority tasks, manage capacity, and create flexibility within teams to improve overall efficiency and quality of work. Key metrics such as cycle time, lead time, and flow efficiency are discussed as ways to assess and enhance performance.

1. WHY WIP
MATTERS

2. Colleen Johnson
• Director, Adaptive Agile Practice at
ImagineX Consulting
• LeanKanban Accredited Kanban Trainer &
Kanban Coaching Professional
• Former AgileDenver Board of Directors
• Co-chair 2016 & 2017
Mile High Agile Conference
• Member Agile Uprising Board of Directors
• CEO & Founder of ScatterSpoke, a team
space for more effective retrospectives
• Mama to three amazing kiddos
@scrumhive

3. Work in Progress
the amount of work started that
has not yet been delivered to the
customer
What is WIP?

5. Our capacity is limited
as a individual, team, and organization we
have a finite amount of output
(regardless of how much caffeine we
consume)
Why should we limit WIP?

6. • I’m too busy!
• I don’t want to say no
• Everything is top priority
• Unplanned work comes up
• Unfinished work is abandoned
• I need to be ”valuable”
Why do we suck at it?

7. 7

8. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
What is a “Pull” System?

9. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Signal of Capacity

10. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Move Work to Done

11. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Measure Cycle Time

12. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
More WIP = Longer CT

13. 1) Focus
2) Flexibility
3) Follow through
Why limit WIP?
4) Sustainable pace

14. • Minimizes multi-tasking/context switching
• Reduces overburdening
• Builds mastery
• Improves quality
Bring Focus

15. Limiting the capacity of the
team forces you to make
decisions about what is
highest priority, and
FOCUS on that priority
WIP Manages Priority

16. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Minimize Multitasking

18. • Reduces the amount of code changes in flight
• Creates opportunity to reprioritize
• Focuses on just-in-time definition
• Facilitate urgent/unplanned work
Create Flexibility

19. Too much inventory creates
INFLEXIBILITY,
when needs change you may be
stuck with inventory you are unable
to sell and
cannot change course.
WIP Manages Inventory

20. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Minimize the Pain of Change

22. • Creates Visibility of Blockers
• Shorter Cycle Times
• Reduces the amount of regressing testing
• Builds in slack time
Follow Through

23. Limiting the amount of work
creates pressure to complete
something in order to
create capacity for new work
WIP Manages Capacity

24. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Minimize Starting
More Work

26. • Reduces varied amounts of work
• Eliminates stress
• Create predictably
• Prevents burnout
Sustainable Pace

27. A consistent amount of
work reduces panic, stress,
and the exhaustion created
by trying to catch up
WIP Manages Cadence

28. To Do
2
Dev
3
Code
Review
1
QA
2
Deploy
6
Minimize Heroics

30. Starting WIP is low enough to identify
bottlenecks & promote a smooth flow, but
is still high enough to not artificially create
bottlenecks.
Experiment, measure, review, refine.
What is the right number?

31. Kanban Metrics
• Lead Time: the duration for a work item from beginning to
end, including process time and wait states.
• Cycle Time: the duration for a work item to move from
point A to point B.
• Through Put: the count of work items processed per a
specific amount of time.
• Work in Progress: the total amount of work you have
committed to but have not completed at any given time
• Flow Efficiency: the ratio between working time and the
cycle time (expressed as a percentage)

32. WIP isn’t a LIMIT
it’s a GO LIGHT

33. #StopSprinting
#LessPilesMorePull
#MoreThanABoard
#NoHeroics
Because HOW you work
is just as important as
how MUCH you deliver.

34. THANK YOU!
Stay in touch!
Email me at:
colleen@imgnx.co
@scrumhive