Upload
arneroock
View
2.398
Download
0
Tags:
Embed Size (px)
DESCRIPTION
This is the story about Justin and how WIP limitation helped him save a project and improve his company.
Citation preview
Justin the hero ‒ he saved a project!
Late project ‒ overtime and bonuses had no effect
Watching the printer ‒ Justin finds enlightment
Systems for knowledge work have limited capacity!
Vsualising the workflow and the state of the work
The board is completely overloaded!
Defining WIP limits
Too much WIP in the System ‒ what to do?
A new way of working
The boards gets emptier ‒ tasks‘re finished faster
Increasing throughput is hard ‒ reducing WIP is easy
Multitasking leads to poor quality
Justin has to hold back and trust the team
Better predictability
Faster feedback, more learnings
Utilisation goes down ‒ a desaster?
„Slack is the ultimate weapon“ ‒ D. Anderson
„Veterans“ are still overloaded
The board has the measles!
Sprints as another kind of limitation
Applying WIP limitation to portfolio mngt.
Limitation by discussion
Wrap up
Wrap up