Written by Jeff on March 29, 2017 in example

This example shows a library of Good Practice bricks. 

This library contains bricks related to the Prince2 method. The library is therefore a “horizontal” library, as it is general purpose, for all types of project. 

This example is illustrative, for discussion purposes only. It is based on real-world feedback from several Prince2 teams which do not follow the Prince2 method closely. The term PINO is sometimes applied to this approach (PINO = Prince in Name Only).

Type Sub-type Brick Description
Lifecycle Early work Mandate A document which triggers a project
Lifecycle Early work Two Gate Start Two gates before project delivery can start
Lifecycle Delivery Un-gated delivery No gates during project delivery
Lifecycle Delivery Gated delivery One or more gates during project delivery
Lifecycle Close Un-gated Close No gate at project closure
Lifecycle Close Gated close Gate at project closure
Lifecycle Close Two Gate close Two gates to close the project (first closes delivery, second confirms handover or benefits)
Planning Plan Project Plan High level plan for whole project
Planning Plan Stage Plan at Gate At gate, plan the next stage
Planning Plan Team Plans based on Product Descriptions When work is given to a team, the work plan is based on written product description(s)
Planning Plan Release Road Map Plan of releases during the project
Scope Specification Description of final product Written description of what the project must deliver or produce
Scope Specification Project PBS A high level product breakdown structure for the entire project. Typically 15-20 products
Scope Specification Product Descriptions Written descriptions of each product
Scope Specification Product Flow Diagram A high level diagram showing the order in which products should be delivered
Scope Investigation of needs Feasibility study before delivery starts Early work to prove concept or feasibility before normal project delivery can start
Scope Investigation of needs Analysis before delivery Business or technical analysis before project delivery starts
Scope Investigation of needs Analysis at start of delivery Business or technical analysis as soon as delivery is authorised
Scope Discovery of needs Iterative Development Project delivery converges towards a solution in an iterative manner. Increases feedback.
Scope Discovery of needs Incremental Deployment During project delivery, intermediate solutions are deployed into operational use.
Scope Confirmation of solution Prototype An approximate solutions with limited functionality. Ensures feedback.
Scope Confirmation of solution Pilot Deployment A deployment in a limited environment. Ensures feedback
Scope Experimentation Safe-to-Fail Experiment Work done to gain knowledge. Failure is acceptable, as it adds knowledge.
Team Small Project Part time PM Project Manager works part time
Team Small Project PM runs integration activity During project delivery, the Project Manager delivers integration products.
Team Small Project PM runs QC team During project delivery, the Project Manager manages a quality control or testing team
Delivery PM tracking doc Risk Log A document to store risks (future uncertain events)
Delivery PM tracking doc Issue Log A document to store issues (current problems or requests)
Delivery PM tracking doc Decision Log A record of project decisions
Delivery PM tracking doc Communications Plan A document to plan communications to project stakeholders
Delivery Method of delivery Delivery by External supplier (PO or Contract) Delivery of work by external party. Contractual specification. Quality is conformity to specification
Delivery Method of delivery Delivery by Internal team (Specification) Delivery of work by internal team. Written specification, agreed plan.
Delivery Method of delivery Agile delivery (Timeboxes, Reviews) Delivery of work with fixed-time timebox or sprint, followed by review by client or user.
Delivery Delivery tracking Checkpoint reports Regular written report from a delivery team to Project Manager
Delivery Delivery tracking Daily Stand-up meeting Short meeting by a delivery team to get feedback from each team member
Delivery Delivery Quality Teams define quality (Definition of Done) Quality is defined by a delivery team during their delivery of work
Delivery Delivery Quality PM defines quality (on Product Specification) Quality is specified by the Project Manager prior to delivery of work by a team.
Facebooktwittergoogle_pluslinkedinmail
Tags