11. MSF Deploy Track: Deploying a Solution
by Michael S. V. Turner
Microsoft® Solutions Framework Essentials
- Microsoft® Solutions Framework Essentials: Building Successful Technology Solutions
- SPECIAL OFFER: Upgrade this ebook with O’Reilly
- Acknowledgments
- Introduction
- I. Solution Delivery Fundamentals
- 1. What Is MSF and Is It Right for You?
- 2. Understanding Solution Delivery Environments
- 3. Foundational Principles, Mindsets, and Proven Practices
- Foundational Principles
- Mindsets
- Proven Practices
- Summary
- 4. Building an MSF Team
- MSF Team Model: Team of Advocates
- Team of Advocates
- Quality Goals: Team of Quality Champions
- Satisfied Stakeholders
- Coordinate Identification and Optimization of Project Constraints
- Define Solution Within Project Constraints
- Deliver Solution Within Project Constraints
- Design Solution Within Project Constraints
- Build Solution to Specification
- Confirm All Aspects of a Solution Meet or Exceed Their Respective, Defined Quality Levels
- Maximize Solution Usability
- Maximize User Readiness and Effectiveness
- Smooth Deployment and Transition to Operations
- Constituents: Team of Ambassadors
- Functional Areas: Team of Representatives
- Quality Goals: Team of Quality Champions
- Foundational Principles Applied to Teaming
- MSF Team Model Fundamentals
- Product Management Advocacy Group
- Program Management Advocacy Group
- Architecture Advocacy Group
- Development Advocacy Group
- Test Advocacy Group
- User Experience Advocacy Group
- Release/Operations Advocacy Group
- Summary
- Team of Advocates
- Adapting the Team Model
- Summary
- MSF Team Model: Team of Advocates
- 5. Managing Project Risks
- What Is Risk (and Why You Should Care)?
- MSF Risk Management Process
- Summary
- 6. Establishing a Solution Delivery Lifecycle
- Solution Delivery Environment
- The Microsoft Solution Delivery Lifecycle
- MSF Governance Model
- Adapting the Microsoft Solution Delivery Lifecycle
- Summary
- II. Inner Workings of Solution Delivery
- 7. MSF Envision Track: Defining a Solution
- Goals
- Team Focus
- Key Deliverables
- Key Checkpoints
- Understanding Stakeholders
- Selecting and Preparing a Project Team
- MSF Readiness Management Discipline
- MSF Readiness Management Process
- Project Structure Document (Deliverable)
- Defining a Solution
- Scoping a Solution
- Establishing a Basis for Review and Change
- Success Criteria for an Envision Track
- 8. MSF Plan Track: Planning a Solution
- Goal
- Team Focus
- Key Deliverables
- Key Checkpoints
- Planning What to Build
- Planning How to Build
- Evolving a Solution Design
- Creating a Master Project Plan (Deliverable)
- Communications Plan
- Roles and Responsibilities
- Staffing Plan
- Readiness Plans
- Risk and Issue Management Plan
- Configuration Management Plan
- Change Management Plan
- Quality Management Plan
- Test Plan
- Pilot Plan
- Training Plan
- Deployment Plan
- Change Enablement Plan
- Knowledge Management Plan
- Disaster Recovery Plan
- Purchasing and Facilities Plan
- Security Plan
- Integration Management Plan
- Benefit Analysis Plan
- Capacity Plan
- Budget Plan
- Planning When to Build
- Preparing Supporting Environments
- Success Criteria for a Plan Track
- 9. MSF Build Track: Building a Solution
- 10. MSF Stabilize Track: Stabilizing a Solution
- 11. MSF Deploy Track: Deploying a Solution
- 12. MSF Governance Track: Guiding the Solution Delivery
- 7. MSF Envision Track: Defining a Solution
- MSFv3 Credits
- About the Author
- Additional Resources for Developers
- More Great Developer Resources
- Index
- About the Author
- SPECIAL OFFER: Upgrade this ebook with O’Reilly
Stakeholders and the project team agree: a solution is ready for release. Operations and support teams are poised to assume responsibility for a solution. Resources needed to deploy a solution are ready, including people, equipment, facilities, tools, and scripts. Deployment plans and approaches have been vetted. Solution deployment to the target environment(s) can commence.
A deployment plan, completed in the Plan Track, should have worked out optimal approaches to deploy the various aspects of a solution. For instance, the chosen installation approach is phased; a deployment mechanism is to use a partially scripted installation; and a deployment team consists of on-site staff with remote assistance from a project team.
As with other tracks, you can approach deployment in numerous ways. Accordingly, this chapter discusses common activities and checkpoints associated with deploying the various aspects of a solution.
The goals for a Deploy Track are to integrate a solution successfully into production within designated environment(s), and to transfer responsibility for the remaining solution delivery from a project team to operations and support teams as smoothly and soon as possible. Ideally, the Operations team is able and willing to deploy a solution at the beginning of a Deploy Track. In this case, the project team plays a supporting role. In the worst case, the Operations team is not able and willing to deploy a solution and, as such, a project team leads the deployment while working with the Operations team to increase their readiness with each successive site deployment.
-
No Comment