Path: utzoo!attcan!uunet!husc6!uwvax!vanvleck!uwmcsd1!ig!agate!garnet.berkeley.edu!csm
From: csm@garnet.berkeley.edu
Newsgroups: comp.software-eng
Subject: Re: Reporting progress on a software project
Keywords: CASE, Planning
Message-ID: <10941@agate.BERKELEY.EDU>
Date: 14 Jun 88 20:07:37 GMT
References: <917@blue.engin.umich.edu>
Sender: usenet@agate.BERKELEY.EDU
Organization: University of California, Berkeley
Lines: 42

In article <917@blue.engin.umich.edu> conliffe@caen.engin.umich.edu (Darryl C. Conliffe) writes:
>the following:  having convinced management that an iterative
>approach to a software design project is appropriate, how do you
>report progress on same? 
>...how do you project how long it will take?
> Darryl C. Conliffe  conliffe@caen.engin.umich.edu  (313) 721-6069

If management cannot judge from the prototype itself how you are
progressing, they sure as hell are not in any position to judge
from a (possibly fudged) PERT chart.  Arrange periodic hands-on
demonstrations (but no more frequently than every two weeks).  

You must have the following guarantees from the powers that be:
   1) Hardware and Software for the project will be delivered
to you on schedule or the project will be extended on a day
for day basis.  If you are not responsible for procurement  
and/or installation make sure that delays in this process are 
documented and added linearly to expected delivery date.  
   2) End-user time will be available.  You must be able to get
personnel when you need them.  Remember, verbal assurances from a
middle manager are going to be forgotten when you say you need 
two secretaries and a supervisor this Friday, all day.  The
middle manager has someone checking his/her department's progress, too.

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.