[378] in Project_DB
Re: The project DB needs "Milestones" not "Tasks".
daemon@ATHENA.MIT.EDU (Tim McGovern)
Tue Dec 1 09:25:14 1998
In-Reply-To: <gqMkNMoGgE6e1_e380@mit.edu>
Date: Tue, 1 Dec 1998 09:27:20 -0500
To: Bill Cattey <wdc@MIT.EDU>
From: Tim McGovern <tjm@MIT.EDU>
Cc: project-db@MIT.EDU, Greg Anderson <ganderso@MIT.EDU>
Everyone --
Bill's observation about what we do is right on. We rarely do task
breakdowns for projects, and less frequently, enter those into the
project-db. I didn't immediately jump to the conclusion that what's needed
is a change in the tool, a change in features. Task Planning and
Milestones Planning share "planning," which might just be the thing we
don't like to do. The change Bill suggests, based in some part on a
reduction in keying time/planning time, is too optimistic for me this
morning, and presumes that the tool is just one feature away from changing
the behavior of project managers. If we have retooling resources to spend,
I'd rather see us eliminate some of the information in the database (or
hide it), simplify the interface, focus on the most salient information
(WWWWH) that will support the work of the ITLT users, particularly the
Practices.
Tim
>Date: Mon, 30 Nov 1998 15:55:52 -0500 (EST)
>From: Bill Cattey <wdc@MIT.EDU>
>To: project-db@MIT.EDU
>Subject: The project DB needs "Milestones" not "Tasks".
>
>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
