Windows 7 / Getting Started

---

Build

The Build SMF is the period during which the team builds and unit-tests the solution. The Build SMF includes six key tasks:

• Start the development cycle In this initial step, the team creates a lab server for development work and begins the process of creating images, installation scripts, and application packages. The team should also create an issue-tracking system so that team members can communicate about and coordinate solutions to issues.
• Prepare the computing environment In this key task, the teams build a deployment environment with facilities such as servers, networking, system backup, and data repositories (such as Microsoft Visual SourceSafe) with separate workspaces (that is, computers and network shares) for each team role. This environment provides the infrastructure for teams to work both independently and jointly as necessary to complete their development tasks.
• Develop the solution scripts In this step, the teams begin the process of packaging applications, creating computer images, and developing remediation steps for application-compatibility issues. The teams also plan how and what user data will be retained and migrated during the deployment and validate that network infrastructure (that is, shares, credentials, and other components) is in place and functioning properly prior to deployment.
• Develop deployment procedures Using the documents, processes, and other resources created up to this point, begin creating the documents that the teams will use to accomplish the deployment and post-deployment tasks. These documents include training materials for users, administrators, and others who will maintain systems and applications after deployment; a plan for communicating with users about the upcoming changes; and site-deployment procedures to simplify and standardize the deployment of solutions across sites.
• Develop operations procedures Create a document that describes the operations procedures to support, maintain, and carry out the solution following deployment. Key processes to describe include maintenance, disaster recovery, new-site installation, performance and fault monitoring, and support and troubleshooting.
• Test the solution Perform test deployments and remedy any issues that arise using the issue-tracking framework created by the Project Planning SMF to monitor and address these issues.

Stabilize

The Stabilize SMF addresses the testing of a solution that is feature-complete. This phase usually occurs when pilots are conducted, with an emphasis on real-world testing and with the goal of identifying, prioritizing, and fixing bugs. Key tasks in this phase include the following:

• Conducting the pilot At this stage, the teams use a small pilot deployment to test the deployment and identify any remaining issues. Procedures, resources, and personnel should be in place to assist in addressing any user issues that arise during the pilot deployment. This key task should also include obtaining user feedback as well as review and remediation of issues identified during the pilot.
• Operational-readiness review All teams at this stage perform a complete operational- readiness review to determine that the deployment plan is ready to move forward to full-scale deployment. The solution is frozen at this stage, and any remaining issues are addressed.
• Final release This task incorporates all fixes and issue resolutions to create the final release of the solution, which should now be ready for full deployment.

Deploy

In the Deploy SMF, the team implements the solution and ensures that it is stable and usable. The key tasks involved in the Deploy SMF include the following:

• Deploying core technology Based on the plans and procedures developed in the Project Planning SMF, install, configure, and test deployment servers at each site. Also train administration staff in preparation for deployment.
• Deploying sites Teams perform the deployment of Windows 7 at each site using the procedures and resources developed by the Project Planning and Build SMFs. Team members remain on site to stabilize each site deployment, ensuring that users can move forward with reliable systems and applications and that the goals of the deployment plan for the site have been met.
• Stabilizing the deployment In this key step, the project team ensures stabilization across all sites and addresses any remaining deployment issues.
• Completing the deployment This step marks the transition from deployment to operations and support. Ongoing operations are transferred from the project team to permanent staff. Reporting systems are activated, and support processes are fully operational.