PMP® Certification Prep

Full-length 180-question practice exam covering all three domains — People, Process, and Business Environment — with PMI's official performance rating system and comprehensive study guides.

Exam Domains

👥

Domain I: People — 42%

Leadership, team building, conflict management, stakeholder engagement, emotional intelligence, and servant leadership across predictive, agile, and hybrid approaches.

📝 ~76 Questions👤 14 Tasks

⚙️

Domain II: Process — 50%

Planning, executing, delivering value, managing changes, risk, quality, procurement, scope, schedule, cost, and communications management.

📝 ~90 Questions📋 17 Tasks

📊

Domain III: Business Environment — 8%

Benefits realization, compliance, organizational change, project governance, and aligning projects with organizational strategy.

📝 ~14 Questions🏢 4 Tasks

PMP Exam & Scoring

The PMP exam consists of 180 questions to be completed in 230 minutes (3 hrs 50 min). Of these, 175 are scored and 5 are unscored pretest items. Questions are split approximately 50/50 between predictive (waterfall) and agile/hybrid approaches.

PMI Performance Rating Categories: PMI does not publish a fixed passing percentage. Instead, your score report rates each domain on a 4-point scale:
Above Target (AT): Exceeds minimum requirements
Target (T): Meets minimum requirements
Below Target (BT): Slightly below, additional prep recommended
Needs Improvement (NI): Significantly below, substantial prep needed

This practice test scores your performance by domain and assigns performance ratings matching PMI's system. Industry experts suggest scoring ~70% or higher on practice exams to feel confident about passing the real PMP exam.

Exam Format: Multiple-choice (single answer), multiple-response (select all that apply), matching, hotspot, and fill-in-the-blank. About half the questions test predictive approaches and half test agile/hybrid. Two 10-minute breaks are provided (after questions 60 and 120).

Study Guides

Comprehensive guides for all three PMP exam domains covering predictive, agile, and hybrid approaches.

👥 Domain I: People (42% of Exam)

The People domain is the largest portion of the PMP exam. It focuses on the skills and activities associated with leading and managing the project team and stakeholders. It covers 14 tasks.

1. Manage Conflict

Conflict is inevitable on projects. Effective project managers handle it proactively rather than avoiding it.

Conflict Resolution Techniques

Collaborate/Problem Solve (Win-Win): Address the root cause; best for long-term resolution. Both parties satisfied.
Compromise/Reconcile (Lose-Lose): Each party gives up something. Neither fully satisfied but workable.
Smooth/Accommodate: Emphasize agreement over differences. Temporary solution.
Force/Direct: One party wins, one loses. Used when quick decisions are needed or safety is at risk.
Withdraw/Avoid: Retreat from conflict. Rarely solves the issue. Use only as a last resort or cooling-off period.

Exam Favorite: PMI strongly prefers Collaborate/Problem Solve as the best conflict resolution approach. If the question doesn't specify constraints, this is usually the correct answer.

2. Lead a Team

Leadership Styles

Servant Leadership: Focus on serving the team's needs, removing impediments, empowering team members. PMI's preferred leadership style for agile environments.
Transformational: Inspire and motivate through vision and purpose. Drive meaningful change.
Transactional: Focus on tasks, rewards, and penalties. Effective for routine work.
Laissez-faire: Hands-off approach. Works with highly skilled, self-managing teams.
Situational: Adapt style based on team maturity and project needs. Considered the most versatile approach.

Tuckman's Team Development Model

Stage Characteristics PM Action Forming Polite, cautious, getting oriented Provide direction & structure Storming Conflict, power struggles Facilitate, manage conflict Norming Trust develops, collaboration Support, delegate more Performing High efficiency, self-managing Empower, remove obstacles Adjourning Team disperses, project ends Recognize, celebrate, transition

3. Support Team Performance

