You don't need Scrum, you just need to do Kanban right (2022)
1–10 of 341 posts
Re: You don't need Scrum, you just need to do Kanban right (2022)
#2Kanban vs Scrum reminds me of:
Re: You don't need Scrum, you just need to do Kanban right (2022)
#3Every team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. Further, many of the promised benefits of Scrum (things like better insight and predictability about delivery rates) never materialized.
Every team that I've worked on that has switched from Scrum to Kanban saw an immediate improvement in speed that never disappeared.
Once, just once, I was lucky enough to work on a team that switched from Kanban to Scrum, and then, mercifully, blissfully, back again. To be fair, I think we actually worked quicker after the return, though I don't know if that could be attributed to having actually learned some lessons from Scrum, or out of a fear that we'd one day return to it.
Re: You don't need Scrum, you just need to do Kanban right (2022)
#4I've heard over and over from managers that scrum is better at anticipating delivery dates. Even when the dates are consistently missed. They'd rather slow teams down with process so they can have a date to give their stakeholders, regardless of its accuracy.
Re: You don't need Scrum, you just need to do Kanban right (2022)
#5There are different problems, depending on your role
1. Communication and Funding - Does your VP know how they are spending money? How is that money allocated? This is why you have agile-fall or SAFE.
2. Planning - Can you deliver the solution your architect drew on the napkin? Does the PM know enough to schedule things.
3. Work handling in the team. This is the one that I think people most want to talk about, and anything that works for the team will work. You don't need anything fancy.
Re: You don't need Scrum, you just need to do Kanban right (2022)
#6What is Kanban?
Re: You don't need Scrum, you just need to do Kanban right (2022)
#7- PM/PO loves scrum, that gives them an illusion of controlling the dev speed/progress...
- the estimate is a joke...
- the standup is useful to know who is pretending work. but no need a daily standup for sure.
and a non-technical PM with scrum makes things worse.
Re: You don't need Scrum, you just need to do Kanban right (2022)
#8Is “doing Kanban” just having tasks on a board without any sort of sprint structure? I feel like it’s a bit of a false equivalence. While I won’t ever defend all the cruft that comes with Scrum, the article seems like a bit of a straw man.
Re: You don't need Scrum, you just need to do Kanban right (2022)
#9Every team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. Further, many of the promised benefits of Scrum (things like better insight and predictability about delivery rates) never materialized. Every team that I've worked on that has switched from Scrum to Kanban saw an immediate improvement in speed that never disappeared. Once, just once, I was lucky…
“The process is the punishment”
Re: You don't need Scrum, you just need to do Kanban right (2022)
#10Every team I've worked on that has switched from Kanban to Scrum has slowed down and never regained the previous velocity. Further, many of the promised benefits of Scrum (things like better insight and predictability about delivery rates) never materialized. Every team that I've worked on that has switched from Scrum to Kanban saw an immediate improvement in speed that never disappeared. Once, just once, I was lucky…
Yes but raw velocity is not the only thing that matters. For some projects it is, but for many the accountability of Scrum + the grouping helps with dependency management across an organization.