[UPHPU] Software Development Scheduling advice
dbaker at efilecabinet.com
Tue Jan 30 13:54:41 MST 2007
> I'm having to put together a software development schedule here at
> work. I'm working on version 2.0 of an app and now my boss wants a
> schedule. I'm having a hard time estimating how long tasks will take.
> I'm looking for techniques and advice on how to set this up. Any ideas?
The general rule of thumb is as follows:
*After* you come up with your estimate, then double the value, and increase
the unit of measure by one.
So, if the estimate ends up being 40 weeks -- it really means 80 months.
Estimating software is a black art. I've met people that are really good at
it. I've also met people that are terrible at it.
To do it justice, you need several years of experience with the following:
1) The team of programmers
2) The project
3) The management staff that will be altering the schedule after you produce
Typically, I allow management to select all but one of the following
criteria, and I fill in the one they didn't. Usually, management picks the
ship date and resources, and I generate the feature set that can be created
within the time allotted with the man power given.
1) When the product will ship
2) Resource for the product (programmers, testers)
3) Feature set
Of course, the reality is that management will mandate all three -- which
never comes out well.
More information about the UPHPU