[211] in magellan
18 June 1999, Minutes, Project Team Leaders
daemon@ATHENA.MIT.EDU (Bill Cattey)
Fri Jun 18 18:44:13 1999
Message-Id: <orOgjW1z00014EZEJd@mit.edu>
Date: Fri, 18 Jun 1999 22:44:50 +0000 ()
From: Bill Cattey <wdc@MIT.EDU>
To: magellan@MIT.EDU, delivery@MIT.EDU, support-tl@MIT.EDU,
integration-ptl@MIT.EDU, tregan@MIT.EDU, vkumar@MIT.EDU,
dbaron@MIT.EDU, hogue@MIT.EDU
Minutes: Project Team Leaders
18 June 1999
Next meeting:
July 23, 1999
10:00-12:00
N42 Demo Center
--------
Agenda:
1. Process for delivering work from the project teams to Support standing
teams (60 minutes or longer - more detail below)
- Introduction - Bob Ferrara
- Small Groups - Greg Anderson
- Report back & discussion - Bill Hogue
2. Project Database rollout - Mike Barker (20 minutes)
3. Roundtable 20 minutes.
--------
2. Project Database Rollout:
Mike Barker described the changes (simplifications, primarily)
to the Project Database.
In concept the changes are:
1. Directors responsible for project db. Information relatively stable
2. Project Leaders/ Team members maintain project notebooks.
The information that chnages goes in the project noteboks.
For project notebook templates:
attach pm
cp /mit/pm/notebook/* mylocker/www
3. The Project Database WILL be used to communicate significant
changes:
status
target date / end date
comments
He handed out a single double-sided page detailing the changes.
Then he gave a demo of the test system.
You should try it out:
http://gypsy.mit.edu
https://gypsy.mit.edu
Please try it and email project-db@mit.edu with any concerns.
VERY SOON we'll switch over to this version.
----
1. Process for delivering work from the project teams to Support standing
teams:
How do we manage the transition of a project from
Discovery/Delivery/Integration into Support?
Questions:
- What, when, and how do Support Team Leaders and standing teams need to
know about projects in order for the project teams to design and build the
support functions for the new product/service?
- What are Support requirements/needs? How can these goals be achieved?
- How can a project team get Support input and design early in the project
work so that it can incorporate those perspectives in the design and
development phases?
- What and when are the key inputs necessary to incorporate Support
principles into new technology design and delivery?
We broke into smaller groups. (I was surprised at how we actually
discovered important new understanding.)
Bill Hogue Facilitated a presentation of the hottest insights from the
subgroups. Greg logged the information.
Another similar discussion will take place with a Service Focus.
----
3. Roundtable Items
* Build vs Buy Process -- Bob Ferrara reminds us that he's working
on changing the Delivery web pages to better document the Buy aspect
of Delivery. But that effort is waiting on more resources.
* Y2K Status Report -- Reid Pinchback in absentia. Reid has cooked
up a very good web page for presenting and updating Y2K reports.
https://y2k.mit.edu/servlets/Y2K.Servlet
(Note capitalization in Y2K.Servlet!)
* BCMT -- Gerry Isaacson. Business Continuity Management Team.
Coordinating Y2K business continuity across New Year's weekend.
* Telecom -- Jana Terashenko -- Telecom financial feeds, for example, Summit
information is going into Data Warehouse. 'B' Class service phones
which take an account number for long distance dialing. A default
account is getting put onto those phones. Telecom applications are
being ported from Ultrix to Solaris, and a Y2K compliant version of
Oracle.
* Pismere -- Tom Thornton. To disseminate information on the mass of
new technologies associated with Pismere, there will be bi-weekly
technical briefings. The first one is today.
* Network Install -- Brenda Gillingham. June 29th *MG will report on
the Network Install team.
* 4.5 SAP -- Bob Ferrara. BIG update of SAP is coming. Consequence:
Going to a new generation of hardware and storage architecture.
* Software Release Team -- Mike Barker. PC and Mac software install
project. Many new Installers being developed.
----
