On 6/19/07, M. Adam Davis <stienman@gmail.com> wrote:
> I'm just curious:
>
> 1. How long (months) is a typical development cycle for your
> successful projects?  (from define requirements through project
> delivery)
>
> 2. What percentage of projects are canceled or put on the back burner
> indefinitely?
>
> 3. How long (months) is a typical development cycle for your cancelled projects?
>
> 4. In very general terms, give your top reason for project
> cancellation/failure/infinite delay.
>
> Assume these are paid-for design projects (either for work,
> consulting, etc).  We'll discount personal free-time projects, as well
> as maintenance and upgrade projects.  Also note that these won't
> amount to a hill of beans since you'd have to take into account
> project size, scope, team, experience, tools, resources, etc.
>
> For me:
>
> 1. Average 10 months product development time, successful projects
> 2. About 25% are canceled
> 3. Average 8 months product development time, unsuccessful projects
> 4. The product doesn't meet cost of goods target

What is the medium complexity of those projects (in number of:
routes/drills, components, PCB layers, number of asm or HLL code lines
per project) ?
thx,
Vasile
-- 
http://www.piclist.com PIC/SX FAQ & list archive
View/change your membership options at
http://mailman.mit.edu/mailman/listinfo/piclist