[421] in Project_DB
Initial Activites for Job Flow
daemon@ATHENA.MIT.EDU (Bill Cattey)
Wed Jan 6 23:37:30 1999
Date: Wed, 6 Jan 1999 23:37:24 -0500 (EST)
From: Bill Cattey <wdc@MIT.EDU>
To: project-db@MIT.EDU
Emboldened by email exchange with Mike, and chat with Bob, I present
this slightly expanded first draft of Who and what activities, in the
hope that people will comment on it.
What is missing?
Job Flow Analysis:
Who uses the Project Database?
For what activities?
Project Leader
Creates a new project in the database
Tracks progress of project in Project Database
Informs Directors, Team Members, Interested IS Parties, and
Interested Outside Parties of project progress.
Uses DB to manage small projects.
As a convenience, for owned projects update status to reflect:
Assert/Revoke formal committment on a project
priority of project
Termination, place on hold, or re-activate of project
Uses DB as convenient list of owned projects.
Team Member
Reviews progress of project.
Tracks project items owned by him or her.
Director
Creates a new project in the database
Asserts/Revokes formal committment on a project
Reviews progress of projects
Assigns priorities to projects
Adds relevant comments on projects
Terminates, places on hold, or re-activates projects.
Uses information about projects to engage in dialogs about priorities
and resource allocation.
Uses DB as a convenient index of Project notebooks.
Uses DB as convenient list of active proejcts.
Interested IS Party
Learns ongoing status of projects
Uses information about projects to inform decision to join a project.
Interested Outside Party
Learns ongoing status of projects.
Uses information about projects to engage in dialog with Directors,
Team Leaders, or Team Members about project direction.
----
