When Scrum doesn't help, Kanban may save your team
Borys Zielonka • February 14, 2024
agileSometimes it seems that the scrum team is in survival mode. No clear sprint goals, missing Product Owner, tons of support tickets, etc... Classic chaos. Here's the thing: you don't need to throw Scrum out the window. You can actually supercharge it with Kanban practices.
Kanban Works for Chaos?
Kanban might be your reality check system. The beauty is that Kanban brings visibility to the madness. It is literally about to see all the work on a board - no more surprises about who's drowning in tickets.
Start Small (Because Change is Hard)
- Visualize Everything - Get a Kanban board up. Show ALL the work - features, bugs, support tickets, that random stuff every one is doing for someone else. When people see 15 items in the "In Progress" column, reality hits hard.
- Set WIP Limits - This is your lifesaver. I know it is hard, in my team we had to manipulate with the limit lots of times. When someone wants to pull new work but you're at the limit, tough luck - finish something first or help others.
- Track Flow Metrics - Forget story points. Track cycle time (how long stuff actually takes) and throughput (how much you actually deliver). These metrics don't lie, unlike those optimistic sprint planning sessions.
No PO around?
Use Service Level Expectations (SLEs). Basically, you promise "85% of support tickets done in 3 days" instead of arguing about priorities.
Daily That Actually Helps
Forget the "what I did yesterday" theater. Stand around the Kanban board and ask:
- What's blocked? Why? How we can solve it together?
- What's taking forever?
- Are we about to break our SLE promises?
For the Skeptics
- No more sprint commitment pressure
- Work flows naturally (pull when ready, not because the sprint starts)
- Less planning meetings, more doing
Final thoughts :D
Don't abandon Scrum - just add a flow-based lens that actually matches the chaotic reality. Keep your sprints as feedback loops, but let work flow continuously. The sprint becomes your "inspect and adapt" checkpoint. Sometimes the best way to manage chaos isn't more control - it's making the chaos visible and manageable.