Training & development: Identify skill gaps, provide learning opportunities, build cross-functional skills.
Recognition & rewards: Acknowledge contributions promptly. Team and individual recognition.
Emotional Intelligence (EQ): Self-awareness, self-regulation, motivation, empathy, social skills. Critical for effective PM leadership.

4. Empower Team Members & Stakeholders

Delegation: Give team authority to make decisions at their level. Builds ownership and accountability.
Self-organizing teams: In agile, teams choose how to accomplish work. The PM facilitates rather than directs.
Shared decision-making: Involve stakeholders in appropriate decisions to increase buy-in.

5. Stakeholder Engagement

Stakeholder Analysis & Management

Identify stakeholders: Anyone affected by or who can affect the project. Document in stakeholder register.
Power/Interest Grid: High Power/High Interest → Manage Closely. High Power/Low Interest → Keep Satisfied. Low Power/High Interest → Keep Informed. Low Power/Low Interest → Monitor.
Engagement levels: Unaware → Resistant → Neutral → Supportive → Leading. Move stakeholders toward Supportive.

Key Principle: Stakeholder engagement is an ongoing activity throughout the project lifecycle, not a one-time event. Regularly assess and adapt engagement strategies as the project evolves.

6. Build Shared Understanding

Ground rules: Establish team norms, working agreements, and definitions of done early.
Communication: Use appropriate channels, be transparent, create psychological safety.
Cultural awareness: Respect diverse backgrounds, time zones, communication styles.

7. Negotiate & Manage Agreements

Negotiation applies to scope, schedule, resources, contracts, and conflict. Key principles: focus on interests not positions, create win-win solutions, use objective criteria, separate people from problems.

8. Agile People Practices

Scrum roles: Product Owner (defines what), Scrum Master (facilitates how), Development Team (builds product).
Daily standups: What did I do yesterday? What will I do today? Any impediments?
Retrospectives: What went well? What needs improvement? What actions will we take?
Velocity: Team's capacity measured in story points per iteration.

PMI Mindset: ~50% of exam questions involve agile/hybrid approaches. Know Scrum, Kanban, servant leadership, self-organizing teams, iterative delivery, and adaptive planning.

⚙️ Domain II: Process (50% of Exam)

The Process domain covers the technical aspects of managing a project — from initiation through closing. It encompasses 17 tasks and is the largest exam domain by question count.

1. Project Integration

Project Charter

Formally authorizes the project. Created by the project sponsor (NOT the PM). Contains: business case, objectives, high-level scope, budget, timeline, key stakeholders, PM authority level.

Change Management

Change Control Board (CCB): Reviews, approves/rejects change requests. The PM does NOT unilaterally approve scope changes.
Integrated Change Control: Evaluate impact of changes on scope, schedule, cost, quality, risk, and resources before approving.
Configuration management: Track and control versions of project deliverables and documents.

Exam Rule: NEVER make a scope/schedule/cost change without going through the formal change control process. Even if the sponsor asks verbally, document it as a change request first.

2. Scope Management

Predictive (Waterfall)

Scope statement: Detailed description of deliverables and acceptance criteria.
WBS (Work Breakdown Structure): Hierarchical decomposition of total project scope into manageable work packages. The 100% rule — WBS must include 100% of the project scope.
Scope baseline: Scope statement + WBS + WBS dictionary. Changes require formal change control.

Agile Scope

Product Backlog: Prioritized list of features/user stories. Continuously refined (grooming/refinement).
User Stories: "As a [user], I want [feature] so that [benefit]." Include acceptance criteria.
Sprint Backlog: Items pulled from Product Backlog for the current iteration.
Scope is flexible in agile: Time and cost are fixed; scope varies based on priorities.

3. Schedule Management

Predictive Tools

Critical Path Method (CPM): Longest path through the network diagram. Determines minimum project duration. Zero float = critical path activity.
PERT Estimates: (Optimistic + 4×Most Likely + Pessimistic) ÷ 6. Three-point estimating reduces bias.
Gantt Charts: Visual timeline showing task duration, dependencies, and progress.
Schedule Compression: Crashing (add resources, increases cost) or Fast Tracking (overlap activities, increases risk).

