Distributed Software Lifecycle Process Models
Formal process is published in the IS&T Library of Procedures: Product and Service Retirement Checklist
| Panel |
|---|
Retirement Process |
Retirement Decision Template
...
At-A-Glance
|
...
|
...
- product end of life
- lack of owner ship (orphan)
- lack of adoption
- support burden
- reasonable alternatives exist
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
...
|
Product & Service Offering Retirement Checklist
To construct your personalized retirement checklist, cut and paste 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 | Low Resources | Moderate Resources | High Resources |
Based on the number of personnel required to execute the retirement (including any client transitions): low, moderate or high | Work can be done generally be done by an INDIVIDUAL staff member or equivalent, within the context of existing assignments and responsibilities; no separate budgeting and resource allocation is usually done for this level; time is usually measured in DAYS
| Usually confined to a single TEAM with contacts into other parts of the organization and into business |
...
stakeholder groups; formal resource allocation is often involved, and an ad-hoc team may be formed; projects in this category may involve software licenses and other materials and services budget items; time is usually measured in WEEKS
| May involve an entire ORGANIZATION of project teams, operational 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 this effort affect and how much will they be affected? | LOW impact confined to behind the scenes, internal areas of IS&T, and business support groups; little to no customer-facing impact
| LOCAL or bounded to small group, roles, or department; group of customers of service offering 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 offering and how they will react to changes
| 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 service offerings for their day-to-day work
|
Risk to IS&T | Low Risk | Moderate Risk | High Risk |
How much will the retirement of the product or decommissioning of the service offering affect IS&T relationship 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 failure to transition customers 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 decommissioning and transition timeline is generally acceptable to stakeholders and customers
| HIGH risk is involved at this level; failure to transition customers 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
|