Process 3: Stabilize Deployment

In this process, the customer and the team agree that the deployment is complete.

Figure 5. Stabilize deployment

Activities: Stabilize Deployment

At the completion of this process, the customer and the project team agree that site deployments are complete and that they are operating satisfactorily. This means that the solution and the site deployments are meeting customer expectations and specifications and that the customer is willing to approve and sign off on them.

Determining when a project is complete and the project team can disengage can be difficult. New solutions are often constantly changing, and the project team is often fire fighting—identifying and managing support issues. Even though the project team might find it difficult to formally close the project because of ongoing issues, the team needs to clearly define a completion milestone.

The following table lists the activities involved in this process. This includes:

• Stabilizing the solution deployment.
• Monitoring the solution during the quiet period.

Table 6. Activities and Considerations for Stabilizing Deployment

Activities

Considerations

Stabilize the solution deployment

Key questions:

• Will some project team members be involved in the solution’s ongoing maintenance and support?
• Have team members and stakeholders begun transferring out of the project? Will any team members move to permanent operations or support roles for the project?
• Is a process in place for escalating the issues that operations and support can’t address to project team members?

Inputs:

• Master project plan, including:
  • Operations plan.
  • Support plan.

Outputs:

• Stable solution deployment

Monitor the solution during the quiet period

Key questions:

• Will some project team members be involved in the solution’s ongoing maintenance and support?
• Have team members and stakeholders transferred out of the project?

Inputs:

• Master project plan, including the support plan

Outputs:

• Performance metrics, such as:
  • Number of incidents.
  • Downtime.
  • Best Practices:
• Ensure that all operations guides are available

This accelerator is part of a larger series of tools and guidance from Solution Accelerators.

Download Get the Microsoft Operations Framework 4.0

Solution Accelerators Notifications Sign up to learn about updates and new releases

Feedback Send us your comments or suggestions