Four pillars, one system: PM² in WORKSPACE.PM
PM², the project management framework of the European Commission, rests on governance, lifecycle, processes and artefacts. WORKSPACE.PM carries all four - role matrix and RAM, phases with their gates, demands with value scoring, and documents straight from your project data. In the same system where your agile teams already work.
PM² between classical order and agile agility
Where the EU framework sits on the method spectrum - and which standards lie next to it
PM²: governance-driven, deliberately lean, hybrid-capable
PM² sits on the structured side of the spectrum - four phases, clear roles, documented approvals. At the same time it is kept deliberately lean and extended by PM² Agile. In WORKSPACE.PM that stays no contradiction: the container concept allows each sub-project its own way of working, so a PM²-governed initiative can run agile strands without losing the governance frame.
The framework stands. The tools don't keep up.
Where PM² creates friction between ambition and day-to-day project work
Governance without matching roles
PM² separates the requesting and providing sides and puts a steering body above them. In standard tools these layers collapse into one flat member list.
Artefacts scattered across file shares
Charter, business case and status reports live as Word files in folders and inboxes - disconnected from the project data they should actually come from.
Approvals without a trail
The move to the next phase is decided in a meeting and confirmed by email. Who approved what, and when, stays buried in minutes.
Agile breaks the frame
As soon as a team delivers iteratively, many tools lose the unified governance view - and the reporting line upward is cut off.
The House of PM² - building block by building block in WORKSPACE.PM
From the foundation to the roof: six building blocks of the method and the tool that carries each in the system.
Project governance & roles
PM² places a steering layer above the project: a governance body and clearly separated roles on the requesting and providing sides.
Role matrix, RAM assignment and project org chart
Custom global and project-specific roles map the steering body as well as the requesting and providing sides - across four permission levels from view to administration. The RAM matrix assigns work packages to each person with unambiguous markers (A/E/I/K/M/P), and the stakeholder register tracks environment and influence.
Business case & project mandate
Every PM² project begins with an evidenced justification - need, benefit and mandate are settled before resources start flowing.
Demand with value scoring and a logged gate decision
Every initiative starts as a demand with its tier, a scoring framework and the appraisal fields urgency, importance, benefit and priority. From the period-by-period cost-benefit plan, return, net present value and payback period are derived; at the gate a logged decision is taken, after which an approved demand converts straight into a project.
The project lifecycle
PM² takes every project through four phases - Initiating, Planning, Executing and Closing - accompanied by continuous monitoring and control.
Phase pipeline, containers and baseline
The pipeline editor maps the PM² lifecycle as a phase sequence; the container tree structures phases, work packages and milestones. Every status change is logged with a comment, and a frozen baseline can later be stepped through and compared against the actual plan.
Phase gates
Between the phases stands a deliberate approval each - ready for planning, for executing and for closing - that authorises the transition.
Quality gates with named approvers
A quality gate bundles its criteria, which named approvers vote on individually before the final gate decision is taken - with a full history and comments. Each gate can be bound to a pipeline phase, so the PM² transitions to planning, executing and closing get their fixed checkpoint.
Artefacts & documentation
PM² bundles each phase into named artefacts - from the charter to the project-end report - that evidence the project's state.
Documents from templates with live project data
From your own Word templates, charter, business case or project-end report are produced straight from the project data - placeholders pull in metrics, risks and financials automatically. Status reports pass through three approval stages (draft, submitted, approved); the project file store and the wiki keep the artefacts versioned together.
The logs: risks, changes, decisions
PM² keeps the project dynamics in logs - every risk, change and decision moves traceably into a maintained register.
Risk, change and decision registers
The risk register computes gross and net, monitors early-warning indicators and reminds of reviews on a 30-to-365-day cycle. Change requests carry impact and approver and link to the affected risk with its originating issue; decisions are logged straight in the project with owner and status.
PM² Agile: as much frame as needed, as much flow as possible
PM² is designed as a lean framework that grows with the initiative. That is exactly what the container blocks provide: each sub-project activates the functions it needs - phase gates and reporting at the overall project, board and iterations in the development strand. One structure, two ways of working, one reporting line.
The project worlds PM² is built for
Initiatives and roles that benefit most from the EU method
Frequently asked questions about PM² in WORKSPACE.PM
Which concrete tools carry the method's four pillars day to day
Yes. Custom global and project-specific roles map the steering body as well as the requesting and providing sides - across four permission levels from view to administration. The RAM matrix assigns work packages with unambiguous responsibility markers, and the stakeholder register tracks environment, influence and communication. For new initiatives, the demand pipeline decides on approval and priority.
The pipeline editor maps the four PM² phases - Initiating, Planning, Executing and Closing - as a phase sequence, and the container tree structures them into work packages and milestones. Every status change is logged with a comment, a frozen baseline can be compared against the actual plan in the Gantt, and status reports accompany monitoring and control throughout.
Each transition gets a quality gate: named approvers vote on the criteria individually, then the final decision is taken - with a full history. Each gate can be bound to a pipeline phase, so the transitions to planning, executing and closing get their fixed checkpoint. Optionally, approval workflows with deadlines and escalation drive the flow, and KPI values feed into the gate assessment.
From your own Word templates, charter, business case or project-end report are produced straight from the project data - placeholders pull in metrics, risks and financials automatically. Status reports pass through three approval stages, the project file store and the wiki keep all artefacts versioned together, and portfolio reporting rolls them up across projects.
The risk register computes gross and net, monitors early-warning indicators and reminds of reviews on a 30-to-365-day cycle. Change requests carry impact and approver and link to the affected risk; decisions are logged straight in the project with owner and status. The AI assistant can additionally derive risks from the project description.
PM² suits governance-driven initiatives in public administration, EU-adjacent organisations and large enterprises. In WORKSPACE.PM it stays hybrid-capable: each sub-project can work agile while the governance frame remains. Those with a broader method mix switch to a PMI/PMBOK-oriented approach per initiative.
Neighbouring PM standards
When your organisation runs several frameworks
Build your next PM² project on a solid foundation
Start for free and set up roles, phases, gates and artefacts in minutes.