Hi Boudewijn,

While I do agree that the more data you have on a project generally enhances your ability to estimate the time that it takes to complete...

1) I question whether knowing how long it takes to build 1 (or even all) of a previous projects components would serve as a good indicator of what it would take to complete a future project.

2) How do you account for previously built components? Do you give them to your clients for free?

3) How does knowing how long a previous project's components took to build, help you in a situation where the client keeps changing the specifications on the new project?

Not sceptical, just interested. May I suggest you take a look at Whil Hentzen's book on the subject: http://www.hentzenwerke.com/catalogpricelists/sdg3.htm

Hugh


>Hi All,
>
>I am about to finish a project. Ready somewhere mid december.
>What it is all about is a projecthook.
>This projecthook is tracking the time needed to develop components that are part of a software application.
>The time needed to develop is stored per component.
>This data is stored in a table that is free to use.
>With that data any calculation or estimation you make about new projects is more solid then just ceiling staring or eye-alling and giving figures a wild guess.
>
>I want to sell this product commercially.
>I am now just looking for the right price.
>
>How about $ 75,= or €75,=?
>
>I am looking forward to your reactions?
>
>Boudewijn Lutgerink