[26] in I/T Delivery
Delivery Team Meeting 14 February 1997
daemon@ATHENA.MIT.EDU (Bill Cattey On the Road)
Tue Feb 18 12:24:32 1997
Date: Fri, 14 Feb 97 11:38:42 EST
From: wdc@MIT.EDU (Bill Cattey On the Road)
To: saurons@MIT.EDU, delivery@MIT.EDU
Next Delivery Team Meeting will be held
March 7th 10:00 AM
In E40 in a room to be announced.
(Wade will be demoing Scopus.)
Updates:
Project Database:
Will the updated project list go in? Yes.
Will the Project Database completely replace the word document?
Not yet.
But DEFINITELY that is the end goal.
There is a problem getting the descriptions in: SQL loader chokes.
Wade has a C program that DOES enable loading of this stuff.
Customers need to set their expectations remembering:
This system is going live without a User Interface Design Review.
The user interface will probably be pretty much as it is now,
but MAY change in the near term.
We have not exhaustively tested every path through the system.
We will be VERY responsive to bug reports and customer feedback.
Energizing IT-PROJECT-LIST:
Everybody should send ONE idea to rferrara to help improve the
dissemination of information of projects.
The list is not the whole solution.
Keeping Delivery Web Pages Current:
Instead of re-converting the latest version of the Word documents
We're gonna use the Projects Database.
This assumes that a useful feed will be available in on the order
of two weeks.
If the access without certificates is not available in that timeframe,
there is no problem with someone manually extracting the Project
DB snapshot and hand-installing it periodically in the Delivery
pages.
Issue of project team web pages:
Bill raised the issue that the Team Athena web pages are not well
represented.
Various folks around the table felt that maybe the project database
should point at project team pages.
Bill reminded everyone that the project database is currently framed
as a project tracking DATABASE, not a coherent forum for
presenting team information.
SAP R/3:
Presentations on visibility of data have been made to senior folks.
(The visibility issue is: Anyone who can submit a requisition to SAP
can view ANYBODY's requisition inside SAP. Changing this is VERY
difficult.)
Recommendations will be brought to Academic Council.
SAP Web is very much alive, and the Access issue may well be
simplified if the recommendations on data visibility
are accepted.
The Process Owner's council on SAP has been convened by Bill Dickson.
Department heads involved in SAP were there. This represents a
good bringing together of stakeholders that hasn't really happend
well enough in the past.
Performance Appraisal:
Primary reviewers are responsible for contacting their reviewees
and announcing themselves as the reviewers.
Comments on IS Forum:
Maybe Bill is being over critical in his expression of wanting to
have seen more about relief from overload, and better unification
of the talks.
