Project Management Fundamentals and Core Concepts
What this domain tests
This domain covers the vocabulary and logic that every other domain assumes: the difference between a project (temporary, unique output) and operations (ongoing, repetitive); the triple constraint of scope, schedule, and cost balanced against quality; and the project life cycle from initiation through closure. Know the role distinctions: the project manager owns delivery, the sponsor funds and champions, the PMO supplies standards and governance, and stakeholders are anyone affected by or interested in the work. Understand organizational structures (functional, matrix, projectized) and how they shift authority from the functional manager toward the project manager.
Concepts to master
- Project charter vs. project management plan: the charter authorizes the project; the plan describes how it will be executed.
- Progressive elaboration: details emerge as understanding improves - a reason estimates early are rough.
- Deliverable vs. milestone: a deliverable is a tangible output; a milestone is a zero-duration marker.
- Benefits realization and lessons learned as closure activities.
- Stakeholder engagement as continuous, not a one-time register entry.
Traps in questions
Watch for wording that swaps authority with responsibility, or that treats the sponsor as the person doing the scheduling. A common distractor says to “escalate immediately” when the better first step is to assess, document, or consult the charter. Another trap: confusing a program (related projects managed together) with a portfolio (projects grouped to meet strategic goals).
Rule of thumb
When a question asks what to do first, choose the action that gathers information or confirms authority - review the charter, consult the plan, or talk to the stakeholder - before acting or escalating.