Stabilizing

  • Article

Figure 4 shows the detailed activities that must be performed during the Stabilizing Phase prior to initiating the deployment to production computers. These activities include testing each server component as well as testing the Windows PE media to assure proper operation. The results of this testing are documented in a test report, which is one of the deliverables.

Figure 4. Activities during the Stabilizing Phase

Figure 4. Activities during the Stabilizing Phase

On This Page

Roles and Responsibilities Roles and Responsibilities
Performing Lab Tests and Pilot Deployments Performing Lab Tests and Pilot Deployments
Preparing Deployment Teams Preparing Deployment Teams
Milestone: Testing Complete Milestone: Testing Complete

Roles and Responsibilities

In addition to the tasks defined in the following process description, note the responsibilities that are allocated to the role clusters. Table 8 defines these focus areas for the different role clusters during this phase.

Table 8. Team Roles and Responsibilities in the Stabilizing Phase

Role

Focus

Product Management

  • Communications plan execution

  • Deployment launch planning

Program Management

  • Bug management

  • Project tracking

Development

  • Bug resolution

  • Code optimization

  • Process optimization

Test

  • Documenting known issues and resolutions

  • Lab testing

Release Management

  • Pilot management and support

  • Test management and support

Performing Lab Tests and Pilot Deployments

Before beginning deployments in the production environment, verify the deployment processes in test labs and by conducting pilot deployments. As the team is creating the design and deployment plans, it can begin testing in the lab.

Start using the test lab in the Planning Phase and continue using the lab throughout the life cycle of the BDD 2007 deployment environment. Figure 5 illustrates the sequence of lab testing and pilot deployments in a deployment process.

Figure 5. Sequence of lab testing and pilot deployments in the deployment process

Figure 5. Sequence of lab testing and pilot deployments in the deployment process

During the lab tests and pilot deployments, complete the following tasks:

  • Test the BDD 2007 deployment process on target computers. The focus is on finalizing the deployment process in labs and pilot deployments just prior to deployment in a production environment. For more information about testing the BDD 2007 deployment process, see the Test Feature Team Guide and the Test Cases Workbook.

  • Document common deployment problems and resolutions. As the team is going through the stages of testing and pilot deployments, they should document any deployment problems that they encounter along with their resolution.

  • Document troubleshooting procedures and diagnostic tools. Document any troubleshooting procedures and diagnostic tools used during lab testing and pilot deployments.

  • Revise deployment plans. After completing the lab tests and pilot deployments, revise the deployment plans to reflect any issues and resolutions that were discovered. Ensure that these revised plans are provided to the deployment teams along with the deployment problems and resolutions, troubleshooting procedures, and diagnostic tools.

Preparing Deployment Teams

After the lab tests and pilot deployments are complete, prepare the deployment teams. The deployment teams must know what was learned during the lab tests and pilot deployments.

To prepare the deployment teams, complete the following tasks:

  • Notify the Deployment feature team and IT Operations about the deployment start date. The team must notify the teams when it plans to start the deployment so that they can be ready to provide support.

  • Notify users of changes in contacts for support (IT Operations to the Deployment feature team). Users must know the appropriate contact information for deployment-related issues (if this number is different from the usual support contact information).

  • Identify the group of computers to be deployed. Provide the deployment teams with a list of the computers to be included in the deployment. Ensure that the appropriate sequencing of groups of computers is provided when required.

  • Identify computer configurations that were successfully deployed during lab and pilot tests. Ensure that the deployment teams know the configurations that should work without difficulty based on lessons learned in the lab tests and pilot deployments.

  • Identify computer configurations that failed during lab and pilot testing. Ensure that the deployment teams know the computer configurations that resulted in problems so they can monitor those configurations more closely.

  • Identify any troubleshooting procedures and diagnostic tools. Provide the deployment teams with documentation that describes troubleshooting procedures and diagnostic tools used during the lab testing and pilot deployments.

Milestone: Testing Complete

Milestones are synchronization points for the overall solution. For more information, see the Plan, Build, and Deploy Guide.

At this milestone, the teams have completed the tasks listed in Table 9. All the testing prior to deployment in the production environment is complete.

Table 9. Stabilizing Phase Project Milestones and Deliverable Descriptions

Stabilizing Phase Milestone

Deliverable description

Owner

Lab tests and pilot deployments performed

All deployment scenarios—New Computer, Upgrade Computer, Refresh Computer, and Replace Computer—are tested in a lab environment and in pilot deployments.

Test

Deployment teams prepared

Appropriate documentation, troubleshooting processes, diagnostic tools, and common deployment issues are transferred from the design team and the Test feature team to the Deployment feature team.

Program Management

Download

Get the Microsoft Solution Accelerator for Business Desktop Deployment 2007

Update Notifications

Sign up to learn about updates and new releases

Feedback

Send us your comments or suggestions