Process 2: Deploy Sites
In this process, the team deploys the solution at each site.
.jpg)
Figure 4. Deploy sites
Activities: Deploy Sites
This process is the ultimate goal of all of the project’s previous processes. During this process, the project team deploys the solution to all targeted users and computers at each site. Customer and user feedback from the deployed sites may reveal additional problems with the solution. Therefore, the project team may have to revisit some sites after deployment. Still, the project team is making a concentrated effort to complete deployment and close the project. At the completion of this process, all targeted users and computers have access to the solution. Additionally, each site owner has signed off that their site is operating as expected.
Table 5. Activities and Considerations for Deploying the Sites
Activities
Considerations
Deploy the solution at each site
Key questions:
- Does the solution actually involve client-side deployment?
- Did the team deploy the core infrastructure components successfully?
- Has the project team set expectations with customers and users?
- Did the project team communicate the deployment schedule to each site?
- Will the team use a phased rollout at each site?
- How much network bandwidth and other resources are required?
Inputs:
- Final release, including:
- Solution deliverables.
- Solution documentation.
- Master project plan, including:
- Deployment plan.
- Communications plan.
Outputs:
- Site deployments complete sign-off sheet
Best practices:
- Deploy each site separately as each may have unique requirements, making an overall deployment impractical.
- Make decisions about deployment strategy early in the project, in the Envisioning or Project Planning phases, to minimize risk.
.jpg)
This accelerator is part of a larger series of tools and guidance from Solution Accelerators. |
| Download |
| Solution Accelerators Notifications |
| Feedback |