Page History

Low Priority

Moderate Priority

High Priority

Requester

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
 

• Email retirement date to release-core@mit.edu

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 release 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
 

• (Include low resources task list)
• Complete Retirement Decision Template https://wikis-mit-edu.ezproxyberklee.flo.org/confluence/x/iMrGB
• Review with Release Core
• Create retirement team

• an individual staff or student
• a small group of users (<20)

• faculty

• VIP staff and faculty
• large student organization
• entire department, lab or center

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
 

• (Include low and medium resource task lists)
• Obtain senior staff approval

Impact to the MIT Community

• users do not intend to use the product that often (<once per week)

•  purpose is specifically for one class

• potential for expanded user base over time
• will be used on an ongoing basis

Risk To IS&T

LOW impact confined to behind the scenes, internal areas of IS&T, and business support groups; little to no customer-facing impact

• Update IS&T Service Portfolio listings
• Place retirement date on Change Communication Calendar
• Send announcement and change log to release-core@mit.edu once retirement is complete
• Update any known open issues affected by retirement and close

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

• (Include steps from low impact list)
• Contact help desk at inception to determine proper level engagement
• If transitioning customers to an alternative product or service offering, contact training at inception to determine proper level engagement
• Contact documentation/content owners at inception to determine proper level engagement
• Contact key stakeholders at inception to determine proper level engagement
• Review need to de-support of previous version(s)
• Discuss retirement with DITR
• If sending outside of IS&T, send draft retirement announcement to IS&T communications team (ist-comm@mit.edu) at least 2 business days prior to retirement
• Contact production@mit.edu to schedule changes in software grid (if applicable) to coincide with sending of retirement announcement
• Inform release-core@mit.edu of retirement at least 1 business day prior to release
• Execute (Send announcement, remove any applicable software from download server, etc.)
• If actual dates do not match previously expected dates, update Change Communication 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 service offerings for their day-to-day work

Risk To IS&T