Re:Poor developer estimates, a.k.a. guesstimation
by jacques_chester on Sunday September 15, 2013 @10:52AM
(#6389244)
> It's important to understand that by separating these concepts, you're not pressured to make time commitments when spitballing story difficulty. That's a good thing. Decouple those concepts and leave them decoupled.
I was taught by my software engineering professor to estimate software projects by size first and then to transform that into effort, then from effort into cost/schedule. He emphasised, like you do, that they need to be treated separately.
In his day size was projected in kSLOC or function points. These days you'd use story points. It's the same principle, in my opinion.
I was taught by my software engineering professor to estimate software projects by size first and then to transform that into effort, then from effort into cost/schedule. He emphasised, like you do, that they need to be treated separately.
In his day size was projected in kSLOC or function points. These days you'd use story points. It's the same principle, in my opinion.