I think organizing software work is hard. It's easy if there are only maybe 2-5 people involved, objectives are clear and not conflicting. Usually though, you

I think organizing software work is hard. It's easy if there are only maybe 2-5 people involved, objectives are clear and not conflicting. Usually though, you can't afford to implement every idea you have, you need to maintain old stuff while also making new stuff, teams have non trivial dependencies on each other's work, and time predictions are nebulous at best. Also software managers are generally software engineers first, not managers. Is sprint good at these things? I don't think so (though I never managed a team with sprints, only saw other teams do it badly). But is there a better blueprint? I'm not sure either. It's a hard problem, and hearing about what doesn't work isn't so insightful.