8 ms·
No. Even bad estimates are better than no estimates. If you are having meltdowns your reputation is being tied too closely to your ability to give estimates.
by xwdv 7y ago
No.
Even bad estimates are better than no estimates. If you are having meltdowns your reputation is being tied too closely to your ability to give estimates.
You must never turn estimates into a promise, always remind people they are estimates.
Want to give fast estimates? Here’s how:
1) first determine the scale of the task? Is it a year, month, week or day kind of task?
2) Then, it’s just 3 of those units. The smallest task takes 3 days. One day to completely fuck up, one day to figure out why, one day to get right. The longest takes 3 years. One year to fuck it all up, one year to learn why, one year to finish it.
I suggest never giving estimates in units smaller than a day. They just become noise. If a task is smaller than dayscale just say the task is too small to provide any meaningful estimate but won’t take more than a day.
- deleted 7y ago[deleted]
- bb88 7y ago> Even bad estimates are better than no estimates. No estimate is clearly better. Here's a common story I've seen across multiple companies. 1. Marketing management asks Engineering management how long it takes to do feature X so they know when to launch the online ad campaign. 2. Engineering management then asks potentially good coder how long it will take. Coder replies with a time and "it's just an estimate." 3. Engineering management reports to Marketing that coder's estimate leaving off the most important caveat, and Marketing treats that as the gospel truth. 4. Coder takes longer than expected because of some bad technical cruft that some other engineer put in because he was potentially rushed or just plain inept. 5. Marketing is pissed because they now have to withdraw the ad campaign, and starts blaming engineering. 6. Under increased scrutiny, Engineering gets a bad reputation, who then throws the coder under the bus in front of Marketing and other managers. 7. This shows up on the coder's annual review who then leaves. 8. Engineering hires replacement which will have a 3-6 month learning cycle, and potentially writes worse code than the person that just left. EDIT: The point is that if there's no estimate, management has to deal with the uncertainty that the coder experiences. Hope for the best, plan for the worst.
- 50656E6973 7y ago>1. Marketing management asks Engineering management how long it takes to do feature X so they know when to launch the online ad campaign. Why can't Marketing just wait until the feature has been built to launch their campaign?
- bb88 7y agoLots of reasons: 1. Marketing management is full of idiots. 2. The coder's estimate is used to tell the CEO when a product will be rolled out. Who then questions why it didn't get rolled out on time. 3. Marketing gets a bonus for rolling out ad campaigns on time. 4. Marketing is using this for their big trade show coming up and wants to make a big announcement for maximum impact. Why do you assume management is always competent?
- rch 7y agoBecause if they launch on the original schedule with Partner X they get Massive Benefit Y that could make or break the product. For example.
- ScottFree 7y agoThis. Most developers either don't want to or can't understand that there are real and valid reasons for wanting a predictable software production schedule. That said, I've only ever seen one software project consistently meet production deadlines. Is there benefit to committing to the original schedule with Partner X if there's no way you can deliver on schedule? Or is it one of those things where Partner X has committed itself and they have no real choice but to work with the sliding deadlines?
- rch 7y agoIn the example I'm thinking of the partner wasn't really bothered that the schedule slipped, but the ideal marketing window came and went before the product officially launched, which certainly affected sales. They were really excited that all the planned features made it to market though. I'd say that some aspects of the capability maturity model make sense, even for engineering groups that practice agile day-to-day.
- matwood 7y ago> Even bad estimates are better than no estimates. I disagree. The only bad estimates that are ok have to error on the high side. I have found that biz side may not like the longer estimate, but they much prefer that over missing a date.
- humanrebar 7y agoRight. If they asked for a 95% confidence number, they would get something to depend on more whole heartedly. But that date will be too far in the future to be comfortable. So they look for more of a natural median. And then are shocked when dates are missed more than half of the time (!). So if you want honesty, ask for estimate ranges or 95% sure estimates. Then pareto your plan to hell and back so everyone understands the risk. Then reestimate periodically as you home in on completion.
- freshhawk 7y ago> You must never turn estimates into a promise, always remind people they are estimates. The person giving the estimate isn't the one who does this. Other people turn them into promises, because that's what they were actually asking for when they asked for "an estimate". Giving some kind of uselessly vague estimate isn't particularly useful from an engineering perspective and everyone else has been trained by scrum the last decade to treat them as promises. So don't do the thing that you know will have a bad effect.
- Redoubts 7y ago> The person giving the estimate isn't the one who does this. Other people turn them into promises, Why is that your problem? If someone tried to hold me to such an estimate, I would simply say "I never promised this, in fact I explicitly didn't promise this. I'm sorry X lied to your face about this." Don't own other people's failures.
- ryanthedev 7y agoFeatures and stories should be completable in the span of an iteration. Epics and Features are prioritized by the business and product. They can be expected to slide from iteration to iteration. Any User Story or task should be expected to be completed an a single iteration. If you keep having open stories stop bringing in a complete story. Just assign tasks. Features and Epics are pointed. Business looks at points earned per year or quarter. Look for trend. IT leadership looks at amount of open stories and tasks that were moved from iteration back to the backlog. Over the span of all iterations. This will ensure teams are breaking down work into actionable goals.
- Redsquare 7y agoSo said the 2 day scrum master
- rramadass 7y agoGood lord! Buzzword Bingo and Obfuscation at its finest! Nothing personal, but you have just confirmed to me why i loathe the Agile/Scrum/[fad] processes so much. Take easily understood commonsense ideas/terms and invent fancy names for them, convert heuristics to axioms and sell a business around it.
- loup-vaillant 7y ago> You must never turn estimates into a promise, Whoever asked you for that estimate will do that for you… > always remind people they are estimates. …even if you remind them. I mean, the reasonable ones won't, but many people aren't that reasonable. I've been in an interview last week where they told me the teams were strongly committed to the features they planned to do each sprint. Which I interpreted to mean that their estimates are promises. > Want to give fast estimates? Here’s how: My, this looks like it could actually work. I'm going to try it right away.
- davidjnelson 7y agoIt’s funny because even with capital a Agile / Scrum, in 2011 the term commitment got changed to forecast [1]. But then many companies who are dogmatic about Agile still use estimates as commitments anyway. That makes technical debt really hard to avoid... One solution is to create technical debt tickets in the backlog so people become aware of it. 1. https://www.scrum.org/resources/commitment-vs-forecast https://www.scrum.org/resources/commitment-vs-forecast
- ehrm2017 7y agoGreat you know how you work best. There are other ways. The best of humanity have a wide range of methods they use to get shit done at a level most of us dream of. So I have a hard time taking a straight jacket process like you suggest as some sort of panacea. It’s essentially another manifesto. What’s the expiration date on this. Everyone goes on about the value of writing less code, and here we are incentivizing manufacturing line processes for crafting more code? Note the authors of things like the Phoenix Project: rich Silicon Valley types. We’re just discussing how to be better assembly line workers for tech aristocracy. Figure out how to build your business in such a way it works for the business. Google didn’t get big because it has perfect process; it can and often is a mess. It got big solving it’s problems and monetizing the solution (every company will need to search for digital files, send email, edit docs, etc). Figure yourself out, compare with others. There’s is no one size fits all to thinking about problems and even the biggest winners don’t have all the customers there is. Why isn’t Gmail the only email solution? There’s never a perfect process.
- sbov 7y agoI do something similar, except don't assign to a number. My back of the envelope estimates are: hours, days, weeks, months. This gives people enough information as to whether or not a change is worth it. If the difference between, say, 2 and 5 days makes or breaks the feature it's probably not worth exploring in the first place.
- DigitalSea 7y ago>You must never turn estimates into a promise, always remind people they are estimates. Herein lies the problem. Many companies that do "Agile" fail to realise that estimates are just guesses, they're not accurate and yet, the issue is companies taking these estimates and holding developers to them. That's the real problem. It's all well and good to say, remind people they're only estimates, but many of us who have been in this industry longer than a minute knows that estimates nine times out of ten are taken as promises and that's when we get crunch and burnout as developers are forced to achieve the impossible with excessive hours. Deadlines need to drop dead. Code quality suffers when you put a timeframe on it.
- rramadass 7y ago>Even bad estimates are better than no estimates Absolutely not! An estimate should not be a random number but should be constrained with available data however small it might be. If you feel that you don't have enough to form a "guesstimate" do not give me a number but first work on finding the data which will enable you to form a proper estimate. Once you give an estimate, no matter how many times you explain that it is a "guesstimate" people tend to lock on to the given number. It then becomes a real battle trying to explain the hurdles (and there are always some unknowns) while revising the original estimate. Soon mutual distrust develops between the implementation engineers (stressful and detrimental to actual execution) and the management leading to everybody losing faith in estimates. Agile/Scrum have exacerbated the problem with their short time windows and sprints. In one team that i was on, people just gave up and started quoting 2 weeks for any and every feature, trivial or non-trivial and the whole exercise became meaningless. PS: The book "How to Measure Anything: Finding the Value of Intangibles in Business" is worth reading to get some ideas on how one might do proper estimation.
- dragonwriter 7y ago> Even bad estimates are better than no estimates Bad estimates are worse than no estimates, but if you are doing work complexity estimation and measuring velocity (which you need to do to evaluate internal process changes, manage workload, and for lots of other purposes), you are incidentally gathering the info you should need for excellent estimates, which are not necessarily hyperprecise but are excellent instead because they can explicitly quantify uncertainty as well as mean expected delivery time.