From 98f7e07d8e10f31650ea4078e9b0b37ac9b67604 Mon Sep 17 00:00:00 2001 From: Minimata Date: Fri, 15 Sep 2023 14:46:42 +0200 Subject: [PATCH] vault backup: 2023-09-15 14:46:41 --- Notes/Literature/PRINCE2.md | 4 +++- 1 file changed, 3 insertions(+), 1 deletion(-) diff --git a/Notes/Literature/PRINCE2.md b/Notes/Literature/PRINCE2.md index 5cb018d..3e932f1 100644 --- a/Notes/Literature/PRINCE2.md +++ b/Notes/Literature/PRINCE2.md @@ -59,7 +59,9 @@ Increasing the number of stages increases control over the project at the cost o - having both a very detailed and high level project plan - [[Learn from experience]] from stage to stage ## [[Manage by exception]] -Manage by exception is to allow a layer of management to have some control over another layer while letting them room to work. +Manage by exception is to allow a layer of management to have some control over another layer while letting them room to work. The lower layer works as it can and only informs the upper managing layer when a big issue (i.e. an exception) is outside of their ownership. An exception is a big issue that takes a level out of their agreed tolerance. +Therefore, a PRINCE2 project has defined tolerances for each project objective to establish limits of delegated authority, as defined by [[Defined roles and responsibilities|the second principle]]. + --- # References