[377] in Project_DB
The project DB needs "Milestones" not "Tasks".
daemon@ATHENA.MIT.EDU (Bill Cattey)
Mon Nov 30 15:56:02 1998
Date: Mon, 30 Nov 1998 15:55:52 -0500 (EST)
From: Bill Cattey <wdc@MIT.EDU>
To: project-db@MIT.EDU
In our trying to guess the right way to apply the Project Database, we
put in support to record tasks, along with time estimates. The activity
of planning, estimating, and reviewing actual time elapsed is an
important part of project management.
We virtually never do it.
Right now, I feel that the work flow of the Project Database makes
planning and tracking of tasks very difficult. I have a radical
proposal:
Convert the task interface of the Project DB to a milestones interface.
----
I have the sense that there is consensus from ITLT that the Project
Database needs to improve its ability to help us report project status.
A sentence at the beginning of each quarter is not enough.
A sentence every time we complete a significant milestone may be just
the ticket!
Thinking to the experience Team Athena has had with weekly status
reports, people can actually get into the habit of reporting one major
task accomplished.
I've taken this approach for reporting status on the E-Thesis Submission
project:
https://arachne.mit.edu/fcgi-bin/brlfcgi/brlpdb/projpage.html?projid=286
What say the rest of you?
-wdc
