WATERFALL

Scrum AGILE
to Scrumban vs CHEATSHEET
CHEATSHEET

1 2 3
Visualise the work Impose WIP limits Add more columns

This space is the signal -

the kanban - that indicates
that this process is ready
to receive more work.

This line is the WIP limit.

This one’s easy: all you need is a board! If you already have an The Work in Process Limit (WIP) is the enabler for the kanban Add columns to match your processes. Add a WIP limit to
“Agile Board”, you’ve taken your first step - congratulations! pull system. each process, so that each benefits from the pull system.

4 Stop early binding. Start
 5 Stop Estimating 6 Trigger your planning

ordering So far, so Scrum. But now we break away from Scrum as
we… stop estimating!
Instead of
planning every
two weeks, let
If you’re assigning That’s right: no more Story Points, no more Planning Poker. “the work” trigger
work to specific team the planning
members as part of 3 3 2 3 2
meeting.
Backlog Refinement
or Sprint Planning…
then stop! 3 3
3 3
2 2
3 3
2 2

Instead, focus on This line - the

ordering the work. A Not only will this save time, but it will put the focus where it “trigger point”

dedicated “Ready” should be: on prioritisation. - is the enabler.
column is a great way
to do this.
We’re no longer doing Scrum… but there’s one more step we
need to take before was can claim to be doing Scrumban → Congratulations: you’re doing Scrumban!

© 2018 Development That Pays | Issue 1.0 (margherita) https://www.DevelopmentThatPays.com - Cutting-edge strategies for profitable software development
© 2017 Development That Pays | Issue 0.4 (american hot) http://www.DevelopmentThatPays.com Cutting-edge strategies for profitable software development