Project Management Fundamentals and Organizational Context
What this domain tests
This domain tests whether you can separate projects from operations, map governance and decision rights, and predict how organizational structure changes a project manager's authority. Questions often describe a reporting line and ask what the PM can decide.
Core rules
- A project is a temporary effort to create a unique product, service, or result. Operations are repetitive and ongoing. A deadline alone does not make work a project.
- The performance domains interact: scope, schedule, cost, quality, resources, and risk. A change in one usually affects others, so approved baselines and integrated change control matter.
- Functional organizations group staff by specialty; the PM usually coordinates and has limited budget authority. Projectized organizations give the PM strong authority. Matrix organizations share authority: weak matrix favors functional managers, balanced shares it, strong matrix favors the PM.
- PMO types: supportive (templates, coaching), controlling (compliance and methods), directive (PMs report to the PMO).
- Stage gates and charters create governance. A charter authorizes the project and names the PM before detailed planning.
Worked example
A utility must launch a regulatory portal in nine months. Engineers remain in engineering, but the PM owns the budget and schedule and the engineering manager approves technical standards. This is a strong matrix: the PM can drive delivery, while the functional manager retains technical authority. If the PM only tracked status and had no budget control, the structure would be weak matrix or functional.
Traps
- Calling recurring month-end reporting a project because it has a due date.
- Assuming projectized is always better; it can reduce functional expertise.
- Confusing the product lifecycle with the project lifecycle.
- Treating a PMO as always directive; supportive PMOs mainly provide templates and coaching.