3 ms·
We've been trying a more "Kanban" approach vs scrum, but who knows if we're actually implementing it correctly, which is perhaps the point of all this.
by spelunker 4y ago
We've been trying a more "Kanban" approach vs scrum, but who knows if we're actually implementing it correctly, which is perhaps the point of all this.
- sirwhinesalot 4y agoThere's no need to implement any sort of internal process like this "correctly". It's working correctly if it makes your team happier and more productive. It is not working correctly if it does not. Kanban vs Scrum is not really the issue, but Kanban is certainly more honest. When a server goes down in the middle of the day and someone needs to spend 2 hours debugging the logs to get it back up, do you add a task to do that for next sprint? No, you do it right there and then. At least in Kanban the task has some chance of actually being registered in the issue tracker. The only thing I will suggest is if you do Kanban (meaning continuous adjustments to the backlog with devs picking the higher priority tasks and doing them as needed), have a synchronization meeting from time to time, almost like a sprint retro meeting, but mainly to have the team talk about how things are going and to make it clear what everyone is working towards. The meeting doesn't need to have a specific goal or structure. It can feel like a bit of treadmill if all you do is grab task -> do task -> mark task done all day with no larger vision, so having some synchronization moments where the whole team regroups can help with that.