[51] in I/T Delivery
Reminder - next Delivery Team Leaders meeting 5/9 in W91-250
daemon@ATHENA.MIT.EDU (Robert V. Ferrara)
Fri May 2 19:17:44 1997
Date: Fri, 2 May 1997 19:21:16 -0400
To: delivery@MIT.EDU
From: rferrara@MIT.EDU (Robert V. Ferrara)
Cc: ehoffer@MIT.EDU
Delivery Team Leaders,
I'll be away much of next week, so this is an early reminder for the
next meeting which is Friday, 5/9 in W91-250. There are at least 3 items
I'd hope you can give some attention to prior to then, however.
1) Project Database. Please update all your project by 5/9. This database
has been "delivered" and is to become our system of record. An I/S Forum is
planned for late May and whatever is in the database on 5/15 is what's
going to be printed and distributed from now on. Several projects are out
of date. Also, it's OK to put any marginal or personal ones in there as
well. Thank you. And thanks to the project-db team for getting it to this
point.
2) I/S Forum "exhibits". Several teams have already decided to put up a
simple but informative exhibit at the next I/S Forum. Erin Hoffer's offer
to ILEAD described a very low overhead, quick preparation approach to
putting something together. If you want to do something simple to inform
(or recruit?) Forum attendees, please let Erin or me know.
3) Delivery Vision. Back in October, we put together a "vision" document
and now it's time to review it. (See attached).
Also, a lot has happened in the SAP project world (e.g. new rollout plan)
and I'm looking forward to discussing that with you. Please suggest any
other items,
updates, etc.
Cheers, see you Friday, Bob
-------------------------------------------------------------------------------
DELIVERY VISION FOR 7/1/98
This is a formatted, organized list of the ideas developed at the
10/11/96 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
