3 ms·
Not really. Developers are just held accountable or feel accountable for their own forced guesstymates. It was better when managers were guessing becouse they a
by rightbyte 7y ago
Not really. Developers are just held accountable or feel accountable for their own forced guesstymates. It was better when managers were guessing becouse they also have the means to change scope.
- mcv 7y agoThere's a very good reason why story points in scrum do not directly relate to time worked. You guess story points only in relation to each other. Over time, you can see how many story points you finish per sprint. By seeing how many story points are still on the backlog, you can estimate how long it will take. Add one or two sprints for unforeseen problems, and there's your estimate. Not based on anyone's guess, but on the time it takes to do actual work. This, in short, is the core of value that Scrum adds to the ideas of Agile. The only problem is that people insist on misunderstanding these simple ideas and try to do Scrum as wrong as possible. The problem isn't Scrum, the problem is people insisting on doing it wrong.
- AlexandrB 7y agoIf nearly everyone is doing it wrong, the problem is Scrum.
- baq 7y agoIt’s a very naive thing to say. The problem is usually management misunderstanding what scrum is supposed to be. It’s a variant of ‘estimates become deadlines’.
- shantly 7y agoI'm not sure any system's going to do better. There aren't a ton of people who are good at applying (let alone thinking up) systems such that they work effectively and as intended. Too many will slice up and build atop a system then wonder why it's working so poorly, because they didn't understand the purpose of the parts they removed, or why the things they added will screw it up. "Well this is great, but we really need to..." NO. No you fucking don't. Unless you want to screw it up. But the people who get that, and who have the independence of action to prevent others from screwing up their processes, are uncommon. Even in management, which is exactly where that kind of thinking should be extremely valuable.
- mcv 7y agoBut not everybody is doing it wrong. Most companies I've worked for have invested in understanding Scrum, and have applied it very successfully. The problem here is toxic corporate culture. Scrum and Agile are not magic spells that miraculously turn idiots into reasonable people. Sure, they could be used as levers to change that culture, but the culture absolutely needs to change, otherwise it's not going to work. And that's something you can throw in their face: that they're not taking Scrum and Agile development seriously. If they say they want Scrum and Agile, then make sure you understand what they really mean, and hammer on it every time they trample on the autonomy of the developers. Every time they ask why things aren't done, tell them management is interfering with the process.
- rightbyte 7y agoMaybe. My guess is that Agile etc are suitible for some fields of programming and not others. I'm just fed up with this Agilescrum thing. My present RnD workplace have been transitioning to it in the last years and it's really bad. The prior V-iteration process was good enough. We are mostly just making up estimates and report time accordingly to make the burndown chart look good.
- commandlinefan 7y ago> story points in scrum do not directly relate to time worked Except in the minds of absolutely every single person who applies them to anything.
- mcv 7y agoNo. Not in the minds of people who grok the point of scrum. Just start pointing this out to people every time this comes up. It's not an exact time estimate, it's an abstract complexity estimate. Insist that the idiots get some actual training in Agile before they start corrupting it beyond recognition. If they want Agile, then they should invest in training people for it, and in spreading the culture that goes along with it. Because Agile is perhaps more about culture than about process.
- nradov 7y agoAccurate software estimation is a technical skill that can be learned like any other. It's disappointing that so many developers don't take it seriously or make disciplined efforts to improve their skills. https://stevemcconnell.com/books/ https://stevemcconnell.com/books/
- tra3 7y agoI feel like this is misleading. There’s no magic bullet for software estimation. McConnell’s book talks about various techniques but the takeaway is that you know very little at the beginning of the project. There various techniques for estimation but you can never get away from the essential unknown unknowns.
- mcv 7y agoExactly. To make accurate estimates of how long it's going to take, you need to know how the team estimates the complexity of the work that still needs to be done, how they estimated the past, and how much they actually did in the past. In this particular team, with this way of working. Only then do you have the information to make a halfway reliable estimate. Without that, it's just going to be guess work.