OpenProject is the leading open source project management software for product, project and portfolio management. A powerful Jira alternative with agile planning, issue tracking, roadmaps, Gantt charts, time tracking, collaboration features, and more. Available on premises or in the cloud. ⭐ Star us on GitHub
Ruby agile-developmentangularbcfboardsbug-trackerganttgantt-chartifcissue-trackerjira-alternativekanbanopenprojectproduct-managementproject-managementproject-planningroadmaprubyscrumtimelineworkflows
harmonising pm2 documentation and use case (#20554)
Maya Berdygylyjovac63ceb3c95c2
diff --git a/docs/project-management-guide/1-introduction/README.md b/docs/project-management-guide/1-introduction/README.mdindex b6b43d2e8f2..dd848c9b43e 100644--- a/docs/project-management-guide/1-introduction/README.md+++ b/docs/project-management-guide/1-introduction/README.md@@ -1,18 +1,18 @@---sidebar_navigation:- title: 1 An Introduction to the PM² Guide - OpenProject+ title: 1 Introductionpriority: 999description: Explains the purpose and audience of the PM² methodology. It introduces PM² as a light, practical, and adaptable approach suitable for various project types, developed by the European Commission. It outlines the structure of the guide and how to use it.keywords: user guide----# 1 An Introduction to the PM² Guide+# 1 An introduction to the PM² guide## 1.1 ObjectivesThis 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+## 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.@@ -23,11 +23,11 @@ This guide sets out to provide an introduction to the PM² Project Management Me- 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).+- an introduction to other PM² models, such as PM²-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+## 1.3 About the PM² methodologyPM² 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).@@ -51,11 +51,11 @@ PM² incorporates elements from a wide range of globally accepted project manage- proposing management activities and outputs (plans, meetings, decisions)- providing a link to agile practices.-## 1.4 The Centre of Excellence in PM² (CoEPM²)+## 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+## 1.5 The Open PM² initiativeOpen PM² is a European Commission initiative, which brings the PM² Methodology and its benefits closer to its broader stakeholders and user community.@@ -79,7 +79,7 @@ Opening PM² does this by:- 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.-### 1.5.1 PM² Publications+### 1.5.1 PM² publicationsThe Centre of Excellence in PM² (CoEPM²) provides a central online location for all PM² information, and resources.diff --git a/docs/project-management-guide/2-project-management/README.md b/docs/project-management-guide/2-project-management/README.mdindex e30c9de1f05..13e1e3073c8 100644--- a/docs/project-management-guide/2-project-management/README.md+++ b/docs/project-management-guide/2-project-management/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: 1 Project management+ title: 2 Project managementpriority: 950description: Provides the general project management concepts on which PM² is built. It covers the definition of projects, their environment, key success factors, and essential project management competencies (knowledge, skills, and mindsets).keywords: user guide@@ -84,15 +84,15 @@ The table below illustrates this with a simple example:| Project Outcomes | - Increased project quality. <br> - Improved visibility of project objectives, status and forecasts. <br> - Capability to have better control over contractor work and deliverables. || Project Benefits | - Project cost overruns decreased by 30\% <br> - Productivity increased by 30\%. |-## 2.2 About Project Management+## 2.2 About project management-### 2.2.1 What is 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.+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+### 2.2.2 Project documentationProject documentation is a key activity in project management. It carries through from the start of a project to its completion. Project documentation:@@ -121,13 +121,13 @@ A Project Support Office (PSO) is an organisational body (or entity) that provid- tailor the project management methodology to new best practices and help project teams implement the updated methodology effectively.-### 2.2.4 Programme Management+### 2.2.4 Programme managementA 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+### 2.2.5 Project portfolio managementA 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@@ -136,7 +136,7 @@ in terms of meeting strategic objectives. The projects or programmes in a portfoIt 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).-### 2.2.6 Projects vs Operations+### 2.2.6 Projects vs operationsProjects 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.@@ -154,27 +154,27 @@ How do you recognise that a project has slipped into operations mode?- Maintenance activities are undertaken.- Minor updates (improvements) are planned and implemented over time.-## 2.3 Project Environment+## 2.3 Project environment-### 2.3.1 Project Organisation+### 2.3.1 Project organisationIt 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**+**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**+**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**+**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+### 2.3.2 Developing project management competencesProject 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.@@ -193,7 +193,7 @@ It is up to the Project Manager (PM) to acquire these skills and invest in their-### 2.3.3 Project Management Competences+### 2.3.3 Project management competencesProject Managers (PMs) need to:diff --git a/docs/project-management-guide/3-overview-pm2/README.md b/docs/project-management-guide/3-overview-pm2/README.mdindex dae4e0c0838..8559e99acfd 100644--- a/docs/project-management-guide/3-overview-pm2/README.md+++ b/docs/project-management-guide/3-overview-pm2/README.md@@ -1,13 +1,13 @@---sidebar_navigation:- title: 3 Overview of the PM² Methodology+ title: 3 PM² methodology overviewpriority: 850description: "Presents the House of PM² framework and explains its four pillars: Governance, Lifecycle, Processes, and Artefacts, all supported by PM² Mindsets. It introduces the four project lifecycle phases (Initiating, Planning, Executing, Closing) and explains tailoring to different project contexts."----# 3 Overview of the PM² Methodology+# 3 Overview of the PM² methodology-## 3.1 The House of PM²+## 3.1 The house of PM²The PM² Methodology is built on Project Management best practices and is supported by four pillars:@@ -22,7 +22,7 @@ The PM² Methodology is built on Project Management best practices and is supporThe 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+## 3.2 The PM² lifecycleThe 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).diff --git a/docs/project-management-guide/4-project-organisation-and-roles/README.md b/docs/project-management-guide/4-project-organisation-and-roles/README.mdindex a31fe9ee7e4..87a78dbab80 100644--- a/docs/project-management-guide/4-project-organisation-and-roles/README.md+++ b/docs/project-management-guide/4-project-organisation-and-roles/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: 4 Project Organisation and Roles+ title: 4 Project organisation and rolespriority: 800description: Describes the PM² governance model in detail, including the main project roles and responsibilities for example the Project Steering Committee, Project Owner, Business Manager, Project Manager, and Project Core Team. It explains reporting lines, decision-making, and escalation mechanisms.keywords: project stakeholders, project organisations, appropriate governance body, project steering committee, PSC, project owner, business manager, project manager, business implementation group, project core team, project support team, ramdiff --git a/docs/project-management-guide/5-initiating-phase/README.md b/docs/project-management-guide/5-initiating-phase/README.mdindex e5a1694bcc7..bcfbee73e58 100644--- a/docs/project-management-guide/5-initiating-phase/README.md+++ b/docs/project-management-guide/5-initiating-phase/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: 5 Initiating Phase+ title: 5 Initiating phasepriority: 750description: Defines the activities needed to start a project. This includes preparing the Project Initiation Request (PIR), developing the Business Case, drafting the Project Charter, and obtaining formal approval through the Request for Planning (RfP) phase gate.keywords: initiating meeting, project initiation request, business case, project charter, ready for planningdiff --git a/docs/project-management-guide/6-planning-phase/README.md b/docs/project-management-guide/6-planning-phase/README.mdindex 5070e749fc4..06c76106001 100644--- a/docs/project-management-guide/6-planning-phase/README.md+++ b/docs/project-management-guide/6-planning-phase/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: 6 Planning Phase+ title: 6 Planning phasepriority: 700description: Focuses on defining how the project will be executed and controlled. It covers developing the Project Handbook and detailed management plans (scope, schedule, cost, risk, stakeholder, etc.), creating the Work Breakdown Structure (WBS), scheduling, resource planning, and getting approval through the Request for Execution (RfE) gate.keywords: project handbook, project stakeholder matrix, project work plan, outsourcing plan, deliverables acceptance plan, transition plan, business implementation plan, ready for executingdiff --git a/docs/project-management-guide/9-monitor-and-control/README.md b/docs/project-management-guide/9-monitor-and-control/README.mdindex 216ff9e8e02..3d12bfe9e36 100644--- a/docs/project-management-guide/9-monitor-and-control/README.md+++ b/docs/project-management-guide/9-monitor-and-control/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: 9 monitor & control+ title: 9 Monitor & controlpriority: 550description: A transversal section that applies across all phases. It details how to monitor project performance, schedule, cost, stakeholder engagement, requirements, change requests, risks and issues, quality, acceptance, transition, and outsourced activities. It ensures the project stays aligned with plans and objectives.keywords: control schedule, monitor project performance, control cost, manage stakeholders, manage requirements, manage project change, manage risk, manage issues and decisions, manage quality, manage deliverables acceptance, manage transition, manage business implementation, manage outsourcingdiff --git a/docs/project-management-guide/Appendecies/README.md b/docs/project-management-guide/Appendices/README.mdsimilarity index 99%rename from docs/project-management-guide/Appendecies/README.mdrename to docs/project-management-guide/Appendices/README.mdindex 32724512bce..5347ed761b4 100644--- a/docs/project-management-guide/Appendecies/README.md+++ b/docs/project-management-guide/Appendices/README.md@@ -6,7 +6,7 @@ description: Appendices to the PM² project management guidekeywords: Contributions and acknowledgements, project management plans and logs,----# Appendix A: Contributions and Acknowledgements+# Appendix A: contributions and acknowledgementsThe European Commission is grateful to all those who have contributed in the development of the PM² Project Management Methodology and wishes to acknowledge their contribution and support.In alphabetical order:@@ -116,9 +116,9 @@ Former CoEPM² members who recently moved on to other assignments:3. Elias MICHOTTE Alexandra4. VAN GAEVER Alain-# Appendix B: Project Management Plans and Logs+# Appendix B: project management plans and logs-## B. 1 Requirements Management Plan+## B. 1 Requirements management planThe Requirements Management Plan defines and documents the requirements management approach, process steps and responsibilities, as well as tools, techniques and artefacts that will be used. Note that requirements themselves are documented and managed in separate artefact(s) (e.g. requirements matrix).@@ -128,7 +128,7 @@ Requirements are traditionally defined in detail early in the project lifecycle.The Requirements Management Plan can be tailored and customised to the project's needs. In the absence of a more specialised role, the Project Manager (PM) is responsible for executing the process from project initiation until all requirements have been implemented and validated.-| Key Participants | Description |+| Key participants | Description || :-- | :-- || Project Manager (PM) | Prepares this artefact. || Business Manager (BM) | Consulted for the tailoring and elaboration of this artefact. |@@ -165,13 +165,13 @@ The Requirements Management Plan can be tailored and customised to the project's- Requirements Management Plan-## B. 2 Project Change Management Plan+## B. 2 Project change management planThe Project Change Management Plan defines and documents the change process for a project. It defines the activities, roles and responsibilities related to identifying, documenting, assessing, approving, prioritising, implementing, controlling, and communicating requested project changes.Project change management brings transparency, accountability and traceability to all project changes implemented after the project scope and project plans have been baselined. The escalation procedure ensures that changes with a significant impact on project performance are properly assessed and approved by the appropriate level of authority. The Project Change Log is used to document requested changes and trace all related decisions and planned actions.-| Key Participants | Description |+| Key participants | Description || :-- | :-- || Project Manager (PM) | Prepares the Project Change Management Plan. || Project Owner (PO) | Approves the Project Change Management Plan. |@@ -200,7 +200,7 @@ Project change management brings transparency, accountability and traceability t| Project Change Management Plan | | I | I | A | C | I | I | R | I |-| Related Artefacts | Initiating | Planning | Executing | Monitor \& Control | Closing |+| Related artefacts | Initiating | Planning | Executing | Monitor \& control | Closing || :--: | :--: | :--: | :--: | :--: | :--: || Project Change Management | Project <br> Charter | Project Handbook Project Change Management Plan | Project Reports Change Requests | Change Log <br> Project Logs <br> Project Work Plan | Project-End Report |@@ -209,7 +209,7 @@ Project change management brings transparency, accountability and traceability t- Project Change Management Plan- Change Log (setup)-## B. 3 Risk Management Plan+## B. 3 Risk management planThe Risk Management Plan defines and documents the Risk Management Process for a project. It describes how risks will be identified and assessed, what tools and techniques can be used, what the evaluation scales and tolerances are, the relevant roles and responsibilities, how often risks need to be revisited, etc. The Risk Management Plan also defines the risk monitoring and escalation process as well as the structure of the Risk Log, which is used to document and communicate the risks and their response actions.@@ -255,7 +255,7 @@ Risk management brings visibility to risks and accountability as to how they are- Risk Management Plan- Risk Log-## B. 4 Issue Management Plan+## B. 4 Issue management planThe Issue Management Plan defines and documents the activities, roles and responsibilities related to identifying, assessing, assigning, resolving and controlling project issues. Issues are defined as unplanned project-related events that require a project management action.@@ -263,7 +263,7 @@ The issue management process helps the Project Manager (PM) to assess and act upAn Issue Log is used to document the identification, evaluation and assignment of issues and to trace all key decisions and planned actions. It also helps keep track of who is responsible for solving specific issues by a certain deadline. It brings visibility and accountability as to how issues are acted upon, and ensures that they are properly managed and resolved.-| Key Participants | Description |+| Key participants | Description || :-- | :-- || Project Manager (PM) | Prepares the Issue Management Plan. || Business Manager (BM) | Consulted for the elaboration of this artefact. |@@ -305,7 +305,7 @@ An Issue Log is used to document the identification, evaluation and assignment o- Decision Log-## B. 5 Quality Management Plan+## B. 5 Quality management planThe Quality Management Plan defines and documents the project's quality requirements, the quality management approach, process and responsibilities. It also outlines the quality assurance and control activities undertaken throughout the project.@@ -372,7 +372,7 @@ A configuration management procedure is also documented in the Quality Managemen- Phase-exit Review Checklist-## B. 6 Communications Management Plan+## B. 6 Communications management planThe Communications Management Plan helps to ensure that all project stakeholders have the information they need to perform their roles throughout the project. Planning and executing project communication activities is essential for project success.@@ -408,7 +408,7 @@ The Communications Management Plan defines and documents communication activitie| Communications Management Plan | | I | I | A | S | C | I | R | C |-| Related Artefacts | Initiating | Planning | | Executing | | Monitor \& Control | | Closing |+| Related artefacts | Initiating | Planning | | Executing | | Monitor \& control | | Closing || :--: | :--: | :--: | :--: | :--: | :--: | :--: | :--: | :--: || Communications <br> Management | Project <br> Charter | Project Stakeholder <br> Matrix <br> Communications <br> Management Plan | | Project <br> Reports | | Project Logs | | Project-End <br> Report |@@ -416,7 +416,7 @@ The Communications Management Plan defines and documents communication activitie- Communications Management Plan-## B. 7 Change Log+## B. 7 Change log| Change Identification and Description | || :--: | :--: |@@ -441,7 +441,7 @@ The Communications Management Plan defines and documents communication activitie| Actual Delivery Date | The date on which the change was actually delivered. || Traceability and Comments | The ID(s) of the tasks (in the Project Work Plan) that implement the change, and/or the IDs of related issues, risks or decisions. Also include any additional information/comments related to the change. |-## B. 8 Risk Log+## B. 8 Risk log| Risk Identification and Description | || :--: | :--: |@@ -464,7 +464,7 @@ The Communications Management Plan defines and documents communication activitie| Target date | The date on which the action is expected to be implemented. || Traceability/Comments | The ID(s) of the tasks (in the Project Work Plan) that implement the risk response actions, and/or the IDs of related changes, issues, or decisions (log entries). Also include any additional information/comments related to the risk. |-## B. 9 Issue Log+## B. 9 Issue log| Issue Identification and Description | || :--: | :--: |@@ -485,7 +485,7 @@ The Communications Management Plan defines and documents communication activitie| Escalation | Whether or not the issue is to be escalated to the Directing or Steering Layers (Yes or No). || Traceability/Comments | The ID(s) of the tasks (in the Project Work Plan) that implement the issue actions, and/or the IDs of related changes, risks or decisions (Log entries). Also include any additional information/comments related to the issue. |-## B. 10 Decision Log+## B. 10 Decision log| Decision Identification and Description | || :-- | :-- |@@ -504,7 +504,7 @@ The Communications Management Plan defines and documents communication activitie| Date of Application | The date on which the decision is applicable. || Decision communicated <br> to: | The group, teams, and other audiences to whom the decision should be <br> communicated. |-# Appendix C: Project Management Tools \& Techniques+# Appendix C: Project management tools \& techniquesThis section introduces a number of commonly used Project Management Tools \& Techniques useful for dealing with various project management challenges. Each Tool \& Technique is summarised in a few paragraphs providing a simple and high-level overview of that tool or technique.diff --git a/docs/project-management-guide/Appendecies/d.01.png b/docs/project-management-guide/Appendices/d.01.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.01.pngrename to docs/project-management-guide/Appendices/d.01.pngdiff --git a/docs/project-management-guide/Appendecies/d.02.png b/docs/project-management-guide/Appendices/d.02.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.02.pngrename to docs/project-management-guide/Appendices/d.02.pngdiff --git a/docs/project-management-guide/Appendecies/d.03.png b/docs/project-management-guide/Appendices/d.03.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.03.pngrename to docs/project-management-guide/Appendices/d.03.pngdiff --git a/docs/project-management-guide/Appendecies/d.04.png b/docs/project-management-guide/Appendices/d.04.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.04.pngrename to docs/project-management-guide/Appendices/d.04.pngdiff --git a/docs/project-management-guide/Appendecies/d.05.png b/docs/project-management-guide/Appendices/d.05.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.05.pngrename to docs/project-management-guide/Appendices/d.05.pngdiff --git a/docs/project-management-guide/Appendecies/d.06.png b/docs/project-management-guide/Appendices/d.06.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.06.pngrename to docs/project-management-guide/Appendices/d.06.pngdiff --git a/docs/project-management-guide/Appendecies/d.07.png b/docs/project-management-guide/Appendices/d.07.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.07.pngrename to docs/project-management-guide/Appendices/d.07.pngdiff --git a/docs/project-management-guide/Appendecies/d.08.png b/docs/project-management-guide/Appendices/d.08.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.08.pngrename to docs/project-management-guide/Appendices/d.08.pngdiff --git a/docs/project-management-guide/Appendecies/d.09.png b/docs/project-management-guide/Appendices/d.09.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/d.09.pngrename to docs/project-management-guide/Appendices/d.09.pngdiff --git a/docs/project-management-guide/Appendecies/e.01.01.png b/docs/project-management-guide/Appendices/e.01.01.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.01.01.pngrename to docs/project-management-guide/Appendices/e.01.01.pngdiff --git a/docs/project-management-guide/Appendecies/e.01.02.png b/docs/project-management-guide/Appendices/e.01.02.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.01.02.pngrename to docs/project-management-guide/Appendices/e.01.02.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.01.png b/docs/project-management-guide/Appendices/e.02.01.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.01.pngrename to docs/project-management-guide/Appendices/e.02.01.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.02.png b/docs/project-management-guide/Appendices/e.02.02.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.02.pngrename to docs/project-management-guide/Appendices/e.02.02.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.03.png b/docs/project-management-guide/Appendices/e.02.03.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.03.pngrename to docs/project-management-guide/Appendices/e.02.03.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.04.png b/docs/project-management-guide/Appendices/e.02.04.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.04.pngrename to docs/project-management-guide/Appendices/e.02.04.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.05.png b/docs/project-management-guide/Appendices/e.02.05.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.05.pngrename to docs/project-management-guide/Appendices/e.02.05.pngdiff --git a/docs/project-management-guide/Appendecies/e.02.06.png b/docs/project-management-guide/Appendices/e.02.06.pngsimilarity index 100%rename from docs/project-management-guide/Appendecies/e.02.06.pngrename to docs/project-management-guide/Appendices/e.02.06.pngdiff --git "a/docs/project-management-guide/Appendecies/pm\302\262.png" "b/docs/project-management-guide/Appendices/pm\302\262.png"similarity index 100%rename from "docs/project-management-guide/Appendecies/pm\302\262.png"rename to "docs/project-management-guide/Appendices/pm\302\262.png"diff --git a/docs/project-management-guide/README.md b/docs/project-management-guide/README.mdindex fdcdb64f0dc..d0ac5d581f8 100644--- a/docs/project-management-guide/README.md+++ b/docs/project-management-guide/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: PM² Project Management Methodology Guide - OpenProject+ title: PM² Project Management Guidepriority: 954description: Additional information and application guidelines for using OpenProject in PM² projects.keywords: PM²@@ -16,15 +16,15 @@ Additional information and hands-on application guidelines for using OpenProject| Topic | Content || ------------------------------------------------------------ | ------------------------------------------------------------ |-| [1 An Introduction to the PM² Guide](1-introduction) | Explains the purpose and audience of the methodology. It introduces PM² as a light, practical, and adaptable approach suitable for various project types, developed by the European Commission. It outlines the structure of the guide and how to use it. |-| [2 Project Management](2-project-management) | Provides the general project management concepts on which PM² is built. It covers the definition of projects, their environment, key success factors, and essential project management competencies (knowledge, skills, and mindsets). |-| [3 Overview of the PM² Methodology](3-overview-pm2) | Presents the House of PM² framework and explains its four pillars: Governance, Lifecycle, Processes, and Artefacts, all supported by PM² Mindsets. It introduces the four project lifecycle phases (Initiating, Planning, Executing, Closing) and explains tailoring to different project contexts. |-| [4 Project Organisation and Roles](4-project-organisation-and-roles) | Describes the PM² governance model in detail, including the main project roles and responsibilities: e.g., the Project Steering Committee, Project Owner, Business Manager, Project Manager, and Project Core Team. It explains reporting lines, decision-making, and escalation mechanisms. |-| [5 Initiating Phase](5-initiating-phase) | Defines the activities needed to start a project. This includes preparing the Project Initiation Request (PIR), developing the Business Case, drafting the Project Charter, and obtaining formal approval through the Request for Planning (RfP) phase gate. |-| [6 Planning Phase](6-planning-phase) | Focuses on defining how the project will be executed and controlled. It covers developing the Project Handbook and detailed management plans (scope, schedule, cost, risk, stakeholder, etc.), creating the Work Breakdown Structure (WBS), scheduling, resource planning, and getting approval through the Request for Execution (RfE) gate. |-| [7 Executing Phase](7-executing-phase) | Covers carrying out the project work according to the plan. It includes team coordination, quality assurance, stakeholder communication, performance monitoring, and progress reporting. Formal approval to move forward is given through the Request for Closing (RfC) gate once work is complete. |-| [8 Closing Phase](8-closing-phase) | Describes how to formally close the project. Activities include performing final reviews, accepting deliverables, capturing lessons learned, preparing the Project-End Report, completing administrative closure, and archiving documentation. |-| [9 Monitor \& Control](9-monitor-and-control) | A transversal section that applies across all phases. It details how to monitor project performance, schedule, cost, stakeholder engagement, requirements, change requests, risks and issues, quality, acceptance, transition, and outsourced activities. It ensures the project stays aligned with plans and objectives. |+| [1 An introduction to the PM² guide](1-introduction) | Explains the purpose and audience of the methodology. It introduces PM² as a light, practical, and adaptable approach suitable for various project types, developed by the European Commission. It outlines the structure of the guide and how to use it. |+| [2 Project management](2-project-management) | Provides the general project management concepts on which PM² is built. It covers the definition of projects, their environment, key success factors, and essential project management competencies (knowledge, skills, and mindsets). |+| [3 Overview of the PM² methodology](3-overview-pm2) | Presents the House of PM² framework and explains its four pillars: Governance, Lifecycle, Processes, and Artefacts, all supported by PM² Mindsets. It introduces the four project lifecycle phases (Initiating, Planning, Executing, Closing) and explains tailoring to different project contexts. |+| [4 Project organisation and roles](4-project-organisation-and-roles) | Describes the PM² governance model in detail, including the main project roles and responsibilities: e.g., the Project Steering Committee, Project Owner, Business Manager, Project Manager, and Project Core Team. It explains reporting lines, decision-making, and escalation mechanisms. |+| [5 Initiating phase](5-initiating-phase) | Defines the activities needed to start a project. This includes preparing the Project Initiation Request (PIR), developing the Business Case, drafting the Project Charter, and obtaining formal approval through the Request for Planning (RfP) phase gate. |+| [6 Planning phase](6-planning-phase) | Focuses on defining how the project will be executed and controlled. It covers developing the Project Handbook and detailed management plans (scope, schedule, cost, risk, stakeholder, etc.), creating the Work Breakdown Structure (WBS), scheduling, resource planning, and getting approval through the Request for Execution (RfE) gate. |+| [7 Executing phase](7-executing-phase) | Covers carrying out the project work according to the plan. It includes team coordination, quality assurance, stakeholder communication, performance monitoring, and progress reporting. Formal approval to move forward is given through the Request for Closing (RfC) gate once work is complete. |+| [8 Closing phase](8-closing-phase) | Describes how to formally close the project. Activities include performing final reviews, accepting deliverables, capturing lessons learned, preparing the Project-End Report, completing administrative closure, and archiving documentation. |+| [9 Monitor & control](9-monitor-and-control) | A transversal section that applies across all phases. It details how to monitor project performance, schedule, cost, stakeholder engagement, requirements, change requests, risks and issues, quality, acceptance, transition, and outsourced activities. It ensures the project stays aligned with plans and objectives. |**Disclaimer**diff --git a/docs/use-cases/README.md b/docs/use-cases/README.mdindex 1be5b18b228..3be470efb60 100644--- a/docs/use-cases/README.md+++ b/docs/use-cases/README.md@@ -15,4 +15,5 @@ keywords: use-cases| [Implementing Scaled Agile Framework (SAFe) in OpenProject](safe-framework) | Learn how to set up and configure OpenProject to support the Scaled Agile Framework (SAFe) to successfully deliver value to customers using agile practices at scale. || [Test management](test-management) | OpenProject can be configured to support lightweight test management using custom work package types, workflows and project templates. This guide describes how to manage test cases and test runs in a reusable, scalable way. || [Meeting management](meeting-management) | With OpenProject's meeting management features, you can structure your meetings, define agendas, assign action items, and keep everything transparent and traceable in one place. Ensure your team stays aligned and decisions are well-documented throughout the project life cycle.<br />Learn how plan, conduct, and follow up on meetings with OpenProject. |+| [PM² and PMflex project management with OpenProject](project-management-pm2-pmflex) | Learn how to use OpenProject to manage projects with the **PM² methodology**, developed by the European Commission, and its German extension **PMflex**, maintained by the Federal Office of Administration (BVA).<br /> Get started with customizable workflows, templates, and collaboration tools to apply these frameworks effectively across all project phases. |diff --git a/docs/use-cases/meeting-management/README.md b/docs/use-cases/meeting-management/README.mdindex 2c49c7d8954..8aabf2b9502 100644--- a/docs/use-cases/meeting-management/README.md+++ b/docs/use-cases/meeting-management/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: Meeting Management+ title: Meeting managementpriority: 900description: Meeting management in OpenProjectkeywords: meetings, meeting management, use case, use-case, agendadiff --git a/docs/use-cases/portfolio-management/README.md b/docs/use-cases/portfolio-management/README.mdindex af5d841b1ea..487b3afee73 100644--- a/docs/use-cases/portfolio-management/README.md+++ b/docs/use-cases/portfolio-management/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: Portfolio Management and Custom Reporting+ title: Portfolio management and custom reportingpriority: 800description: Step-by-step instructions about portfolio management and custom reportingkeywords: use-case, portfolio managementdiff --git a/docs/use-cases/project-management-pm2-pmflex/README.md b/docs/use-cases/project-management-pm2-pmflex/README.mdindex 1d2d5b9e244..ca7d6926893 100644--- a/docs/use-cases/project-management-pm2-pmflex/README.md+++ b/docs/use-cases/project-management-pm2-pmflex/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: PM² and PMflex project management with OpenProject+ title: PM² and PMflex project managementpriority: 600description: Learn how to set up and configure OpenProject to support the PM²/PMflex methodology with OpenProjectkeywords: pmflex, PM², PM2,diff --git a/docs/use-cases/resource-management/README.md b/docs/use-cases/resource-management/README.mdindex e7b52542c89..62e32a75c59 100644--- a/docs/use-cases/resource-management/README.md+++ b/docs/use-cases/resource-management/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: Resource Management+ title: Resource managementpriority: 700description: Step-by-step instruction about resource managementkeywords: use-case, resource managementdiff --git a/docs/use-cases/test-management/README.md b/docs/use-cases/test-management/README.mdindex 347aee09e9e..c62445164fe 100644--- a/docs/use-cases/test-management/README.md+++ b/docs/use-cases/test-management/README.md@@ -1,6 +1,6 @@---sidebar_navigation:- title: Test Management with OpenProject+ title: Test managementpriority: 950description: OpenProject can be configured to support lightweight test management using custom work package types, work packages and project templates. This guide describes how to manage test cases and test runs in a reusable, scalable way.keywords: test plan, test case, test case, test management