Overview

The main reason for this set of sub-processes is to ensure that the project retains its focus of delivering business benefits as outlined in the Business Case. Before each project's stage has finished the next stage is planned. The Project Plan and then the Business Case is updated. In addition the Project Quality Plan and Project Approach are updated to reflect any feedback or revelations from the current or past stages. Not surprisingly 'central' to this process is SB2 Updating a Project Plan. During this process an Exception Plan would be created, the Project Management Team structure and Job Description(s) are examined for any changes.

Tips

Notes

• Responsibility of the Project Manager
• Basic process:
  • Gather results
  • Plan next stage
  • Update Project Plan and Risk Log if required
  • Seek stage approval.
• Key points:
  • Ensure that any changes to the Project Plan still support the Business Case
  • Check the Project Approach and Configuration Management for improvements
  • Options at the end of each stage include redirecting the project or stopping the project.
• Key objectives:
  • Assure the Project Board that products have been completed
  • Provide information about the on going viability of the project
  • Obtain next stage authorisation and Tolerances (cost and time)
  • Update Lessons Learned Log.

Case studies and examples

Related links

• Search our forum for 'SB Managing Stage Boundaries'
• Take our SB - Managing Stage Boundaries - Quiz
• Lessons Learned Report
• Tolerance.