2 ms·
Note that Kanban requires a certain maturity and self-discipline from the development team and the stakeholders. If that's a given, Kanban can work very well.
by perlgeek 6y ago
Note that Kanban requires a certain maturity and self-discipline from the development team and the stakeholders. If that's a given, Kanban can work very well.
Scrum was really invented for situations where management is constantly asking "when do we get X?" and the development always says "we aren't done yet".
In this scenario, the sprint is meant to reassure management that they'll get at least *something (even if not a full X) in a predictable time, and forces the development team to put something out in a given time frame even if not yet perfect / finished / whatever.
If that's not a problem, Kanban can be indeed be a much better fit, and come with far less overhead.
- pracer 6y ago> the sprint is meant to reassure management that they'll get at least *something (even if not a full X) in a predictable time I would rephrase it as "sprint is meant to make management to believe that they'll get at least something in a predictable time". I also notice that lots of comments seem to be coming from front-end or customer-based companies. For backend and b2b, 2 weeks sprint for some new functionality is funny.
- perlgeek 6y ago> I also notice that lots of comments seem to be coming from front-end or customer-based companies. For backend and b2b, 2 weeks sprint for some new functionality is funny. I develop internal tooling for a b2b company, and we ship features multiple times a week. Much of that is backend. Often not huge features, but still features that make life easier for colleagues.