5 ms·
> The business wants to know how much feature X is going to cost and when they can expect it. Of course they do. We all want things that are impossible to have
by BurningFrog 8y ago
> The business wants to know how much feature X is going to cost and when they can expect it.
Of course they do. We all want things that are impossible to have. I want to know the AAPL stock price in 6 months.
The traditional way to manage this impossibility is that engineering lies about it (they have to lie, because they can't know either), and once people are lying to each other, trust is unlikely to arise.
The agile concept of "velocity" is the best way I know of managing this. It's not very good, and it's often a victim of Goodhart's law.
- jrs235 8y agoAnd velocity should be an internal team measurement not shared with outsiders because (Goodhart's Law) when management says "Let's increase our velocity" and the team and developers are GRADED/PROMOTED on their velocity then you'll get point/estimate inflation which will hurt you more in the long run since the inflated estimates actually now allow for the work to fill the time (Parkinson's law).
- borski 8y agoEngineering does not have to lie. All this takes is design and specification upfront, a well-defined feature set, and room for error. Also, avoiding scope creep is paramount.
- pas 8y agoWhat's the usual processing speed of a software engineer when it comes to reading through and understanding design & specification? We found that usually either the documentation/specification/requirements are too fine grained (and then they then change all the time, but then there's no real effort/bandwidth to do change management on the specs), or they are not detailed enough, which makes the estimation process a useless guessing game on what might they mean by this or that.
- borski 8y agoSee, I would expect the engineers to pipe up and explain that. It takes collaboration to get it right, and it takes the engineers setting expectations properly for what they need to estimate accurately. It’s a collaborative effort, not a one-way street, as with most things.
- BurningFrog 8y ago“Walking on water and developing software from a specification are easy if both are frozen.” - Edward V Berard
- mattmanser 8y agoIt's not impossible to estimate roughly how long something will take. If you consistently get it wrong, either: 1. You're not breaking down the work into small enough chunks to properly think about how long it will take 2. You are probably consistently under (or rarely over) estimating and should be able to fix that. For me, I have to triple my estimates, it always takes 3 times longer than I think it would To claim estimating is "impossible", when many of us do it absolutely fine, is ludicrous. Separately, there's scope creep, but that's another matter and again can be managed (e.g. "if you want X extra functionality for the same cost, you're going to have to drop feature Y, which will take roughly the same time").
- andrewprock 8y agoAdvocating process solutions over people solutions is precisely non-agile. If people are burning out, then you need to address that. Estimation is hard. Accurate estimation is even harder. Doing it in the face of noon stationary scope is a fools game. Who is in charge of estimating how long it will take to correctly break down a problem into accurately estimable sizes?
- mattmanser 8y agoIt doesn't have to be accurate it just has to be order-of-magnitude right. We're talking about a rough estimate of how much feature X costs. If something costs 15k instead of 10k, that's understandable, if you estimated 10k and it ultimately costs 1.5 million to develop, obviously not.
- v-erne 8y ago50% off is understandable ? Where can I find such forgiving clients? My clients lawyers would eat me alive if I would start to bill them in such manner. They dont want to hear about uncertainty - they are buying professionals and this kind of estimations looks to them like we dont know what we are doing.
- AlexCoventry 8y ago
- dragonwriter 8y ago> The traditional way to manage this impossibility is that engineering lies about it (they have to lie, because they can't know either) Honest estimates with uncertainty are not lies, and not having certainty doesn't prevent estimation. But, yes, people seem to often decide that being uncertain justifies self-serving lies instead of honesty (and sometimes the environment encourages that by punishing honest estimates.)