4 ms·
There are several ways in which it's bad. Forcing all the work to fit into sprints, for instance. What if the natural way to divide the work results in some ch
by Scarblac 2y ago
There are several ways in which it's bad. Forcing all the work to fit into sprints, for instance.
What if the natural way to divide the work results in some chunks that probably don't fit? Normally you'd just do them and it's be fine, but "we're doing Scrum" so now they have to be divided further and the parts have to be developed separately, even if that makes no sense.
Also Scrum assumes things -- that the product owner is very competent, that dev teams are self managing, that the business is interested in updates in the same frequency as the sprint -- that aren't necessarily true.
And everything that goes wrong is blamed on Scrum not being done exactly to the letter. So nothing else is fixed and everybody is more and more focused on doing Scrum ceremonies precisely right even if that was never their intention.
- shiroiushi 2y ago>There are several ways in which it's bad. Forcing all the work to fit into sprints, for instance. That's misusing it. The sprints are just forcing regular meetings to assess progress and make changes if necessary. There's no reason to absolutely force everything to get done in 2 weeks. If something doesn't get finished in a sprint, discuss what happened in the biweekly meeting and if any changes need to be made, and then move it to the next sprint.