[242] in Project_DB
Notes, 10/9
daemon@ATHENA.MIT.EDU (Mike Barker)
Thu Oct 16 12:57:15 1997
To: project-db@MIT.EDU
Date: Thu, 16 Oct 1997 12:57:02 EDT
From: Mike Barker <mbarker@MIT.EDU>
Attending: wdc, miki, brlewis, tjm, mbarker
1. http://web.mit.edu/mbarker/www/process/projectdb.html
provides a beginning on the top page.
action item: mike should move this into http://web.mit.edu/project-db
action item: set up a project notebook location under that
2. Tim suggests we make a placeholder FAQ -- include whatever
questions (or problem workarounds) we already have, but mostly leave
this as a placeholder for the future.
Action Item: someone needs to grovel out the symptoms and workarounds
for old personal certificates and for when the site certificates go
bad...
Action Item: wdc wrote down that he would get common error messages
for the FAQ
3. the king is dead, long live the king! bill is going to focus on
other activities, and mike will push the project database (no, not
like Sisyphus).
There are at least two parts of what we are about: the service part,
keeping v2 running; and a discovery part, investigating customer
requirements, available technology, and baseline changes.
Action Item: Mike needs to get v3 on Greg Anderson's agenda, as a new
discovery project needing a scope, charter, etc.
4. Brenda is working on a letter to help investigate the scope of the
project. Bruce pointed out three questions of interest: What do we
want? What can we get? When can we get it?
We also talked about who "we" are and whether "we" really know what
"we" want/need/will use.
Next meeting: 10/30, e40-316
Agenda Items:
1. Action item review
Anything else? Let me know before the meeting.
Offline stuff I thought I would include:
Bill suggests that customer requirements may come from:
- directors
- project leaders
- task doers
- outsiders (interested in seeing what we are up to)
- HR (understanding where people's efforts are going)
Mike and Tim talked about the possibility of doing something with
deliverables--every "task" or "step" having a defined, visible,
concrete deliverable. This replaces tracking time with tracing
products, an easier task.
mike
