1 PMP Exam Foundations and Project Management Principles
An overview of the current PMP exam structure and eligibility, practical preparation methods, and project management principles for delivering value through context-appropriate approaches.
What the PMP exam assesses
The PMP exam assesses whether candidates can apply project management judgment to realistic situations, not merely recall terms or processes. Use PMI’s current as the primary map of what is tested. As of November 4, 2026, the exam reflects the update launched in July 2026.
Exam structure and emphasis
The exam has 180 questions and lasts 240 minutes. Ten questions are unscored pretest items, mixed randomly with scored questions; candidates cannot identify them. Question formats can include single-response and multiple-response items, case or scenario sets, matching, graphic-based questions, and practical questions involving tools or data.
There are two 10-minute breaks. At a test center, the first follows the case-study section, and the second comes about midway through the independent-question portion. Once a break begins, candidates cannot return to the preceding section.
The exam has three domains, with approximate shares of questions:
People:
Process:
Business Environment:
Predictive, adaptive/agile, and hybrid approaches appear throughout the domains. PMI estimates that approximately of questions reflect predictive approaches and reflect adaptive/agile or hybrid approaches. The precise mix can vary by exam form. The updated exam also emphasizes outcomes, , stakeholder engagement, sustainability, and AI-related situations.
Eligibility and training requirements
Candidates need one of the following education-and-experience combinations. Experience must involve leading projects in a professional setting, fall within the 10 years before application, and be counted in non-overlapping months.
Secondary-school completion or equivalent: 60 months, or 5 years, of project-leading experience.
Recognized associate-level qualification or qualifying post-secondary technical or vocational program: 48 months, or 4 years.
Bachelor’s degree or higher, or a formally recognized bachelor-equivalent qualification: 36 months, or 3 years.
Bachelor’s or postgraduate degree from a PMI Global Accreditation Center (GAC)-accredited program: 24 months, or 2 years.
Applicants generally also need 35 hours of project management training aligned with the ECO. An active CAPM® certification provides credit for this training requirement. Training records may be audited, so retain course and completion documentation; books and practice exams alone do not count as qualifying training.
Beginning December 1, 2026, PMI’s published rules restrict qualifying live training to approved providers or eligible accredited academic programs. Training completed before that date remains eligible under the rules in place when it was completed. Check PMI’s current requirements before enrolling.
Preparing with applied judgment
Start with the current ECO and map its domains and tasks to your strengths and gaps. Balance study of people and team leadership, project planning and delivery, and the business context, including governance, organizational change, and alignment to strategy. Practice predictive, adaptive, and hybrid situations rather than treating agile as an isolated topic.
For each scenario, identify the goal, relevant constraints, stakeholders, and approach already in place. Choose a response that addresses the issue, involves the right people, follows appropriate governance, and protects . Avoid rushing to escalate, reject a change, or implement a solution before understanding its impact.
Review every practice answer. Record why the best answer fits and why tempting alternatives do not. Group missed questions by underlying gap, such as stakeholder engagement, change control, risk response, or benefits, and revisit the relevant concept before taking more questions.
Rehearse with timed practice in the current format, including long scenario sets, chart interpretation, and questions requiring multiple responses. Practice pacing across the 240 minutes and the break boundaries. Use current PMI materials and the ECO; older resources may still teach fundamentals but may not reflect the current exam structure and emphasis.
Principles for project decisions
Principles guide decisions and behavior; they are not a fixed sequence of steps. PMI’s current PMBOK® Guide—Eighth Edition presents six core principles intended to connect project leadership with practical delivery and apply across different project contexts and approaches.
Adopt a holistic view. Consider how decisions interact across the team, organization, stakeholders, and external environment. A local improvement can create a wider problem: speeding delivery by adding features may increase support costs or delay adoption.
Focus on . Keep work aligned with intended benefits and strategic objectives. Reassess priorities when evidence or circumstances change; completing the original scope is not enough if it no longer serves the business need.
Embed quality into processes and deliverables. Build appropriate standards, reviews, and acceptance criteria into the work instead of relying only on final inspection. Quality means fitness for intended use as well as conformance to requirements.
Be an accountable leader. Take responsibility for decisions and outcomes, act ethically, and adapt leadership to the situation. Leadership is not limited to the person with formal authority.
Integrate sustainability within all project areas. Consider long-term environmental, social, and economic effects alongside immediate delivery needs. For example, compare a low initial purchase price with lifecycle energy use, maintenance, and disposal impacts.
Build an empowered culture. Enable capable people to collaborate, make appropriate decisions, learn, and raise concerns. The project manager helps create clarity and remove barriers rather than micromanaging every task.
The principles reinforce one another: an empowered team can identify quality problems earlier, holistic thinking can reveal downstream effects, and accountable leadership helps keep decisions focused on .
From deliverables to
A project’s , , and are related but distinct. For example, in a project to install an online appointment system, the system is the ; patients being able to book more easily is an ; and reduced missed appointments and shorter call-center queues are potential benefits. Whether those benefits create depends on stakeholder needs, costs, adoption, and organizational goals.
Benefits realization links organizational strategy through project deliverables to expected benefits and . The project team should plan for feedback, implementation, and benefits measurement, not just technical completion. A project can meet its schedule and budget yet fail to deliver expected if users do not adopt the result or the business need changes. Conversely, stakeholders may a result even when some original assumptions change.
The project manager and sponsor should monitor whether the work remains justified, then adjust, redirect, or stop it when appropriate.
the project approach
means selecting and adapting project practices, methods, governance, and controls to fit the work. It is not a reason to ignore necessary oversight. Use enough structure to manage complexity, risk, compliance, and stakeholder expectations without adding process that does not help produce the desired outcomes. Revisit the approach as project conditions evolve.
Predictive: Useful when requirements and the solution are sufficiently stable and work can be planned in stages. A regulated facility upgrade may need defined design reviews, approvals, and inspection points.
Adaptive: Suited to work where requirements are uncertain or feedback is essential. A software team might deliver a small usable increment, gather user feedback, and reprioritize the backlog.
Hybrid: Combines elements of both. A product launch might use predictive milestone and compliance planning while software features are developed iteratively.
When , consider uncertainty, technical novelty, delivery cadence, team capabilities, stakeholder availability, risk, regulation, and organizational policy. A small internal website with stable requirements may need a light plan and a few reviews; a safety-critical system may need formal traceability, independent testing, and documented approvals. In either case, the chosen approach should support the intended and .