Loading
Scrum commits to a batch of work for a fixed period and protects it. Kanban limits how much can be in progress at once and pulls new work as capacity frees up.
Both exist to stop teams starting more than they can finish. They differ in whether the protection comes from a time box or from a work-in-progress limit.
Work that can be planned a couple of weeks ahead, with a team that can protect its time. Product development is the standard case.
It gives a rhythm — planning, review, retrospective — which is genuinely valuable for teams that would otherwise never stop to change how they work.
Commonly, as sprints with reserved interrupt capacity. It works if the reservation is honoured.
Kanban. Support work cannot be committed to two weeks in advance.
No. It means planning at the point of pull rather than in a batch.
Half an hour with your own data usually saves reading three of these. The guides will still be here afterwards.