Product-Release Checklist

To construct your personalized release checklist, cut and paste all the lists that match your criteria into a master checklist for your project.

Resources Required for the Release

Based on the number of personnel required to perform the release; not the whole project team; low, moderate, or high.

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  Create/update portfolio listing  Place release date on calendar  Send announcement and change log to release-core@mit.edu once release is complete  Update any known open issues affected by release and close	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  (Include steps from low impact list)  Contact help desk at inception to determine proper level engagement  Contact training at inception to determine proper level engagement  Contact documentation 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 release with DITR  If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release  Contact production@mit.edu to schedule publication of software grid to coincide with sending of release announcement  Inform release-core@mit.edu of release at least 1 business day prior to release  Send software grid revision to production@mit.edu for review at least 1 business day prior to release  Execute (Send announcement, post software for download, etc.)  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  (Include steps from low & medium impact lists)  Contact DLCs at inception to determine proper level engagement  Contact Testing & QA at inception to determine proper level engagement  Contact User Experience at inception to determine proper level engagement  Consider how to support early adopters  Create communication plan

Impact to the MIT Community

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  Create/update portfolio listing  Place release date on calendar  Send announcement and change log to release-core@mit.edu once release is complete  Update any known open issues affected by release and close	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  (Include steps from low impact list)  Contact help desk at inception to determine proper level engagement  Contact training at inception to determine proper level engagement  Contact documentation 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 release with DITR  If sending outside of IS&T, send draft release announcement to IS&T communications team at least 2 business days prior to release  Contact production@mit.edu to schedule publication of software grid to coincide with sending of release announcement  Inform release-core@mit.edu of release at least 1 business day prior to release  Send software grid revision to production@mit.edu for review at least 1 business day prior to release  Execute (Send announcement, post software for download, etc.)  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  (Include steps from low & medium impact lists)  Contact DLCs at inception to determine proper level engagement  Contact Testing & QA at inception to determine proper level engagement  Contact User Experience at inception to determine proper level engagement  Consider how to support early adopters  Create communication plan

Risk to IS&T

How much will a failure to perform a smooth or seemless release affect IS&T's relationships with our customers?

Child pages

Product-Release Checklist