[watters]

Most organizations use a widespread corrupted form of Scrum, the most important features of which are the two-week sprint and task estimates expressed in "ideal developer days" but labeled story points.

This allows managers to engage in Planning and Predictability Theater™, which they seem to find reassuring.

This corruption of Scrum also has the effect of reframing imperfect estimates as IC failures.

Genuine Kanban works better in cultures where ICs are highly trusted and failures are primarily examined through the lens of systems breakdowns, and views those systems as primarily the responsibility of management.