3 ms·
One of the most important things I think Kanban[1] emphasizes is that once you eliminate unnecessary bottlenecks, you're left with unavoidable bottlenecks, and
by habitue 6y ago
One of the most important things I think Kanban[1] emphasizes is that once you eliminate unnecessary bottlenecks, you're left with unavoidable bottlenecks, and this naturally means there will be slack. Explicitly expecting slack time is super useful to allow developers at all levels of seniority to do surprising and necessary things like this that would otherwise never be scheduled.
[1] not the project board shape, but the original process it's named after where you set a hard cap on work in progress in each stage to find out where bottlenecks are.
- emodendroket 6y agoI think the reason people don't like Kanban is there are a bunch of tasks that suck to get stuff over the line and without the "deadline" there's little incentive to help with them instead of just pulling something else off the backlog.
- habitue 6y agoTake this with a grain of salt, because I haven't done Kanban personally, but I think the theory is that if you hard cap work in progress, and everyone is sitting around on their hands, it puts a lot of pressure to eliminate bottlenecks to progress.