Difference between revisions of "Work in progress limit"
(→Sources: += Personal Kanban » Jim Benson » Finding Hidden WIP) |
m (,) |
||
| (2 intermediate revisions by the same user not shown) | |||
| Line 6: | Line 6: | ||
|wish full=Working on less items at the same time increases focus, reduces waste and lead times, increases throughput, flow and liquidity of the system, and triggers conversations about bottlenecks that surface. | |wish full=Working on less items at the same time increases focus, reduces waste and lead times, increases throughput, flow and liquidity of the system, and triggers conversations about bottlenecks that surface. | ||
|background={{p|work in progress limit}} brings extreme {{verb|focus}} when tightened up. | |background={{p|work in progress limit}} brings extreme {{verb|focus}} when tightened up. | ||
If your wip limits don't hurt, they're not wip limits, they're decorations. | |||
|therefore full=Impose and uphold a limit on the work in progress at each state in the {{p|visual workflow}} to create a pull system in which individuals take [[responsibility]]. Tighten the limits until a bottleneck surfaces and turn it into a {{p|busy buffered bottleneck}} or collect them in the {{p|accelerator list}}. Put limits on {{p|swim lanes}} to balance work capacity. Leverage a {{cfd}} to proactively manage undesired behavior of the system. Encourage everyone to take [[responsibility]], facilitated by the pull system. Repeat ad infinitum. | |therefore full=Impose and uphold a limit on the work in progress at each state in the {{p|visual workflow}} to create a pull system in which individuals take [[responsibility]]. Tighten the limits until a bottleneck surfaces and turn it into a {{p|busy buffered bottleneck}} or collect them in the {{p|accelerator list}}. Put limits on {{p|swim lanes}} to balance work capacity. Leverage a {{cfd}} to proactively manage undesired behavior of the system. Encourage everyone to take [[responsibility]], facilitated by the pull system. Repeat ad infinitum. | ||
}} | }} | ||
| Line 27: | Line 29: | ||
|person=Jim Benson | |person=Jim Benson | ||
|title=Finding Hidden WIP | |title=Finding Hidden WIP | ||
}} | |||
{{WebSourceListItem | |||
|url=http://www.infoq.com/news/2014/12/convince-limit-WIP | |||
|site=InfoQ | |||
|person=Jim Benson | |||
|title=Getting People to Limit Their Work In Progress | |||
}} | }} | ||
Latest revision as of 08:14, 4 July 2016
…a heap of work to be processed.
✣ ✣ ✣
Working on less items at the same time increases focus, reduces waste and lead times, increases throughput, flow and liquidity of the system, and triggers conversations about bottlenecks that surface.
work in progress limit brings extreme focus when tightened up.
If your wip limits don't hurt, they're not wip limits, they're decorations.
Therefore:
Impose and uphold a limit on the work in progress at each state in the visual workflow to create a pull system in which individuals take responsibility. Tighten the limits until a bottleneck surfaces and turn it into a busy buffered bottleneck or collect them in the accelerator list. Put limits on swim lanes to balance work capacity. Leverage a cumulative flow diagram to proactively manage undesired behavior of the system. Encourage everyone to take responsibility, facilitated by the pull system. Repeat ad infinitum.
✣ ✣ ✣
✣ ✣ ✣
Maturity
Shu
work in progress limits are in place, yet need to be tightened up to discover key improvement areas.
Ha
A sophisticated, yet elegant use of work in progress limits govern the system as a whole, filling the accelerator list as they start hurting when tightened up, using scientific method and models.
Ri
Connecting parts of the ecosystem—both internal and external—ask you to help them set up a similar, pull-based system with explicit policy and a crystal clear interface and protocol at the boundaries.