Agile Schedule

Iterations/Sprints: Fixed time-boxes (typically 1-4 weeks). Deliver working increment each sprint.
Velocity: Average story points completed per sprint. Used for forecasting.
Burndown chart: Shows remaining work vs. time. Trending above the ideal line = behind schedule.
Release planning: How many sprints needed to deliver a release based on velocity and backlog size.

Critical Path Example: Task A (3 days) → Task B (5 days) → Task D (2 days) = 10 days Task A (3 days) → Task C (4 days) → Task D (2 days) = 9 days Critical Path = A → B → D (10 days, longest path) Float on Task C = 10 - 9 = 1 day

4. Cost Management

Earned Value Management (EVM): Integrates scope, schedule, and cost to measure performance.

EVM Formulas (MUST MEMORIZE): PV (Planned Value) = Budgeted cost of work scheduled EV (Earned Value) = Budgeted cost of work performed AC (Actual Cost) = Actual cost of work performed SV (Schedule Variance) = EV - PV (positive = ahead) CV (Cost Variance) = EV - AC (positive = under budget) SPI (Schedule Index) = EV / PV (>1 = ahead) CPI (Cost Index) = EV / AC (>1 = under budget) EAC (Estimate at Completion) = BAC / CPI ETC (Estimate to Complete) = EAC - AC VAC (Variance at Completion) = BAC - EAC

Critical for Exam: EVM questions appear frequently. Know: CPI > 1 = under budget (good). SPI > 1 = ahead of schedule (good). Negative CV or SV = problems. Practice calculating EAC and ETC.

5. Quality Management

Plan Quality: Define quality standards, metrics, and processes. Cost of Quality (COQ) = Prevention + Appraisal + Failure costs.
Manage Quality (Quality Assurance): Audit processes to ensure standards are followed. Proactive.
Control Quality (Quality Control): Inspect deliverables to ensure they meet requirements. Reactive.
Tools: Pareto charts (80/20 rule), fishbone/Ishikawa diagrams (root cause), control charts (process stability), histograms, scatter diagrams.

6. Risk Management

Risk Register: Document all identified risks, owners, probability, impact, response strategies.
Qualitative Analysis: Probability × Impact matrix. Prioritize risks.
Quantitative Analysis: Monte Carlo simulation, decision trees. Numerical analysis of risk impact.

Risk Response Strategies

Negative Risks (Threats): Positive Risks (Opportunities): Avoid — Eliminate the risk Exploit — Ensure it happens Transfer — Shift to third party Share — Partner to capture benefit Mitigate — Reduce probability/impact Enhance — Increase probability/impact Accept — Acknowledge and budget for Accept — Acknowledge without action Escalate — Beyond PM authority Escalate — Beyond PM authority

7. Resource & Procurement Management

RACI Matrix: Responsible, Accountable, Consulted, Informed. Only ONE person Accountable per task.
Contract Types: Fixed Price (buyer risk ↓), Cost Reimbursable (buyer risk ↑), Time & Materials (hybrid).
Make-or-buy analysis: Should we build in-house or purchase/contract externally?

8. Communications Management

Communication channels formula: n(n-1)/2 where n = number of stakeholders.
Communication methods: Push (email, reports), Pull (wiki, intranet), Interactive (meetings, calls).
Communication model: Sender → Encode → Message → Decode → Receiver → Feedback.

9. Agile Process Artifacts

Sprint Review: Demo working product to stakeholders. Get feedback. Adapt backlog.
Sprint Retrospective: Team reflects on process improvement. What to start, stop, continue.
Kanban board: Visualize workflow: To Do → In Progress → Done. Limit WIP (Work in Progress).
Definition of Done (DoD): Shared understanding of what "complete" means. Applied to every increment.

📊 Domain III: Business Environment (8% of Exam)

