Project Management Fundamentals
What this domain tests
This domain checks whether you can tell a project from ongoing operations and use governance, lifecycle, and organizational vocabulary accurately. Questions often present a short scenario and ask for the best classification, the project manager's authority level, or the correct success measure.
Core distinctions
- A project is a temporary endeavor undertaken to create a unique product, service, or result; it has a definite start and end and is progressively elaborated.
- A program groups related projects for coordinated benefits; a portfolio groups projects, programs, and operations to meet strategic objectives.
- Operations are ongoing and repetitive. Recurring service work is not a project merely because it is managed.
- The triple constraint links scope, schedule, and cost; quality is often shown at the center. Changing one constraint normally affects the others.
Lifecycle and organization
- A predictive lifecycle runs through phases such as initiation, planning, execution, and closure. Process groups are not phases: executing and monitoring/controlling repeat across phases.
- Functional organizations place authority with department managers. Projectized organizations give the project manager strong authority. Matrix organizations balance the two; weak matrix favors functional managers, strong matrix favors the project manager.
- The sponsor authorizes and funds the project; the project manager delivers within constraints; the PMO supports or governs project work.
Worked example
A bank calls a six-month core-banking migration a "project." It has a fixed go-live, a dedicated cross-functional team, and a business case. The project manager reports to the CIO, but team members still report to their functional managers for performance reviews. This is a strong matrix. Reasoning: the work is temporary and unique, so it is a project; the project manager has substantial authority, but resources remain owned by functions, so it is not projectized.
Traps
- Treating process groups as sequential lifecycle phases.
- Assuming the triple constraint is fixed rather than traded off.
- Calling recurring operational work a project.
- Confusing a program (related projects) with a portfolio (strategic collection).
- Assuming a projectized structure is always best; it depends on context.