3 ms·

I’m not a huge scrum defender - I’ve seen it done right and wrong. Same with Kanban. The only real problems I have with Kanban is that without those annoying te

I’m not a huge scrum defender - I’ve seen it done right and wrong. Same with Kanban. The only real problems I have with Kanban is that without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability. And that’s not exclusively true of Kanban. But I feel like the lack of organization can turn it from less of a “flow state agile” and more into an insane command economy/death march/spaghetti factory. I usually feel Scrum teams are happier, more close-knit and aware of the impacts of teammates work, and more excited about “doing agile right” than in Kanban - which often feels very siloed and “heads down”. Different strokes, I guess.

Yhippa 3y ago
Those same problems still happen in Scrum and it's very hard to get out of duplication hell once the backlog gets sufficiently large. I personally think Scrum is theoretically great if done right and with smart people, but that is rarely the case.
- zerbinxx 3y ago
  Duplication hell is the current bane of my existence - I think we would agree that it’s more of an inter-team coordination issue than it is the type of thing that you and the four other people on your team can fix with Kanban/Scrum. But I do feel like Scrum is better at the very least at stopping this from happening because that longer ramp up time from “customer wants X” gives people a chance to say “wait so and so already did that for their turn”
paulmooreparks 3y ago
> without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability I don't see why that is necessarily the case. It certainly didn't happen on the Kanban teams I've led. Maintaining the backlog and reviewing the work in progress is just as important in Kanban as in any other process.

Yhippa 3y ago

Those same problems still happen in Scrum and it's very hard to get out of duplication hell once the backlog gets sufficiently large. I personally think Scrum is theoretically great if done right and with smart people, but that is rarely the case.

zerbinxx 3y ago
Duplication hell is the current bane of my existence - I think we would agree that it’s more of an inter-team coordination issue than it is the type of thing that you and the four other people on your team can fix with Kanban/Scrum. But I do feel like Scrum is better at the very least at stopping this from happening because that longer ramp up time from “customer wants X” gives people a chance to say “wait so and so already did that for their turn”

paulmooreparks 3y ago

> without those annoying team planning/documentation meetings, work will get duplicated, done hastily, done with no discussion or thought toward testing, architecture, maintainability I don't see why that is necessarily the case. It certainly didn't happen on the Kanban teams I've led. Maintaining the backlog and reviewing the work in progress is just as important in Kanban as in any other process.