2 ms·
This is one reason I hate Scrum. Companies that (I've worked for) have really tried to implement it don't understand that sometimes you just won't be as produc
by kemiller2002 6y ago
This is one reason I hate Scrum. Companies that (I've worked for) have really tried to implement it don't understand that sometimes you just won't be as productive. It's always, "Well you committed to it...." They can't (or don't want to) understand those miracles they want their employees to perform comes at a cost. It means those people are less productive at times while they are exploring an idea or they are just exhausted. If they just want someone to do the minimum set each sprint, that's fine, just don't expect anyone to walk on water when you need to be saved.
- Viliam1234 6y agoEstimates are by nature probabilistic. Saying "two weeks on average" means something like: 20% it is one week, 60% it is two weeks, 20% it is three weeks. And that assumes you are already pretty good at estimating! Most people are not. This is by sleight of hand changed into a commitment to make it in two weeks, 100% sure. Then, 20% of time, developers are blamed for not fulfilling their committments or not estimating correctly. But they did! If the most important thing for you is getting your commitments done with as high probability as possible, have a three-week sprint, but estimate only for two. Even this will fail once in a while, but less often. And maybe let developers work on the tasks of their choice in the remaining time. Autonomy, yeah! "Two weeks on average" literally means it could be less but just as often it could also be more. If it is always two weeks or less, then it is not two weeks on average. What if it is always exactly two weeks, not a day more or less? No, that level of precision simply does not happen in real life.