minimata/ObsidianHome
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

vault backup: 2023-09-18 23:08:54

Browse Source
This commit is contained in:
Alexandre Serex
2023-09-18 23:08:54 +02:00
parent c93c524e98
commit 474e12dcd7
1 changed files with 23 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files

25
Notes/Literature/PRINCE2.md
View File

@@ -122,8 +122,29 @@ Risk management is about actions you take to enable you to identify, assess and
- Respond: How best to respond to a risk and responsibilities
## Theme 6 - [[Change]]
This theme aims to help identify, assess and control any potential changes to the products that have already been approved, which is inevitable. Issue and change control happen during the full lifecycle of the project. The objective is not to prevent it but to get changes agreed upon before execution.
Each project requires a [[Configuration management system]] that tracks products, records when products are approved and helps ensure the correct versions are being used.
Each project requires a [[Configuration management]] system that tracks products, records when products are approved and helps ensure the correct versions are being used.
Definitions:
- Issues: event that has happened that was not planned and that requires some management action. Raised anytime by anyone.
- Configuration management is the technical and administrative activity concerned with the creation, maintenance, and controlled change of the configuration of a product.
- Configuration item: name given to an entity managed by the configuration management.
- Baseline: A point of time for a product against which the product is monitored and controlled.
- Release: a complete and consistent set of products that are managed, tested and deployed as a single entity.
## Theme 7 - [[Progress]]
This theme aims to:
- establish how to monitor and compare actual achievements against those planned
- provide a forecast for the project objectives and continued viability
- be able to control any unacceptable deviations
Progress is about comparing current project state to baseline. Project control involves measuring actual progress against the six aspects of [[Project performance]]. Progress can be monitored at three levels:
- Project level (project board)
- Stage level (project manager)
- Work package level (team manager)
Progress control involves measuring actual progress against the performance targets and each project layer wishes to monitor the layer below. Each layer does the following:
- Monitor actual progress against the plan (review plans with forecast)
- Detect problems and identify risks
- Initiate corrective action to fix issues
- Authorize further work to be done
An exception is a situation where it can be forecast that there will be a deviation beyond the agreed tolerance levels. Tolerances are the deviation above and below a plan’s target. For example, the project should take 6 months, with a tolerance of ±1 month. Tolerance levels could also be set for all 6 tolerance areas.
# PRINCE2 processes
---