- Pass The PRINCE2 Exam First Time
- PRINCE2 In Bite-Sized Chunks.
- Key Foundation and Practitioner Learning Points - PRINCE2
- Change Management
- Managing and Controlling a PRINCE2 Delivery Stage
- PRINCE2 Project Closure
- PRINCE2 Starting Up A Project Process
- Using PRINCE2 Initiating A Project Process
- PRINCE2 Authorizing Initiation
- The PRINCE2 Controlling a Stage Process
- Appoint The Executive and Project Manager
- Authorising a PRINCE2 Project
- Authorize a Stage or Exception Plan
- Authorize a Work Package
- Capture and Examine Issues and Risks
- Change Control
- Change control procedures
- Configuration Management
- Configuration Management and Change Control
- Controlling a stage
- Create the PRINCE2 Communication Management Strategy
- Creating a PRINCE2 Plan
- Design and appoint the Project Management Team
- Execute a PRINCE2 Work Package
- Give Ad-hoc direction in a PRINCE2 project
- Hand over products and evaluate a PRINCE2 project
- Managing A Stage Boundary
- Managing Product Delivery process
- PRINCE2 - Authorise Project Closure
- PRINCE2 - Directing a Project PRocess
- PRINCE2 Configuration Management and Change Control
- PRINCE2 Controls and Tolerance
- PRINCE2 Estimating Techniques
- PRINCE2 Management Stages
- PRINCE2 Plans
- PRINCE2 Principles
- PRINCE2 Product-based Planning video
- PRINCE2 Product-based planning technique
- PRINCE2 Progress reporting
- PRINCE2 Quality Theme
- Plan The Next Stage or Exception Plan
- Plan the Initiation Stage in PRINCE2
- Prepare the PRINCE2 Quality Management Strategy
- Prepare the Risk Management Strategy
- Prepare the outline Business Case
- Product Based Planning
- Project Board and Project Manager PRINCE2 Controls
- Project Startup
- Quality Expectations and Acceptance Criteria
- Quality Management Strategy
- Quality review technique
- Report Highlights
- Reporting PRINCE2 Stage End
- Select the project approach and assemble the Project Brief
- Set up the PRINCE2 project controls
- Simple Study Aid
- Tailoring PRINCE2 Themes
- Take corrective action
- The Closing a Project Process
- The Controlling a Stage Process
- The Core Seven
- The Only PRINCE2 Sample Practitioner Exam Paper On The Internet!
- The PRINCE2 Business Case
- The PRINCE2 Change Theme
- The PRINCE2 Initiating a project process
- The PRINCE2 Process Sequence
- The PRINCE2 Processes
- The PRINCE2 Quality Review Technique
- The PRINCE2 Risk Management procedure
- The PRINCE2 Themes
- The Prince2 Process Sequence
- The risk management procedure
- prepare for planned or premature closure
- The PRINCE2 Article Library
- 38 Speedy Power Keys For Your PRINCE2 Project Health Check.
- Carrying out a PRINCE2 Quality Check
- The Product Description
- The plans theme and product based planning
- Creating a PRINCE2 Product Description
- PRINCE2 - Keeping Your Project On track - Part 2
- PRINCE2 Article Database
- PRINCE2 – Keeping Your Project On Track – PART 1
- Tailoring PRINCE2 for a feasibility study.
- Tailoring PRINCE2 with Agile (DSDM Atern)
- The Benefits Review Plan
- The PRINCE2 Risk Theme – Uncertainty Mastered!
- The PRINCE2 Work Package
- The Secrets Of tailoring PRINCE2
- The Use and Content of the Issue Register and Issue Report
- Applying earned value calculations to PRINCE2.
- PRINCE2 Foundation and Practitioner Exam Tips
- Using Project Sc ale In A PRINCE2 Project
- Creating a PRINCE2 Exception Report
- Agile verses PRINCE2 - a new species in evolution
- PART TWO of my Configuration Management In PRINCE2 Video
- PRINCE2 Quality
- Real-World PRINCE2 Planning
- Reviewing the progress on a PRINCE2 project
- Risk management
- Things You Might Not Know About PRINCE2
- The PRINCE2 Project Board and Governance
The Secrets Of tailoring PRINCE2
The Secrets Of Tailoring PRINCE2
One of the many reasons for the success of PRINCE2 is its ability to be tailored to suit the context and the environment within which the project is to be delivered. Applying PRINCE2 has a framework for your project can be done independently of the project scale, its complexity, risk, geography or culture.
Tailoring of a PRINCE2 project is driven by the amount of planning that is required, the amount of control that is required, the government’s that is needed, and the application of the use of the seven PRINCE2 processes and the PRINCE2 themes.
It is important to compare and contrast the use of tailoring verses embedding. Tailoring involves adapting the PRINCE2 method to suit the context of an individual project, whereas embedding is carried out at organisation level to adopt and adapt PRINCE2 for all of its project endeavours.
PRINCE2 consists of a set of interlocking and holistic framework elements, and therefore should not be seen as just a collection of bits and pieces related to project management that can be picked and mixed at a whim or preference. The seven processes incorporate the seven themes which draw upon the various techniques to apply in the themes in an appropriate manner, and all of these are used and applied by the project management and a specialist teams.
The watch word here is that PRINCE2 must be tailored as an entity, and if any element of PRINCE2 is arbitrarily discarded, the project will be negatively impacted with an increased risk of failure.
Factors external to the project will determine how PRINCE2 is to be adapted to suit the environment within which the project is to be delivered, and a rule of thumb here is to adapt and adopt PRINCE2 at its minimal level conducive to the size, complexity and risk of the project.
Aspects which will influence and how PRINCE2 is tailored will depend upon environmental and project factors, and these must be used as the drivers to adapt PRINCE2 – ‘lean and mean’ is a good way of thinking here.
Environmental factors.
These could include the importance of the project within the organization, the culture of the organisation, standards that must be met, organisational maturity, etc. Other examples may include if the project is part of a programme, whether it is an internal or external project, and whether or not third party suppliers are to be used. Also use of PESTLE can be helpful here.
Project factors.
These could include aspects such as the complexity of the solution, the amount of risk both within the project including the risk appetite of the management team, the level of governance, the maturity and skills set of the team, the approach and life-cycle model that must be applied, etc.
Aspects of tailoring.
The seven PRINCE2 principles must never be tailored as they are the bedrock upon which the method is based. Instead, these principles must be used as the key drivers to adapt the processes and themes against the back drop of the environmental and project factors.
PRINCE2 processes.
Similarly, all seven of the PRINCE2 processes must be used, but the secret here, is to consider carefully how each of the process activities are to be carried out and who is to be responsible for them. This is important because roles may have been adapted or shared. Similarly, management products may also have been adapted and this will have an effect on carrying out the activities within the processes.
PRINCE2 themes.
The environmental and project factors will influence the level of control required and how formal and often such controls are applied during the monitoring, reviewing and reporting of the project. A key aspect here is to apply a them organizations policies and standards and two documents these within the risk, quality, configuration, and communication management strategies. Since these documents described the ‘How’ of the project, they will drive how the themes are to be adapted and tailored.
PRINCE2 roles and management products.
PRINCE2 does not dictate the number of individuals involved within a project, rather it describes a Project Management Team set of roles which can be filled by one or more individuals, or shared by a single individual. Some of the responsibilities laid out for each role may be given to others if the individual filling that role does not have appropriate knowledge, skills, experience, or authority to carry them out.
PRINCE2 describes the set of management products via product descriptions for each, and if a product is to be tailored, then its product description should also be modified. To ensure that each modified product description remains affective, it must still described the products purpose, its composition and derivation, and its quality criteria.
It may also be appropriate to consider the language and descriptive terms of an organization uses, and considers this when naming products for example. This may also include combining some of the PRINCE2 management products under a new name. Again, what is important here, is that each management product retains a clear understanding of its use an application within the project.
PRINCE2 tailoring factors.
There are probably an infinite number of factors against which PRINCE2 may be modified or tailored in some way, but some obvious examples are:
- Projects that form part of a programme
- The business and organisational environment
- The level of complexity of quality assurance and control
- Project planning methods
- The approach and tools used for risk management
- The change control procedure to be used
- The formality and frequency of reviewing and reporting
- The complexity and number of management stages to be used
- The scale of the project
- The level of formality of the project
- The commercial customer and supplier environment
- Processes and procedures to be followed
- The use of multiple organizations
- The lifecycle model to be used
- Evolving projects
- Industry and sector differences
- The project management body of knowledge
- The technical or specialist complexity of the project
For more information CLICK HERE



