News for hackers. Stuff that matters.
Re:Software Estimation Is a Losing Game (2014) by AnimalMuppet on Monday October 12, 2015 @08:31PM (#10377754)
They're not useless. Except sometimes they are.

I have to give estimates all the time. They're estimates, but they're in the ballpark.

But recently, I had to give an estimate for porting some software to a new environment. I knew it was going to present me with a bunch of obstacles, and I didn't know what the obstacles were, or how long each one would take. I didn't even know how many obstacles there would be.

I didn't want to give an estimate for that. They made me give them one anyway. I did, but I knew that no reliance whatsoever could be placed on the estimate. Whereas other tasks, estimates were close to "bet the company on it" solid.

Re:Software Estimation Is a Losing Game (2014) by knieveltech on Tuesday October 13, 2015 @12:32AM (#10378567)
When we run into stuff like that at work we budget a set number of hours to breaking the problem up into chunks, researching and prototyping the sticky parts, and then using that information to put together a realistic estimate. We call it a "planning project".
Re:Software Estimation Is a Losing Game (2014) by lifeisstillgood on Tuesday October 13, 2015 @01:48AM (#10378741)
That's sensible - and is a way to lose bad clients (not itself a problem).

I am not saying project mgmt does not work, I am saying the plan the task, do the task approach is not appropriate for software development, at a given level of granularity.

If you ever watch Grand Designs, they start with a design, a plan, a schedule, and it all goes out the window ten minutes later. This is not that being on top of the process will not give you control, but that relying on estimates and plans as a means of control is worthless - and that's for something people have been doing for hundreds of years