Lean WIP Limit and Pull (bootstrap)
This skill is a bootstrap skill. It is the hand-run form of the practice, kept so lanes can test and iterate on the process while the real mechanism is built; it is a tool to make tools. It enforces nothing: it asks you to apply by hand the limit and the pull order that the WIP gate and the slot assignment will apply mechanically. It is replaced by its node-backed skill when that skill comes online.
Replaced by the node-backed WIP skill on node_wip_gate_reducer (plan task T-W1: WIP gate reducer,
overlay limits and reader), with T-W2 (node_slot_assignment_reducer: slot assignment with pull-first order
and the no-idle rule), T-W3 (node_lane_brief_pr_gate_compute: the brief gate names the repositories a lane
opens pull requests in, and refuses past a limit) and T-W4 (node_flow_measures_compute: flow measures).
Replace this skill with the node-backed skill when T-W1 to T-W3 are merged and deployed.
The practice
Work in progress that cannot land is waste. The open count rising while merges fall means the line is pushing, not pulling. Keep the number of open, unlanded pull requests per repository small, and take work from what blocks flow before the backlog.
When to use
Before you start or dispatch work that opens a pull request, and when choosing what to pick up next.
Steps by hand today
- Count WIP for the repository you would open a pull request in: open pull requests including drafts, not merged and not in a merge queue. Read it from the pull request watcher state and print both the count with drafts and without.
- Compare to the limit. Use the repository's recorded limit. If none is recorded, use your own best estimate and write it down: hours of landing times merges per hour, with a floor of three. A limit you cannot cite is a guess; label it as one.
- At or over the limit, do not open a new pull request. Exempt work: reducing WIP (a cause fix, a controller fix, a land or review lane, work on an open unlanded pull request), read-only work, and the swarm lane of an andon stop.
- Pull in this order.
- The cause of a stopped class.
- A missing lander or an unowned shared red.
- Pull requests held or red with no owner.
- The rest of the backlog, only for repositories under their limit.
- Work that opens no pull request.
- As a last resort, a pull-request-opening item at a limit.
- Never leave a slot idle. A limit diverts the slot to work that opens no pull request: fixing bugs, running tests, experiments. When no such work exists, take the last-resort item and say so in your closing note.
Factory task per step
Each step above is replaced by this task of the lean practices plan.
| Step | Factory task |
|---|---|
| 1 | T-W1 (WIP gate reader) |
| 2 | T-W1 (overlay limits) |
| 3 | T-W3 (brief gate refuses past a limit) |
| 4 | T-W2 (pull-first order) |
| 5 | T-W2 (no-idle rule) |
| Measures to report | T-W4 (flow measures) |
Measures to report
Merges per hour per repository, the open count and its trend, green-to-merged time, pull requests held, and slots that took the last-resort item. Report what you read and when; do not estimate a reading you did not take.
What this skill cannot do
It cannot refuse a dispatch or read the watcher for you. The limit holds only as long as every lane chooses to apply it.