📘 PMP® Examination Content Outline
Project Management Professional (PMP)® — January 2021 | Complete Interactive Study Guide
180 Questions
230 Minutes
3 Domains
50% Agile/Hybrid
50% Predictive
📌 Introduction
The PMI (Project Management Institute) PMP® exam is globally recognized as the premier project management certification. The exam is criterion-referenced, meaning every question is tied to real project manager job tasks validated through a Global Practice Analysis (GPA) and Job Task Analysis (JTA).
The PMP exam is NOT based solely on the PMBOK® Guide. It reflects real-world practice and covers predictive, agile, and hybrid approaches equally.
Accredited against ISO 9001 and ISO/ANSI 17024 standards. This means every question is validated by real practitioners, not textbooks alone.
About ~50% predictive and ~50% agile/hybrid questions — distributed across ALL three domains. Don't study agile only in one section!
📊 Exam Structure & Format
| Item | Details |
|---|---|
| Total Questions | 180 (175 scored + 5 pretest) |
| Time Allotted | 230 minutes (≈77 sec/question) |
| Breaks | 2 optional breaks: after Q60 and after Q120 |
| Pretest Qs | 5 unscored questions hidden among scored ones |
| Retakes | Up to 3 attempts within 1-year eligibility period |
| Delivery | Computer-based (center) or online proctored |
Once you finish Q60 or Q120 and start a break, you CANNOT go back to the previous section. Plan your time carefully — the 230 minutes runs across all 3 sections combined.
Pace yourself: 230 min / 180 Qs = ~77 seconds per question. Flag difficult questions and return. Don't spend more than 2 minutes on any single question during the first pass.
You're at question 58 and notice you've used 95 minutes. You're slightly ahead of pace (should be at ~75 min). Continue confidently — you have a small buffer. At Q60, review flagged answers, then take your optional break to reset mentally.
🗂️ Three Domains Overview
Domain breakdown memory trick: "People Own Process — Business is Last!"
People = 42% | Process = 50% | Business = 8% → Total = 100%
People = 42% | Process = 50% | Business = 8% → Total = 100%
Domain II (Process) carries the most weight at 50%. But Domain I (People) questions are often the trickiest because they require judgment about leadership, not just knowledge of processes.
✅ My Study Progress Tracker
Auto-saved to your browser. Check off each domain task as you study it!
👥 DOMAIN I: PEOPLE — 42% of Exam (~74 Questions)
This domain tests your ability to lead, motivate, empower, and guide project teams and stakeholders. It emphasizes servant leadership, emotional intelligence, conflict resolution, and team building across predictive and agile environments.
Task 1: Manage Conflict
- Interpret the source and stage of the conflict
- Analyze the context for the conflict
- Evaluate/recommend/reconcile the appropriate conflict resolution solution
What it is: Conflict management is the process of identifying, analyzing, and resolving disputes within the project team or with stakeholders. Conflicts can arise from schedule pressures, resource allocation, technical opinions, personalities, priorities, costs, or administrative procedures.
The 5 Conflict Resolution Techniques (Thomas-Kilmann Model)
| Technique | Also Called | When to Use | Outcome |
|---|---|---|---|
| Collaborate | Problem-Solve / Confront | Best long-term; when time permits | Win-Win ⭐ |
| Compromise | Reconcile | Both parties give up something | Lose-Lose (partial) |
| Smooth/Accommodate | Accommodate | Preserve relationship short-term | Yield |
| Force/Direct | Direct | Emergency or safety | Win-Lose |
| Withdraw/Avoid | Avoid | Buy time; low priority | Lose-Leave |
The PMP exam ALWAYS favors Collaborate/Problem-Solve as the best approach unless the scenario has an emergency or time constraint. If you see "best approach," think Collaborate first.
Two developers disagree on the architecture approach. One prefers microservices; the other prefers monolithic. As PM, you arrange a facilitated technical session where both present pros/cons, then the team agrees on a hybrid approach. ✅ This is Collaborate/Problem-Solve — the PMP preferred answer.
The 5 stages of conflict (Tuckman-adjacent): Latent → Perceived → Felt → Manifest → Aftermath. In the exam, "manifest" conflict means it's visible and active — most critical to address immediately.
A team member refuses to meet deadlines because they believe the schedule is unrealistic. The PM acknowledges the concern (smooth), then schedules a working session to re-examine the schedule with data (collaborate). This two-step approach is common on the exam.
Task 2: Lead a Team
- Set a clear vision and mission
- Support the team's varied experiences and perceptions
- Value servant leadership
- Determine an appropriate leadership style (directive, collaborative)
- Inspire, motivate, and influence team members/stakeholders
- Analyze team members and stakeholders' influence
What it is: Leadership is about inspiring people to accomplish shared project goals. The PMP exam heavily tests whether you understand WHEN to use which leadership style and WHY.
Key Leadership Styles
| Style | Description | When Used |
|---|---|---|
| Servant Leader | Removes obstacles, enables team | Agile/Scrum PM role ⭐ |
| Directive | Tells team what to do | Crisis, new/junior team |
| Collaborative | Involves team in decisions | Experienced, cross-functional teams |
| Laissez-faire | Hands-off, team is self-directed | Expert/autonomous teams |
| Transformational | Inspires vision and change | Change initiatives |
| Transactional | Reward/penalty system | Predictive, contract-based work |
The PMP exam strongly favors Servant Leadership and Collaborative Leadership. If a question asks "how should the PM respond?", the best answer usually involves removing barriers, facilitating decisions, or empowering the team — NOT commanding them.
Motivation Theories Quick Reference:
• Maslow's Hierarchy: Physiological → Safety → Social → Esteem → Self-Actualization
• Herzberg: Hygiene factors (salary, conditions) prevent dissatisfaction; Motivators (achievement, recognition) create satisfaction
• McGregor Theory X/Y: X=people hate work (directive); Y=people enjoy work (collaborative)
• McClelland: Need for Achievement, Affiliation, Power
• Expectancy Theory: People act based on expected rewards
• Maslow's Hierarchy: Physiological → Safety → Social → Esteem → Self-Actualization
• Herzberg: Hygiene factors (salary, conditions) prevent dissatisfaction; Motivators (achievement, recognition) create satisfaction
• McGregor Theory X/Y: X=people hate work (directive); Y=people enjoy work (collaborative)
• McClelland: Need for Achievement, Affiliation, Power
• Expectancy Theory: People act based on expected rewards
Your agile team is highly experienced and self-organizing. A new PM is inclined to control every task. As a PMP, the correct action is to adopt a servant leadership style — ask the team what they need, remove blockers, and facilitate retrospectives. Don't micromanage!
Task 3: Support Team Performance
- Appraise team member performance against KPIs
- Support and recognize team member growth and development
- Determine appropriate feedback approach
- Verify performance improvements
What it is: Continuously monitoring how individuals and the team perform, and coaching them to improve. This includes both formal performance appraisals and informal daily coaching.
The PMP exam often asks about feedback. Remember: feedback should be timely, specific, and behavior-focused — not personal. "You missed the deadline" is bad. "The report was due Monday; let's discuss what caused the delay" is good.
A team member consistently delivers low-quality code. Rather than escalating to HR immediately, the PM first discusses specific quality metrics with the member, sets improvement targets, provides training resources, and schedules a 2-week check-in. This coaching approach is the PMP-preferred answer.
Tuckman's Team Development Stages
| Stage | What Happens | PM's Role |
|---|---|---|
| Forming | Team meets, excited but uncertain | Direct, set expectations |
| Storming | Conflicts emerge, roles questioned | Coach, manage conflict |
| Norming | Team finds rhythm, norms established | Support, facilitate |
| Performing | High performance, self-directed | Delegate, remove obstacles |
| Adjourning | Project ends, team disbands | Celebrate, document lessons |
If the exam describes team conflict or role confusion, the team is in Storming. If the team is highly productive and collaborative, they're in Performing. The PM's response should match the stage!
Task 4: Empower Team Members and Stakeholders
- Organize around team strengths
- Support team task accountability
- Evaluate demonstration of task accountability
- Determine and bestow level(s) of decision-making authority
What it is: Empowerment means giving team members ownership and authority to make decisions within their scope. In agile, this is central — self-organizing teams decide HOW to do the work.
In a Scrum project, the Development Team (not the Scrum Master or Product Owner) decides how many items to take from the backlog into a sprint. If the PM tries to dictate the sprint capacity, they are NOT empowering the team — this is a wrong answer on the exam.
Empowerment ≠ Abandonment. The PM sets boundaries and provides resources, but lets the team own the execution. Think of it as giving someone the steering wheel while you help with the map.
RAM / RACI Chart — Who does what:
R = Responsible (does the work) | A = Accountable (one person, owns result) | C = Consulted (provides input) | I = Informed (kept in the loop)
R = Responsible (does the work) | A = Accountable (one person, owns result) | C = Consulted (provides input) | I = Informed (kept in the loop)
Task 5: Ensure Team Members/Stakeholders Are Adequately Trained
- Determine required competencies and elements of training
- Determine training options based on training needs
- Allocate resources for training
- Measure training outcomes
What it is: Identifying skill gaps and filling them with appropriate training to ensure the team can successfully execute project work.
You're managing a digital transformation project. Your team has strong process skills but limited data analytics knowledge. You identify this gap early, arrange a 2-day data visualization workshop, allocate budget from contingency, and measure outcomes by assessing team deliverable quality after training.
Training costs are a direct project cost. They should be planned in the project budget during the planning phase — not treated as an afterthought when gaps are discovered mid-project.
Task 6: Build a Team
- Appraise stakeholder skills
- Deduce project resource requirements
- Continuously assess and refresh team skills
- Maintain team and knowledge transfer
What it is: Acquiring and developing the right people for the right roles. Team building is both a planning activity (choosing who's on the team) and an ongoing activity (growing their capabilities).
Team Building Activities (PMP Exam Context):
• Co-location (War Room) — physical proximity boosts collaboration
• Virtual team tools — Zoom, Slack, collaboration platforms
• Team social events — improve relationships
• Training workshops — build competency
• Ground rules — establish behavioral norms
• Co-location (War Room) — physical proximity boosts collaboration
• Virtual team tools — Zoom, Slack, collaboration platforms
• Team social events — improve relationships
• Training workshops — build competency
• Ground rules — establish behavioral norms
The PMP exam may ask about building a virtual global team. Remember: cultural differences, time zones, and language barriers must be explicitly addressed in your communication and team-building plans.
Task 7: Address and Remove Impediments, Obstacles, and Blockers
- Determine critical impediments, obstacles, and blockers
- Prioritize them
- Use network to implement solutions
- Re-assess continually
What it is: The PM/Scrum Master's classic servant leadership role — clearing the path so the team can work without friction.
Your agile team reports that they're waiting on approval from the Legal department for 3 sprints. As the PM/Scrum Master, you escalate to the Legal VP, arrange a dedicated reviewer for the project, and the impediment is resolved in 2 days. This is the PMP-correct "use your network" approach.
In agile: Scrum Master removes impediments. In predictive: the Project Manager removes impediments. But the PMP approach is always: identify → prioritize → escalate if needed → resolve → monitor. Never ignore or wait passively.
Task 8: Negotiate Project Agreements
- Analyze the bounds of the negotiations
- Assess priorities and determine objectives
- Verify objective(s) of the project agreement is met
- Participate in agreement negotiations
- Determine a negotiation strategy
Key Negotiation Strategies
| Strategy | Description | Best For |
|---|---|---|
| Win-Win (Integrative) | Both parties gain value | Long-term relationships ⭐ |
| Win-Lose (Distributive) | One party gains at other's expense | One-time transactions |
| BATNA | Best Alternative to Negotiated Agreement | Knowing your walkaway point |
Always know your BATNA before negotiating. The PMP exam tests whether you can identify when to walk away versus when to compromise.
Negotiation applies to: contracts, resource allocation, stakeholder expectations, schedule/budget trade-offs, scope changes, vendor agreements. It's not just about contracts!
Task 9: Collaborate with Stakeholders
- Evaluate engagement needs for stakeholders
- Optimize alignment between stakeholder needs, expectations, and project objectives
- Build trust and influence stakeholders
Stakeholder Engagement Levels (Ladder):
Unaware → Resistant → Neutral → Supportive → Leading
Goal: Move all key stakeholders toward Supportive or Leading.
Unaware → Resistant → Neutral → Supportive → Leading
Goal: Move all key stakeholders toward Supportive or Leading.
A key sponsor is "Resistant" to the new ERP system your project will implement. You schedule one-on-one meetings, share success stories from similar implementations, involve them in key design decisions, and gradually move them to "Supportive." This targeted engagement strategy is the PMP preferred approach.
Never assume a stakeholder who was supportive at project start remains supportive. Continuously reassess engagement levels, especially after major scope changes or setbacks.
Task 10: Build Shared Understanding
- Break down the situation to identify root cause of misunderstanding
- Survey all necessary parties to reach consensus
- Support outcome of parties' agreement
- Investigate potential misunderstandings
The client expects the software will be delivered with training materials, but the SOW only mentions the software itself. The PM calls a joint meeting, reviews the SOW, documents the gap, and either formally includes training in scope via change control OR clarifies that training is out of scope with the client's written acknowledgment.
Shared understanding is the antidote to scope creep and unmet expectations. Tools: project charter, scope statement, WBS, requirements traceability matrix, Definition of Done (agile), team charter.
Task 11: Engage and Support Virtual Teams
- Examine virtual team member needs (environment, geography, culture, global)
- Investigate alternatives for virtual team member engagement
- Implement engagement options
- Continually evaluate effectiveness
Virtual Team Challenges & Solutions:
Time zones → Establish overlapping "core hours" and rotate meeting times
Cultural differences → Cultural awareness training, shared norms document
Communication gaps → Video-first meetings, clear written protocols
Isolation → Virtual social events, buddy systems, recognition programs
Time zones → Establish overlapping "core hours" and rotate meeting times
Cultural differences → Cultural awareness training, shared norms document
Communication gaps → Video-first meetings, clear written protocols
Isolation → Virtual social events, buddy systems, recognition programs
Virtual team advantages: access to global talent pool, 24/7 work cycles, reduced office costs. The PM must be more intentional about communication, inclusion, and trust-building than with co-located teams.
Task 12: Define Team Ground Rules
- Communicate organizational principles with team and external stakeholders
- Establish an environment that fosters adherence to the ground rules
- Manage and rectify ground rule violations
What it is: Ground rules are explicit behavioral expectations for the team — covering meetings, communication, decision-making, and accountability.
A team charter (also called a Working Agreement in agile) might include: "All Scrum ceremonies are mandatory," "Decisions require consensus; if not reached in 20 min, PM decides," "Code reviews completed within 24 hours," "Slack messages responded to within 2 hours during business hours."
Ground rules should be established early in the project during team formation. In agile, the team creates their own working agreements — ownership increases adherence.
Task 13: Mentor Relevant Stakeholders
- Allocate time to mentoring
- Recognize and act on mentoring opportunities
What it is: Providing guidance, sharing experience, and developing the knowledge and skills of team members and stakeholders. Mentoring is relationship-based and longer-term than training.
A junior team member shows promise as a future PM. You include them in stakeholder meetings, explain your decision-making rationale, and gradually assign them to lead small work packages. This intentional mentoring develops future talent and is valued by PMP standards.
Distinguish: Mentoring (long-term, relationship-based guidance) vs. Coaching (skill-specific, performance-focused) vs. Training (structured education). The exam tests these distinctions!
Task 14: Promote Team Performance Through Emotional Intelligence
- Assess behavior through personality indicators
- Analyze personality indicators and adjust to emotional needs of key stakeholders
What it is: Emotional Intelligence (EI/EQ) is the ability to recognize, understand, and manage your own emotions and those of others.
Daniel Goleman's 5 EI Components
| Component | Description | Example |
|---|---|---|
| Self-Awareness | Know your emotions | Recognizing you're frustrated before a meeting |
| Self-Regulation | Control your emotions | Staying calm under budget pressure |
| Motivation | Internal drive for goals | Committed to project success despite setbacks |
| Empathy | Understand others' feelings | Recognizing team burnout before it becomes a crisis |
| Social Skills | Manage relationships | Building stakeholder coalitions |
The PMP exam will often describe a situation where a team member is struggling or resistant. The EI answer is to first acknowledge their feelings/concerns, then problem-solve. Jumping straight to solutions without empathy is wrong.
Myers-Briggs (MBTI) and DISC are personality assessment tools used to understand team dynamics. The PMP exam may reference personality assessments in the context of adapting communication or leadership style.
⚙️ DOMAIN II: PROCESS — 50% of Exam (~88 Questions)
The largest domain, covering the technical and procedural aspects of project management — from initiating through closing. Tests both predictive (waterfall) and agile process knowledge.
Task 1: Execute Project with the Urgency Required to Deliver Business Value
- Assess opportunities to deliver value incrementally
- Examine business value throughout the project
- Support the team to find the Minimum Viable Product (MVP)
What it is: Delivering value early and often, rather than waiting for the end of the project. This task embodies the agile philosophy of iterative, incremental delivery.
Business Value Types:
Tangible: Revenue, cost savings, market share, buildings, infrastructure
Intangible: Brand equity, customer satisfaction, employee morale, goodwill
Tangible: Revenue, cost savings, market share, buildings, infrastructure
Intangible: Brand equity, customer satisfaction, employee morale, goodwill
A software team is building a 12-feature platform. Rather than delivering all 12 features in month 12, they release 3 core features in month 2 (MVP), get user feedback, and iterate. Users can start getting value immediately, and the team can pivot based on real data.
The exam often tests whether you understand when to use incremental delivery vs. a single final delivery. If the client can receive and use partial work → incremental delivery adds value. If not (e.g., a bridge must be complete to be useful) → single delivery is appropriate.
Task 2: Manage Communications
- Analyze communication needs of all stakeholders
- Determine methods, channels, frequency, and level of detail
- Communicate project information and updates effectively
- Confirm communication is understood and feedback is received
Communication Formula: N(N-1)/2 = Number of communication channels
Example: 5 stakeholders = 5(5-1)/2 = 10 channels
Example: 10 stakeholders = 10(9)/2 = 45 channels
Example: 5 stakeholders = 5(5-1)/2 = 10 channels
Example: 10 stakeholders = 10(9)/2 = 45 channels
The PM spends approximately 90% of their time communicating. The PMP exam expects you to know: (1) tailor communication to each stakeholder, (2) written communication is best for formal/complex info, (3) face-to-face (or video) is best for sensitive topics.
Communication Methods
| Type | Direction | Examples |
|---|---|---|
| Interactive | Multi-directional | Meetings, video calls, phone ⭐ Best for sensitive/complex topics |
| Push | One-way outbound | Email, reports, memos, press releases |
| Pull | Recipient retrieves | Intranet, SharePoint, databases |
Stakeholder A is a technical developer → detailed technical reports. Stakeholder B is the CFO → high-level financial dashboards. Stakeholder C is a remote team member → weekly video calls + shared project dashboard. Tailored communication = better engagement.
Task 3: Assess and Manage Risks
- Determine risk management options
- Iteratively assess and prioritize risks
Risk Management Process Flow
Identify → Analyze (Qualitative) → Analyze (Quantitative) → Plan Responses → Implement → Monitor
Risk Response Strategies
| For Threats (Negative Risks) | For Opportunities (Positive Risks) |
|---|---|
| Avoid — Eliminate the risk | Exploit — Make it happen |
| Transfer — Shift to third party (insurance) | Share — Partner with others |
| Mitigate — Reduce probability/impact | Enhance — Increase probability/impact |
| Accept — Do nothing (active/passive) | Accept — Take advantage if it occurs |
Risks in agile are managed iteratively at every sprint/iteration. Risk register is continuously updated. The PMP exam now tests risk management in both predictive AND agile contexts.
Risk Priority Number: P(Probability) × I(Impact) = Risk Score
High Score → Prioritize for active response
Residual Risk: Risk remaining after response
Secondary Risk: New risk created by a response action
High Score → Prioritize for active response
Residual Risk: Risk remaining after response
Secondary Risk: New risk created by a response action
The exam distinguishes: Risk (uncertain event, may or may not occur) vs. Issue (has already occurred, needs immediate action). Always manage risks proactively before they become issues!
Task 4: Engage Stakeholders
- Analyze stakeholders (power interest grid, influence, impact)
- Categorize stakeholders
- Engage stakeholders by category
- Develop, execute, and validate a strategy for stakeholder engagement
Power/Interest Grid Strategy:
High Power + High Interest → Manage Closely (Key Players)
High Power + Low Interest → Keep Satisfied
Low Power + High Interest → Keep Informed
Low Power + Low Interest → Monitor (Minimal Effort)
High Power + High Interest → Manage Closely (Key Players)
High Power + Low Interest → Keep Satisfied
Low Power + High Interest → Keep Informed
Low Power + Low Interest → Monitor (Minimal Effort)
Your project has 50 stakeholders. Using the Power/Interest grid, you identify 5 key players (closely manage), 10 to keep satisfied, 15 to keep informed, and 20 to just monitor. This targeted approach saves time and maximizes engagement effectiveness.
Stakeholder engagement is an ongoing process, not a one-time analysis. If a key stakeholder moves from "Supportive" to "Resistant" mid-project, you must update your engagement strategy immediately.
Task 5: Plan and Manage Budget and Resources
- Estimate budgetary needs based on scope and lessons learned
- Anticipate future budget challenges
- Monitor budget variations and work with governance process
- Plan and manage resources
Key Budget Formulas (Earned Value Management)
| Formula | What It Measures | Good/Bad |
|---|---|---|
| CV = EV - AC | Cost Variance (over/under budget) | Positive = Under budget ✅ |
| SV = EV - PV | Schedule Variance (ahead/behind) | Positive = Ahead ✅ |
| CPI = EV / AC | Cost Performance Index | >1 = Efficient ✅ |
| SPI = EV / PV | Schedule Performance Index | >1 = Ahead ✅ |
| EAC = BAC / CPI | Estimate at Completion | Future total cost projection |
| ETC = EAC - AC | Estimate to Complete | Remaining cost to finish |
| VAC = BAC - EAC | Variance at Completion | Positive = Will finish under budget ✅ |
| TCPI = (BAC-EV)/(BAC-AC) | To Complete Performance Index | <1 = Easy to achieve ✅ |
EVM is heavily tested! Remember: EV (Earned Value) is always the starting point for all calculations. EV = % complete × BAC. Master this formula table and you'll get multiple points on the exam.
BAC=$100K, EV=$40K, AC=$50K, PV=$45K. Calculate:
CPI=40/50=0.80 (over budget!), SPI=40/45=0.89 (behind schedule!), EAC=100/0.80=$125K (project will overrun by $25K). Action: investigate cost overruns immediately.
CPI=40/50=0.80 (over budget!), SPI=40/45=0.89 (behind schedule!), EAC=100/0.80=$125K (project will overrun by $25K). Action: investigate cost overruns immediately.
Task 6: Plan and Manage Schedule
- Estimate project tasks (milestones, dependencies, story points)
- Utilize benchmarks and historical data
- Prepare schedule based on methodology
- Measure ongoing progress based on methodology
- Modify schedule as needed
- Coordinate with other projects and operations
Schedule Techniques
| Technique | Description | Approach |
|---|---|---|
| CPM | Critical Path Method — Longest path, zero float | Predictive |
| PERT | (O+4M+P)/6 = Expected Duration | Predictive (with uncertainty) |
| Story Points | Relative effort estimation | Agile |
| Velocity | Story points completed per sprint | Agile |
| Fast Tracking | Parallelize sequential activities | Schedule compression |
| Crashing | Add resources to critical path | Schedule compression (costs more) |
CRITICAL PATH = longest path through the network. Tasks on the critical path have ZERO float. If any CP task is delayed, the entire project is delayed. Fast tracking increases risk; crashing increases cost.
Float (slack) = LS-ES or LF-EF. Total Float is shared among a path; Free Float belongs to one activity. Negative float means you're already behind schedule when you plan.
Task 7: Plan and Manage Quality of Products/Deliverables
- Determine quality standards required
- Recommend options for improvement based on quality gaps
- Continually survey project deliverable quality
Quality Key Distinctions:
Quality Planning: What standards apply?
Quality Assurance (QA): Are we FOLLOWING the right processes? (Audit-based)
Quality Control (QC): Are the DELIVERABLES meeting standards? (Inspection-based)
Grade ≠ Quality: Low grade (few features) with high quality (no defects) is acceptable. Low quality (defects) is never acceptable.
Quality Planning: What standards apply?
Quality Assurance (QA): Are we FOLLOWING the right processes? (Audit-based)
Quality Control (QC): Are the DELIVERABLES meeting standards? (Inspection-based)
Grade ≠ Quality: Low grade (few features) with high quality (no defects) is acceptable. Low quality (defects) is never acceptable.
Cost of Quality: Prevention Costs (training, planning) + Appraisal Costs (inspections, testing) = Cost of Conformance. Internal Failure (rework, scrap) + External Failure (warranty, recalls) = Cost of Non-Conformance.
Ishikawa (Fishbone) Diagram identifies root causes. Pareto Chart (80/20 rule) prioritizes which causes to fix first. Control Charts monitor if a process is within limits (7 consecutive points on one side = out of control).
Task 8: Plan and Manage Scope
- Determine and prioritize requirements
- Break down scope (WBS, backlog)
- Monitor and validate scope
Scope Concepts:
Product Scope: Features/functions of the deliverable
Project Scope: Work needed to deliver the product
WBS: Hierarchical decomposition of project work (predictive)
Backlog: Prioritized list of work items (agile)
Scope Creep: Unauthorized scope changes → control with change management
Product Scope: Features/functions of the deliverable
Project Scope: Work needed to deliver the product
WBS: Hierarchical decomposition of project work (predictive)
Backlog: Prioritized list of work items (agile)
Scope Creep: Unauthorized scope changes → control with change management
Scope is VERIFIED (Validate Scope process) with the customer → formal acceptance. Scope is CONTROLLED (Control Scope process) internally → prevents unauthorized changes. Validate Scope produces formal acceptance; Control Scope produces change requests.
A client casually asks your team developer to "add a small feature." If the developer does it without a change request, that's scope creep. The PM must implement a formal change request, assess impact on schedule/cost/risk, and get approval before any changes are made.
Task 9: Integrate Project Planning Activities
- Consolidate the project/phase plans
- Assess for dependencies, gaps, and continued business value
- Analyze data collected
- Determine critical information requirements
What it is: Integration Management ensures all subsidiary plans (scope, schedule, cost, quality, risk, communications, procurement, stakeholder) are aligned and work together as a coherent whole.
The Project Management Plan is NOT a single document — it's a collection of subsidiary plans and baselines. Changes to one plan often require changes to others. The PM is responsible for this integration.
Baselines (cannot change without formal change control):
Scope Baseline = Scope Statement + WBS + WBS Dictionary
Schedule Baseline = Approved project schedule
Cost Baseline = Approved budget (S-curve)
Performance Measurement Baseline = Scope + Schedule + Cost combined
Scope Baseline = Scope Statement + WBS + WBS Dictionary
Schedule Baseline = Approved project schedule
Cost Baseline = Approved budget (S-curve)
Performance Measurement Baseline = Scope + Schedule + Cost combined
Task 10: Manage Project Changes
- Anticipate and embrace the need for change
- Determine strategy to handle change
- Execute change management strategy according to methodology
- Determine a change response to move the project forward
Change Control Process (Predictive):
1. Change Request submitted → 2. CCB (Change Control Board) reviews → 3. Impact analysis (scope/cost/schedule/risk) → 4. Approve/Reject/Defer → 5. Update plans & baselines → 6. Communicate decision → 7. Implement approved changes
1. Change Request submitted → 2. CCB (Change Control Board) reviews → 3. Impact analysis (scope/cost/schedule/risk) → 4. Approve/Reject/Defer → 5. Update plans & baselines → 6. Communicate decision → 7. Implement approved changes
In agile: change is WELCOMED and managed through the backlog — the Product Owner reprioritizes items. In predictive: change goes through formal change control. Hybrid projects may use formal change control for scope/cost but agile delivery for implementation.
The exam often presents a situation where a stakeholder requests a change. The FIRST step is always to evaluate the impact on scope, schedule, cost, and risk — NEVER just implement it, and NEVER just refuse it. Follow the process!
Task 11: Plan and Manage Procurement
- Define resource requirements and needs
- Communicate resource requirements
- Manage suppliers/contracts
- Plan and manage procurement strategy
- Develop a delivery solution
Contract Types
| Type | Buyer Risk | Seller Risk | Best When |
|---|---|---|---|
| FFP (Firm Fixed Price) | Low | High | Scope is well-defined |
| FP-EPA | Medium | Medium | Long duration, inflation risk |
| FPIF (Incentive Fee) | Medium | Medium | Encourage performance |
| CPFF (Cost Plus Fixed Fee) | High | Low | Scope uncertain, R&D |
| CPIF (Cost Plus Incentive) | High | Medium | Uncertain + performance reward |
| T&M (Time & Material) | Highest | Lowest | Undefined scope, short duration |
FFP (Firm Fixed Price) = Maximum risk to SELLER. T&M = Maximum risk to BUYER. Remember: who carries more risk = who benefits more if the project goes well.
Task 12: Manage Project Artifacts
- Determine requirements (what, when, where, who) for managing artifacts
- Validate information is kept up to date (version control) and accessible
- Continually assess effectiveness of artifact management
Project artifacts include: project charter, project management plan, risk register, issue log, change log, stakeholder register, lessons learned, status reports, contracts. All must be version-controlled and stored in the project repository (SharePoint, Confluence, etc.).
In agile, key artifacts include: Product Backlog, Sprint Backlog, Burndown Charts, Definition of Done, Sprint Review demos, and retrospective notes. These must also be maintained and accessible to all team members.
Task 13: Determine Appropriate Project Methodology/Methods and Practices
- Assess project needs, complexity, and magnitude
- Recommend project execution strategy
- Recommend a methodology (predictive, agile, hybrid)
- Use iterative, incremental practices throughout the project life cycle
Choosing the Right Methodology
| Factor | Use Predictive | Use Agile | Use Hybrid |
|---|---|---|---|
| Scope clarity | Well-defined | Evolving/unclear | Partial clarity |
| Change frequency | Low | High | Moderate |
| Stakeholder availability | Limited | High | Moderate |
| Team experience w/ agile | Low | High | Mixed |
| Regulatory requirements | Strict | Flexible | Partial |
The PMP exam will describe a project scenario and ask you to recommend the best approach. Key signals: "Requirements are unclear/changing" → Agile. "Well-defined scope, strict regulatory requirements" → Predictive. "Mix of both" → Hybrid.
Task 14: Establish Project Governance Structure
- Determine appropriate governance for a project
- Define escalation paths and thresholds
Governance Components:
CCB (Change Control Board) — approves/rejects changes
Project Steering Committee — executive-level oversight
Escalation Matrix — who decides what at each level
Decision-making thresholds — what the PM can decide alone vs. escalate
CCB (Change Control Board) — approves/rejects changes
Project Steering Committee — executive-level oversight
Escalation Matrix — who decides what at each level
Decision-making thresholds — what the PM can decide alone vs. escalate
If a change is within the PM's authority level, handle it independently. If it exceeds thresholds (cost, schedule, scope), escalate to the CCB or sponsor. The exam tests whether you know when to escalate vs. handle it yourself.
Task 15: Manage Project Issues
- Recognize when a risk becomes an issue
- Attack the issue with the optimal action
- Collaborate with relevant stakeholders on the resolution approach
An issue is a risk that HAS occurred. Issues are logged in the Issue Log with: issue description, date raised, owner, priority, status, and resolution date. Issues require IMMEDIATE action — unlike risks which are managed proactively.
You identified a risk that a key vendor might go bankrupt. You had a contingency plan: alternate vendor list. When the vendor does go bankrupt (risk → issue), you immediately activate the contingency plan, contact the alternate vendor, and update stakeholders. This proactive planning turned a potential crisis into a managed response.
Task 16: Ensure Knowledge Transfer for Project Continuity
- Discuss project responsibilities within team
- Outline expectations for working environment
- Confirm approach for knowledge transfers
Before a key team member leaves mid-project, the PM documents: (1) current work status, (2) pending decisions, (3) stakeholder relationship notes, (4) technical design rationale, (5) lessons learned. This knowledge package is handed to the replacement or distributed to the team. Critical for project continuity!
In agile, cross-functional teams and pair programming naturally facilitate knowledge transfer. In predictive projects, formal knowledge transfer sessions, documentation standards, and succession planning must be deliberate activities.
Task 17: Plan and Manage Project/Phase Closure or Transitions
- Determine criteria to successfully close the project or phase
- Validate readiness for transition (to operations team or next phase)
- Conclude activities to close out project or phase (final lessons learned, retrospective, procurement, financials, resources)
Project Closure Checklist:
✅ Formal acceptance from customer/sponsor
✅ Final lessons learned documented
✅ All contracts closed (procurement closure)
✅ Resources released (team members returned to functional managers)
✅ Financial accounts closed
✅ Project documents archived
✅ Final performance report issued
✅ Formal acceptance from customer/sponsor
✅ Final lessons learned documented
✅ All contracts closed (procurement closure)
✅ Resources released (team members returned to functional managers)
✅ Financial accounts closed
✅ Project documents archived
✅ Final performance report issued
Projects can be closed normally (completed) or early (cancelled, terminated). Even terminated projects require formal closure — document why it was terminated, preserve artifacts, and release resources properly.
🌐 DOMAIN III: BUSINESS ENVIRONMENT — 8% of Exam (~14 Questions)
Though the smallest domain, Business Environment questions require strategic thinking. They test whether you can connect project decisions to organizational strategy, compliance, and external factors.
Task 1: Plan and Manage Project Compliance
- Confirm project compliance requirements (security, health and safety, regulatory)
- Classify compliance categories
- Determine potential threats to compliance
- Use methods to support compliance
- Analyze consequences of noncompliance
- Determine approach and action to address compliance needs (risk, legal)
- Measure the extent to which the project is in compliance
A hospital IT project must comply with HIPAA (health data privacy), OSHA (safety), and Joint Commission standards. The PM creates a compliance matrix, assigns a compliance lead, conducts compliance audits, and includes compliance milestones in the project schedule.
Noncompliance consequences: fines, legal liability, project shutdown, reputational damage, safety hazards. The exam expects the PM to prioritize compliance — even if it costs more time/money, safety and legal compliance are non-negotiable.
Compliance is NOT the same as quality. Quality is meeting project requirements. Compliance is meeting external legal/regulatory standards. Both must be managed, but compliance failures carry legal consequences quality failures may not.
Task 2: Evaluate and Deliver Project Benefits and Value
- Investigate that benefits are identified
- Document agreement on ownership for ongoing benefit realization
- Verify measurement system is in place to track benefits
- Evaluate delivery options to demonstrate value
- Appraise stakeholders of value gain progress
Benefits Realization Management:
Benefits are realized DURING and AFTER project completion (in operations).
The PM defines benefits, plans how to measure them, and hands off measurement to the business owner post-project.
Example: A CRM system project delivers the system (project output), but the benefit (increased sales by 20%) is realized 6 months after go-live.
Benefits are realized DURING and AFTER project completion (in operations).
The PM defines benefits, plans how to measure them, and hands off measurement to the business owner post-project.
Example: A CRM system project delivers the system (project output), but the benefit (increased sales by 20%) is realized 6 months after go-live.
Projects create OUTPUTS (deliverables). Outputs enable OUTCOMES (changes in behavior/performance). Outcomes realize BENEFITS (measurable improvements). Benefits contribute to STRATEGIC VALUE. This chain is increasingly tested on the PMP exam.
Task 3: Evaluate and Address External Business Environment Changes for Impact on Scope
- Survey changes to external business environment (regulations, technology, geopolitical, market)
- Assess and prioritize impact on project scope/backlog
- Recommend options for scope/backlog changes
- Continually review external environment for impacts
Mid-project, a new data privacy regulation (like GDPR) is enacted that affects your software development project. As PM, you: (1) assess impact on current scope, (2) engage your legal/compliance team, (3) submit change requests to add compliance features to the scope, (4) update schedule and budget accordingly, (5) inform stakeholders of the changes.
Use PESTLE analysis to systematically scan external factors: Political, Economic, Social, Technological, Legal, Environmental. Regularly review these factors, especially for long-duration projects.
Task 4: Support Organizational Change
- Assess organizational culture
- Evaluate impact of organizational change to project
- Evaluate impact of the project to the organization
- Determine required actions
Organizational Change Management Models:
Kotter's 8 Steps: Urgency → Coalition → Vision → Communicate → Empower → Quick Wins → Build Momentum → Anchor
Prosci ADKAR: Awareness → Desire → Knowledge → Ability → Reinforcement
Lewin's 3 Stages: Unfreeze → Change → Refreeze
Kotter's 8 Steps: Urgency → Coalition → Vision → Communicate → Empower → Quick Wins → Build Momentum → Anchor
Prosci ADKAR: Awareness → Desire → Knowledge → Ability → Reinforcement
Lewin's 3 Stages: Unfreeze → Change → Refreeze
Projects are agents of organizational change. Resistance to change is NORMAL and must be managed proactively. The PM must help stakeholders understand the "why" (urgency/vision) and support them through the transition.
📋 PMP Eligibility Requirements
| Education Level | PM Experience Required |
|---|---|
| Secondary Degree (High School / Associate's) | 60 months (5 years) of PM experience |
| 4-Year Degree (Bachelor's) | 36 months (3 years) of PM experience |
| GAC-Accredited Degree (Bachelor's or Master's) | 24 months (2 years) of PM experience |
All PM experience must be within the last 8 consecutive years. You also need 35 contact hours of formal PM education — unless you hold an active CAPM certification.
Overlapping project months count ONCE (non-overlapping). If you worked on Project A (Jan-Apr) and Project B (Feb-Jun), you have 6 months, not 10.
Application review takes ~5 calendar days online. Audit process may add time.
Application review takes ~5 calendar days online. Audit process may add time.
🎓 PMP Examination Details
| Item | Value |
|---|---|
| Total Questions | 180 (175 scored + 5 pretest) |
| Exam Duration | 230 minutes |
| Breaks | 2 optional breaks (after Q60, after Q120) |
| Maximum Attempts | 3 times within 1-year eligibility period |
| Re-exam wait (if 3 fails) | 1 year from last exam date |
| Hand rescore fee | $45 USD (paper-based only) |
| Predictive vs Agile split | ~50% / ~50% |
After starting a break, you CANNOT go back to the previous section. Use breaks strategically — review flagged questions BEFORE clicking "Start Break."
📋 Master Cheat Sheet — Quick Reference
Domain %
People=42% | Process=50% | Biz Env=8%
People=42% | Process=50% | Biz Env=8%
Exam Format
180 Qs | 230 min | 2 breaks | 3 retakes max
180 Qs | 230 min | 2 breaks | 3 retakes max
EVM Formulas
CV=EV-AC | SV=EV-PV
CPI=EV/AC | SPI=EV/PV
EAC=BAC/CPI | ETC=EAC-AC
VAC=BAC-EAC
CV=EV-AC | SV=EV-PV
CPI=EV/AC | SPI=EV/PV
EAC=BAC/CPI | ETC=EAC-AC
VAC=BAC-EAC
Conflict Resolution Order
Best: Collaborate → Compromise → Smooth → Avoid → Force :Worst
Best: Collaborate → Compromise → Smooth → Avoid → Force :Worst
Contract Risk
Buyer most risk: T&M
Seller most risk: FFP
Balanced: FPIF, CPIF
Buyer most risk: T&M
Seller most risk: FFP
Balanced: FPIF, CPIF
Team Stages
Forming→Storming→Norming→Performing→Adjourning
Forming→Storming→Norming→Performing→Adjourning
Leadership
PMP favors: Servant Leadership (agile)
Collaborative Leadership (mixed)
Directive only in emergencies/new teams
PMP favors: Servant Leadership (agile)
Collaborative Leadership (mixed)
Directive only in emergencies/new teams
Critical Path
Longest path = 0 float
Delay on CP = project delay
Fast Track: parallel (more risk)
Crash: add resources (more cost)
Longest path = 0 float
Delay on CP = project delay
Fast Track: parallel (more risk)
Crash: add resources (more cost)
Stakeholder Grid
Hi Power+Hi Interest → Manage Closely
Hi Power+Lo Interest → Keep Satisfied
Lo Power+Hi Interest → Keep Informed
Lo Power+Lo Interest → Monitor
Hi Power+Hi Interest → Manage Closely
Hi Power+Lo Interest → Keep Satisfied
Lo Power+Hi Interest → Keep Informed
Lo Power+Lo Interest → Monitor
Quality
QA = Process audit (prevent defects)
QC = Product inspection (find defects)
Grade ≠ Quality
Prevention > Inspection
QA = Process audit (prevent defects)
QC = Product inspection (find defects)
Grade ≠ Quality
Prevention > Inspection
Comm Channels
Formula: N(N-1)/2
5 people = 10 channels
10 people = 45 channels
20 people = 190 channels
Formula: N(N-1)/2
5 people = 10 channels
10 people = 45 channels
20 people = 190 channels
Agile Key Terms
Sprint=2-4 week iteration
Velocity=story pts/sprint
DoD=Definition of Done
WIP=Work In Progress
Burndown=remaining work chart
Sprint=2-4 week iteration
Velocity=story pts/sprint
DoD=Definition of Done
WIP=Work In Progress
Burndown=remaining work chart
🔑 Key Terms Glossary (Click to Explore)
Click any term below for a quick definition:
PMI
PMP
GPA
JTA
Servant Leadership
Emotional Intelligence
BATNA
MVP
EVM
KPI
WBS
Critical Path Method
Float / Slack
CCB
RACI
Scope Creep
Risk vs Issue
PESTLE
Agile
Hybrid Approach
Sprint
Burndown Chart
Velocity
Definition of Done
Sources of Conflict
Decision-Making Authority
PERT
Lessons Learned
Stakeholder
Project Charter
📝 My Study Notes
Type your personal notes below — they save automatically:
✅ Saved!