3 ms·
I’ve got to do a lot of contract software work back in the day and was the one working first draft requirements with clients before the actual contract. It was
by LoSboccacc 8y ago
I’ve got to do a lot of contract software work back in the day and was the one working first draft requirements with clients before the actual contract.
It was common to spend a week into planning for every six man/month of project
Using that as ballpark we never got an estimate having more than 10% error.
Anectodal, I know, but without that kind of effort one is not doing an estimate is doing a guess.
That also why I don’t like the agile approach of piling up efforts and then use actual time to tune speed hoping the inaccuracies will level off one another. It just feel like a sequence of dice rolls hoping you don’t end up at the far tail of the gaussian.
- andrewflnr 8y ago> It just feel like a sequence of dice rolls hoping you don’t end up at the far tail of the gaussian. That's exactly, precisely what it is, by design AFAICT. The thing about gaussians is, what with the central limit theorem and all, you provably don't end up on their tail very often. That said, gathering a bunch more data can make your gaussian even narrower. I think you and (platonically ideal) Agile are just at different spots on the same spectrum of risk tolerance.