PM² Project Management Methodology Guide 3.1 PDF
Document Details
Uploaded by Deleted User
2023
Tags
Summary
This document is a guide to the PM² project management methodology, version 3.1. It covers project initiation, planning, execution, monitoring, and closing. The guide is aimed at professionals in project management.
Full Transcript
Project Management Methodology Guide 3.1 European Commission Centre of Excellence in Project Management (CoEPM²) PM² Project Management Methodology Guide 3.1 Brussels | Luxembourg, 2023 N...
Project Management Methodology Guide 3.1 European Commission Centre of Excellence in Project Management (CoEPM²) PM² Project Management Methodology Guide 3.1 Brussels | Luxembourg, 2023 Neither the European Commission nor any person acting on behalf of the Commission is responsible for the use which might be made of the following information. Europe Direct is a service to help you find answers to your questions about the European Union. Freephone number (*): 00 800 6 7 8 9 10 11 (*) The information given is free, as are most calls (though some operators, phone boxes or hotels may charge you). More information on the European Union is available on the internet (http://europa.eu). Luxembourg: Publications Office of the European Union, 2023 ISBN: 978-92-68-10314-2 doi: 10.2799/970188 © European Union, 2023 Reproduction and reuse is authorised provided the source is acknowledged. Document licensed under CC BY 4.0 license (https://creativecommons.org/licenses/by/4.0/). The Commission’s reuse policy is implemented by Commission Decision 2011/833/EU of 12 December 2011 on the reuse of Commission documents (OJ L 330, 14.12.2011, p. 39 – https://eur-lex.europa.eu/eli/dec/2011/833/oj). The PM² logo is the property of the European Union and may not be registered as a trademark or otherwise, nor used separately from these documents. Neither the publication nor the logo can be used in a way which suggests endorsement of an external organisation by the European Union. Title: The PM² Project Management Methodology Guide 3.1 Current Edition: The PM² Guide v3.1, December 2023 Previous Editions: The PM² Guide, v2.5, September 2015 The PM² Guide, Open Edition, v0.9, November 2016 The PM² Guide, v3.0, December 2018 The PM² Guide v3.0.1, March 2021 Authors and Contributors of the PM² Methodology Guide: Appendix A: Contributions and Acknowledgements Produced and published by the European Commission, DG DIGIT, Centre of Excellence in Project Management (CoEPM²) Web: https://pm2.europa.eu/index_en Email: [email protected] I The PM² Methodology Guide v3.1 Table of Contents Table of Contents 1 An Introduction to the PM² Guide................................................................................................1 1.1 Objectives.......................................................................................................................................... 1 1.2 Intended Audience............................................................................................................................ 1 1.3 About the PM² Methodology............................................................................................................ 1 1.4 The Centre of Excellence in PM² (CoEPM²)....................................................................................... 2 1.5 The Open PM² Initiative..................................................................................................................... 2 1.5.1 PM² Publications.......................................................................................................................... 3 1.5.2 Project Support Network............................................................................................................. 3 2 Project Management...................................................................................................................5 2.1 About Projects................................................................................................................................... 5 2.1.1 What is a project?........................................................................................................................ 5 2.1.2 Why we do projects..................................................................................................................... 6 2.1.3 Project outputs, outcomes, benefits............................................................................................ 6 2.2 About Project Management.............................................................................................................. 7 2.2.1 What is Project Management?..................................................................................................... 7 2.2.2 Project Documentation................................................................................................................ 7 2.2.3 The Project Support Office (PSO)................................................................................................. 7 2.2.4 Programme Management............................................................................................................ 7 2.2.5 Project Portfolio Management.................................................................................................... 7 2.2.6 Projects vs Operations................................................................................................................. 8 2.3 Project Environment.......................................................................................................................... 9 2.3.1 Project Organisation..................................................................................................................... 9 2.3.2 Developing Project Management Competences......................................................................... 9 2.3.3 Project Management Competences........................................................................................... 10 3 Overview of the PM² Methodology............................................................................................ 13 3.1 The House of PM²............................................................................................................................ 13 3.2 The PM² Lifecycle............................................................................................................................. 13 3.2.1 Initiating Phase........................................................................................................................... 14 3.2.2 Planning Phase........................................................................................................................... 15 3.2.3 Executing Phase......................................................................................................................... 15 3.2.4 Closing Phase.............................................................................................................................. 16 3.2.5 Monitor & Control...................................................................................................................... 16 3.2.6 Phase Gates and Approvals........................................................................................................ 17 3.3 PM² Phase Drivers and Key Artefacts.............................................................................................. 17 3.4 What is a PM² Project...................................................................................................................... 18 3.5 PM² Mindsets.................................................................................................................................. 19 3.6 Tailoring and Customisation............................................................................................................ 20 3.7 PM² and Agile Management............................................................................................................ 20 4 Project Organisation and Roles.................................................................................................. 23 4.1 Project Stakeholders........................................................................................................................ 23 4.2 Project Organisation: Layers and Roles........................................................................................... 23 4.3 Appropriate Governance Body (AGB).............................................................................................. 24 4.4 Project Steering Committee (PSC)................................................................................................... 24 4.5 Project Owner (PO).......................................................................................................................... 25 4.6 Solution Provider (SP)...................................................................................................................... 25 4.7 Business Manager (BM)................................................................................................................... 26 4.8 Project Manager (PM)..................................................................................................................... 26 4.9 Business Implementation Group (BIG)............................................................................................ 27 4.10 Project Core Team (PCT).................................................................................................................. 27 4.11 Project Support Team (PST)............................................................................................................. 28 4.12 RAM (RASCI) — Documenting Responsibility Assignments............................................................. 29 The PM² Methodology Guide v3.1 II II II Table of Contents 5 Initiating Phase......................................................................................................................... 31 5.1 Initiating Meeting............................................................................................................................ 31 5.2 Project Initiation Request............................................................................................................... 32 5.3 Business Case.................................................................................................................................. 34 5.4 Project Charter................................................................................................................................ 36 5.5 Phase Gate RfP (Ready for Planning).............................................................................................. 37 6 Planning Phase.......................................................................................................................... 39 6.1 Planning Kick-off Meeting............................................................................................................... 40 6.2 Project Handbook........................................................................................................................... 42 6.2.1 Project Roles & Responsibilities................................................................................................ 43 6.2.2 Project Management Plans....................................................................................................... 43 6.2.3 Project-Specific Plans................................................................................................................. 43 6.2.4 Domain-Specific Artefacts......................................................................................................... 44 6.2.5 Other.......................................................................................................................................... 44 6.3 Project Stakeholder Matrix............................................................................................................. 44 6.4 Project Work Plan........................................................................................................................... 46 6.4.1 Work Breakdown....................................................................................................................... 47 6.4.2 Effort & Cost Estimates.............................................................................................................. 47 6.4.3 Project Schedule........................................................................................................................ 47 6.5 Outsourcing Plan............................................................................................................................. 48 6.6 Deliverables Acceptance Plan......................................................................................................... 49 6.7 Transition Plan................................................................................................................................ 51 6.8 Business Implementation Plan........................................................................................................ 52 6.9 Phase Gate: RfE (Ready for Executing)............................................................................................ 53 7 Executing Phase........................................................................................................................ 55 7.1 Executing Kick-off Meeting............................................................................................................. 56 7.2 Project Coordination....................................................................................................................... 57 7.3 Quality Assurance........................................................................................................................... 58 7.4 Project Reporting............................................................................................................................ 59 7.5 Information Distribution................................................................................................................. 61 7.6 Phase Gate: RfC (Ready for Closing)............................................................................................... 62 8 Closing Phase............................................................................................................................ 63 8.1 Project-End Review Meeting........................................................................................................... 64 8.2 Lessons Learned and Post-Project Recommendations................................................................... 65 8.3 Project-End Report.......................................................................................................................... 66 8.4 Administrative Closure.................................................................................................................... 67 9 Monitor & Control..................................................................................................................... 69 9.1 Monitor Project Performance......................................................................................................... 70 9.2 Control Schedule............................................................................................................................. 71 9.3 Control Cost.................................................................................................................................... 72 9.4 Manage Stakeholders..................................................................................................................... 73 9.5 Manage Requirements.................................................................................................................... 74 9.6 Manage Project Change.................................................................................................................. 76 9.7 Manage Risk.................................................................................................................................... 78 9.8 Manage Issues and Decisions......................................................................................................... 79 9.9 Manage Quality............................................................................................................................... 80 9.10 Manage Deliverables Acceptance................................................................................................... 81 9.11 Manage Transition.......................................................................................................................... 83 9.12 Manage Business Implementation................................................................................................. 84 9.13 Manage Outsourcing....................................................................................................................... 85 III The PM² Methodology Guide v3.1 Table of Contents Appendix A: Contributions and Acknowledgements......................................................................... 87 Appendix B: Project Management Plans and Logs............................................................................ 89 B.1 Requirements Management Plan.................................................................................................... 89 B.2 Project Change Management Plan.................................................................................................. 90 B.3 Risk Management Plan.................................................................................................................... 91 B.4 Issue Management Plan.................................................................................................................. 92 B.5 Quality Management Plan............................................................................................................... 93 B.6 Communications Management Plan............................................................................................... 95 B.7 Change Log...................................................................................................................................... 96 B.8 Risk Log............................................................................................................................................ 97 B.9 Issue Log.......................................................................................................................................... 98 B.10 Decision Log..................................................................................................................................... 99 Appendix C: Project Management Tools & Techniques................................................................... 101 C.1 PESTEL Analysis.............................................................................................................................. 101 C.2 Make or Buy Analysis..................................................................................................................... 101 C.3 Stakeholder Interest/Influence Matrix (SIIM)............................................................................... 101 C.4 Risk Likelihood/Impact Matrix....................................................................................................... 101 C.5 Work Breakdown Structure (WBS)................................................................................................ 102 C.6 Deliverables Breakdown Structure (DBS)...................................................................................... 102 C.7 Effort and Cost Estimates.............................................................................................................. 102 C.8 Three-Point Estimates................................................................................................................... 102 C.9 Decision Trees................................................................................................................................ 102 C.10 Project Scheduling......................................................................................................................... 103 C.11 Resource Levelling......................................................................................................................... 103 C.12 Gantt Charts................................................................................................................................... 103 C.13 Critical Path Method (CPM)........................................................................................................... 103 C.14 Critical Chain Method (CCM)......................................................................................................... 103 C.15 Earned Value Management (EVM)................................................................................................ 104 C.16 Pareto Analysis.............................................................................................................................. 104 C.17 Lessons Learned............................................................................................................................ 104 Appendix D: PM² Extensions & Considerations............................................................................... 105 D.1 Agile, Programme, and Portfolio Management............................................................................ 105 D.2 Considerations in PM²: Sustainability, Data Protection, IT Security, UX....................................... 110 Appendix E: Additional Resources.................................................................................................. 112 E.1 PM² Artefacts & Activities Summary Tables and Diagrams................................................................. 112 E.2 Getting Started with PM² - Quick Start Tips........................................................................................ 115 E.3 Useful Online Resources...................................................................................................................... 116 Appendix F: Ethics and Conduct..................................................................................................... 118 F.1 PM² Code of Professional Conduct...................................................................................................... 118 F.2 Personal and Professional Virtues....................................................................................................... 119 Appendix G: Glossary..................................................................................................................... 122 The PM² Methodology Guide v3.1 IV IV IV 1. An Introduction to the PM² Guide 1 An Introduction to the PM² Guide 1.1 Objectives This guide sets out to provide an introduction to the PM² Project Management Methodology. It has been kept as lean as possible, while still providing enough information to allow for an effective understanding of the PM² Methodology as practitioners start to use it. 1.2 Intended Audience Entry-level Project Managers (PMs) and project teams wishing to learn more about project management and the PM² Methodology. Experienced Project Managers (PMs) and team members who wish to learn more about the PM² Methodology. Project teams that wish to start using the PM² Methodology in their projects. This guide provides: a common vocabulary (glossary) which makes it easier for project teams to communicate and apply project management concepts best practices—it is up to the Project Managers (PMs) and project teams to choose the PM² practices that will bring most value to their projects links to PM² resources (online resources, Artefact templates and examples) an introduction to other PM² models, such as PM2-Agile, PM²-PgM (for Programme Management) and PM²-PfM (for Portfolio Management). This guide can be read from beginning to end, to learn about the methodology, or it can be used as a reference, to help you as you practise PM². 1.3 About the PM² Methodology PM² is a Project Management Methodology developed by the European Commission. Its purpose is to enable Project Managers (PMs) to deliver solutions and benefits to their organisations by effectively managing the entire lifecycle of their project. PM² has been created with the needs of European Union Institutions and projects in mind, however, the best practices described in PM² are applicable to projects in any organisation. PM² is a light and easy-to-implement methodology which project teams can tailor to their specific needs. PM² is fully supported by a comprehensive training programme (including workshops and coaching sessions), online documentation and an active Community of Practice (currently only available within the European Commission and to a number of affiliate European Institutions). PM² incorporates elements from a wide range of globally accepted project management best practices, captured in standards and methodologies. Its development has also been influenced by operational experience on various projects both within European Union Institutions and external bodies. The PM² Methodology provides: a project governance structure process guidelines artefact templates guidelines for using the artefacts a set of effective mindsets. PM² improves the effectiveness of project management by: improving communication and the dissemination of information clarifying expectations as early as possible in the project lifecycle defining the project lifecycle (from Initiating to Closing) providing guidelines for project planning introducing monitor and control activities proposing management activities and outputs (plans, meetings, decisions) providing a link to agile practices. 1 The PM² Methodology Guide v3.1 1. An Introduction to the PM² Guide 1.4 The Centre of Excellence in PM² (CoEPM²) The purpose of the Centre of Excellence in PM² (CoEPM²) is to provide the European Commission and European Union Institutions with high-quality project management infrastructure, support and consulting services. The CoEPM² supports the PM² Methodology internally, coordinates an inter-institutional Project Support Network, and promotes the wider adoption and use of PM² beyond the European Union Institutions through the Open PM² initiative and the Digital Europe Programme. 1.5 The Open PM² Initiative Open PM² is a European Commission initiative, which brings the PM² Methodology and its benefits closer to its broader stakeholders and user community. The Open PM² Initiative provides European Union institutions, contractors and public administrations, as well as broader stakeholders, with open access to the PM² publications and associated resources. Its goal is to enable increased effectiveness in the management of projects, programmes, and portfolios and thus to serve the objectives of the European Union and the needs of member states and citizens. One common PM Methodology open to all EU Institutions, Member States, Contractors, and EU Citizens. Fig 1.1 Open PM² Synergies The Initiative also seeks to rectify mistakes of the past, when efforts were duplicated and divergent project management approaches were sponsored rather than promoting convergent approaches based on similarities and the common interest of the broader European community. By opening PM², the Initiative aims to enhance project management competency within Europe, leading to increased project efficiency and success. Opening PM² does this by: rationalising project management approaches across European Union Institutions and beyond establishing a common language and processes, resulting in effective project communication providing a common set of productive mindsets enabling transparency and visibility for cross-organisational project collaborations enabling better project management, leading to improved cost/effort efficiency enabling the improved monitor and control of European Union-funded projects and grants applying the European Commission decision of 12 December 2011 (2011/833/EU) on the reuse of Commission documents to promote accessibility and reuse. The PM² Methodology Guide v3.1 2 2 2 1. An Introduction to the PM² Guide 1.5.1 PM² Publications The Centre of Excellence in PM² (CoEPM²) provides a central online location for all PM² information, and resources. PM² website https://pm2.europa.eu Contact https://pm2.europa.eu/contact-us_en You can also download directly all PM² Guides from the Publications Office of the European Union. 1.5.2 Project Support Network The PM² Project Support Network is an EU Institutions wide network of Local Project Support Offices (LPSOs) which are coordinated and supported by the Centre of Excellence in PM² (CoEPM²). The PM² Project Support Network (PSN) aims to become a decentralised project management support network which provides guidance and support to PM² users on both the PM² Methodology and the effective use of project management tools & techniques more broadly. The Project Support Network: promotes the exchange and sharing of knowledge, experiences and best practices makes it possible to collect feedback to continuously improve and build on the PM² Methodology enables the Local Project Support Offices (LPSOs) to support each other as a community depends on the contributions of PM² champions (individuals and organisations). 3 The PM² Methodology Guide v3.1 This page is intentionally left blank 4 v3.1 The PM² Methodology Guide 4 4 2. Project Management 2 Project Management This section introduces basic project management concepts and provides the context for a better understanding of the PM² Methodology. 2.1 About Projects 2.1.1 What is a project? A project is a temporary organisational structure set up to create a unique product or service (output) within certain constraints such as time, cost, and quality. Temporary means that the project has a well-defined start and end. Unique output means that the project’s product or service has not been created before. It may be similar to another product, but there will always be a degree of uniqueness. A project’s output may be a product (e.g. a new application) or a service (e.g. a consulting service, a conference or a training programme). The project is defined, planned, and executed under certain external (or self-imposed) constraints. These can relate to scheduling, budgeting, quality, but also to the project’s organisational environment (e.g. risk attitude, capabilities, available capacity, etc.). Fig 2.1 Key project characteristics A successful project ends when its scope objective has been achieved and all deliverables have been produced and accepted by the organisation or person that requested the project (the client). The deliverables are then handed over to the client and the project team is disbanded. Projects are different from normal day-to-day work (operations) and are best managed with a special temporary organisational structure in order to: define the project scope and its deliverables (products or services) create a business justification for the investment (by defining the project’s value for the organisation, outlining the business context, listing alternative solutions, etc.) identify project stakeholders and define a project core team create the project plans to help guide and manage the project assign and coordinate project work to teams monitor and control the project daily (progress, changes, risks, issues, quality, etc.) hand over the deliverables and administratively close the project. Fig 2.2 A project as a transformational process which turns ideas into reality 5 The PM² Methodology Guide v3.1 2. Project Management 2.1.2 Why we do projects Every project aims to introduce a new product/service or to improve an existing one. Achieving the goal is expected to bring about benefits to the organisation (e.g. a new organisation-wide document management system can increase productivity by introducing a new way of searching, reading and filing documents). A project can also be seen as a transformational process, which turns ideas into reality. Projects may be carried out to maintain current business operations (e.g. sustain the current level of service), to transform business operations, or to improve the way of working so the organisation can be more efficient in the future. Projects start for many different reasons: In response to a client request for a new product or service. In response to a market demand or opportunity for a new product or service. In response to a change in legislation or organisational needs. In response to an audit which outlines improvements that should be made. In response to a new product or service from a competitor. To make use of a new technology. To integrate processes in the light of the merger of two or more departments or organisations. To update an existing process. To relocate to new premises. To raise awareness on a topic. To provide a proof-of-concept. To migrate information to a new document management system. To improve an existing service. 2.1.3 Project outputs, outcomes, benefits Although project teams tend to focus their efforts on producing deliverables, it should be remembered that project deliverables are merely a means to an end. The real purpose of a project is to achieve given outcomes that will yield measurable benefits. Therefore, it is important for everyone involved in managing and executing a project (managers and team members) to understand the relationship between project outputs, outcomes and benefits. They must be able to identify the outputs, outcomes and benefits of their projects. Without this understanding, the project participants can lose sight of the project’s original purpose and produce deliverables, which are of little (or no) value to the organisation. Thus: Project outputs (deliverables) are products/services, which introduce something new (a change). The change results in an outcome. The benefits are the measurable improvements resulting from this outcome. Project Outputs Outcomes Benefits Fig 2.3 Project outputs, outcomes and benefits Note that project outcomes and benefits are often realised only after the project has closed. The table below illustrates this with a simple example: Example of outputs, outcomes and benefits. Project Output Adoption of the PM² Methodology within an organisation. Increased project quality. Project Outcomes Improved visibility of project objectives, status and forecasts. Capability to have better control over contractor work and deliverables. Project cost overruns decreased by 30% Project Benefits Productivity increased by 30%. 6 v3.1 The PM² Methodology Guide 6 6 2. Project Management 2.2 About Project Management 2.2.1 What is Project Management? Project Management can be described as the activities of planning, organising, securing, monitoring and managing the resources and work necessary to deliver specific project goals and objectives in an effective and efficient way. The project management approach used should always be tailored to the needs of the project. When using PM², a Project Manager (PM) should use (and if needed after tailoring) only those parts that contribute to the effective management of their project. 2.2.2 Project Documentation Project documentation is a key activity in project management. It carries through from the start of a project to its completion. Project documentation: sharpens thinking by forcing people to put vague thoughts and plans into words crystallises planning defines the project scope for approval, ensuring that all project stakeholders and project team members share the same expectations on what is to be delivered and when provides all stakeholders with a clear picture of the project requirements facilitates communication with internal and external groups provides a baseline for monitoring and controlling a project’s progress provides a record of important decisions provides the information required by official audits supports organisational memory and acts as a historical reference, which can be used to increase the chances of success of future projects. Project documentation should of course, adhere to the quality standards of the organisation and the project regarding format, style, etc. However, above all, it should add value fulfilling its purpose and be clear and easy to understand. 2.2.3 The Project Support Office (PSO) A Project Support Office (PSO) is an organisational body (or entity) that provides services, which support project management. These can range from providing simple support functions to helping link projects to strategic goals. Not all organisations have a Project Support Office (PSO).A Project Support Office (PSO) can: offer administrative support, assistance and training to Project Managers (PMs) and other staff collect, analyse and report on project progress data and information assist with project scheduling, resource planning, coordination and Project Management Information System (PMIS) use maintain a central project repository (of Project Documents, Risks, Lessons Learned) coordinate configuration management and quality assurance activities monitor adherence to methodology guidelines and other organisational standards tailor the project management methodology to new best practices and help project teams implement the updated methodology effectively. 2.2.4 Programme Management A programme is a set of related projects and activities managed in a coordinated way to achieve strategic objectives and benefits that could not be obtained if they were managed individually. The projects within a programme all contribute to the common programme goals and are interdependent. In addition to projects, a programme often includes elements of related work (programme-level activities) outside the scope of its projects. Programme management is different from multi-project management (managing many projects in parallel). Thus, while a Programme Manager (PgM) coordinates efforts between projects, s/he does not directly manage the individual projects. 2.2.5 Project Portfolio Management A project portfolio is a collection of projects, programmes and other activities, which are grouped together to allow better control over their financial and other resources and to facilitate their effective management 7 The PM² Methodology Guide v3.1 2. Project Management in terms of meeting strategic objectives. The projects or programmes in a portfolio are not necessarily inter-dependent on inter-related. From a strategic point of view, portfolios are higher-level components than programmes and projects. It is at the portfolio level that investment decisions are made, resources allocated, and priorities identified. It is very important for people involved in project definition and management to understand the differences between—and specific management requirements of—projects, programmes and portfolios. They should also be able to define or position their work at the right level (i.e. know if their work would be better managed as a programme or a network of projects), while always being aware of the management and organisational context of their work (see Appendix D). Fig 2.4 Relationships between strategy, project, programme, portfolio and operations 2.2.6 Projects vs Operations Projects are temporary and should therefore have a definite start and end. A project should be considered complete when it is determined that its goals and objectives have been accomplished. Once this happens, the project team should be disbanded. Operations, on the other hand, comprises the ongoing day-to-day activities undertaken by a permanent organisation to deliver services or products. However, people often find themselves involved in so-called projects that have been going on for years, working with moving targets or a continuously expanded scope, which sometimes includes activities that should be classified as maintenance or operations. These are situations where the projects have been allowed to either become uncontrollable, or to move into operations (maintenance) mode. In most projects, the operations period begins after the project’s main products have been produced and accepted by the client. How do you recognise that a project has slipped into operations mode? The main project deliverables have been produced and the client has accepted them. The main project output (deliverable) is in use. Support is provided to users. Maintenance activities are undertaken. Minor updates (improvements) are planned and implemented over time. 8 v3.1 The PM² Methodology Guide 8 8 2. Project Management 2.3 Project Environment 2.3.1 Project Organisation It would be convenient to assume that all PM² Project Managers (PMs) operate within their organisations in a homogenous environment and with consistent levels of authority and responsibility. This is generally not the case, however. There are typically several ways of organising projects within an organisation, which utilise one of the following structures or a combination of them. The Functional Structure In a functional organisational structure, project work is integrated into the work performed by the permanent organisation. Project members and other resources are borrowed from multiple sections of the functional organisation. The Project Manager (PM) tends to have limited authority and needs to involve senior management in the management of important project issues. Project work is often viewed as having lower priority than everyday work. The Projectized Structure On the other end of the spectrum, in a projectized organisation, there is only a basic permanent (functional) hierarchy, and all work is organised and performed within temporary project organisations. Project resources are brought together specifically for the purpose of a project and work more or less exclusively for the project. At the end of the project, resources are either reassigned to another project or returned to a resource pool. The Matrix Structure A matrix organisation is a blended organisational structure. Additional temporary project organisations are created alongside the functional hierarchy to achieve specific project goals and work. The role of the Project Manager (PM) is recognised as central and key to the project’s success, and the Project Steering Committee (PSC) typically delegates enough authority and responsibility to the Project Manager (PM) and the Business Manager (BM) for them to manage the project and its resources. Matrix organisations can be further categorised as weak, balanced and strong matrix organisations, the difference being the level of authority and autonomy given to the project organisation. 2.3.2 Developing Project Management Competences Project management involves much more than creating schedules and budgets, and Project Managers (PMs) must have a wide range of technical and behavioural skills at their disposal. To develop the competences required to manage projects effectively. Project Managers (PMs) need to: understand how projects are handled within the organisation (talk to colleagues) review any project methodologies, standards and frameworks that exist in the organisation follow a project management course (e.g. a course offered by a recognised PM2 training provider) reflect on their project management—what is successful, what could be improved? become an active member of the PM² Community—participate in forum discussions and learn from questions asked by other Project Managers (PMs) talk to more experienced Project Managers (PMs) about how they run their projects. It is up to the Project Manager (PM) to acquire these skills and invest in their project management skills set. Project management knowledge comes from study and practice, from discussing, sharing experiences and reflecting on what went well and what can be improved. 9 The PM² Methodology Guide v3.1 2. Project Management Fig 2.5 What Project Managers (PMs) need to understand. 2.3.3 Project Management Competences Project Managers (PMs) need to: understand the project management methodology used in their organisation (e.g. PM²) have the technical competences required to effectively manage the initiation, planning, execution, monitoring, controlling, and closing of a project. On top of this, the role requires skills to work effectively with people and within the broader organisational context. These include the contextual and behavioural skills necessary to manage complex projects with diverse teams and stakeholder groups that have pluralistic and conflicting priorities. Project Managers (PMs) thus also need to know/understand: how to communicate, lead, motivate, negotiate, solve problems and deal with issues, conduct meetings and workshops, report project status, etc. the business context and the general project environment (i.e. sociocultural, political, physical, etc.) organisational policies and standards (e.g. security, organisational architecture, audits, etc.) how the end-product or service will be maintained after it is delivered. Additionally, subject-specific knowledge (e.g. IT, policy, etc.) is often relevant and useful to a Project Manager’s (PM) role. Most, if not all, of the above-mentioned points are also required of Business Managers (BM). The table below lists the main competences for Projects Managers (PMs) and Business Managers (BMs): People Competences Perspective Competences Self-reflection and self-management Strategy Personal integrity and reliability Governance, structures and processes Personal communication Compliance, standards and regulations Relationships and engagement Power and interest Leadership Change and transformation Teamwork Culture and values Conflict and crisis management Resourcefulness Negotiation Results orientation Source: IPMA-ICB (adapted) 10v3.1 The PM² Methodology Guide 10 10 2. Project Management The above competences may not necessarily be independent and each can have an impact on others. However, the filter that determines what is more important (e.g. self or common interest, time or quality, results or balance, etc.) lies in our values and ethics. Therefore, competences related to the appreciation of values and ethics have a prominent position compared to the rest because it is our ethical profile that guides us on how we should apply our competencies, and determines what we consider good or bad, right or wrong, in any given situation, decision and action. Note that Project Managers (PMs) and Business Managers (BMs) should demonstrate these competencies effectively, consistently and appropriately to the given situation, while remaining aligned with organisational and professional values and ethics. The aim is to achieve the project goals by making (and acting on) the right decisions, at the right time, in the right way and for the right reasons. This can be a challenge for Project Managers (PMs), who often face tensions between making decisions based on goals and values, and meeting the needs of various stakeholders. Such decisions and tensions become easier to manage when Project Managers (PMs) have developed an ethical disposition, which involves the balancing of goals and skills, personal integrity and moral virtue. Although all virtues (logical and moral) affect all competences, the virtues of judgment, prudence and insightfulness are (comparatively) more related to demonstrating the perspective competencies, while the moral virtues of honesty, fairness, friendliness, generosity, temperance, courage, humour, and magnanimity and magnificence, are (comparatively) more related to demonstrating people competences (see Appendix F). 11 The PM² Methodology Guide v3.1 This page is intentionally left blank 12v3.1 The PM² Methodology Guide 12 12 3. Overview of the PM² Methodology 3 Overview of the PM² Methodology 3.1 The House of PM² The PM² Methodology is built on Project Management best practices and is supported by four pillars: 1. a project governance model (i.e. Roles & Responsibilities) 2. a project lifecycle (i.e. Project Phases) 3. a set of processes (i.e. project management activities) 4. a set of project Artefacts (i.e. documentation templates and guidelines). Fig 3.1 The House of PM² The spirit of the PM² Methodology is further defined by the PM² Mindsets, which provide the glue that holds together the PM² practices and provide a common set of beliefs and values for PM² project teams. 3.2 The PM² Lifecycle The PM² project lifecycle has four sequential and non-overlapping phases with a different type of activity predominant in each phase (i.e. initiating activities are predominant in the Initiating Phase, etc.). However, while phase-related activities peak in terms of effort during a specific phase, activities of this type can also be executed during neighbouring phase(s) (e.g. planning activities are also repeated in the Executing Phase). A project moves on to the next phase when the goals of its current phase have been deemed achieved as the results of a formal (or less formal) phase-exit review. Fig 3.2 The PM² project lifecycle: indicative overlap of phase activities and cumulative effort 13 The PM² Methodology Guide v3.1 3. Overview of the PM² Methodology The focus of a project shifts from initiating and planning activities in the beginning to executing, monitoring and controlling activities in the middle and acceptance, transitioning and closing activities at the end. Inexperienced project teams sometimes underestimate the importance of the work done in the initial project phases and start working on deliverables that are inadequately defined or planned. This results in the delivery of outputs, which are of poor quality and of little value to end-users. This is a common and costly mistake, which is often the root cause of overall project failure and the failure to realise the project’s intended benefits. It is therefore important to invest adequate time during the Initiating Phase to define the desired outcomes by engaging a broad spectrum of stakeholders. Project Phase Description 1. Initiating Define the desired outcomes. Create a Business Case. Define the project scope. Get the project off to a good start. 2. Planning Assign the Project Core Team (PCT). Elaborate the project scope. Plan the work. 3. Executing Coordinate the execution of project plans. Produce deliverables. Coordinate formal acceptance of the project. Report on project performance. 4. Closing Capture Lessons Learned and post-project recommendations. Close the project administratively. Monitor Oversee all project work and management activities over the duration of the project: & monitor project performance, measure progress, manage changes, address risks and Control issues, identify corrective actions etc. 3.2.1 Initiating Phase Initiating Planning Executing Closing Monitor & Control The first phase of a PM² project is the Initiating Phase. During this phase, the people involved formulate the project’s objective(s), ensure the project’s alignment to the organisation’s strategic objectives, undertake some initial planning to get the project off to a good start, and put together the information required to gain approval to continue to the Planning Phase. The main input of this phase is a (client) request to address a need, problem or opportunity. The following activities are part of the Initiating Phase: Creation of the Project Initiation Request which contains information about the requestor, business needs and the desired project outcomes. Creation of the Business Case, which provides a business justification, defines the project’s budgetary requirements, and outlines the business context, problem and project descriptions, alternative solutions, and a high-level roadmap. Creation of the Project Charter, which provides more details on the project definition in terms of scope, cost, time and risk. It also defines milestones, deliverables, project organisation, etc. Fig 3.3 Overview of the Initiating Phase The Business Case and Project Charter define the project’s scope and direction. The Project Manager (PM) and the Project Core Team (PCT) reference and use both throughout the project. At the end of the Initiating Phase, the Project Steering Committee (PSC) or other Appropriate Governance Body (AGB) reviews the above documents and decides whether to allow the project to move forward. 14v3.1 The PM² Methodology Guide 14 14 3. Overview of the PM² Methodology 3.2.2 Planning Phase Initiating Planning Executing Closing Monitor & Control The second phase of a PM² project is the Planning Phase. During the Planning Phase, the project’s objective is developed into a specific and workable plan ready to be executed. The Project Work Plan specifies the project scope and appropriate approach, decides on a schedule for the tasks involved, estimates the necessary resources and develops the detail of the project plans. Several times during the Planning Phase, the Project Work Plan can be updated. Once agreed and finalised it is baselined and signed off. The following activities are part of the Planning Phase: Running the Planning Kick-off Meeting to officially start the Planning Phase. Creating the Project Handbook, which defines the project’s management approach. Developing the Project Work Plan (Work Breakdown, Effort and Costs, Schedule). Updating the Project Stakeholder Matrix, which identifies all project stakeholders. Creating other important plans such as the Communications Management Plan, the Transition Plan and the Business Implementation Plan. Fig 3.4 Overview of the Planning Phase The Project Manager (PM) uses the outputs of the Planning Phase to request approval to move on to the Executing Phase. This decision to move on is taken by the Project Steering Committee (PSC). 3.2.3 Executing Phase Initiating Planning Executing Closing Monitor & Control The third phase of a PM² project is the Executing Phase. During the Executing Phase the project team produces the project deliverables (outputs) as outlined in the Project Work Plan. This is typically the stage of the project lifecycle that involves the most resources and requires the most monitoring. The following activities are part of the Executing Phase: Running the Executing Kick-off Meeting. Distributing information based on the Communications Management Plan. Performing Quality Assurance (QA) activities as defined in the Quality Management Plan Coordinating project, work people and resources, and resolving conflicts and issues. Producing the project deliverables in accordance with the project plans. Handing over the deliverables as described in the Deliverables Acceptance Plan. 15 The PM² Methodology Guide v3.1 3. Overview of the PM² Methodology Fig 3.5 Overview of the Executing Phase Once the project deliverables have been accepted by the Project Owner (PO), the Project Manager (PM) can request approval to move on to the Closing Phase. This decision to move on is taken by the Project Steering Committee (PSC). 3.2.4 Closing Phase Initiating Planning Executing Closing Monitor & Control The final phase of a PM² project is the Closing Phase. During a project’s Closing Phase, the finished deliverables are officially transferred into the care, custody and control of the Project Owner (PO) and the project is administratively closed. Information on overall project performance and Lessons Learned is captured in the Project-End Report. The Project Manager (PM) ensures that the deliverables produced are accepted, all project documents are correctly filed and archived, and that all resources used by the project are formally released. The following activities are part of the Closing Phase: Finalising all activities in order to formally close the project. Discussing the overall project experience and Lessons Learned with the project team. Documenting Lessons Learned and best practices for future projects. Closing the project administratively and archiving all project documents. Fig 3.6 Overview of the Closing Phase 3.2.5 Monitor & Control Initiating Planning Executing Closing Monitor & Control Monitor & Control activities run throughout the project’s lifecycle. During Monitor & Control, all work is observed from the point of view of the Project Manager (PM). Monitoring is about measuring ongoing activities and assessing project performance against project plans. Controlling is about identifying and taking corrective action to address deviations from plans and to address issues and risks. 16v3.1 The PM² Methodology Guide 16 16 3. Overview of the PM² Methodology Fig 3.7 Monitor & Control activities 3.2.6 Phase Gates and Approvals At the end of each phase, the project passes through a review and approval gate. This ensures that the project is reviewed by the appropriate people (i.e. the Project Manager (PM), Project Owner (PO), the Project Steering Committee (PSC) or other delegated role) before it moves on to the next phase. These checkpoints contribute to the overall project management quality and allow the project to proceed in a more controlled way. The three PM² phase gates are: RfP (Ready for Planning): at the end of the Initiating Phase RfE (Ready for Executing): at the end of the Planning Phase RfC (Ready for Closing): at the end of the Executing Phase. 3.3 PM² Phase Drivers and Key Artefacts Projects depend on people to define, plan and execute them. These project drivers change from phase to phase in a PM² project. During the Initiating Phase, the Project Owner (PO) is the main driver, initiating the project and being accountable for all documentation. In the Planning Phase, the main driver is the Project Manager (PM), who is responsible for coordinating the delivery of all project plans. The carrying out of the Project Work Plan and creation of the project deliverables in the Executing Phase is driven by the Project Core Team (PCT). Finally, the Closing Phase is driven by the stakeholders who evaluate the project’s overall performance. 17 The PM² Methodology Guide v3.1 3. Overview of the PM² Methodology Fig 3.8 PM² Swimlane Diagram Key Phase Input/Output Description Formalises the commitment to explore a problem, need or Project Initiation Request opportunity further and captures the context. Captures the reasoning behind the project, provides justification and Business Case establishes the budgetary constraints. Builds on the Business Case and defines the project scope, high-level Project Charter requirements and deliverables. Presents the project management objectives and overall management Project Handbook approach. Documents the roles & responsibilities. Includes a breakdown of the work to be carried out, estimates of the Project Work Plan effort and costs involved, and the project schedule. Lists the complete set of project deliverables as defined in the Project Project Deliverables Charter and Project Work Plan. Summarises the project experience, project performance and Lessons Project-End Report Learned (successful project practices and potential pitfalls). 3.4 What is a PM² Project Many PM² best practices can be applied to any type of project or work activity. However, to be able to apply the whole PM² Methodology, a project must have certain characteristics. Thus, a PM² project: is (above all) a project (i.e. not operations, not a work activity, not a programme, etc.) has a duration of more than 4–5 weeks and involves more than 2–3 people runs within an organisation and can be subject to internal or external audits requires a clearly defined governance structure and clearly assigned roles and responsibilities requires approval of its budget and scope includes more than just construction/delivery activities includes transition and business implementation activities requires a certain level of documentation, transparency and reporting requires a certain level of control and traceability has a broad base of internal (and external) stakeholders may require the collaboration of several organisations or organisational units contributes to raising the organisation’s project management maturity. 18v3.1 The PM² Methodology Guide 18 18 3. Overview of the PM² Methodology The number of the above characteristics, apparent in a project, drive the tailoring and customization that will have to be applied to the PM2 methodology. 3.5 PM² Mindsets The PM² processes, artefacts, tools and techniques help project teams make decisions on trade-offs between a project’s time, cost, scope and quality dimensions. The PM² Mindsets are the attitudes and behaviours that help project teams focus on what is crucial to achieving their project’s goals. They help project teams navigate the complexities of managing projects in organisations and make the PM² Methodology both more effective and complete. Thus, Project Managers (PMs) and project teams that practise PM²: 1. Apply PM² best practices to manage their projects. 2. Remain mindful that project management methodologies are there to serve projects and not the other way around. 3. Maintain an outcomes orientation in relation to all projects and project management activities. 4. Are committed to delivering project results with maximum value rather than just following plans. 5. Foster a project culture of collaboration, clear communication and accountability. 6. Assign project roles to the most appropriate people for the benefit of the project. 7. Balance in the most productive way the often-conflicting project management “Ps” of product, purpose, process, plan, planet, people, pleasure/pain, participation, perception and politics. 8. Invest in developing technical and behavioural competences to become better project contributors. 9. Involve project stakeholders in the organisational change needed to maximise project benefits. 10. Share knowledge, actively manage Lessons Learned, and contribute to the improvement of project management within their organisations. 11. Draw inspiration from the PM² Guidelines on Ethics and Professional Virtues (see Appendix F). To remain mindful of the PM² Mindsets, Project Managers (PMs) and project teams that practise PM² should ask themselves the following important Infrequently Asked Questions (IAQs): Do we know what we are doing? Tip: Develop a clear and shared project vision. Manage the project using a holistic approach and optimise the whole project, not just parts of it. Follow a process but stay Agile and try to regularly remind yourself why you are doing something. Do we know why we are doing it? Does anyone really care? Tip: Make sure your project matters. Understand its goals, value and impact, and how it relates to the organisational strategy. Define upfront what project success is and deliver maximum value and real benefits, not just outputs. Are the right people involved? Tip: People make projects work. The primary criterion for involving people and assigning project roles should be to serve the needs and objectives of the project, and not politics, friendship, functional hierarchy, proximity or convenience. Do we know who is doing what? Tip: Know what you should be doing, and make sure others know what they should be doing. Is it clear to everyone? Clearly define and understand roles, responsibilities and accountabilities. Deliver at any cost or risk? Tip: Show respect for people’s work and organisational funds and avoid high-risk behaviour and tactics. Always keep in mind that it is not just about the end result - how you get there also matters. Manage your projects based on positive values and principles. Is this important? Tip: Everything is NOT equally important. Identify, and agree on, the project’s Critical Success Criteria (CSC), Minimum Viable Product (MVP), and Critical Success Factors (CSFs), and allocate effort and attention both tactically and strategically for the benefit of both the project and project management goals. Is this a task for “them” or for “us”? Tip: Make sure that client and provider groups work as one team towards a common goal. Real teamwork really works; so foster clear, effective and frequent communication. Should I be involved? Tip: Contribute from any position. Be proud of the skills, value and positive attitude you bring to the project. Help everyone who needs to be involved get involved. Promote and facilitate the contributions of all stakeholders. 19 The PM² Methodology Guide v3.1 3. Overview of the PM² Methodology Have we improved? Tip: Commit to ongoing self- and organisational improvement by gathering and sharing knowledge. Project teams should reflect on how they can become more effective and adjust their behaviour accordingly. Is there life after the project? Tip: The product (or service) lifecycle has just begun! Make sure you have contributed to its success. The PM² Mindsets are the glue that holds the PM² processes and practices together. They provide a common set of beliefs and values for all PM² practitioners. The PM² Mindsets: help project teams navigate through the complexities of project realities. help project teams (re)position project management goals in a wider organisational context. remind project teams what is important for project success. are useful reminders of effective attitudes and behaviours. 3.6 Tailoring and Customisation To ensure that the PM² Methodology effectively serves an organisation’s and a project’s needs, some level of tailoring or/and customisation may be required. Tailoring refers to changing specific parts of the methodology, such as process steps, the content of artefacts, the distribution of responsibilities amongst the various roles, etc. Organisations do this to adapt the methodology to the specific needs of their structure and culture, and to align the methodology to organisational processes, policies, etc. Tailoring makes more sense at the organisation/departmental level, but some tailoring can also take place at the project level, based, for instance, on the complexity, size or type of a project. In addition to any tailoring, further customisation may also be required at the project level to reflect the project’s specific management needs. Examples of such customisations are the definition of decision thresholds for escalation, risk tolerances based on the risk appetite of the stakeholders, etc. All tailoring and customisations should be documented in the Project Handbook. The following guidelines should be considered when tailoring or customising the PM² Methodology: First, understand the purpose and value of the methodology element to be tailored, and then proceed with its tailoring. Avoid simplifying the methodology by eliminating whole chunks (e.g. a phase, a role, an activity or an artefact), but rather scale down (or up) the scope of that element. Balance the level of control a project needs against the extra effort such control requires. Eliminate waste (lean approach) but remain aligned with the spirit of the PM² Methodology as this is reflected by its four pillars and mindsets. Remember that the methodology was designed as an integrated whole, so avoid unnecessary deviations. 3.7 PM² and Agile Management PM² recognises the complex and uncertain nature of many types of project and the positive contribution of the Agile way of thinking to their effective management. Agile approaches meet various challenges, which often grow with the size of the organisations in which they are applied. These challenges may include coordination between Agile and non-Agile teams, compliance with various organisational governance and audit requirements, and organisational architecture and interoperability constraints. What is Agile? Agile is an approach to managing projects based on a specific set of principles and practices, which promote adaptive planning, evolutionary development, early incremental delivery and continuous improvement. It encourages rapid and flexible responses to change. Agile takes into account the inherent uncertainty of the project environment and creates an organisation that is highly adaptive. It uses short feedback loops to allow for rapid responses to changes in product requirements and for ongoing improvements to processes. 20v3.1 The PM² Methodology Guide 20 20 3. Overview of the PM² Methodology Agile’s key characteristics are: a focus on delivering value early on and frequently throughout a project decisions made based on what is known close cooperation among all parties involved continuous stakeholder involvement at all levels involving team members in planning incremental development with short cycles scope management through the continuous (re)prioritisation of tasks embracing change, continuous learning and improvement just enough documentation and control. PM² provides a structure that helps Agile teams achieve the desired agility while still accommodating tight procurement and audit requirements, good coordination with programme and portfolio levels, and collaboration with other projects, contractors, other organisational units and external organisations (see Appendix D). 21 The PM² Methodology Guide v3.1 This page is intentionally left blank 22v3.1 The PM² Methodology Guide 22 22 4. Project Organisation and Roles 4 Project Organisation and Roles 4.1 Project Stakeholders Project stakeholders are people (or groups) who can affect, be affected by, or believe to be affected by the activities carried out during a project’s lifecycle and/or by its output(s) and outcome(s). Stakeholders can be directly involved in a project’s work, members of other internal organisations or external to the organisation (e.g. contractors, suppliers, users or the general public). The number of stakeholders depends on the complexity and scope of a project. However, the more people the project has an impact on, the more likely it is that it will affect people who have some power or influence over the project. Given that stakeholders can be useful supporters of the project or may choose to block it, the effective management and involvement of them is crucial for its success. 4.2 Project Organisation: Layers and Roles The diagram below provides an overview of the layers and main roles in project organisation from a project management point of view. Fig 4.1 Project organisation Note that there is only one project team, which is composed of the people assuming the roles defined in the Performing, Managing and Directing layers. For the project to succeed, these people need to work together as a team. Business Governing Layer The Business Governing Layer determines the vision and strategy for the organisation as a whole. It consists of one or more management committees operating at a high or the highest management level. It is here that priorities are defined, investment decisions are made, and resources are allocated. Steering Layer The Steering Layer provides general project direction and guidance. It keeps the project focused on its objectives. It reports to the Appropriate Governance Body (AGB). The Steering Layer is composed of the roles defined in the Directing and Management Layers plus other optional roles. Directing Layer The Directing Layer champions the project and owns its Business Case. It mobilises the necessary resources and monitors the project’s performance in order to realise the project’s objectives. The Directing Layer comprises the roles of Project Owner (PO) and Solution Provider (SP). 23 The PM² Methodology Guide v3.1 4. Project Organisation and Roles Managing Layer The Managing Layer focuses on day-to-day project management. It organises, monitors and controls work to produce the intended deliverables and implement them in the business organisation. Members of the Managing Layer report to the Directing Layer. The Managing Layer comprises the roles of Business Manager (BM) and Project Manager (PM). It is of utmost importance for the success of the project that there is close collaboration and good communication between these two roles. Performing Layer The Performing Layer carries out the project work. It produces the deliverables and implements them in the business organisation. Members of the Performing Layer report to the Managing Layer. The Performing Layer comprises the roles of the Business Implementation Group (BIG) and the Project Core Team (PCT). 4.3 Appropriate Governance Body (AGB) The Appropriate Governance Body (AGB) is the entity responsible for the strategic planning and portfolio management. In terms of projects, this is the body with the authority to approve a project, agree its stated objective and release the funding required to implement it. As a key decision-making body, this role comprises members from the requestor and provider side of the project. Responsibilities: Defines the corporate and business domain strategy. Agrees to and implements a portfolio management framework to achieve the strategic objectives. Identifies, evaluates and authorises programmes and projects for implementation. Monitors and controls portfolio delivery performance. Optimises and manages portfolio resources and benefits. 4.4 Project Steering Committee (PSC) The Project Steering Committee (PSC) comprises at least the four roles in the Managing and Directing Layers, providing a balanced mix of requestor- and provider-side representatives. Other roles can also participate as per the project’s needs. Fig 4.2 The Project Steering Committee (PSC): Permanent and indicative optional roles The Project Steering Committee (PSC) is chaired by the Project Owner (PO) and is the key decision-making and issue-resolution body for the project. Any significant decisions that may affect the project or the team’s ability to deliver on the objectives will be escalated to the Project Steering Committee (PSC). Approval of key documents, resolution of important project issues or significant change requests will be discussed and decided upon here. 24v3.1 The PM² Methodology Guide 24 24 4. Project Organisation and Roles Responsibilities: Champions the project and raises awareness of it at a senior level. Guides and promotes the successful execution of the project at a strategic level, keeping the project focused on its objectives. Ensures adherence to the organisation’s policies and rules (e.g. IT governance, data protection, information security, document management, etc.). Provides high-level monitoring and control of the project. Authorises transition between Phases unless this is performed by the Appropriate Governance Body (AGB). Authorises deviations and scope changes with a high project impact and has the final say on decisions. Deals with escalated issues and conflicts. Approves key project artefacts (e.g. Project Charter, Project Work Plan). Optional Project Steering Committee (PSC) members: People with other roles can also participate in the Project Steering Committee (PSC) as per the project’s needs. Some indicative roles are listed in the table below. Roles Description Represents the interests of the project’s users, ensuring that User Representative (UR) project deliverables are fit-for-purpose. Contractor’s Project Manager (CPM) Responsible for the outsourced parts of the project. Architecture Office (AO) Plays an advisory role on architectural aspects of IT projects. Administers Project Steering Committee (PSC) meetings and Project Support Office (PSO) project documentation. Produces consolidated reports for large projects. Project Quality Assurance (PQA) Responsible for quality assurance and auditing. Ensures the coherent implementation of document Document Management Officer (DMO) management roles. Data Protection Coordinator (DPC) Consults and advises on data protection issues. Local Information Security Officer (LISO) Consults and advises on security issues. 4.5 Project Owner (PO) The Project Owner (PO) is the client of the project, and as such sets the business objectives and ensures that project outcomes are in line with business objectives and priorities. As the key Directing Layer role from the requestor side, the Project Owner (PO) is accountable for the overall project’s success, and later becomes the owner of the project’s outputs (product or service). Responsibilities: Acts as the project champion, promoting the project’s success. Chairs the Project Steering Committee (PSC). Provides leadership and strategic direction to the Business Manager (BM) and Project Manager (PM). Sets the business objectives and accepts the Business Case for the project. Owns the business risks and ensures that project outcomes are in line with business objectives and priorities. Mobilises the resources necessary for the project, in accordance with the agreed budget. Regularly monitors project progress. Coordinates the resolution of escalated issues and conflicts. Drives organisational change and monitors proper evolution and change implementation. Approves key project artefacts (Business Case, Project Charter, Project Handbook, Work Plan, Deliverables Acceptance Plan, Transition Plan, Business Implementation Plan). 4.6 Solution Provider (SP) The Solution Provider (SP) assumes overall accountability for project deliverables and represents the interests of those who design, manage and implement (or outsource) the project’s deliverables. 25 The PM² Methodology Guide v3.1 4. Project Organisation and Roles As the key Directing Layer role from the provider side, the Solution Provider (SP) usually has a management position in the functional hierarchy of the organisation undertaking the project, and therefore often works with the Project Owner (PO) in defining the project’s business objectives. Responsibilities: Assumes overall accountability for the project deliverables and services requested by the Project Owner (PO). Mobilises the required resources from the provider side and appoints the Project Manager (PM). Approves the objectives of any outsourced activities and deliverables and becomes accountable for the contractor’s performance. 4.7 Business Manager (BM) The Business Manager (BM) represents the Project Owner (PO) on a daily basis within the project and helps in defining the project’s business objectives via the Project Initiation Request, Business Case and Business Implementation Plan. The Business Manager (BM) collaborates closely with the Project Manager (PM) and coordinates client-side activities and roles (e.g. user and business representatives), ensuring that the project’s deliverables fulfil the business and user needs. Responsibilities: Guarantees cooperation and an efficient communication channel with the Project Manager (PM). Coordinates the Business Implementation Group (BIG) and acts as a liaison between the User Representatives (URs) and the provider organisation. Ensures that the products delivered by the project fulfil the user’s needs. Manages the activities on the business side of the project and ensures that the required business resources are made available. Decides on the best way to introduce business change or re-engineering actions, when needed. Ensures that the business organisation is ready to accommodate the project’s deliverables when they are made available by the Solution Provider (SP). Leads the implementation of the business changes within the user community. Coordinates the schedule and delivery of any user training (and production of related material). 4.8 Project Manager (PM) The Project Manager (PM) oversees the project on a daily basis and is responsible for delivering high- quality results within the identified objectives and constraints, ensuring the effective use of the allocated resources. More widely, the Project Manager’s (PM) responsibility also includes risk and issue management, project communication and stakeholder management. Responsibilities: Executes the project plans as approved by the Project Steering Committee (PSC). Coordinates the Project Core Team (PCT), ensuring the effective use of the allocated resources. Ensures that project objectives are achieved within the identified constraints, taking preventive or corrective measures where necessary. Manages stakeholder expectations. Oversees the creation of all management artefacts (except the Project Initiation Request, Business Case and Business Implementation Plan) and secures approval from the Project Owner (PO) or the Project Steering Committee (PSC). Ensures the controlled evolution, of products delivered, through proper change management. Performs risk management activities for project-related risks. Monitors project status and reports to the Project Steering Committee (PSC) on project progress at regular predefined intervals. Escalates unresolvable project issues to the Project Steering Committee (PSC). Liaises between the Directing and Performing Layers of the project. 26v3.1 The PM² Methodology Guide 26 26 4. Project Organisation and Roles 4.9 Business Implementation Group (BIG) The Business Implementation Group (BIG) sits on the requestor side and consists of representatives of business and user groups. Coordinated by the Business Manager (BM), it is responsible for planning and implementing the business changes that need to be made for the organisation to effectively integrate the project deliverables into its everyday work. Responsibilities: Analyses the impact of the project’s implementation on ongoing operations, existing business processes, staff and organisational culture. Participates in the design and updating of affected business processes. Prepares the affected business area for the upcoming change. Advises the Business Manager (BM) on the organisation’s readiness for change. Embeds the project deliverables into business operations and implements the organisational change activities that fall within the project’s scope. User Representatives (URs) User Representatives (URs) represent the interests of the project’s end-users and are part of the Business Implementation Group (BIG). It is important to designate User Representatives (URs) and involve them throughout the project, keep them up to date with developments and provide them with a sense of ownership. User Representatives (URs) help define project requirements and validate them at regular intervals, ensuring that the final deliverables are fit for the business purpose. Responsibilities: Help define the business needs and requirements. Ensure that the project specifications and deliverables meet the needs of all users. Review the project specification and acceptance criteria on behalf of the users. Communicate and prioritise user opinions in the Project Steering Committee (PSC) and ensure that these opinions are taken into consideration when decisions are made whether or not to implement a proposed change. Participate in demonstrations and pilot phases as needed. Perform user acceptance tests. Sign off on user-related documents (requirements document, deliverable acceptance testing, etc.). Guarantee business stability during the transition towards the new operational state. 4.10 Project Core Team (PCT) The Project Core Team (PCT) comprises the specialist roles responsible for creating the project deliverables. Its composition and structure depend on the project size and type (e.g. IT project, policy development project, etc.) and is defined by the Project Manager (PM) based on the project’s needs. Responsibilities: Coordinated by the Project Manager (PM), the Project Core Team (PCT): Participates in developing the project scope and planning project activities. Carries out project activities based on the Project Work Plan and schedule. Produces project deliverables. Provides the Project Manager (PM) with information on the progress of activities. Participates in project meetings as needed and helps resolve issues. Participates in the Project-End Review Meeting during the collection of Lessons Learned. Aside from the specialist roles that create the project deliverables, there are two specific Project Core Team (PCT) roles that deserve to be discussed in more detail from a project management point of view: the Contractor’s Project Manager (CPM) and the Project Manager Assistant (PMA). Contractor’s Project Manager (CPM) The Contractor’s Project Manager (CPM) leads the contractor’s staff working on the project, planning controlling and reporting on the production of outsourced deliverables. Working closely with the Project Manager (PM), the Contractor’s Project Manager (CPM) ensures that all work is carried out on time and to the agreed standards, guaranteeing the successful completion and delivery of subcontracted activities. 27 The PM² Methodology Guide v3.1 4. Project Organisation and Roles Project Management Assistant (PMA) For large projects, the Project Manager (PM) might find it useful to delegate some management tasks to an assistant. This Project Management Assistant (PMA) can work on a range of coordination and supportive tasks as assigned by the Project Manager (PM), and acts as the Project Manager’s (PM) backup in meetings, etc. However, the Project Manager (PM) remains the person responsible for all project management tasks and deliverables. The Project Management Assistant (PMA) may also be part of a Project Support Team (PST) and assigned to the project. 4.11 Project Support Team (PST) The Project Support Team (PST) is an optional role that consists of the people responsible for providing support to the project. Its composition and structure depend on the needs of the project. The Project Support Team (PST) is often composed of representatives from various horizontal services or units. Responsibilities: Provides administrative support to the project. Defines requirements for reporting and communication. Administers Project Steering Committee (PSC) meetings and drafts related reports. Supports the Project Manager (PM) in planning, monitoring and controlling the project. Advises on project management tools and administrative services. Manages the project documentation (versioning, archiving, etc.). Project Support Office (PSO) The Project Support Office (PSO), also called Project Management Office or Project Office, is an optional structure that can provide services to project teams such as the application of the methodology and use of the artefacts, information systems, governance, logistics and various support. Project Quality Assurance (PQA) Assigned by the Project Steering Committee (PSC) and working independently of the Project Manager (PM), the Project Quality Assurance (PQA) ensures the high quality of the project and its deliverables, by reviewing processes and artefacts, identifying non-conformities with the set quality standards and recommending corrective actions. This is an optional role in an organisation, reporting directly to the Project Steering Committee (PSC), and may take the form of either a group or individual staff member. Other Depending on the project’s nature and characteristics, the Project Support Team (PST) can be further extended and include representatives from other departments/units, e.g. Legal, Procurement, Data Protection, etc. 28v3.1 The PM² Methodology Guide 28 28 4. Project Organisation an
