[6] in I/T Delivery
Re: 10/25 Delivery Team Leaders meeting
daemon@ATHENA.MIT.EDU (Robert V. Ferrara)
Mon Dec 30 08:46:23 1996
Date: Mon, 30 Dec 1996 08:49:24 -0500
To: delivery-mtg@menelaus.mit.edu
From: rferrara@MIT.EDU (Robert V. Ferrara)
>Date: Thu, 24 Oct 1996 07:38:53 -0500
>To: delivery
>From: rferrara@mit.edu (Robert V. Ferrara)
>Subject: Re: Delivery Team Leaders meeting
>Cc: cavan, ken, sm, greg
>Bcc:
>X-Attachments:
>
>Delivery Team Leaders,
> Our third meeting is this Friday 10/25 at 10:00 in E40-262. It should
>not last beyond noon. The topics right now include:
>
> * The Goals submitted for the Five Year Plan (attached) - Thanks for
>the good
> input ast meeting
> * A look at the new SAP organization chart
> * How Pubs can help in our Delivery projects
> * A discussion of the Admissions discovery effort, led by Greg Anderson
> * Roundtable, including brief status of each delivery effort
>
>If you have a topic that belongs of this or future agendas, please let me
>know. For the following meeting on November 8, Susan Minai-Azary will go
>over with us the Integration "checklist" that is evolving.
>
>See you then, Bob
>
>---------------------------------------------------------------------------
>---
>
> DELIVERY GOALS and VISION FOR 7/1/98
>
> This is a formatted, organized list of the ideas developed at the
>10/11 Delivery Project Leaders meeting in W91. In addition, Mike
>Barker's notes have been plagiarized extensively, particularly in the
>Operational section.
>
>BASIC (ACHIEVABLE MUCH EARLIER)
>
>* All projects "on the radar" in widely visible project database
>* Project notebooks standard, updates managed by project leaders
>* IS/resources database, maintained by Competency Groups, also widely visible
>* Predictable forums and sources of additional help for Delivery Leaders
>
>OPERATIONAL
>
>* Strong integration influence, including "checklist" (e.g. warehouse, roles)
>* Core project techniques established, including :
> - Planning and estimating techniques
> - Standard peer reviews
> - Project tracking system, with early warning ability
>* Better calibration of organizational "capacity"
>* Pilot of recommended methodology, with quality metrics, in process
>
>ORGANIZATIONAL
>
>* Process-oriented style firmly established
>* People comfortable with multiple projects, fluid movement between
> projects and processes
>* Opportunities and skill requirements very visible
>* Small number of research projects supported (e.g. web interfaces,
>object-oriented prototyping)
>
>PROJECT-RELATED
>
>* Several successful completion and transfers to Service and Support
>* Athena source trees fully functional
>* Strong IT partnerships to all non-IS staffed projects
>* Good links to Reengineering initiatives
>
>SKILLS (FOR COMPETENCY GROUP CONSIDERATION)
>
>* ABAP and SAP skills in MIT community, less Contractor dependency
>* More business analyst, system integration, project management talent
>* Deeper Powerbuilder, Oracle, and Release Engineering skills
>* Maintain leading edge security and web capabilities
>