Figure 11 shows the detailed activities that must be performed during the Stabilizing Phase prior to initiating the deployment to production workstations. These activities include testing each server component as well as testing the Windows PE CDs to assure proper operation. The results of this testing are documented in a test report, which is one of the deliverables. On This PageIdentifying Roles and ResponsibilitiesIn addition to the tasks defined in the following process description, take note of the responsibilities that are allocated to the role clusters. Table 40 defines these focus areas for the different role clusters during this phase. Table 40. Team Roles and Their Responsibilities During the Stabilizing Phase Product management | Communications plan execution; deployment launch planning | Program management | Project tracking; bug management | Development | Bug resolution; process optimization; code optimization | Test | Lab testing; documenting known issues and resolutions | Release management | Pilot management and support; test management and support |
Identifying Milestones in the Stabilizing PhaseTable 41 lists the project milestones and deliverables that you need to complete during the Stabilizing Phase. The project plan you create needs to include these milestones, the resources required for each milestone, and the length of time to complete each milestone. Table 41. Stabilizing Phase Project Milestones and Deliverable Description Lab tests and pilot deployments performed | All deployment scenarios—New 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 and test teams to the deployment team. | Program Management |
Performing Lab Tests and Pilot DeploymentsBefore you begin deployments in your production environment, verify your deployment processes in test labs and by conducting pilot deployments. As you are creating your ZTI design and deployment plans, begin testing in your lab. You start using the test lab in the Planning Phase and continue using the lab throughout the life cycle of the Solution Accelerator for BDD deployment environment. Figure 12 illustrates the sequence of lab testing and pilot deployments in a deployment process.  Figure 12. Sequence of lab testing and pilot deployment in the deployment process
See full-sized image During the lab tests and pilot deployments, you need to: | • | Test the Solution Accelerator for BDD Deployment Process. As early as possible in your deployment process, start testing components of your deployment plan. In the early stages, the type of your testing will be more proof-of-concept and focus on individual components. In the later stages, testing will focus on the overall process. For more information about testing the Solution Accelerator for BDD deployment process, see the Test Feature Team Guide and the Test Case Workbook. | | • | Document Common Deployment Problems and Resolutions. As you are going through the various stages of testing and pilot deployments, document any deployment problems that you encounter along with a resolution. For some examples of common deployment problems and resolutions, see Appendix H: Resolving Common ZTI Deployment Problems, later in this guide. The deployment problems listed in this appendix are those found during the testing of these procedures in a lab environment and actual deployments. However, you need to perform your own testing to discover any issues that are unique to your environment. | | • | Document Troubleshooting Procedures and Diagnostic Tools. You need to document any troubleshooting procedures and diagnostic tools used during lab testing and pilot deployments. For information about common deployment problems, see Appendix H: ZTI Troubleshooting Procedures and Diagnostic Tools, later in this guide. | | • | Revise Deployment Plans. After you have completed your lab tests and pilot deployments, revise your deployment plans to reflect any issues and resolutions that you discovered. Ensure these revised plans are provided to the deployment teams along with the deployment problems and resolutions, troubleshooting procedures, and diagnostic tools. |
Preparing Deployment TeamsAfter the lab test and pilot deployments are complete, you need to prepare the deployment teams. The deployment teams need to know what was learned during the lab tests and pilot deployments. To prepare your deployment teams, complete the following tasks: | • | Notify the Deployment and Operations feature teams about the deployment start date. Notify the teams when you plan start the deployment so that they can be ready to provide support. | | • | Notify users of changes in contacts for support (operations to deployment). Users need to know the appropriate contact information for deployment-related issues (if this number is different from the usual support contact information). | | • | Communicate the group of workstations to be deployed. Provide the deployment teams with a list of the workstations to be included in the deployment. Ensure that you provide the appropriate sequencing of groups of workstations when required. | | • | Identify workstation 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 test and pilot deployments. | | • | Identify workstation configurations that failed during lab and pilot testing. Ensure that the deployment teams know the workstation configurations that resulted in problems so that 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. |
| |
