The FINAL Product Release Checklists can be found in Hermes at: http://kb.mit.edu/confluence/x/bgK9
To construct your personalized release checklist, cut and paste all each of the nine possible lists that match your criteria into a master checklist for your project. Each checklist category is divided into Low, Moderate, and High levels. If you are undecided on the right level, you should round up (That is, if you are torn between a Low or Moderate level, go for Moderate.).
Resources Required for the Release | Low Resources | Moderate Resources | High Resources |
|---|---|---|---|
Based on the number of personnel required to perform the release; not the whole project team; low, moderate, or high. | |||
Low | Moderate | High | |
Work can be done generally be done Release is performed by an INDIVIDUAL staff member or equivalent , within the context of existing assignments and responsibilities; no . No separate budgeting and resource allocation is usually done for this level; time . Time is usually measured in DAYS.
| Release usually performed by a SINGLE calendar Usually confined to a single TEAM with contacts into other parts of the organization and into business stakeholder groups; . Often involves formal resource allocation is often involved, and an ad-hoc release team may be formed; projects . Projects in this category may involve software licenses and other materials and services budget items; time . Time is usually measured in WEEKS.
If a custom installer is required, complete SWRT's Installer Support Request Form at least two week prior to release
| May involve an entire ORGANIZATION of project teams, release teams, and transition teams, staff in many parts of the organizations, consultants, formal budgets usually accounted for as part of IS&T’s central budgeting process, significant licensing, materials and services, and capital budgets; time is usually measured in MONTHS or YEARS.
| |
Impact to the MIT Community | Low Impact | Moderate Impact | High Impact |
How much of the MIT Community will your project affect and how much will they be affected? | |||
Low | Moderate | High | |
LOW impact confined to behind the scenes, internal areas of IS&T, and business support groups; little to no customer-facing impact.
Place
Send
| LOCAL or bounded to small group, roles, or department; group of customers of service or product, while it may be significant in size, is usually within a specific domain with well-established communications channels; we know who uses product or service and how they will react to changes.
If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release Contact
Inform release-core@mit
| If actual dates do not match previously expected dates, update calendar WIDE impact to large segments of the MIT community, often with incomplete understanding of precise impact and user base, and without complete communication channels into community segments; customers often rely on affected products and services for their day-to-day work.
| |
Risk to IS&T | Low Risk | Moderate Risk | High Risk |
How much will a failure to perform a smooth or seemless release affect IS&T's relationships with our customers? | Negligible to LOW; service alternatives are readily available, service continuity is not at risk, and changes can be backed out quickly and quietly.
| MEDIUM, with failures of potentially significant impact but affecting a limited audience; contingency and roll-back checklists are needed, but can be executed and communicated quickly in the event of a problem; limited, well-understood downtime is generally acceptable to stakeholders and customers.
| HIGH risk is involved at this level; failures will have significant negative impact on IS&T’s reputation and customer’s ability to get work done; formal mitigation plans, fully tested and approved contingency plans, and communications plans in the event of failures are called for.
|