Issues in managing projects using prince2 methodologies



What is PRINCE 2?

PRINCE2 is one of the world’s most widely used project management methodology. It was originally developed for UK government IT projects, its use has been widened to large projects of all kinds, and it has been taken up internationally in more countries in both public and private sectors such as police forces, telecommunication companies, banks, as well as other large commercial organisations and also used in enterprise resource planning implementations.

(Reference: Managing Successful Projects with PRINCE2. 2005 Edition).

PRINCE2 stands for Projects in Controlled Environment and it was developed at a time when the UK government was outsourcing an increasing amount of its work, and the methodology incorporates best practice on the integration of internal teams and external agencies.

The focus throughout PRINCE2 is on the business case, which describes the rationale and business justification for the project.

PRINCE2 takes a process approach to project management, fitting each process in to a framework of essential components that need to be applied throughout the project. PRINCE2 focuses mainly on the aspects of managing projects in the lifecycle for project managers in an ideal world, PRINCE2 ensure that every step within the project lifecycle is completed on time and within the budget while using the right resources.

The technique of PRINCE 2 methods works with most project management techniques but specifically describes the quality reviews for project documented, output driven product based planning and a change control process for agreeing potential changes and fixing faults.

(Reference: OGC. (13 January 2011) ‘PRINCE2′)

Benefits of Prince 2

The Prince 2 methodology has many advantages and benefits to it. In recent years, large IT projects and government departments have implemented the method, where it has had a huge benefit to the project through using Prince 2. The office of government commerce (2007) has stated that the Prince 2 methodology has guided projects with the right terminology. It is a constant, reliable and organised approach to adapt to a project from the beginning, middle and end stages. It brings a product base to the project which divides the project into stages making the project very easy to manage. This assist the project team to maintain a motivated and focused workforce and being capable to deliver the outcome expected on time.

Another benefit it brings to project teams is that it improves all communications between members and other stakeholders; this provides the project to be more controlled and team members to work sufficiently with one another without having any problems. It gives stakeholders the opportunity to express their opinions when decision making as they are always informed through project reports and regular meetings.

PRINCE2 comprises of established and proven best practice and governance for project management. It can also be applied to any type of project and can be easily be implemented in specialised industry models; either construction, engineering models, IT, business, financial or development lifecycles. This is because PRINCE2 plans are carefully designed to meet the needs of the different levels in the management team, improving communication and control. As it is widely recognised and comprehensive, it enables good communication channels between all project participants and has an explicit recognition of project responsibilities in order for participants to understand each other’s roles and needs; with a well defined structure by limiting delegation of authorities among participants.

(Reference: OGC. (2009), Managing Successful Projects with PRINCE2TM, 5th Edition, and London: The Stationary Office)


PRINCE 2 takes a process based approach to project management; any project run under this methodology will need to address each of these processes in some form. There are seven processes in PRINCE 2 which provide a set of activities to direct, manage and deliver a project successfully.

Ø Starting up a project (SU)

This is the first process in PRINCE 2. It is a pre project process, designed to ensure that the basics for initiating the project are in place. The process expects the existence of a project Mandate that defines in high level terms the reason for the project and what product is required.

Directing a project (DP)

This process is aimed at the project board, the management team representing the sponsors, the users of the final product and the suppliers of the product. The project board sets the direction and makes key decisions throughout the life of the project, this process is owned by the project the project board and provides authorisation for work to be carried out and resources to be committed.

Ø Initiating a project (IP)

Initiating a project (IP) is aimed at laying the foundations for the fulfilment of the principles just described. It follows the pre- project process “Starting up a project (SU) it is triggered by authorising initiation, leads to authorising a project, and invokes the planning process to create the project plan and the managing stage boundaries (SB) process to create the next stage plan.

Ø Managing Stage Boundaries (SB)

During the initiation stage and at the end of each stage, this process is used to plan the next stage in detail, it reports on the achievements of the current stage and the impact on the overall project plan and business case and produces the information on which the project board will take key decisions on whether to continue with the project or not.

Ø Controlling a stage (CS)

