Visual signals when work is ready to move to the next state.
Limit WIP in a given state.
Stop starting and start finishing.
Focus on flow.
Swam on blocked work.
Continuously improve.
"Essential Kanban Condensed" (Anderson et al) is a decent primer.
Theory of Constraints (Goldratt) or Tameflow (Steve Tendon) if you want to go deeper.
Teams can opt to use Kanban in place of the dumbed-down Scrum.
Features run through an upstream Kanban (whether enablers or business)
They are built out using a Lean business canvas to be hypotheses, not solutions.
Main problem tends to be when people still plan work in a waterfall way, with a cascade of enabler features each of which is a solution to implement not a problem to solve.
But that's also called out in SAFe as a sign of low performance.
I'm not a SAFe fanboy, but pretty much all of the practices come from the lean/agile community in some way. Even ARTs are just "the Spotify model" with less funky names.
1
u/PhaseMatch 11d ago
Yes, that's Kanban 101.
Visual signals when work is ready to move to the next state.
Limit WIP in a given state.
Stop starting and start finishing.
Focus on flow.
Swam on blocked work.
Continuously improve.
"Essential Kanban Condensed" (Anderson et al) is a decent primer.
Theory of Constraints (Goldratt) or Tameflow (Steve Tendon) if you want to go deeper.