[301] in I/T Delivery

home help back first fref pref prev next nref lref last post

Monthly project reporting

daemon@ATHENA.MIT.EDU (Robert Ferrara)
Wed Jun 7 18:35:32 2000

Message-Id: <4.3.2.7.2.20000607090208.00b5baf8@po9.mit.edu>
Date: Wed, 07 Jun 2000 18:32:56 -0400
To: delivery@mit.edu
From: Robert Ferrara <rferrara@MIT.EDU>
Cc: itlt@mit.edu
Mime-Version: 1.0
Content-Type: multipart/alternative;
	boundary="=====================_2114410==_.ALT"

--=====================_2114410==_.ALT
Content-Type: text/plain; charset="us-ascii"

Hello Delivery Project Leaders,  

At the last Project Leaders meeting, we discussed updating the Project Leaders Responsibilities. Since then, I have talked to a number of you individually and can now be very specific about expectations. All your comments, including those at the meeting,   have been incorporated  and the updated set of responsibilities is now the "official" one at  http://web.mit.edu/pm/projectresp.html. Please recall that these involved  the introduction of regular monthly reporting, like the Magellan (Discovery) group does today. These reports will be due at the last Friday of month, or June 30th. 

As you may be aware, we now have a renewed requirement for Quarterly Reports that begins at the conclusion of this month, so this timing will work out very well from that standpoint. Please recall that the outline is identical to Magellan's (see example below). Magellan uses a two week cycle. For Delivery, however, since our project cycles are somewhat longer, an update is expected only by the last Friday of the month. 

As most of you know, the Discovery leaders have found these useful, and especially after the first one is done, quite easy to update and send out. They guarantee that there is at least some periodic record of the progress of your project. You should send your monthly report to delivery@mit.edu. All reports are automatically archived for your convenience, and for others to see, in the delivery discuss meeting on menelaus.mit.edu. In addition, you should strongly consider sending your monthly report to your project's  sponsor, to the project team doing the work, and with any other individuals or groups who would be appropriate.

A similar request is being made by Susan Minai-Azary for monthly reporting on Integration projects, so all our projects should soon be following a similar, simple pattern. At our Friday, June 23rd Project Leaders Meeting we have reserved some time for questions and comments on this new monthly reporting procedure. So please bring any items up then, or feel free to contact me beforehand. 

Cheers, Bob 

--------------------Beginning of Report Sample------------------
Project Name: EHSS - Environmental Health & Safety Management System 
Project Leader: Rob Smyser, Rocklyn Clarke 
Report Date: May 12, 2000 
Submitted by: Rob Smyser 
URL: http://web.mit.edu/is/discovery/ehss/ 

Accomplishments past period: 
- Jim Curtis and Rocklyn presented a second executive level summary view of the project to members of the larger Environmental, Health and Safety staffs at an offsite at University Park hotel.

Goals for the coming period: 
- meet with EMAX technical people next week (5/16) to discuss their purchasing authorizations technology versus ours. Lorraine Rappaport, Tom Hoole and Jim Repa should be attending. 
- Refine underlying data model with Scott and the team. 
- Have a conversation with Susan Azary re integration perspective. 
- Assemble more design details to support ballpark cost estimates. 
- being to prepare for a ExecVP/Provost/Chancellor level presentation to occur in June.

Issues: 
Nothing new at the moment. (Any target milestone schedule changes would normally be reported here) 

Key learnings: 

Team dynamics: 
All is well.

Additional comments: 

--------------------End of Report Sample------------------





--=====================_2114410==_.ALT
Content-Type: text/html; charset="us-ascii"

<html>
Hello Delivery Project Leaders,&nbsp; <br>
<br>
At the last Project Leaders meeting, we discussed updating the Project
Leaders Responsibilities. Since then, I have talked to a number of you
individually and can now be very specific about expectations. All your
comments, including those at the meeting,&nbsp;&nbsp; have been
incorporated&nbsp; and the updated set of responsibilities is now the
&quot;official&quot; one at&nbsp; http://web.mit.edu/pm/projectresp.html.
Please recall that these involved&nbsp; the introduction of regular
monthly reporting, like the Magellan (Discovery) group does today. These
reports will be due at the last Friday of month, or June 30th. <br>
<br>
As you may be aware, we now have a renewed requirement for Quarterly
Reports that begins at the conclusion of this month, so this timing will
work out very well from that standpoint. Please recall that the outline
is identical to Magellan's (see example below). Magellan uses a two week
cycle. For Delivery, however, since our project cycles are somewhat
longer, an update is expected only by the last Friday of the month. 
<br>
<br>
As most of you know, the Discovery leaders have found these useful, and
especially after the first one is done, quite easy to update and send
out. They guarantee that there is at least some periodic record of the
progress of your project. You should send your monthly report to
delivery@mit.edu. All reports are automatically archived for your
convenience, and for others to see, in the delivery discuss meeting on
menelaus.mit.edu. In addition, you should strongly consider sending your
monthly report to your project's&nbsp; sponsor, to the project team doing
the work, and with any other individuals or groups who would be
appropriate.<br>
<br>
A similar request is being made by Susan Minai-Azary for monthly
reporting on Integration projects, so all our projects should soon be
following a similar, simple pattern. At our Friday, June 23rd Project
Leaders Meeting we have reserved some time for questions and comments on
this new monthly reporting procedure. So please bring any items up then,
or feel free to contact me beforehand. <br>
<br>
Cheers, Bob <br>
<br>
--------------------Beginning of Report Sample------------------<br>
Project Name: EHSS - Environmental Health &amp; Safety Management System
<br>
Project Leader: Rob Smyser, Rocklyn Clarke <br>
Report Date: May 12, 2000 <br>
Submitted by: Rob Smyser <br>
URL:
<a href="http://web.mit.edu/is/discovery/ehss/" eudora="autourl"><font color="#0000FF"><u>http://web.mit.edu/is/discovery/ehss/</a></u></font>
<br>
<br>
Accomplishments past period: <br>
- Jim Curtis and Rocklyn presented a second executive level summary view of the project to members of the larger Environmental, Health and Safety staffs at an offsite at University Park hotel.<br>
<br>
Goals for the coming period: <br>
- meet with EMAX technical people next week (5/16) to discuss their purchasing authorizations technology versus ours. Lorraine Rappaport, Tom Hoole and Jim Repa should be attending. <br>
- Refine underlying data model with Scott and the team. <br>
- Have a conversation with Susan Azary re integration perspective. <br>
- Assemble more design details to support ballpark cost estimates. <br>
- being to prepare for a ExecVP/Provost/Chancellor level presentation to occur in June.<br>
<br>
Issues: <br>
Nothing new at the moment. (Any target milestone schedule changes would normally be reported here) <br>
<br>
Key learnings: <br>
<br>
Team dynamics: <br>
All is well.<br>
<br>
Additional comments: <br>
<br>
--------------------End of Report Sample------------------<br>
<br>
<br>
<br>
<br>
</html>

--=====================_2114410==_.ALT--


home help back first fref pref prev next nref lref last post