Task: Plan Deployment Strategy
Plan Deployment Strategy
Disciplines: Release Management


To determine the best approach to deploying the solution to end users.


RolesPrimary Performer: Additional Performers:

    Main Description

    Deployment can be quite complex, especially when the user base is physically dispersed or there is a wide range of system configurations. The deployment strategy should be defined early in the process, in order to be successful. Keep the plan at a high level at first and focus on the major dependencies. The people doing the work should plan the details. To create a successful plan, understand who the solution is being deployed to and understand their current work practices and policies, the amount of change they are willing to tolerate and how the solution will affect them once it is deployed. It may be easier to work backwards when planning the deployment strategy. Envision the system in production – users are working with it, operations are keeping it going, support staff are helping users work with the system, and developers are potentially evolving the system to address defects and to implement new requirements. Compare the vision with the current environment today and determine what needs to occur to successfully deploy the solution.


    Identify the Release Approach

    Determine the strategy and activities addressed in planning for the release.

    Define the Rationale for the Chosen Approach

    Determine the rationale for establishing the specific release approach. The following documentation may determine the type of release that is best suited for a particular project: Requirements document, Design document, Project Management Plan, and Project Processes.

    Describe the Strategy for the Approach

    At a high level, determine the overall strategy for segmenting the delivery of the solution into specific releases. Identify if the release strategy is for a phased function rollout/deployment or for a phased user base rollout/deployment.

    Identify the Content that will be Released

    Determine for each specific release, a description of the functionality to be. Explain what the proposed system will do (and not do, if necessary). Identify which individual requirements from the Requirements document will be satisfied in which specific release(s). Provide any additional rationale for dividing the content into the specific releases.

    Identify the Release Schedule

    At a high level, determine the schedule for the planned delivery of the releases and the significant milestones associated with transitioning each release through the Life Cycle to production.

    Define the Impacts of the Release

    Determine any business and/or system impacts associated with each release and the business processes that will be modified as a result of the deployment specified in the Release Plan. Determine any systems and interfaces that are directly impacted by the release strategy and any impacts to end users during the release cycle.

    Determine Release Specific Communication Needs

    Determine if it is necessary to provide release-specific communication that is not already described in the Project Management Plan. Determine the individual stakeholders and/or groups requiring notification of an impending release. Also, determine the method for providing notification prior to and/or following the successful release of the solution.

    Key Considerations

    The deployment plan should be updated regularly in order to set realistic expectations of both the project team and the deployment audience.