vault backup: 2023-09-19 22:21:59

Notes/Literature/PRINCE2.md

@@ -175,7 +175,47 @@ Other objectives are to:
 - Provide direction and control during the project and be interface to the CPC
 - Ensure that post-project benefits will be reviewed (see that meetings are planned)
 ## Process 4 - [[Controlling a stage]]
-
+This process aims to help the project manager to assign the work to be done, monitor it, deal with issues, report progress to the board and take action to keep the stage within tolerance.
+The objectives are to:
+- Ensure that attention is focused on the delivery of the products
+- Keep risks and issues under control
+- Keep the business case under review (ask is the project still viable)
+- Deliver the products for the stage to the agreed quality within agreed cost and time.
+## Process 5 - [[Managing product delivery]]
+This process aims to bridge the gap between the project manager and the team manager.s by agreeing on the requirements for acceptance, execution and delivery.
+Objectives:
+- Products assigned to the team are authorized and agreed on (work packages)
+- The team is clear about what has to be produced and understands effort, time, and cost
+- Planned products are delivered to the quality expectations and within tolerance
+- Accurate progress information is provided by the team manager
+## Process 6 - [[Managing a stage boundary]]
+This process aims to have the project manager provide the board with a report of the performance of the current stage, update the project plan, business case and create a stage plan for the next stage. The board then reviews this and approves or disapprove the next stage.
+Objectives:
+- Assure that all products in the current stage are produced and approved
+- Review and update the usual documents (business case, project plan)
+- Record lessons in the lessons log that can help in later stages or in future projects
+- Prepare the stage plan for the next stage and the request authorization to start the next stage
+Activities for this process include:
+- Plan next stage: Create the next stage plan
+- Update the project plan: Confirm what has been done (actuals)
+- Update the business case: Update with the latest cost information
+- Report stage end: Create the end stage report
+- Option: If exception then produce an exception plan (to replace current plan)
+## Process 7 - [[Closing a project]]
+This process aims to provide a fixed point to check that the project has reached its objectives and that the products have been accepted by the customer.
+Objectives:
+- Verify user acceptance of the project’s products (delivered by the project)
+- Ensure that products can be supported after the project
+- Review the performance of the project
+- Assess the benefits already realized and plan post project reviews
+- Address open issues and risks with a follow-up on action recommendations
+The project board close the project and the project manager only prepares the project for closure.
+Closing a project activities:
+- Prepare planned closure: Confirm the completion and acceptance of the products
+- Prepare premature closure: Only if requested by the project board (optional)
+- Hand over products: This is described in the change control approach
+- Evaluate the project: Compare project objectives and write end project report.
+- Recommend project closure: Send a notification to the project board
 
 ---