While the smallest domain, Business Environment questions test your understanding of how projects connect to organizational strategy, governance, and value delivery. It covers 4 tasks.

1. Plan & Manage Project Compliance

Regulatory compliance: Legal, safety, environmental, industry standards that the project must satisfy.
Organizational compliance: Internal policies, governance frameworks, quality management systems.
Compliance categories: Legal/regulatory, health & safety, quality standards (ISO), environmental, data protection (GDPR/HIPAA).
PM responsibility: Ensure the project meets ALL applicable compliance requirements throughout the lifecycle.

2. Evaluate & Deliver Project Benefits & Value

Benefits Realization

Business case: Justification for the project. Includes cost-benefit analysis, ROI, NPV, IRR, payback period.
Benefits management plan: How and when benefits will be realized. Benefits may extend beyond project completion.
Value delivery: In agile, value is delivered incrementally with each iteration. MVP (Minimum Viable Product) delivers core value early.

Financial Selection Criteria: NPV (Net Present Value) Higher NPV = better investment IRR (Internal Rate of Return) Higher IRR = better return ROI (Return on Investment) Higher ROI = better return Payback Period Shorter = faster investment recovery BCR (Benefit-Cost Ratio) >1 = benefits outweigh costs

Exam Tip: When asked which project to select, choose the one with the highest NPV (not just highest ROI or shortest payback). NPV accounts for the time value of money and is PMI's preferred metric.

3. Evaluate & Address External Changes

External factors: Market conditions, regulations, technology changes, economic shifts, competitor actions.
Enterprise Environmental Factors (EEFs): External conditions that influence the project (market, regulations, culture, infrastructure).
Organizational Process Assets (OPAs): Internal plans, policies, procedures, historical information, lessons learned.
Adaptability: Project managers must continuously scan the environment and adjust project approach as external conditions change.

4. Support Organizational Change

Change management (organizational): Helping people adopt new processes, tools, or structures resulting from the project.
Stakeholder impact assessment: Who is affected by the change? How will they be affected? What support do they need?
Transition & readiness: Training, documentation, communications, pilot/phased rollout to ease adoption.
Resistance management: Address concerns, involve people in the change process, communicate the "why" behind the change.

Key Insight: The PM is responsible for ensuring the project's deliverables can be successfully integrated into the organization. Technical delivery is not enough — organizational readiness and change adoption are equally critical.

5. Governance & Structure

PMO (Project Management Office): Supportive (templates/guidance), Controlling (compliance/oversight), Directive (directly manages projects).
Organizational structures: Functional (PM has little authority), Matrix (shared authority), Projectized (PM has most authority).
Project governance: Framework for decision-making, escalation, and oversight. Includes roles, policies, and approval processes.

6. Ethics & Professional Responsibility

PMI's Code of Ethics requires: Responsibility, Respect, Fairness, and Honesty. Key points:

Report unethical behavior and violations.
Respect cultural differences and intellectual property.
Avoid conflicts of interest or disclose them transparently.
Provide accurate information; never falsify reports or credentials.
Make decisions in the best interest of society, public safety, and stakeholders.

Ethics on the Exam: When ethical dilemmas appear, always choose the answer that involves transparency, disclosure, and following established processes. Never hide information, even if it reflects poorly on the project.

PMP Full-Length Practice Exam

180 questions across 3 domains, simulating real PMP timing with performance rating scoring.

👥

People — 42%

~76 questions on leadership, team dynamics, stakeholder engagement, conflict resolution, and emotional intelligence.

⏱ Included in 230 min

⚙️

Process — 50%

~90 questions on planning, executing, monitoring, change control, risk, quality, schedule, cost, and agile delivery.

⏱ Included in 230 min

📊

Business Environment — 8%

~14 questions on compliance, benefits realization, organizational change, governance, and strategy alignment.

⏱ Included in 230 min

180 questions | 230 minutes | Performance rated per domain

No Results Yet

Complete a practice exam to see your score report.