A project may have many stages. This process describes the monitoring and control activities of the project manager involved in allocating work, ensuring that a stage stays on course and reacting to unexpected events. The process forms the core of the project manager’s effort on the project, being the process that handles day to day management of the project.

Ø Managing product Delivery (MP)

This is where the main development work for the project happens, and where the majority of resources are consumed. This process focuses on the creation of the specialist products; progress whereby a checkpoint report is provided to the project manager and the quality activities defined in each product description are implemented and the products approved.

Ø Closing a project (CP)

This process covers the project manager’s work to wrap up the project at the end; this includes the activities for closing the project in an orderly way. Acceptance for the project is confirmed and the projects products are handed over, and any activities required to review benefits that have not yet been realised are documented in the Benefit Review plan. The end project report is prepared to include a review of the business case, the projects objectives and team performance.

All these aspects would normally be termed good management. The difference here is the level of structure and documentation that is required by the standard.


PRINCE 2 has a process based approach to project management. The PRINCE2 themes describes aspects of project management that need to be continually addressed, it defines the management activities to be carried out during the project. The strength of PRINCE2 lies in the way that the seven themes are integrated: they are carefully designed to link together effectively. The themes are used throughout the processes to give more detailed guidance on the common aspects of project management.

All seven themes must be applied but can be tailored according to scale, nature and complexity of the project concerned. The seven PRINCE2 themes are as follows:

Business Case

Every project should be driven by a business need. This theme addresses how an idea that could have value for the organisation is considered and developed into a viable business proposition.

It also explains how project management should maintain focus on the business objectives throughout the project.


The structure of a project management team. This theme defines the roles and responsibilities and relationships of all staff involved to manage the project effectively. These roles are separate from day to day line management.


This theme describes how an initial idea is developed so that all participants can understand the quality aspects of the products to be delivered. It also explores how the project managers ensure these delivered the required standards.


PRINCE2 offers a series of plan levels that can be tailored the size and needs of a project and an approach to planning based on products rather than activities. Plan is the focus if communication and control as the project proceeds.


Risk is a major factor to be considered during the life of a project. PRINCE2 defines the key moment when risks should be reviewed, outlines an approach to the analysis and management of risk, and tracks these through all the processes.


This theme describes how project management assesses the potential impact on any of the project tolerances of Time, Cost, Quality, Scope, Risk and Benefits. These issues could be unanticipated general problems, requests for change or instances of quality failure.


This theme explains the decision making process for approving plans, the monitoring of performance and the means of escalating events that do not go according to plan. This enables the project board to determine whether the project should proceed.

(Reference: Managing Successful Projects with PRINCE2, 4th Edition and Managing Successful Projects with PRINCE2TM, 5th Edition)

Issues in using PRINCE2 Methodology

CriticismsrelatenottothePRINCE2frameworkormanual,butrathertoorganizationalshortcomingsincludingpoorprojectgovernanceandtheinabilityoforganizations tosuccessfullyintroduceandimplementPRINCE2 oralackofprojectleadership.

PRINCE2 is a structured project management principles and procedures with an intension to its application to cover all types of projects. PRINCE2 strength is in its wide applicability and it is entirely generic but it has been criticised for not been able to provide specialist aspects, detailed techniques and leadership capability.

Specialist Aspects

In terms of specialist aspects, some project experts are required especially industry-specific or type specific to carry out specific technical part of a project, which PRINCE2 does not cover. Also such aspects of activities that are excluded in PRINCE2 methodology are engineering models, project lifecycle or specific techniques like organisational change management or procurement while PRINCE2 categorizes all these aspects of project work as “specialist”. Specialist products needs to be identified and included in project scope and plans.

PRINCE2 methodology also excludes some proven techniques of project management in planning and control like the critical path analysis in planning control and earned value analysis in progress control hence, the recommendation is that some of these techniques could be use in support of the PRINCE2 components or themes.


When dealing with leadership capability, it is impossible to codify in PRINCE2 methodology the leadership skills, motivational skills and interpersonal skills which are greatly important in managing any projects as all these are deliberately and carefully omitted. PRINCE2 did not address this aspect of project management directly as leadership styles vary considerably and the style that works in one situation may be entirely inappropriate in another.

