[789] in I/T Delivery
Delivery monthly report + Project notebook reminder - June 7th
daemon@ATHENA.MIT.EDU (Robert Ferrara)
Fri May 31 10:06:52 2002
Message-Id: <5.0.2.1.2.20020530233901.00bb54c8@po9.mit.edu>
Date: Thu, 30 May 2002 23:45:07 -0400
To: delivery@mit.edu
From: Robert Ferrara <rferrara@MIT.EDU>
Mime-Version: 1.0
Content-Type: multipart/alternative;
boundary="=====================_3272044==_.ALT"
--=====================_3272044==_.ALT
Content-Type: text/plain; charset="us-ascii"
Hello,
Please send in your May monthly by Friday, June 7th. Last month everyone (save one) did a fine job. Thank you.
Also, many of you caught the request to include a new field, but several missed it, so I am repeating it here:
Please include one additional field, called "Next Community Milestone:". It should appear after "Goals for the coming period:". This has been requested by several people, and will serve to highlight for Practice Directors and others when the project is likely to have a community visible impact. There has been much discussion about this field. Here are some of the high points:
- the purpose is to provide a heads up to those who deal directly with IS customers that something new is coming
- for Team Activity (as opposed to Project) reports, there may not be any milestones in this category (e.g. we installed a better backup system isn't a Community visible milestone). In this case, please indicate "none".
- many projects as well may *not* have any customer-visible milestones, though there will be certainly be project milestones.
Thanks, Bob
--=====================_3272044==_.ALT
Content-Type: text/html; charset="us-ascii"
<html>
Hello, <br>
<br>
Please send in your May monthly by Friday, <b>June 7th</b>. Last month
everyone (save one) did a fine job. Thank you. <br>
<br>
Also, many of you caught the request to include a new field, but several
missed it, so I am repeating it here:<br>
<br>
Please include one additional field, called "<b>Next Community
Milestone:</b>". It should appear after "Goals for the coming
period:". This has been requested by several people, and will serve
to highlight for Practice Directors and others when the project is likely
to have a community visible impact. There has been much discussion about
this field. Here are some of the high points:<br>
- the purpose is to provide a heads up to those who deal directly with IS
customers that something new is coming <br>
- for Team Activity (as opposed to Project) reports, there may not be any
milestones in this category (e.g. we installed a better backup system
isn't a Community visible milestone). In this case, please indicate
"none". <br>
- many projects as well may *not* have any customer-visible milestones,
though there will be certainly be project milestones. <br>
<br>
Thanks, Bob </html>
--=====================_3272044==_.ALT--
