PROJECTS wiki Prince2

PRINCE2 area - Organization

Universal Practical Simple Benefit focused Principles Implement Templates Ready apps for Jira

If you will compare PRINCE2 with other project management body of knowledge like PmBoK or IPMA competence baselines or Agile practices you will discover that PRINCE2 is very Roles & responsabilities driven standard. There are 9 roles very clearly defined from thousands of historical projects aggregated expierence. There are even few more additional roles are high level defined that can be used and tailored.

Why roles are so important to set - traditional management best practices say - if you are not able to define the roles you will struggle with delegation. In addition to this you will probably expierence increased team chaos, number of team member conflict risen and some power game potentialy.

PRINCE2 roles cover several management levels - from Top management to Team manager(s) - this is standard strong point as many other body of knowledge unfortunatelly miss some of this vital info.

PRINCE2 knowledge areas here will be provided only in executive summary as PRINCE2 standard gives much more details.

GOAL:

Create empowered structure with clear accountability & responsability in the project

MUST MANAGEMENT PRACTICES:

  • Documented project management team must be created with roles, responsabilities & authority in project plan
  • Documented Communication guide must be created in project plan
  • Two leading roles are must in each project Project owner/executive and Project manager
  • It is mandatory to decide regarding Change authority - role will be or not present in the project with described responsabilities
  • TAILORING PRACTICES:

    Here are just some limited number of management practices.

    All recommended practices you can read in stardard manual yourself or learn it in PRINCE2 trainings.

  • It is highly recommended to have separated these management levels - 1) Directing, 2) Managing, 3) Delivering
  • It is almost must to establish for each really important project Project steering comittee, where chairman must be Project owner/executive
  • Most empowered Project steering comittee will be created if it includes these three roles - 1) Project owner/executive, 2) Senior User(s), 3) Senior Supplier(s)
  • Based on the need these roles should be established in the project - Project assurance, Project support, Team manager(s)
  • It is recommended to give focus to quality to Project support role if such is established
  • Majority of PRINCE2 roles :

  • Project steering commitee
  • Project owner/executive, internal employee accountable for project benefit who’ takes overall responsability for project business case and project benefit.
  • Project user(s), who represent project users’ responsible for requirements and post-project benefit reporting
  • Project supplier(s), who represent supplier interest’ responsible for project result/output and its quality
  • Top management, who provides mandate to project owner/executive
  • Project manager, coordinate project stage implementation according to authority recieved from project steering committee or/and project owner
  • Project assurance, supports project steering committee (usually as audit function, optional)
  • Change authority, empowered by project steering commitee with limited authority to approve project changes
  • Project support, helps project manager with any day to day items where needed. High focus to quality activities. Optional role, if not existant duties are performed by project manager.
  • Team manager(s), responsible for project product implementation ( deliver project output) with focus to quality
  • Risk Owner, responsible for assigned particular risk management
  • All 7 PRINCE2 knowledge areas:

    Recommended solutions for Jira cloud:

    discussion iconPROJECS wiki helps you to understand & implement best project management practices fast & easy & cost-efficient

    discussion iconCreated by : Artūras Bučinskas, PRINCE2 Practitioner