In the planning process Prince2 states that activities and indecencies should be identified in which indecencies for the activities are identified but not for the products. There are so many products in an organisation which uses Prince2 does not explain the impact the products have on other products. In this way more work is generated which becomes too much meaning the costs on the project will increase and huge cost overruns will be the outcome. If not managed properly accordingly to the needs of the project it can become very difficult for small projects to handle.

Risk Management

Another issue is risk management, which is well known as a great threat to project failure. PRINCE2 shows that the earlier the stage is, the more important that stage is. That is, the project may become more successful if they improve risk management at the project brief stage. (Paul Elkington et al, 2000). This shows that risk management should be carried out as early as possible. In the software development life-cycle for example, its faults and defects are generated in every early stages of development. The earlier they are discovered corrected, the less cost and risk the project has. But yet, PRINCE2 does not provide advice of estimating the project risks for the project manager. It is agreed by Bob Hughes in ITNOW interview (2006) that PRINCE does not offer much guidance on how problems are resolved and how judgements are to be made, when they are identified. When problems aren’t resolved properly they can lead to several consequences, leading to the project to have more risk. As Paul Elkington et al (2000) states that ‘eight of the project managers felt that they could benefit from further training in risk management, highlighting that the Prince2 method is weak in this area’.

Analysis Requirements

There is no explicit treatment requirement for analysis; requirements are the most core level of forming a project. If there are no requirements, there are no projects. Also if the wrong requirements, the project will be ‘wrong’ too. When developing IT systems, two questions are always asked: Are we doing the right product? The first question is directly related to requirements gathering. If the requirements are not gathered accurately, the function provided within that system would not meet the requirements specified. PRINCE2 is an ‘implementation methodology, which can lead to projects being adopted on false premises, and thereby inevitably lead to failure of the project.’ (Reference: Lau, K. S. S. (2007) ‘Difficulties and weaknesses of using PRINCE2 Methodology’)

Case Study

There is a case study on PFI project where Prudhoe and Northgate NHS Trust are conducting a PFI project for three neurobisability services that includes a new build. George Slater is the Project Manager; Molly Worts is the Project Administrator. They both have a word on PRINCE2 methodology that benefits and drawbacks are experienced. George emphases that risk are obstacles to delivery, icebergs, which could sink the project. Therefore risk management is important throughout the project. And Risk Log can keep the Project Board an eye on risks. Highlight report makes the Project Board keep up to date in a time efficient way. Yet sometimes assigning people ‘who in and who out’ within the Project Board will be quite difficult to decide. Sometimes the Project Board will become too large that meetings become difficult to handle and time consuming. Therefore people management on Project Board is necessary. Molloy states that Project administration is very time consuming and repetitious. For example, an hour of meeting can generate loads of documentation: typing, which is timing consuming. As heavy workload for Project administrator, it will become difficult when dealing with urgent issues, or approval of every processes and stages, which can be stressful. (Reference: ‘PRINCE2 Case Study: The National Health Service’ by Richard Pharro)


Prince2 involves a lot of documentation which makes the series of its processes difficult to manage in terms of keeping trace of it how it going and understanding. Just documenting can become the main focus in which can lead the project in major trouble. Organisations with the matrix structure it can be an issue for small organisations in that Prince2 recognises four management levels “Corporate or programme management”, “Directing a project”, managing a project” and “managing product deliverer”. So in smaller organisations to employ people with such skills equivalent to the management level is not easy.

Also PRINCE2 can become a heavy duty approach for small projects as it may produce too much work load, especially on documentary, if the method is not tailored to the need of the project properly.

(Reference: Lau, K. S. S. (2007) ‘Difficulties and weaknesses of using PRINCE2 Methodology’)


Prince2 requires to work with technologies for it cannot work on it’s on to meet the specific organisational needs and projects The problem in this is training of staff on such a technology that works with Prince2 can be quiet costly and having such a technology itself.

