RP Version X.X <Project and release name>
CMS XLC Release Approach 2. Assumptions/Constraints/Risks 2.1 Assumptions This section identifies the statements believed to be true for the release of the product or information technology (IT) system. Instructions: Describe any assumptions about the current capabilities and use of the system when it is released in accordance with this plan. Include any information regarding external circumstances or commitments that may impact the release of the system. Describe any dependencies that can affect the deployment of the system. Be sure to identify any other systems or subsystems that are impacted directly as a result of this Release Plan. Describe any dependencies including staffing, divisional/group participation, external system dependencies or dependencies due to specific business cycles that can impact this Release Plan. 2.2 Constraints This section identifies any limitation that must be taken into consideration prior to the release of the product or IT system. Instructions: Describe factors that limit the ability to deploy the system or have some impact to the release of the system in accordance with this plan (e.g., budget and schedule constraints). Be sure to include constraints due to group/divisional involvement or any other external system or infrastructure constraints that impact the environment. 2.3 Risks Instructions: Describe any risks associated with release of the system in accordance with this Release Plan. Identify any adverse impacts to stakeholders (e.g., end users) during the release cycle. Be sure to include any factors that may adversely impact a successful deployment. Also provide a mitigation strategy for each identified risk that describes specifically the fallback position if a risk is realized. This information should also be documented in the project’s Risk Log or Risk Register and managed in accordance with the Project Management Plan (Risk Management Plan). RP Version X.X <Project and release name>
CMS XLC Release Approach 3. Release Approach Instructions: Describe the strategy and activities that will be addressed in the planning for the release. The RP outlines the activities necessary to ensure that the project’s product is available for use by its end-users as originally planned. 3.1 Rationale Instructions: Describe the rationale for establishing this release approach. Reference any information or other deliverables (e.g. Requirements Document, Design Document, Project Management Plan (Communication Management Plan, Acquisition Management Plan, Risk Management Plan), and Project Process Agreement (PPA)) that may have influenced the development of the release approach. Include key considerations such as how the assumptions, constraints, and risks from the previous section impact the Release Plan. Also consider lessons learned from other deployments. 3.2 Release Plan Instructions: Describe at a high level the overall strategy for segmenting the delivery of the Business Product/Code into specific releases. Identify if the Release Plan is for a phased function rollout/deployment or for a phased user base rollout/deployment.