[631] in magellan
Minutes: 13 April 2001 Project Team Leaders meeting.
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Apr 13 12:06:40 2001
Message-ID: <oupmEKlz000143t0Ij@mit.edu>
Date: Fri, 13 Apr 2001 16:06:46 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: magellan@mit.edu, delivery@mit.edu, integration-ptl@mit.edu
Minutes:
Project Team Leaders
13 April 2001
Next Meeting: May 18th at 10:30 in a location to be announced.
Agenda:
1. Project Leader Responsibilities
2. Project Closout Process
3. Performance Appraisal
4. Roundtable
----
Detail:
1. Project Leader Responsibilities
Bob handed out a paper copy of the Project Leader Responsibilities
web page and we went over it. Observations:
We're not consistently enough announcing projects.
Praise for our having made project notebooks nearly universal.
With regards to checkins:
Everybody pretty much understands about Integration checkins.
Doing Post Project Review has demonstrated benefits, but is not
being done by the majority of projects.
Check ins with Usability and Service should be added to the
Responsibilities.
--
2. Project Closeout Process:
Bob drafted a basic closeout process and solicited feedback.
1. Post Project Review
2. Performance Appraisals
3. Button up Notebook -- Final Documentation
4. Rewards!
5. Party! (Can be part of #1 above)
Comments:
Post project review clinics in Magellan (Discovery Team Leaders) has
been shown to be valuable.
Debrief among peers
Debrief with team itself
What did success look like? With regards to:
results
process
relationships
What about different kinds of sponsor conversation?
Example of "Design Objectives Sign Off" document.
Final cleanups of the Project Notebook have not been happening enough.
Suggestion for a 30 day review period during which final project
notebook work is reviewed and finalized.
Who pays for the rewards and parties? There are proper ways to
account for this so that MIT will pay.
--
3. Performance Appraisal
Quick update and follow-on to the presentation made at ILEAD of the
Project Performance Review and Project Team Member Evaluation.
Ed Dolan handed out a paper copy of the Project Team Member Evaluation
web page which serves as a checklist for what to do.
Comments:
The Team Member Evaluation form is supposed to be sa quick and easy
way to review how members tune into the "team norms". Team norms are
the relationships, ground rules, and way of working that gets
established early in the project, and get refined as the project goes
on. The Form was designed to be independent of any specific set of
team norms. For that reason it rightly seems a bit abstract. :-)
--
4. Roundtable:
wdc -- "Bill's guesses"
Bill asked for some time to share some prognostications about
certain UNIX application packages. [Please forgive the length of
the entry in the minutes, but I want to get wide circulation of these
ideas. -- wdc]
"More robust web browser", and "Microsoft Word for UNIX" are
frequent requests from customers. It may be that within the
next 12-18 months, the world may provide relief here:
OpenOffice.org + Sun Star Office: Star Office was some of the
way there, and is now under active development with the OpenOffice.org
free software project. Sun will periodically synch Star Office with
that effort. Formal usability testing is under way. Significant
input from the community is being incorporated. Very exciting!
Netscape 6 + Mozilla: It looks like Netscape 6 as we have it was a
marketing ploy to keep Netscape on people's lips. ("Any publicity,
even bad publicity is good.") Looking at the issue logs it seems like
Netscape will synch with Mozilla periodically, and that the resulting
product, when it crosses the 'good enough' threshold will be easier to
maintain, more cross platform, and very responsive. Also very
exciting!
These are two examples of where partnering with a company was tried
and failed, but where stepping back, and becoming involved in a free
software project turns into a low cost way to close the gap between
the product's functionality and our requirements.
dsheehan -- Libraries GIS hire / Delivery
Libraries GIS hiring is moving along. Several candidates have been
interviewed.
The GIS Delivery is moving forward.
Kelley -- ITS (Internet Transaction Server -- SAP Web front end to R3
server.)
SAP has delayed delivery of ITS on Linux, so the ITS on NT has been
reactivated. The primary work is to resolve the security issues in
deploying an NT ITS server.
Gerry Isaacson - Business Continuity -- On April 4 a simulation of the
burn-down of Facilities was made. Writing of the final report is
under way. Things of value to averting disasters were learned.
rferrara -- EAST
The Enterprise Application Software Team has been formed. Coeus and
Telecom apps are the big applications, but the others are also
significant. The team's job is to see to the ongoing care and
maintenance of certain enterprise-wide applications in a way that
makes best balance of resources and benefits.
rferrara -- IS Work Activities
Directors are finding the IS-Work database helpful as they check in
each quarter. The database has been extended to activities, and there
is the hope that all the standing teams will be represented by the end
of this month.
jag/ganderso -- Web Surveys
MIT has a need for web-based surveys to the extent that the various
ad-hoc methods are being codified into something more common and
widely applicable. Expect a project announcement soon.
edolan -- Mastering Meetings
May 14 there will be a new session of Mastering Meetings as a one-day
event. The one-day format is in response to people asking for a
different way of organizing the material. There have been 2 and 3 day
formats in the past.
