Can't find what your looking for?

Call us on +44 (0)1273 622272 or contact us.

Courses

showing {{courseLimit}} of {{(courses | filter:query).length}} results Show All

Hide All

Categories

showing {{courseLimit}} of {{(tags | filter:query).length}} results Show All

Hide All

theBLOG

Managing a Stage Boundary (SB) PROCESS

Written by Andy Trainer – Wed 11 Jul 2007


PRINCE2® PROCESSES - Managing a Stage Boundary

PRINCE2 Managing a Stage Boundary Process Diagram

The purpose of the Managing a Stage Boundary process is to enable the Project Board to be provided with sufficient information by the Project Manager so that it can review the success of the current stage, approve the next Stage Plan, review the updated Project Plan, and confirm continued business justification and acceptability of the risks. Therefore, the process should be executed at, or close to the end of, each management stage. The PRINCE2 Processes are covered in detail on our PRINCE2 Foundation training and PRINCE2 Practitioner training courses.

The objective of the Managing a Stage Boundary process is to:

  • Assure the Project Board that all products in the Stage Plan for the current stage have been completed and approved
  • Prepare the Stage Plan for the next stage
  • Review and, if necessary, update the Project Initiation Documentation (in particular the Business Case, Project Plan, project approach, strategies, project management team structure and role descriptions)
  • Provide the information needed for the Project Board to assess the continuing viability of the project – including the aggregated risk exposure
  • Record any information or lessons that can help later stages of this project and/or other projects
  • Request authorization to start the next stage.

The main products of this process are as follows:

  • An End Stage Report produced by the Project Manager and given to the Project Board, outlining information on the current stage achievements.
  • Current Stage Plan actuals showing the performance against the original Stage Plan.
  • The Next Stage or Exception Plan for approval.
  • Project Initiation Documentation may require updating.
  • A revised Project Plan incorporating all the actual metrics.
  • An updated Risk register, together with the Updated Business Case and Project Plan, which is used by the Project Board to review that the Project has continuing ongoing viability.
  • Configuration item records created/updated for new stage products.
  • An updated Business Case.
  • The Lessons Log.
  • Any changes to the Project Management Team with updated Job Descriptions.

Team plans may also be produced when planning the next stage, defining the work packages that will be produced in the next stage.

Posted under:

Back

blog comments powered by Disqus