Let's start by recalling that the seven principles of PRINCE2 are continuous business validation, experiential learning, roles and responsibilities, phased management, exception management, product focus, tailoring.
The fifth principle: Exception Management.
PRINCE2 defines tolerances for each project objective to establish the scope of authorization, and establishes the appropriate system by defining, directing and delivering the responsibilities required at these three levels. Usually performed in three ways
1, set three levels, each level for six performance indicators of tolerance, a layer of authorization, before the six major performance indicators (time, cost, scope, quality, plus risk and income)
2, the establishment of control: If the forecast project will break through the tolerance deviation, will report to a higher level of management, determine how the project continues
3, the implementation of the guarantee mechanism: so that all levels of management confidence, effective control of the project
The implementation of exception management can efficiently utilize the time of senior management to ensure that decisions are made at the right level of the organization, thereby reducing the burden on the top and not weakening their control. In fact, the exception management is the issue of authorization, at each level has how many rights, and in the actual combat is often the headache is authorization, authorization is not enough, timid. Too much authorization, nothing to do, no restraint
"What is PRINCE2" the Seven Principles of PRINCE2 Certification (5)