Close Release Plan

(Activity) for Tier: Release

View Training

PURPOSE

Project Plans and documents must be updated in light of the latest release. By formally closing each successive release as a distinct project phase, the project team is able to engage with project stakeholders and customers in order to ensure that released Working Product meet the customer’s standards of satisfaction and that Project Plans, schedules, risks and issues are managed to keep the customer’s priorities on track. These actions will help us develop and maintain highly satisfied customers.

WHEN

Once a new Product Version has been successfully released.

PARTICIPATING ROLES

• ACCOUNTABLE

  • Project Manager

• RESPONSIBLE

  • Development Manager
  • Lead Developer
  • Test Manager
  • User Education Specialist
  • Release Manager
  • Product Owner

INPUTS

• Product Version
• Release Plan
• Project Plan
• Mitigation Plans
• Issues
• Risks
• Tasks

ENTRY CRITERIA

• Executed Release Plan

  The objectives outlined in the Release Plan have been verified and validated by the team to be complete.

SUB-ACTIVITIES

1. Confirm Accomplishment of Release Plan Objectives

   • Meet with appropriate stakeholders and review the objectives of the Release Plan.
   • Utilizing appropriate quality and project performance data, document, with stakeholder concurrence, if the objectives outlined in the Release Plan were satisfactorily met.
   • Determine if there were any variances from the Release Plan.

2. Reconcile the Project Plan and Documents

   • Review Project Plans and documents to determine if project milestones have been reached or missed according to the status of the release objectives outlined in the Release Plan.

   • Review any variance noted and determine if Project Plans or documents need to be updated or if corrective action is required.

   • Revisit Plan Project in order to reconcile the Project Plan with variances that occured during the release.

   • Updates to the Project Budget based on the status of release plan objectives and/or project milestones, Events and activities

     • Revised human resource allocations
     • Revised project travel allocations
     • Revised purchase plans

3. Sign-off Release

   • Sign-off the release with stakeholders in accordance with the customer acceptance approach established within the Release Strategy section of the Project Plan.
   • Consider collecting valuable accomplishments for later CPARS submittal.

OUTPUTS

• The Accepted Release
• Issues
• Risks

EXIT CRITERIA

• Consensus is gained with stakeholders that the objectives of the release plan have been satisfied.
• Project plans and documentation have been reconciled to reflect project status at the time of Release Plan closure.
• Outstanding risks and issues have been reviewed and updated as required.

NEXT ACTIVITY

• Plan a Release

SEE ALSO

Process Guidance Version: 10.4