[lodwick]

A comment on schedules:
Ok, how long will it take?
For each manager involved in initial meetings add one month.
For each manager who says "data flow analysis" add another month.
For each unique end-user type add one month.
For each unknown software package to be employed add two months.
For each unknown hardware device add two months.
For each 100 miles between developer and installation add one month.
For each type of communication channel add one month.
If an IBM mainframe shop is involved and you are working on a non-IBM
system add 6 months.
If an IBM mainframe shop is involved and you are working on an IBM
system add 9 months.
Round up to the nearest half-year.
--Brad Sherman
By the way, ALL software projects are done by iterative prototyping.
Some companies call their prototypes "releases", that's all.

[Sundog]

Good one.

And the corrolary, If a developer gives you an estimate in time for a project, double the number and up the units. If he says 2 days, that means 4 weeks. If he says 1 month, that means 2 quarters. If he says 3 hours, that means 6 days, etc.

1 year is a special value. It means the time is indeterminate, and after working for a year he should be asked again. 1 year is typically the upper limit that management can conceive for a software project.