[83] in Tooltime
Tooltime meeting notes April 30, 1996
daemon@ATHENA.MIT.EDU (Steven Wade Neiterman)
Tue Apr 30 12:51:02 1996
Date: Tue, 30 Apr 1996 12:51:24 -0400
To: tooltime@MIT.EDU
From: wade@MIT.EDU (Steven Wade Neiterman)
Cc: dupuis@MIT.EDU
Tooltime meeting April 30, 1996
Attending: Sousa, Dupuis, Fermann, Thomas, Lane, Charbonneau, Wade
Agenda:
- Team dynamics
- Review project plan
- Prep for kick-off meeting
- Review status/checklist
- Review roles and responsibilities
- Issues
1. Team dynamics
- Established that tooltime mailing list will be used as often as
possible to convey status, ask questions, solicit people for tasks.
- Welcome Chad Dupuis from ACS. Chad represents the Faculty Liaison and
OLTA issues. He will help write a document evaluating Scopus for
deployment to business customers beyond the Help Desk. (Carla to
add Chad to the tooltime mailing list).
- Wade started to write short weekly status reports. Last week's report
is on the Web. The team decided that these reports will be sent to
the tooltime list.
- There may be a number of requests to attend meetings on specific topics,
e.g. legacy data transfer, testing, quality assurance, communication,
forms definition, etc.
2. Review project plan
- Consultant starts today or tomorrow (4/30). Carla to establish
an account for tarnett@mit.edu.
- Wade handed out project plan detailed for the first nine days. The
summary task (document release 1.0 functionality) has 13 items.
- Issue: Important to give adequate feedback to consultant. People
identified for this activity. Some people are in transition (vacation,
new job). This document represents the work that will be conducted
for an estimated June 30 release.
- Team to send changes on either the project plan or the calendar
representing the monthly activities.
3. Prep for kick-off meeting
- Kick-off meeting 10:00 am 11-124A 5/1/96
- Kick-off meeting Goal:
a. Have consultant meet team members, ask questions
b. Team meet consultant, ask questions
c. Consensus on next nine days of activities
d. Answer questions, help consultant set expectations
- Expect around a dozen people
4. Review status/checklist
- Not much feedback, updated version available on the Web
- Team should send in comments, updates.
- The major list of activities are maintained in four status/checklist
documents. The goal is to keep a global view of what needs to be
done, track progress.
5. Review roles and responsibilities
- Not much feedback
- Wade would like people to take on specific roles, e.g. someone to
lead with testing, deployment, configuration, operational stability, etc.
- No volunteers for specific roles, for now, we will maintain a list of
what needs to get done and evaluate if these tasks are being performed.
If not, we will need to change how we operate.
6. Issues
- Short time period for implementation. Need to review two goals:
1. Meet core business (enter data, etc.), 80/20 rule stuff
2. Create operational stability
- Some items will not get done, need to understand trade-offs,
communicate and prioritize
- Need others to help pick up tasks before being asked
