- A detailed description, including cross-references to all “parent” configuration management database (CMDB) document numbers (including change request, project, and maintenance request numbers).
- A high-level work breakdown that includes start and end date/time for all major tasks and milestones, plus an overall duration for the work plan.
- A high-level description of any dependencies, issues, and concerns.
- A logistics plan, including staffing, escalation process, and outline of communication method.
Build Plan
- An outline of the steps required to build the change.
- Setup list to deploy the change.
- This might involve
- Building a software bundle
- Requesting special backups
- Researching a hardware modification
- Producing new or amended documentation
- Confirming receipt of and staging hardware and software
- Preparing to train support and operations staff on the new or amended release, or a combination of such tasks.
“Day of” Test Plan
The “Day of” test plan should include the following:
- Vendor and user testing.
- Plans to have a different person perform the test than the person who built and implemented the change.
- Testing to cover performance and security, as well as functionality.
- Log files of when the work is complete and documentation of any discrepancies between expected and actual results.
Contingency Plan
The contingency plan should include the following:
- Details of the back out and recovery plan.
- This should include an overall description of the plan, the length of time required to back out, and the latest possible date/time for a go/no-go decision to back out.
Contact Information
The contact information should include:
- Primary update contact information, including business telephone, home telephone, and pager.
- Secondary update contact information, including business telephone, home telephone, and pager.
- Primary testing contact information, including business telephone, home telephone, and pager.
- Secondary testing contact information, including business telephone, home telephone, and pager.
- Executive sponsor communications plan and contacts.
Transition Plan
The transition plan should include:
- An outline of the steps required to transfer responsibility for the deployed release to the support and operations staff.
- The steps to update any impacted release documentation.
