This free PMP study guide walks through everything the Project Management Professional exam tests, organized to the current PMI Examination Content Outline (ECO).[2]
It’s interactive, not a wall of text: every module has built-in checkpoint quizzes, flashcards, and practice questions, so you learn by doing — not just reading.
The PMP tests three official domains — People (42%), Process (50%), and Business Environment (8%) — and about half the questions involve agile or hybrid approaches.[2] We teach one module per domain (Process is split into focused subsections because it’s half the exam), starting with the PMI mindset that drives most correct answers.
Read a module, test yourself at each checkpoint, then drill gaps with our free practice test and flashcards. This is a high-yield overview mapped to the official outline — not a replacement for the PMBOK Guide.
PMP Exam Snapshot
| Detail | PMP Exam |
|---|---|
| Questions | 180 (mix of multiple-choice, multiple-response, matching, hotspot, fill-in) |
| Time | 230 minutes, with one optional 10-minute break |
| Domains | People 42% · Process 50% · Business Environment 8% |
| Content mix | ≈50% predictive + ≈50% agile/hybrid |
| Result | Pass/Fail — no fixed % cut score; per-domain rating (Above Target → Needs Improvement) |
| Delivery | PMI via Pearson VUE (test center or online proctored) |
| Eligibility | 35 contact hours + (4-yr degree & 36 mo experience) or (HS/associate & 60 mo) |
| Cost (US) | $405 member / $555 non-member (re-exam $275 / $375) |
| Validity | 3 years; renew with 60 PDUs |
Study by weight. Process (50%) and People (42%) are 92% of the exam, so that’s where most of your time goes — but don’t skip Business Environment, especially if you sit the new exam:
Leading & developing the team (≈76 Qs)
The technical project-management work (≈90 Qs)
Compliance, value & org change (≈14 Qs)
Foundations · The PMI Mindset & Delivery Approaches
Before the domains, internalize how PMI thinks — because the exam rewards a specific judgment, not trivia. Most questions are scenarios where several answers are “not wrong,” and you pick the one a would choose: proactive, value-focused, and people-first.
PMBOK 7 principles & performance domains
The current PMBOK Guide (7th edition) is principle-based, not process-based. It defines 12 principles of project management — stewardship, team, stakeholders, value, systems thinking, leadership, , quality, complexity, risk, adaptability & resilience, and change — and 8 performance domains where the work happens.[3] You don’t memorize them like a list; you absorb the values behind them, because they explain why the “right” answer is right.
| Performance domain | What it covers |
|---|---|
| Stakeholders | Engaging stakeholders productively throughout the project |
| Team | Building and leading a high-performing, collaborative team |
| Development approach & life cycle | Choosing predictive, agile, or hybrid and the life-cycle phases |
| Planning | Organizing and coordinating the work, scope, schedule, and budget |
| Project work | Running processes, managing resources, communications, and procurement |
| Delivery | Producing the scope and quality that deliver the intended value |
| Measurement | Assessing performance and taking action (e.g., earned value) |
| Uncertainty | Navigating risk, ambiguity, complexity, and change |
Predictive, agile & hybrid
Roughly half the exam is agile or hybrid, so you must be fluent in all three approaches and know when each fits. Predictive (waterfall) fixes scope up front and is best for stable, well-understood work.
Agile fixes time and cost and flexes scope by priority, delivering value in short increments — best when requirements are uncertain. A blends both and is where most real projects land.[4]
Predictive (plan-driven)
- Scope fixed up front; time & cost flex
- Detailed plan, then execute in phases
- Change controlled via a formal process
- Best for stable, well-understood work
Hybrid
- Blends both — e.g. predictive build, agile UI
- Tailored to the project and organization
- Stable parts planned; uncertain parts iterated
- Most real projects land here
Agile (change-driven)
- Time & cost fixed; scope flexes by priority
- Iterative — deliver value in short increments
- Change is welcomed and re-prioritized
- Best for uncertain, evolving requirements
Module 1 · People (42%)
The largest single people-focused domain — 42% of the exam, about 76 questions. It is about leading, building, and empowering the team and engaging stakeholders. Because so many answers turn on leadership judgment, mastering this domain lifts your whole score.
1.1 Leading & building the team
The modern PM leads as a : you serve the team by removing impediments, providing what they need, and growing their skills, so the team can self-organize and perform. That mindset — empower, don’t command — is the single most useful lens for People-domain questions.[4]
Teams develop through predictable stages. The runs forming → storming → norming → performing → adjourning, and the leader’s job changes at each stage: direct early, coach through conflict, then delegate once the team performs. Adding or losing a member can reset a team to an earlier stage.
Forming
Team comes together, polite and uncertain; the leader sets direction.
Storming
Conflict surfaces as members assert ideas; the leader coaches and resolves conflict.
Norming
Norms and trust form; the team starts working together effectively.
Performing
High-performing and largely self-organizing; the leader delegates.
Adjourning
Work completes and the team disbands; recognize and release members.
is the foundation of all of this — self-awareness, self-regulation, empathy, motivation, and social skill let you read the team and respond well. To assign work clearly, PMs use a (Responsible, Accountable, Consulted, Informed); there should be exactly one Accountable person per task.
| Role | Meaning |
|---|---|
| Responsible (R) | Does the work to complete the task |
| Accountable (A) | Owns the outcome and signs off — exactly one per task |
| Consulted (C) | Provides input and expertise (two-way) |
| Informed (I) | Kept up to date on progress (one-way) |
1.2 Conflict, stakeholders & collaboration
Conflict is normal and can be healthy. The five modes range from best to worst: (problem-solving to a win-win) is the preferred PMP answer; splits the difference; papers over differences; imposes one side; and avoids the issue. Almost always, confront the problem and collaborate.
Collaborate / Problem-solve
Work together to a win-win that satisfies everyone — the best, most durable resolution.
Compromise / Reconcile
Each side gives up something for a partial win — a lose-lose middle ground.
Smooth / Accommodate
Emphasize agreement over differences; concede your position. Temporary at best.
Force / Direct
Push one viewpoint at others' expense — win-lose; fast but breeds resentment.
Withdraw / Avoid
Retreat or postpone; the conflict is unresolved. Sometimes buys time to cool off.
Stakeholder engagement is continuous: identify stakeholders, analyze their power, interest, and influence, plan how to engage each, and keep that engagement active. A power/interest grid helps you decide whom to manage closely versus simply keep informed. The goal is a shared understanding of the project’s goals so support stays high and surprises stay low.[2]
| Power | Interest | Engagement strategy |
|---|---|---|
| High | High | Manage closely — partner and involve them |
| High | Low | Keep satisfied — meet needs, don't overload |
| Low | High | Keep informed — they care; communicate often |
| Low | Low | Monitor — minimal effort |
Checkpoint · People
Question 1 of 10
Two senior developers on your agile project openly argue during a daily standup about which database technology to use, and their disagreement is now delaying a key feature. As the project manager applying servant leadership, what should you do first?
Module 2 · Process (50%)
The biggest domain — 50% of the exam, about 90 questions. This is the technical work of managing a project: integrating the plan, controlling scope, schedule, and cost, and managing quality, risk, and procurement. It also covers choosing and running the right methodology.
2.1 Integration, scope & change
Integration is the PM’s unique job: pulling all the plans together so they work as one. It starts with the , which authorizes the project and the PM, and runs through a single integrated change-control process. Define scope carefully — the (WBS) decomposes the total scope into ; under the 100% rule, nothing outside the WBS is in scope.
Guard against scope creep (uncontrolled additions) and gold plating (adding unrequested extras). Every change runs through the integrated change-control process and, in a predictive project, a before the baselines are updated.[3]
| Term | What it is | Why it's a problem |
|---|---|---|
| Scope creep | Uncontrolled changes added without review | Blows budget and schedule; bypasses change control |
| Gold plating | Team adds extras the customer didn't ask for | Wastes effort and adds risk for no agreed value |
| Progressive elaboration | Detail added as the project unfolds | Healthy — not the same as uncontrolled change |
2.2 Schedule, cost & earned value
Build the schedule from the activities, their dependencies, and durations. The is the longest path through the network and the shortest time to finish; its activities have zero , so any delay there delays the project. To compress, you can use (add resources to critical-path activities, raising cost) or (run activities in parallel, raising risk).
Cost performance is measured with , which combines scope, schedule, and cost. The building blocks are , , and . From them you get the variances and indices:
- Cost variance: — negative means over budget.
- Schedule variance: — negative means behind schedule.
- : — below 1 is over budget.
- : — below 1 is behind schedule.
- (if current performance continues): .
CV = EV − AC
Cost variance
Positive = under budget; negative = over budget
SV = EV − PV
Schedule variance
Positive = ahead; negative = behind schedule
CPI = EV ÷ AC
Cost performance index
> 1 = under budget; < 1 = over budget
SPI = EV ÷ PV
Schedule performance index
> 1 = ahead; < 1 = behind schedule
| Index value | Cost (CPI) | Schedule (SPI) |
|---|---|---|
| Greater than 1 | Under budget — favorable | Ahead of schedule — favorable |
| Exactly 1 | On budget | On schedule |
| Less than 1 | Over budget — unfavorable | Behind schedule — unfavorable |
2.3 Quality, risk & procurement
Quality means meeting requirements and fitness for use, and it’s built in, not inspected in. Distinguish (process-focused — are we following good processes?) from (product-focused — does the deliverable meet spec?). Prevention is cheaper than inspection, and the cost of quality includes both conformance and non-conformance costs.
Risk is uncertainty that matters. The process runs from planning through identifying, analyzing, responding, and monitoring, all tracked in the . Use to prioritize by probability and impact, and to model the numbers when stakes are high.[3]
- 1
Plan Risk Management
Define how risk will be identified, analyzed, and handled on this project.
- 2
Identify Risks
Find individual risks and overall project risk; record them in the risk register.
- 3
Perform Qualitative Analysis
Prioritize risks by probability × impact to focus attention.
- 4
Perform Quantitative Analysis
Numerically model the effect of top risks on cost and schedule (when needed).
- 5
Plan Risk Responses
Choose responses — threats: avoid/transfer/mitigate/accept/escalate; opportunities: exploit/share/enhance/accept/escalate.
- 6
Implement & Monitor Risks
Carry out responses, watch for new risks and triggers, and keep the register current.
| Threats (negative) | Opportunities (positive) |
|---|---|
| Avoid — eliminate the threat | Exploit — make the opportunity happen |
| Transfer — shift it (e.g., insurance) | Share — partner with someone who can capture it |
| Mitigate — reduce probability or impact | Enhance — increase probability or impact |
| Accept — take no active action | Accept — take no active action |
| Escalate — raise it above the project | Escalate — raise it above the project |
brings in goods or services from outside via contracts. Know the contract types and who bears the cost risk: a puts cost risk on the seller, while a puts more on the buyer; time-and-materials sits in between.
| Contract type | How it pays | Cost risk on |
|---|---|---|
| Fixed price (FP) | A set price for the work | Seller |
| Cost-reimbursable (CR) | Allowable costs plus a fee | Buyer |
| Time & materials (T&M) | Hourly/unit rates, no fixed total | Shared |
2.4 Agile & hybrid delivery
Half the exam touches agile, so know the frameworks. delivers work in fixed with three roles (product owner, scrum master, developers) and a set of ceremonies (planning, daily standup, review, retrospective). The product owner orders the ; the team forecasts using ; and the goal each iteration is a usable increment, often building toward a .[4]
is different: continuous flow with a visual board and work-in-progress (WIP) limits rather than sprints. Both are tools; a mixes them with predictive elements, to the project.
- 1
Sprint planning
The team selects backlog items it can complete and sets a sprint goal.
- 2
Daily standup
A short daily sync: progress, plan, and impediments to remove.
- 3
Development
The team builds a usable, potentially shippable increment.
- 4
Sprint review
Demo the increment to stakeholders and gather feedback.
- 5
Retrospective
Inspect how the team worked and commit to improvements.
| Aspect | Scrum | Kanban |
|---|---|---|
| Cadence | Fixed-length sprints | Continuous flow |
| Roles | Product owner, scrum master, developers | No prescribed roles |
| Work limits | Sprint backlog commitment | WIP limits per column |
| Change mid-cycle | Avoided during a sprint | Allowed any time |
Checkpoint · Process
Question 1 of 10
A project sponsor asks the project manager to choose a delivery approach for a new product. The requirements are well understood and unlikely to change, regulatory documentation must be produced at defined gates, and the customer expects a single final delivery. Which approach best fits these conditions?
Module 3 · Business Environment (8%)
The smallest domain on the current exam — 8%, about 14 questions — but growing. It connects the project to the wider organization: compliance, the value and benefits the project should deliver, and supporting organizational change. If you sit the new July 2026 exam, this domain jumps to 26%, so weight it accordingly.
3.1 Compliance & external changes
Projects don’t run in a vacuum. The PM plans and manages compliance with laws, regulations, standards, and organizational policy — for example data-privacy rules or industry regulations — and treats violations as risks to identify and address early. You also watch the external environment for changes (new regulations, market shifts, technology) and assess their impact, adjusting scope or plans through change control.[2]
Two terms anchor this: (EEFs) are conditions outside the team’s control that influence the project, and (OPAs) are the organization’s own processes, templates, and knowledge you draw on.
| Enterprise environmental factors | Organizational process assets | |
|---|---|---|
| What | Conditions outside the team's control | The org's own plans, processes & knowledge |
| Examples | Regulations, market, culture, infrastructure | Templates, policies, lessons learned, archives |
| You can change it? | Usually no — you adapt to it | Yes — and you add to it as you go |
3.2 Value, benefits & organizational change
The reason a project exists is in its : the documented justification showing the need, options, costs, and expected benefits. Projects are selected to deliver value, often compared using financial measures — (higher is better), , and (shorter is better).
is the point: confirming the intended value is actually achieved, which often happens after the project closes. A project can finish on time and on budget yet fail if the value never materializes. Finally, projects create change, so the PM supports organizational change management — preparing people to adopt the new way of working so the benefits stick.[3]
| Measure | What it tells you | Better when |
|---|---|---|
| Net present value (NPV) | Future cash flows discounted to today, minus cost | Higher (and positive) |
| Return on investment (ROI) | Percentage gain relative to cost | Higher |
| Payback period | Time to recover the initial investment | Shorter |
| Benefit-cost ratio (BCR) | Benefits divided by costs | Greater than 1 |
Checkpoint · Business Environment
Question 1 of 8
A project to launch a healthcare data platform must meet HIPAA privacy rules, OSHA workplace safety standards for the on-site install team, and an internal corporate coding standard. As the project manager begins planning compliance, what is the MOST useful first step?
How to Use This PMP Study Guide
This guide is built to be worked, not just read. The most efficient path to a pass:
- Build the mindset first. The Foundations module is short but high-leverage — the PMI mindset decides most scenario answers.
- Study by weight. Process (50%) and People (42%) are 92% of the exam — spend your time there, then Business Environment.
- Check off as you go. Use the Study Guide Contents to mark each section done; it raises your exam-readiness score.
- Take every checkpoint. The end-of-module quizzes show you exactly which domains need another pass.
- Drill the weak domain. Send your weak area into the flashcards and a practice test until the score climbs.
- Learn the reasoning. The PMP rewards judgment — understand why an answer is right, not just the fact.
PMP Concept Questions
Common PMP concepts candidates study across all three domains — each answered briefly and backed by an official PMI source. Test yourself, then drill them as flashcards.
PMP Glossary
The high-yield PMP terms in one place — hover any dotted term in the guide, or flip the whole deck here as a self-grading flashcard set.
- Actual cost
- AC — the real cost incurred for the work completed by a given date.
- Benefits realization
- Ensuring a project's intended business benefits and value are actually achieved, often after delivery.
- Budget at completion
- BAC — the total authorized budget for the project's planned work.
- Business case
- The documented justification for a project, showing its need, options, benefits, and costs.
- Change control board
- A formally chartered group that reviews, approves, or rejects requested changes to the project.
- Collaborating
- A conflict-resolution mode in which parties work together to a win-win solution; the most effective, durable approach.
- Compromising
- A conflict-resolution mode in which each party gives up something to reach a partial, lose-lose middle ground.
- Cost performance index
- CPI = EV ÷ AC; greater than 1 is under budget, less than 1 is over budget.
- Cost-reimbursable contract
- A contract paying the seller's allowable costs plus a fee; the buyer carries more cost risk.
- Crashing
- Compressing the schedule by adding resources to critical-path activities, which raises cost.
- Critical path
- The longest sequence of dependent activities through the schedule; it has zero total float and sets the shortest project duration.
- Earned value
- EV — the budgeted cost of the work actually completed by a given date.
- Earned value management
- An integrated method that combines scope, schedule, and cost to measure and forecast project performance.
- Emotional intelligence
- The ability to recognize and manage one's own emotions and to read and influence others' emotions.
- Enterprise environmental factors
- EEFs — conditions outside the team's control (culture, market, regulations) that influence the project.
- Estimate at completion
- EAC — the forecast total cost of the project; when current performance continues, EAC = BAC ÷ CPI.
- Fast tracking
- Compressing the schedule by performing activities in parallel that were planned in sequence, which raises risk.
- Fixed-price contract
- A contract with a set price; the seller carries most of the cost risk.
- Float
- The amount of time an activity can be delayed without delaying the project end date (total float) or the next activity (free float).
- Forcing
- A conflict-resolution mode that pushes one viewpoint at others' expense — a fast win-lose outcome.
- Hybrid approach
- A delivery approach that blends predictive and agile elements, tailored to the project and organization.
- Kanban
- An agile method based on visualizing work and limiting work in progress to improve continuous flow.
- Minimum viable product
- The smallest releasable version of a product that delivers value and enables learning.
- Net present value
- NPV — future cash flows discounted to today minus the investment; positive NPV adds value.
- Organizational process assets
- OPAs — an organization's plans, processes, policies, templates, and knowledge bases used on projects.
- Payback period
- The time it takes for a project's cumulative cash inflows to recover its initial investment.
- Planned value
- PV — the authorized budget assigned to the work scheduled to be done by a given date.
- Portfolio
- A collection of projects, programs, and operations managed as a group to achieve strategic objectives.
- Procurement
- Obtaining goods or services from outside the project team, governed by contracts.
- Product backlog
- An ordered, evolving list of everything that might be needed in the product, owned by the product owner.
- Program
- A group of related projects managed in a coordinated way to obtain benefits not available from managing them individually.
- Project
- A temporary endeavor undertaken to create a unique product, service, or result; it has a definite beginning and end.
- Project charter
- The document that formally authorizes the project, names the project manager, and gives authority to apply resources.
- Project life cycle
- The series of phases a project passes through from start to completion (e.g., starting, organizing/preparing, carrying out the work, closing).
- Qualitative risk analysis
- Prioritizing risks by assessing probability and impact, usually with a probability-and-impact matrix.
- Quality assurance
- Process-focused activities that build confidence the project will meet quality requirements (managing quality).
- Quality control
- Product-focused activities that verify deliverables meet requirements (controlling quality).
- Quantitative risk analysis
- Numerically modeling the combined effect of prioritized risks on cost and schedule objectives.
- RACI chart
- A responsibility assignment matrix marking who is Responsible, Accountable, Consulted, and Informed for each task.
- Return on investment
- ROI — the percentage gain from a project relative to its cost.
- Risk appetite
- The degree of uncertainty an organization or stakeholder is willing to accept in pursuit of reward.
- Risk register
- The artifact recording identified risks with their probability, impact, owner, and planned responses.
- Schedule performance index
- SPI = EV ÷ PV; greater than 1 is ahead of schedule, less than 1 is behind.
- Scope baseline
- The approved scope statement, work breakdown structure, and WBS dictionary used to measure scope performance.
- Scrum
- An agile framework delivering work in fixed timeboxes (sprints) with set roles and ceremonies.
- Servant leadership
- A leadership style focused on serving and developing the team — removing impediments and enabling a self-organizing team — rather than commanding it.
- Smoothing
- A conflict-resolution mode that emphasizes agreement over differences; a temporary fix.
- Sponsor
- The person or group that provides resources and support for the project and is accountable for enabling its success.
- Sprint
- A short, fixed-length iteration (often 1–4 weeks) in which a Scrum team produces a usable increment.
- Stakeholder
- Any individual, group, or organization that can affect, be affected by, or perceive itself to be affected by the project.
- Tailoring
- Deliberately adapting the approach, processes, and artifacts to fit the specific project context.
- Tuckman ladder
- The model of team development stages: forming, storming, norming, performing, and adjourning.
- Velocity
- The amount of work an agile team completes per iteration, used to forecast future capacity.
- Withdrawing
- A conflict-resolution mode that retreats from or postpones the conflict, leaving it unresolved.
- Work breakdown structure
- A hierarchical decomposition of the total project scope into deliverables and work packages; nothing outside it is in scope.
- Work package
- The lowest-level deliverable in the WBS — the unit you estimate, schedule, and assign.
PMP Study Guide FAQ
The current PMP exam has 180 questions and a 230-minute time limit, with one optional 10-minute break. Most are scenario-based multiple-choice, but you'll also see multiple-response, matching, hotspot, and fill-in-the-blank items. Answer every question — unscored pretest items are indistinguishable from scored ones.
On the current exam: People (42%), Process (50%), and Business Environment (8%). About half of all questions involve agile or hybrid approaches and the other half predictive (plan-driven) approaches, so PMI tests both across all three domains.
PMI does not publish a fixed percentage cut score. A panel of experts sets the passing standard, and your result is reported as pass/fail along with a performance rating per domain — Above Target, Target, Below Target, or Needs Improvement. Aim well above passing on practice tests to leave a margin.
Two pathways, both requiring 35 contact hours of project-management education (or a current CAPM): (1) a four-year degree plus 36 months leading projects within the last eight years, or (2) a high-school diploma or associate degree plus 60 months leading projects within the last eight years.
In the United States the PMP exam fee is $405 for PMI members and $555 for non-members; re-exams cost $275 (member) or $375 (non-member). Annual PMI membership is about $159, so members often save overall. Treat any price as a dated figure and confirm current fees on pmi.org before you apply.
Yes. PMI launches an updated PMP exam on July 9, 2026 that rebalances the domain weights to People 33%, Process 41%, and Business Environment 26%, with 180 questions over 240 minutes. The three domains stay the same — the new version simply emphasizes the business environment more. This guide teaches the current exam and flags the change.
You should know the core earned-value formulas — CPI = EV ÷ AC, SPI = EV ÷ PV, CV = EV − AC, SV = EV − PV, and EAC = BAC ÷ CPI — and be able to interpret them (below 1 is unfavorable). The exam tests applying and reading these indices in scenarios more than rote recall, but a handful of calculation questions do appear.
The PMP is challenging mainly because it's scenario-based and tests judgment — the 'PMI mindset' of servant leadership, proactive problem-solving, and value delivery — rather than memorized facts. Study by weight (Process and People are 92% of the exam), learn the agile and predictive approaches, take every checkpoint, and drill with our free practice test and flashcards.
Yes — the full guide, the checkpoints, the glossary, the practice test, and the flashcards are 100% free with no account required.
References
- 1.Project Management Institute. “Project Management Professional (PMP) Certification.” pmi.org. ↑
- 2.Project Management Institute. “PMP Examination Content Outline (ECO).” pmi.org. ↑
- 3.Project Management Institute. “A Guide to the Project Management Body of Knowledge (PMBOK Guide), 7th ed..” pmi.org. ↑
- 4.Project Management Institute. “Agile Practice Guide.” pmi.org. ↑
- 5.Project Management Institute. “New PMP Exam (effective July 9, 2026).” pmi.org. ↑
- 6.Project Management Institute. “PMP Handbook (eligibility, fees & scoring).” pmi.org. ↑

Career Employer
Career Employer is the ultimate resource to help you get started working the job of your dreams. We cover topics from general career information, career searching, exam preparation with free study materials, career interviewing, and becoming successful in your career of choice.
All PostsCareer Employer’s Editorial Process
Here at Career Employer, we focus a lot on providing factually accurate information that is always up to date. We strive to provide correct information using strict editorial processes, article editing, and fact-checking for all of the information found on our website. We only utilize trustworthy and relevant resources. To find out more, make sure to read our full editorial process page here.
