During the Stabilizing Phase, the team concentrates on preparing the infrastructure for testing. The final level of testing before the production deployment is pilot testing. Pilot testing involves a test within the production environment and should include every facet of the production environment to ensure that all deployment tasks are validated. The Test feature team leads this process, but the Infrastructure Remediation feature team must be ready to respond to any anomalies that are discovered during this testing. Because the Development Phase involved several lab tests, the deployment architecture and the deployment mechanisms should all be well designed and tested at this stage. Therefore, the key focus in this phase is to identify any unforeseen infrastructure issues.

Figure 7 illustrates the result of pilot testing to deliver a stabilized deployment process.

Figure 7. Stabilize the deployment

Figure 7. Stabilize the deployment

On This Page

Roles and Responsibilities Roles and Responsibilities
Deploy Pilot Deploy Pilot
Milestone: Deployment Readiness Review Milestone: Deployment Readiness Review

Roles and Responsibilities

Table 10 lists the focus areas for the different role clusters when stabilizing the deployment.

Table 10. Roles and Responsibilities During the Stabilizing Phase

Role cluster


Product Management

  • Communications plan execution

  • Launch planning

Program Management

  • Project tracking

  • Issue triage


  • Issue resolution

  • Deployment optimization

User Experience

  • Stabilization of user performance materials

  • Training materials


  • Deployment testing

  • Issue reporting and status

  • Configuration testing

Release Management

  • Pilot setup and support

  • Deployment planning

  • Operations and support training

Deploy Pilot

An automated build process for the pilot test environment benefits the Release Management Role Cluster. This automated process will be reused during the actual deployment and should be as refined as possible at this stage.

Team members should be able to build the pilot test environment quickly and at any time. Most of the time of the deployment project is spent in the pilot test environment. The more time spent on pilot testing and resolving issues, the less time will be spent on deployment troubleshooting.

The most important issues from the pilot test environment should be documented. Issue identification and resolution are invaluable to the Deployment feature team, especially to the help desk. When users can quickly identify an issue—sometimes before contacting the support center—it helps to reduce user downtime as well as help desk costs.

Milestone: Deployment Readiness Review

At this milestone, the infrastructure modifications are finalized, and the deployment architecture is stabilized. The Readiness Review provides a final checkpoint for the go/no-go release of the deployment. Table 11 describes the deliverables for this milestone.

Table 11. Deliverables

Deliverable ID


Deployment Structure Stabilized

The final deployment architecture has been deployed in the pilot test environment and stabilized as testing proceeds. The deployment architecture documentation has been updated.


Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases


Send us your comments or suggestions