The Scrum Commitment/Forecast as an Expectation
Treating the Sprint commitment/forecast as an expectation rather than a promise — a learning vehicle, not a delivery guarantee.
Treating the Sprint commitment/forecast as an expectation rather than a promise — a learning vehicle, not a delivery guarantee.
Can you go straight to Kanban without doing Scrum first? David Anderson says start with what you do now. Yuval explores when each path makes sense.
ScrumBan isn't a process — it's applying the Kanban Method to evolve Scrum toward lean and flow. What that looks like in practice and what usually emerges.
Why treating sprint plans as binding commitments undermines trust, velocity, and team health — and what a healthier take on planning looks like.
How to add sprint mechanics to the getKanban board game — making it a useful simulation for comparing time-boxed and flow-based approaches side by side.
A simple elevator-pitch explanation of Kanban for Scrum practitioners — what Kanban adds, what it changes, and why the two are complementary.