[386] in magellan
Class Participants Lists, February 3, 2000
daemon@ATHENA.MIT.EDU (Tim McGovern)
Thu Feb 3 10:53:42 2000
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Message-Id: <v04020a02b4bf52578a18@[18.152.1.21]>
Date: Thu, 3 Feb 2000 10:53:36 -0500
To: magellan@MIT.EDU
From: Tim McGovern <tjm@MIT.EDU>
Cc: grouper@MIT.EDU
Project Name: Class Participants Lists
Project Leaders: Tim McGovern
Report Date: February 3, 2000
Project Notebooks: http://mit.edu/is/discovery/grouper/ &
http://mit.edu/is/delivery/grouper/
Goals listed in last report
1 Wait on meeting between Registrar and a small number of faculty
2 Brief project sponsors on the completion of Delivery efforts in this project
3 Schedule final meeting (approx. mid-February) and celebration for project.
Accomplishments past period
- Registrar met with a small number of faculty regarding classroom
practices w.r.t. grouper. The upshot of that meeting was this message
from Mary Callahan:
...the sense of the group was that only registered students
may attend the class. To the extent that "guests" go to class,
enforcement of this varies between departments. Although each
person stressed that this is not a large problem in terms of number.
An occasional visiting scholar, an occasional colleague.
In addition, most felt the type of classes where "guests" attend
at this time are not widely web based and really don't require
the class participant security.
- Dan Winship has completed his work to transfer data into Moira's test
database, and has left MIT. The status of the development effort
and operational status is unclear until
- Scheduled a briefing with project sponsor on the Delivery efforts
- No progress on scheduling the celebration.
Goals for the coming period (or so)
- Meet with IS project sponsor
- Attempt to determine where the Moira development -> operations situation is
- Schedule final meeting (approx. mid-February) and celebration for project.
Issues
- There continues to be an over reliance on personalizing tasks. When
a key contributor leaves abruptly, there is no good way to ensure that
the development efforts are continued without major time gaps. The upshot
of this is that promises to sponsors and customers are often held at risk
because of this situation.
Key learnings
- None
Team dynamics
- We're pretty much done.
Additional comments
- None
