Path: utzoo!attcan!uunet!husc6!mailrus!caen.engin.umich.edu!conliffe
From: conliffe@caen.engin.umich.edu (Darryl C. Conliffe)
Newsgroups: comp.software-eng
Subject: Reporting progress on a software project
Keywords: CASE, Planning
Message-ID: <917@blue.engin.umich.edu>
Date: 13 Jun 88 14:14:35 GMT
Organization: caen
Lines: 23

I would like suggestions and/or reports on how others accomplish
the following:  having convinced management that an iterative
approach to a software design project is appropriate, how do you
report progress on same?  Since you are not proceding linearly
through a series of measurable milestones, what *DO* you use to
indicate that the development is "on schedule"?

This seems to be a corollary of the question "why aren't you
coding yet?", but it also represents management's valid need to know
if the appropriate resources are allocated to a job and that the
plan of attack is correct.

Finally, when employing Structured Analysis and while still working
out the layout and definition of your "bubbles", how do you project
how long it will take?  (This is a new system and the design tools
and approach have not been used before on ANY project, no no "history"
is available.)

-- 
___________________

 Darryl C. Conliffe  conliffe@caen.engin.umich.edu  (313) 721-6069
-------------------