Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
1.1 Purpose
1.2 Assumptions
3.1 Overview
Provide an overview of the implementation plan to be executed for this project. Describe the process for
deployment, tools that will be used. Describe the scope of the cutover (system elements such as
database clean up, hardware verification/readiness, application configurations, etc).
Define the prerequisite criteria that must be met prior to cutover or going ‘live’. Include all technical and
business related prerequisites (i.e.: server updates, and end user training)
Outline the approach, timing, steps, tasks, etc. that will be implemented to complete this plan. These
steps should be extremely detailed (often includes exact time of tasks). Describe also the tool that will be
used to manage the cutover steps. Be sure to include roles or named resources for each task.
Document what the process will be if the installation into production fails. This is also a fall back plan.
This should be detailed including any approvals to enter into a fall back state (this is often called the
Go/No Go decision check point). Add dates of when the team might schedule an alternative cutover
date(s). Include who is the responsible party to make the decision of when to enter a fall back state or
alternate go live date.
Define how the process will be communicated to the end user community. Describe how the
implementation team will communicate during the cutover process. This can include but not limited to
Command Center, War Rooms, virtual communication methods such as open teleconference bridges,
exact time of team conference calls or virtual collaborations sessions (WebEx, Go-To-Meetings, etc). Be
sure to be extremely detailed in stating timing and who is coordinating.
*Make sure the team is participating in any Change Management protocols or policies which may be in
effect, either from the Business side or OIT.
The test plan for installation into production or cutover should confirm all key aspects of hardware and/or
software installation adhere to the approved design intentions. Installation verification is intended to
verify that the designed and tested hardware architecture &/or software configuration is installed correctly.
Be sure to include roles and responsibilities, tools, and documentation requirements (i.e.: test scripts), etc
The individuals below agree that they have reviewed and approved the plan outlined in
this Support Documentation.
APPROVED BY:
Project Role Name and Title Approval/Signature Date
First Initial. Last Name MM/DD/YYYY