It is also commonly accepted that one of the most common causes of projects failing to deliver benefits is a neglect of the planning process. There are many reasons for this, one of the most common being is that there is “no time to plan” as there is often a temptation to rush into things so the PRINCE2 business case gets forgotten, instead of having an adequate PRINCE 2 business case the start up phase is rushed or completely ignored and the organisation goes straight into the project initiation stage especially if there is a deadline to be met. The other side of this is where senior management does not recognize the importance of planning and will not make the necessary time available.


Another issue is that projects are often badly planned so they go off track, overspend and are unable to deliver the intended outcomes. Organising a project using the prince project management methodology requires a strong project board but often project boards are not strong and do not function well. They may ignore issues or avoid taking the key decisions they are there to make and so the project goes off track. Also the right skills are not identified to ensure the project goes smoothly or there is no management commitment so the project just lacks sufficient resources.


In PRINCE2 Projects in Controlled Environments is a major worldwide project management framework, or methodology. It takes a different approach than the PMI™s PMBOK but the goal of both is to improve project performance. While PMBOK is generally well-accepted worldwide, it is by far the leading approach in North America. PRINCE2 on the other hand is strongest in the United Kingdom, with a strong presence in Europe, Australia, and other typically English-speaking countries outside North America. But both are expanding there reach on a constant basis as the world gradually “projectizes.”

(Reference: PMcrunch (29 February 2008) ‘Comparing PRINCE2 and PMBOK – 3 Perspectives’)

PRINCE2 is used extensively by the UK government and private sectors has lead to the methodology often been evaluated with other world best project management method or standards, a good example is that of project management body of knowledge as an internationally recognised. It provides the fundamentals of project management, irrespective of the type of project like: construction, software, engineering or automotive.

PRINCE2 as being described as a structured method for effective project management for all types of project while PMBok on the hand is known as Project Management Body of Knowledge is a collection of processes and knowledge areas generally accepted as best practise within the project management discipline.

There are several differences between PMBok and PRINCE2 methodologies. According to Wideman (2002, pg3) explains that “PRINCE2 speaks of “stages” rather than “phase” and states that while use of stages is mandatory, their number is flexible according to management requirement of the project. PRINCE2 also differentials between technical stages and management stages where technical stages are identified as a specialist skill while management stages equate to commitment of resources and authority to spend. Contrarily the Guide (Pmbok) defines a project phase as ‘a collection of logically related project activities usually culminating in the completion of a major deliverable’. It does not distinguish between phase and stages and in the text uses either indiscriminately”.

The Guide to Project Management Body of Knowledge (Pmbok) is a standard manual for any project by Project Management Institute which should be project manager ethics while PRINCE2 is an implementation methodology.

There is differing definition of responsibility of the project manager. According to Wideman (2002, pg3) argue that “the Guide (Pmbok) defines project manager simply as an individual responsible for managing a project, while PRINCE2 defines project manager as the person given the authority and responsibility to manage the day-to-day basis to deliver the required products within the constraint agreed with the project board. These constraints are referred to as “tolerances” and prescribe the ranges of acceptability of each of scope, quality, time and cost within which the project manager must manage”.

Under PRINCE2 methods management is done by the project board and directed by an executive who is mainly responsible for the project; while Pmbok does not recognise either “executive” or “project director” but uses the term “sponsor”. According to Wideman (2002, pg4) argue that “the sponsor is one of the project’s stakeholders and is defined as the individual or group either within or external that provides financial resources, in cash or in kind for the project; this shows under Guide (Pmbok) that it is the project manager who is firmly in charge”.

PRINCE2 and Pmbok takes a very different approach to presentation of their materials which serve different purposes and therefore not directly comparable. According to Wideman (2002, pg7) further explains that “the Guide (Pmbok) takes the best approach for purposes of teaching the subject content of each knowledge area, but it is not effective when it comes to providing guidance for running a particular project”.

Reference: (Wideman, R. M. (2002) ‘Comparing PRINCE2 with PMBoK®)

Some other advantages of PRINCE2 there is no equivalent PMBOK pre-project process to PRINCE2’s ‘Starting up a Project’ (SU), so there is no discussion of what or who should be in place at the beginning of a project.

