[12] in I/T Delivery
Minutes of 13 December 1996 Meeting
daemon@ATHENA.MIT.EDU (Robert V. Ferrara)
Mon Dec 30 08:50:40 1996
Date: Mon, 30 Dec 1996 08:53:42 -0500
To: delivery-mtg@menelaus.mit.edu
From: rferrara@MIT.EDU (Robert V. Ferrara)
>Date: Fri, 13 Dec 96 11:53:02 EST
>From: wdc@MIT.EDU (Bill Cattey On the Road)
>To: sauons@MIT.EDU, delivery@MIT.EDU
>Subject: 13 December 1996 Meeting
>
>Next meeting: Friday 27 December 10:00 AM E19-741
>
>Updates:
> Budget narrative is pretty much there. Dec 20 deadline
> is tight, but should be ready on time.
> Project Database is on track. Goint to ask The Database Group
> to take care of it. Need to find out whether DB group will]
> feel more comfortable housing the DB on their own machine or
> a new machine.
> Next round of Duncan-Nevison Project Management course coming up.
> Soliciting feedback. Especially things that we do different
> and better as a consequence of taking the course.
> Delivery Web pages -- Do please review them.
> Members around the table have the action item to look at these
> pages and sign off on going live on them. Deadline is next Fri.
> (Feedback to jlittell)
> Open Positions: 4 Project Manager Positions (3 related to delivery)
> Brainstormed what sorts of skills these folks should have.
> 5 Year plan section. Has been submitted.
>
>----
>Moving forward on the Technical Competencies.
> Descriptions are "pretty raw".
> "Technical" really means "Disciplinary"
> Talked about issues in setting the scope of the Competency model:
> At what point does the model end, and the interview, or self
> evaluation get into details? The point was made that the
> dichotomy between Skills and Competencies in how we heard about
> the Competency stuff is applicable here.
>
> Need levels for the Disciplinary competencies.
> We think we have 4 levels here, and they're different from
> the 5 levels that Hay has for the Behavioral competencies.
>
> Point: WHEN (in addition to at job interview time) do we use
> this competency stuff? The roll-out will sort of encourage
> people to try the stuff out the first time around. After that
> maybe there'll evolve periodic times to do this formally. Or
> it may turn into a sort of background common way of
> understanding ourselves and talking about ourselves.
>
>----
>Putting more of Delivery Process in place:
> Project leader responsibilities
> Maintain project DB entry for project.
> Generate and maintain Work Breakdown Structure.
> Generate Resource Estimates
> Maintain Proejct notebook.
>
> Initial emphasis on Work Breakdown Structure
> Issue: what is the standard of maintenance -- how often is
> the WBS updated?
> Resource Estimates
> Project notebooks.
>
> Where is it recorded what the project status is? Project DB.
> DB Schema has field for Issues, but how do we find out the REAL
> BIG issues?
>
>----
>Roundtable
>
>Rocklyn: SAP web is clarifying its objectives. Simultaneously
>investigating modifying SAP/r3 web product and developing our own.
>Whichever works best first wins. (This is a discovery poject.)
>
>Jana: TQF: New release being planned. New requirements were discovered.
>Release will incorporate additional functionality requested by customer.
>
>wdc: Quick Stations have been being examined with regards to
>requirements, timeline, resources needed and available. Side issue: if
>we're gonna do Work Breakdowns and Estimates, the initial response to
>them should not be "We don''t believe you. Come back with one we like
>better."
>
>Back of the envelope expectation with regards to what will end up
>getting delivered for Athena Release: We expect we'll be moving and not
>have much resources for this work. We expect Mark Virtue's departure
>will have significant SGI impact. Even so we expect we WILL do an
>Athena 8.1 to take advantage of our new infrastructure. It will
>probably based on Solaris 2.5.1, and Either IRIX 5.3 or 6.2 (NOT 6.3
>which is required to run the O2 hardware.)
>
>Bob: Data Warehouse: Six heavy duty centers at MIT reported to Bill
>Dickson that they want to join up with the IS Data Warehouse. The only
>problem is that they want REALLY ambitious deadlines.
>
