Domain 1: People
- Servant leadership is the PMI-preferred stance: the project manager removes impediments, shields the team from distractions, and enables a self-organizing team rather than assigning tasks and micromanaging.
- Tuckman's model describes team development as forming, storming, norming, performing, and adjourning; conflict is normal in the storming stage, and the leader's job is to coach the team through it, not to avoid or suppress it.
- The Thomas-Kilmann conflict modes are collaborating/problem solving, compromising, smoothing/accommodating, forcing/directing, and withdrawing/avoiding; collaborating (confronting the problem to find a win-win) is generally the best and most durable resolution.
- Forcing and withdrawing are usually the least desirable conflict approaches because forcing creates lose-win resentment and withdrawing only postpones the underlying issue.
- Motivation theories inform how you engage a team: Maslow's hierarchy of needs, Herzberg's hygiene factors versus motivators, McGregor's Theory X and Theory Y, and McClelland's needs for achievement, affiliation, and power.
- A team charter is created with the team and captures shared values, ground rules, working agreements, communication norms, and decision-making and conflict-resolution processes, giving the team ownership of how they will work together.
- Emotional intelligence - self-awareness, self-management, social awareness, and relationship management - lets a project manager read the room, manage their own reactions, and build the trust needed to influence without formal authority.
- A RACI chart clarifies who is Responsible, Accountable, Consulted, and Informed for each activity; exactly one person should be Accountable for any given deliverable to avoid diffusion of ownership.
- Removing impediments (blockers) is a core servant-leader duty, mirroring the Scrum Master role; the project manager escalates blockers the team cannot resolve on its own and protects the team's focus and sustainable pace.
- Virtual and distributed teams need deliberate attention to communication tools, overlapping working hours, inclusion across cultures and time zones, and richer channels (video over email) to preserve engagement and psychological safety.
- Negotiation should aim for principled, interest-based agreements (win-win) rather than positional bargaining; knowing your best alternative to a negotiated agreement (BATNA) strengthens your position while preserving the relationship.
Domain 2: Process
- Selecting a development approach - predictive, agile, or hybrid - depends on how clear and stable the requirements are, how much change is expected, and how quickly value must be delivered; stable, well-understood work suits predictive, while high-uncertainty work suits an adaptive approach.
- The project charter formally authorizes the project, names the project manager and their authority, and captures high-level objectives, assumptions, and constraints; the project management plan then defines how the work will be executed, monitored, and controlled.
- Scope is defined through requirements collection and a work breakdown structure (WBS) in predictive projects, or through a prioritized product backlog (using techniques such as MoSCoW) in adaptive projects; scope creep (uncontrolled change) and gold plating (adding unrequested extras) are both to be avoided.
- The critical path is the longest sequence of dependent activities and determines the shortest possible project duration; activities on the critical path have zero float (slack), so delays there delay the whole project.
- Schedule compression uses crashing (adding resources, which raises cost) or fast-tracking (running activities in parallel, which raises risk); you choose based on whether the constraint is budget or risk tolerance.
- Estimating techniques include analogous (top-down, based on similar past work), parametric (rate times quantity), and three-point/PERT estimating - (Optimistic + 4 x Most Likely + Pessimistic) / 6 - which accounts for uncertainty.
- Earned value management compares planned value (PV), earned value (EV), and actual cost (AC): cost variance CV = EV - AC, schedule variance SV = EV - PV, cost performance index CPI = EV / AC, and schedule performance index SPI = EV / PV; an index above 1.0 is favorable and below 1.0 is unfavorable.
- Risk responses differ for threats (avoid, transfer, mitigate, accept, or escalate) and opportunities (exploit, share, enhance, accept, or escalate); risks are logged in the risk register with an owner, and contingency reserves cover known risks while management reserves cover unknown risks.
- The number of communication channels grows as n(n-1)/2 where n is the number of stakeholders, so adding people increases communication complexity quickly; communication methods are interactive (two-way), push (sent out), and pull (self-served).
- Contract types allocate risk differently: fixed-price puts cost risk on the seller, cost-reimbursable puts it on the buyer, and time-and-materials sits in between; a make-or-buy analysis decides whether to procure the work at all.
- Agile delivery runs on a cadence of iterations with ceremonies - sprint/iteration planning, the daily standup, the review (demonstrating a working increment for feedback), and the retrospective (inspecting and adapting the process) - to deliver value incrementally, often starting with a minimum viable product (MVP).
Domain 3: Business Environment
- The business case justifies the project by linking it to a business need and expected benefits; the project manager continually checks that the project still supports organizational strategy and recommends terminating it if it no longer delivers value.
- A benefits management plan defines the target benefits, how and when they will be measured (for example ROI, net present value, internal rate of return, or payback period), and who owns realizing them after the project closes.
- Understand the hierarchy: a project creates a specific product or result, a program coordinates related projects for combined benefit, and a portfolio groups programs and projects to achieve strategic objectives; governance operates across all three.
- Organizational change management prepares people to adopt the project's deliverable; models such as ADKAR (Awareness, Desire, Knowledge, Ability, Reinforcement) and Kotter's 8 steps help move stakeholders from resistance to adoption.
- Compliance requirements - legal, regulatory, security, privacy, and health and safety - must be identified early, categorized, and prioritized by risk; ignoring compliance can invalidate an otherwise successful deliverable.
- PESTLE analysis (political, economic, social, technological, legal, environmental) scans the external environment for changes that could affect the project, so the team can adjust scope, backlog priorities, or approach in response.
- Enterprise environmental factors (EEFs) are conditions outside the team's control that influence the project (market conditions, organizational culture, regulations), while organizational process assets (OPAs) are the organization's reusable plans, templates, policies, and lessons learned.
- Delivering value incrementally lets the organization begin realizing benefits and reduce risk before the entire scope is complete, which is central to both agile and modern hybrid delivery.
- Project managers support ongoing improvement by capturing and sharing lessons learned and by tracking measures such as key performance indicators (KPIs) and objectives and key results (OKRs) that connect delivery to organizational outcomes.
- External and internal changes cut both ways: the project affects the organization (new capabilities, disruption during transition) and the organization affects the project (strategy shifts, funding changes), and the project manager manages both directions proactively.
- Evaluating and addressing changes to the business environment is an ongoing responsibility, not a one-time analysis; the project manager reassesses the business case, backlog, and priorities as conditions evolve.
PMP exam tips
- Answer with the PMI mindset, not real-world shortcuts: prefer talking directly to people, addressing the root cause over the symptom, being proactive, and collaborating; the option that empowers the team and protects value is usually correct, even when a quicker workaround exists.
- Roughly half the exam is agile or hybrid, so know servant leadership, the core ceremonies (planning, standup, review, retrospective), backlog prioritization, and incremental value delivery as well as you know predictive tools; many scenarios hinge on picking the right response for the development approach described.
- Master the earned value formulas cold - CV = EV - AC, SV = EV - PV, CPI = EV / AC, SPI = EV / PV - and remember that variances above zero and indices above 1.0 are favorable; these underpin many calculation and interpretation questions.
- For conflict questions, default toward collaborating/problem solving to reach a win-win, then compromising; treat forcing and avoiding as last resorts, and remember that conflict is best addressed early, directly, and in private.
- When a scenario asks what to do first or next, prefer understanding the situation (gather information, analyze the impact, consult the plan or risk register) before escalating, and escalate only what is truly beyond your authority or the team's ability to resolve.
Study guide FAQ
What format and length does the PMP exam have?
The PMP exam has 180 questions to be completed in 230 minutes, with two optional 10-minute breaks. Item types include multiple choice, multiple response (choose two or more), matching, hotspot, and a small number of fill-in-the-blank questions.
What passing score do I need?
PMI does not publish a fixed passing percentage. The exam is scored using psychometric analysis, and your result is reported as an overall pass or fail along with a proficiency rating (Above Target, Target, Below Target, or Needs Improvement) for each of the three domains, so it is best to aim for solid, consistent performance across People, Process, and Business Environment.
What are the eligibility requirements to sit the exam?
You need either a four-year degree with 36 months of project management experience and 35 hours of project management education (or CAPM certification), or a high school diploma/associate degree with 60 months of experience and 35 hours of education. The 35 contact hours can be satisfied by qualifying training such as PMI's own courses.
How much of the exam is agile versus predictive?
Approximately half of the questions reflect predictive (waterfall) approaches and about half reflect agile or hybrid approaches. You should be comfortable with servant leadership, iterations and ceremonies, and backlog-driven delivery, not just classic tools like the WBS and critical path.
Which reference materials is the exam based on?
The exam is aligned to the PMP Examination Content Outline (ECO) and draws on the current PMBOK Guide and the Agile Practice Guide. Note that the exam is not a direct test of the PMBOK Guide alone; it tests applied judgment across all three ECO domains and multiple delivery approaches.