PRINCE2 offers a complete change control approach, whereas PMBOK just talks of the need for it. The PMBOK only talks about a Project Plan, whereas PRINCE2 offers Stage and Team Plans and discusses the advantages of breaking the project Plan down. PRINCE2 offers standard roles for its project management team, were PMBOK only covers the creation of a WBS, and does not compare to the PRINCE2 product-based Planning technique in terms of the latter’s Product Descriptions and Product Flow Diagram. Nor is there any real detail in the PMBOK Planning process to take a plan through to a network plan and a Gantt or bar chart.

(Reference: (24 January 2002), A comparison of Prince2 against PMBOK)

Despite PRINCE2 has many excellent ideas for project management, some critics finds the approach to quality management process as inappropriate and not very realistic. At the beginning of a PRINCE2 project you agree with a client about a set of measurable attributes regarding the products you want to use for building. These are called “acceptance criteria” that is when you deliver the products later, the client will only sign it off if they conform to the criteria settled earlier; this assumes that client knows what they want. In reality they often do not know as project work is a creative process, while sometimes it takes trial and error as well as a certain amount of vision to create something the end users will eventually be satisfied with.

The methodology issue of PRINCE2 in terms of making a mountain paper requires a communication plan in the project initiation document that is, the main plan for the project. Communication plan states how each particular communication will be made. This maybe formal with a letter or memo, by meetings or e-mails or by putting information on a project website and also by phone call. All these creates countless of papers and document.

In terms of PRINCE2 is only for big projects is not true because its methodology can be use for small, medium and big projects and this has already been confirmed by many project managers who have applied PRINCE2 in their projects. In fact, part of the skill in using this methodology is to know how to apply it appropriately to each individual project.

In terms of managing a project and having to use PRINCE2, you manage a project using PRINCE2 so there is no cost or little in using the method to manage a project. It is a superb best practise method and if use properly it will be a real help with the job of planning and controlling a project.

PRINCE2 is definitely flexible and unique to use. There is nothing about this method that you cannot adjust. Therefore you can fine tune it to the exact needs of the project. The success of PRINCE2 rest on applicability and tailoring towards the project with greater flexibility.

(Reference: Inspirandum (2008) ‘PRINCE2 Practitioner Paper Common Criticisms of the Method’)


In conclusion to this report we have discovered the principles and each individual component of Prince2, highlighting both positive and negative factors and also explaining the stages from start to finish. After addressing the main issues of Prince2 we have found that prnce2 does not have many specialist, meaning that the task that has to be done will be not be done by professionals. This suggests they could extend the current PRINCE2 certification to recognise practitioners who both understand the framework and can proficiently apply it in managing actual projects. So that Prince2 can focus more on specialists to perform some parts of the projects as this can improve the quality as well as time.

However the methodology does not address leadership and people management. This also another floor in Prince2 is the interpersonal skills the leaders have with their partners/staff. As it is known to Maslow Motivation is a very big factor when it comes to efficiency, so at the initial stages of Prince2 leaders should make sure that apart from the actual project the staff are satisfied, leading to efficiency of the project. As a lot of prince2 is based on documentation, this can cause leaders to focus mostly on the project and not so much the people involved in the project. Prince2 should devise a plan to tackle the main project, but also involving the people’s needs in the plan. This leads to the next issue that was addressed, as it was fount that the Prince2 often rushes the initial part of the planning stage. Planning is essential in project management, as this can determine whether a project is going to be successful. This suggests PRINCE2 should find the time to plan a project properly, as this will improve PRINCE2 drastically.

As well as establishing the issues in Prince2, there were also many positive factors and also many contradictions in some of the criticisms made by theorists. The main advantages from Prince2 suggest that it is not robotic, as you can adjust the needs to your project making this methodology very flexible. And it is very often that managers and directors need guidance when carrying out a project. Prince2 does this very well and it also focuses on what the project has to deliver, to whom and why. As a result it is used worldwide among many organisations including the government and other large organisations.

The post Issues in managing projects using prince2 methodologies appeared first on mynursinghomeworks.


Source link