Lately I’ve been thinking a lot about how teams organize work.
Something I’ve noticed in many teams is how quickly momentum can disappear after a good discussion. You have a quick sync or Slack huddle, someone explains the problem, a few people throw in ideas, and within ten minutes the solution is pretty clear. But then the next step is translating that conversation into the “correct” ticket — writing the user story, defining acceptance criteria, putting it in the right column. By the time that’s done, a lot of the energy from the discussion is gone.
I understand why the structure exists. As teams grow you need some way to align people and make work visible. But sometimes it feels like the system we use to organize work ends up consuming more energy than the work itself.
That’s what made me start wondering if there’s something missing between Scrum and Kanban. Scrum gives structure, but it also introduces quite a bit of ceremony. Kanban removes much of that ceremony, but it can sometimes make priorities and ownership less clear. In practice it often feels like teams drift back and forth between those two extremes.
If you moved away from Scrum at some point, what did you move to instead, and what pushed you to make that change? Did it actually work better, or did you eventually drift back toward something closer to Scrum again?