Skip to main content

PRINCE2 Roles: The Reigning Project Management Methodology


 
A carry on from our previous post, PRINCE2 Fundamentals: The Reigning Project Management Methodology. This post is concerned with the 7 roles of PRINCE2

The 7 roles in PRINCE2

There are 3 principle roles for PRINCE2: the project board, the project manager, and the project team. But there are many supplemental roles that help ensure requirements and standards are met and that work runs smoothly.



  • The customer is the person paying for the project to be completed.
  • The user will either use the project deliverables or will be impacted by the project's outcome. (For some projects, the customer and user may be the same person.)
  • The supplier is a subject matter expert who provides the knowledge needed to complete the project by designing or building the end result.
  • The project manager is responsible for organizing, planning and overseeing work on the project. They select and manage the people who complete project tasks, and they’re responsible for making sure work is done correctly and on time.
  • The project team and team manager actually roll up their sleeves and get project tasks done. Team managers oversee the detailed aspects of daily work and report directly to the project manager.
  • The administrator sets up meetings, keeps everyone updated, tracks documentation, etc. On small projects, project managers will often take over this responsibility, but if there are multiple projects running at once or the project is large/complex, a project support office is typically set up to manage these duties.
One of the 3 main roles, the project board typically includes multiple people: the customer (typically a senior executive), the end user (or a representative), and the supplier. It checks for project assurance from three unique perspectives:
  • The customer ensures the project is still viable financially, typically through cost benefit analysis.
  • The user ensures user needs are being met.
  • The supplier checks whether the project is working towards a realistic, practical solution.
On some projects, PRINCE2 assurance is done by an unbiased, third-party team.
 



Comments

Popular posts from this blog

Revisiting Managing Stakeholders, how to Nurture and thrive the relationship.

  Stakeholders can make or break projects, in order to ensure project success, effective stakeholder management is required. Identifying key stakeholders, dealing with difficult ones and creating a management plan can be overwhelming if you don't know where to start. Building positive relationships with stakeholders and proactively meeting their expectations can make the life of a project manager much, much easier.

How to Resource Plan

When managing a project or a project portfolio, it’s critical that resources and workload for each are intelligently distributed. Without proper resource allocation, projects can quickly get out of control in terms of expense and duration. With the right resource planning techniques, effective planning and management of resources in any industry can set you up for success. But before the break down on how Projectmanagementcompanion.com provides the perfect tools for resource planning and management, there must be a firm understanding on what resource planning is and how to compose a resource plan. Resource planning is one of the steps required when writing a business plan where all the resources in a proposed project are identified. This is achieved by creating a summary for managing workload that is comprehensive enough to make sure all the resources that are needed to complete the project are clearly identified. This summary is going to help get a buy-in from the sponsor an...

The difference between a Project Manager and a Scrum Master

By the nature of the work that Project Managers and Scrum Masters do, the two are not particularly closely aligned, even if it seems at first glance that they are. Managing a project is not the same as being a Scrum Master. Scrum Masters have the role of mentoring, teaching, coaching and facilitating, while the role of the Project Manager is to ensure that the project runs to time and budget. This means that the Scrum Master relies on more of the so-called “soft skills” involved with helping people to move forward, while the Project Manager takes a more methodical, and arguably more of a “hard skills” approach. While both roles have an interest in ensuring a high level of team performance and driving efficiency within the team, the ways in which they go about this are very different. The Scrum Master facilitates and coaches, while the Project Manager assesses risk and manages issues and conflicts.  Looking closer at what Project Managers and Scrum Masters do in terms of ...