[359] in Release_7.7_team
release suggestion form
daemon@ATHENA.MIT.EDU (brlewis@MIT.EDU)
Wed Sep 20 15:32:52 1995
From: brlewis@MIT.EDU
Date: Wed, 20 Sep 95 15:32:20 -0400
To: dryfoo@MIT.EDU
Cc: release-team@MIT.EDU
I have a first draft for you of a release suggestion form. I'm sure
people will want to go over it at tomorrow's meeting and make changes,
if we're having a meeting tomorrow. (I'll be at the team skills
workshop myself.)
By 9/28 we ought to be able to agree on the final form to be publicized
Oct 2.
Please give your suggestion a short title.
Title: [ ]
Please describe your suggestion.
Description:
Please explain the benefits of your suggestion.
Benefits:
Cost Guestimate
Implementing any suggestion in the Athena environment will cost some
amount of effort doe various groups within MIT Information Systems. For
simplicity, three broad categories of effort are used. It is often
difficult to determine in advance how much effort is involved, but a
rough guess is helpful. If you are guessing wildly, please say so in
the comments.
Delivery/Integration cost
Please estimate the amount of effort involved in acquiring/developing,
building, testing, auditing, installing and documenting your suggestion.
Use the following 5-point scale:
1 - 1 day or less
2 - 1-5 days
3 - 5-10 days
4 - 10-20 days
5 - more than 20 days
Comments:
Service cost
Please estimate the amount of effort required for ongoing maintenance of
your suggestion. Include maintenance of servers as well as files
containing information that must be kept up-to-date. If this does not
apply to your suggestion, choose 2.
1 - suggestion reduces maintenance of a current service
2 - neutral
3 - changes an existing service
4 - new service needs attention less than once a month (except backups)
5 - new service needs attention once a month or more
Comments:
Support cost
Please estimate the impact this change will have on the user community.
This estimate will roughly correspond to the cost of this suggestion in
consulting, documentation and training.
1 - suggestion reduces the support burden
2 - small change affecting few users
3 - large change affecting few users
4 - small change affecting many users
5 - large change affecting many users
Comments:
