PRINCE2® is a project management methodology of 7s. The principles, practices and processes all follow this model. In this blog, we’ll break down each one and discuss how they are related to each other.

What are the 7 principles of PRINCE2?

The seven principles are a set of guiding values that shape the framework, and provide a solid foundation for managing a project.

1. Continued business justification: A project must make good business sense. There needs to be a clear return on investment, and the use of time and resources should be justified
2. Learn from experience: Project teams should take lessons learnt from previous projects into account. A lessons log is monitored and updated for this purpose
3. Define roles, responsibilities and relationships: Everyone involved in a PRINCE2 project, internal team members and external stakeholders, have defined and agreed upon roles and responsibilities
4. Manage by exception: A project running well doesn’t need intervention from the project board or other authority figures within the business. These individuals should only be informed should an agreed upon tolerance limit be reached
5. Manage by stages: Break the project up into manageable stages, each of which should be effectively planned, monitored and controlled
6. Focus on products: Your project should be focused on its product, and ensuring this meets the expectations and requirements of the user
7. Tailor to suit the project: PRINCE2 can be scaled and tailored to all projects regardless of their size, environment, complexity, team capability, etc. Projects that adapt PRINCE2 to their needs are more likely to succeed than projects that use PRINCE2 dogmatically

What are the 7 practices of PRINCE2?

The practices provide insight into how the project should be managed. These are set up at the beginning of a project, and should be monitored and addressed throughout.

1. Business case: The business case is used to support decision making ensuring the project remains desirable, viable and achievable
2. Organizing: This practice aims to define and establish the project’s structure of accountability and who is responsible for what
3. Plans: Plans define the who, what, when, where, how and for how much of a project
4. Quality: This practice helps ensure that the users’ requirements and expectations are met
5. Risk: The purpose of this practice is to identify, assess and control uncertain events during a project
6. Issues: Aims to address issues and control changes to the project’s baseline
7. Progress: The progress practice is all about tracking and monitoring the project, encouraging teams to check and control where they are in relation to the project plan

What are the 7 processes of PRINCE2?

The PRINCE2 methodology separates the running of a project into seven processes. Each one is overseen by the project manager and approved by the project board.

Starting up a project

This process ensures that the prerequisites for initiating a project have been established. This involves:

• Creating a project mandate which answers logical questions about the project. It explains the purpose of the project, who will carry it out and how to execute it
• Establishing a project brief, this is derived from the mandate, lessons log and discussions with people involved in the project
• Assigning a team, the brief should give them all the information needed for the next process

Directing a project

This process details the role of the project board, and should be an ongoing process through a project.

The main responsibilities of the project board include:

• Initiating a project
• Making key decisions
• Ensuring a project remains viable
• Dictating project closure

Initiating a project

The purpose of this process is to establish solid foundations for the project, outlining how the following performance targets will be managed:

• Time
• Cost
• Quality
• Scope
• Benefits
• Risk

Controlling a stage

In accordance with the PRINCE2 principles, a project should be split into manageable stages. The ‘controlling a stage’ process involves:

• Assigning the work within a stage
• Monitoring that these tasks are complete
• Handling issues
• Reporting progress to the project board
• Ensuring a stage remains within agreed tolerances

Managing product delivery

This process regards the communication between a project manager and team manager. Team managers may be internal or external. Their role is to coordinate the work that needs to be complete to deliver one or more of the specialist products that make up the final project product.

The majority of communication will be regarding the following steps:

• Accepting a work package
• Executing a work package
• Evaluating a work package
• Completing a work package

Managing stage boundaries

The project will be reviewed by the project manager and board at every stage, at which point the board will decide whether or not to continue with the project.

This process consists of the following activities:

• Confirming the stage end and completion of all related tasks
• Planning the next stage
• Reviewing and updating the PID
• Requesting authorisation to start the next stage

Closing a project

This process establishes an agreed upon fixed point at which the project is closed, and all objectives must have been met. This process involves:

• Checking the user is happy with the final product and that it meets all expectations
• Ensuring the business can continue to support the use of the product
• Review and evaluating the impact of the project
• Putting provisions in place to address any ongoing risks or issues
• Closing the project in an orderly manner

Team building, autonomy and engagement are big contributors to a project’s success. Some teams communicate poorly or feel disengaged from their work. There are countless projects that have suffered as a result of this. PRINCE2 has a number of methods aimed at improving teamwork.

***UPDATE***
PRINCE2 Agile is now available as an e-learning and classroom product. There are no formal pre-requisites for the Foundation qualification, but you will need to have either PRINCE2® Foundation or PRINCE2 Agile Foundation to take the PRINCE2 Agile Practitioner qualification.

—

Attentive visitors may have noticed a new kid on our course roster this year. Its name is PRINCE2 Agile. Published by Axelos in June 2015, it is the latest training option provided by ILX Group and PRINCE2.com. It is currently available as a classroom course in the UK, Australia, Europe and New Zealand. But what is it? Is it for you, and why? How do we know whether to embrace or shun this new course on the block? Allow us to explain …

Over the past few months, we invited two of our customers to act as guest bloggers and tell our readers about their experiences with PRINCE2 classroom and PRINCE2 online/e-learning training courses. Both candidates came away satisfied with their course. One, a novice to project management, achieved a PRINCE2 Practitioner qualification within five days. The other accrued enough fundamental knowledge that it could be readily applied in their management of projects and other day-to-day work.

At ILX Group, we’re proud of all the varieties of training course that we provide. We believe that we offer some of the best computer-based online self-study solutions in the world, created by specialists in learning development, subject matter experts and multimedia strategists. We’re not shy about the quality of our classroom courses either, with invaluable face-to-face instruction coming from adept teachers who are well-versed in their subjects, both as instructors and practiced professionals.

Our guest bloggers did a great job providing some insights into what to expect from either style of learning. However, we appreciate it can be difficult to know which is the best option, especially as there are similar exam pass rates across both styles worldwide. As a result, we have decided to compile some lessons and observations into one post for you, directly comparing the advantages and drawbacks of the classroom and the e-learning options.

“One day my Prince will come”, they said. And so it did – in the form of a project management qualification.

Welcome to the final part in this series about my experience of the PRINCE2 Foundation and Practitioner classroom course. The previous two posts – which you can visit here and here – covered three days of training in London, culminating in my encounter with the Foundation exam. Along the journey I’ve tried to provide tips for the would-be trainee, and insights into what to expect if you’re considering classroom-style learning.

To sit the Practitioner exam, a pass at Foundation level is an absolute prerequisite. Since I first entered the training centre a total novice to the subject of project management, I admit there was some doubt in my mind that I would be a certified Practitioner by the end of the week. Nevertheless, Foundation level was behind me. What lay in wait now, nobody could be certain of. However, I had a strong hunch that the course was going to be more in-depth, and perhaps even more intense.

Welcome to the second part of this series of blogs about my experience, as a newbie to project management, going through the PRINCE2 Foundation & Practitioner Classroom course. Part one covered my first day’s training at London’s Imparando Learning Centre. If you’ve considered taking an ILX classroom course and you missed that post, do go back and read it through. It covers useful tips for making the most out of being a PRINCE2 delegate and what else you can expect in the event that you attend.

This post will begin where the last left off, taking you through what happened during my second and third days’ training, and ultimately how it felt to come face-to-face with the PRINCE2 Foundation Exam. My hope is that, by reading it, you will get more valuable information about the course from the perspective of an average PRINCE2 trainee.

Have you ever thought about undertaking PRINCE2 training? If so, you’ve likely spent some time on the fence. When you’re looking to get certified, how to be sure what’s best between the e-learning course (allowing more personal time to complete but requiring more self-motivation) and the classroom-based version (the more intensive option, requiring up to five straight days of your time before becoming qualified in PRINCE2 Foundation & Practitioner)?

It’s not unusual for even the most adept project manager, with the firmest grip on organisation, to fall victim to the occasional overwhelming workload. This is especially true for managers who always say “yes” to more work, aiming to demonstrate their value, or to impress the stakeholders in a project. If you are taking on too many jobs though, it’s inevitable that you will end up with deadlines chasing faster than you can outrun them.

Collaboration is a fundamental requirement for delivering any project successfully. Project professionals and their teams cannot possibly hope to plan and execute their projects without involving contractors, suppliers and stakeholders. Projects that fail will invariably suffer a breakdown in collaboration between one or more parties.