Ch1. PMP Exam Overview and the Project Management Framework
What Is PMP?
PMP (Project Management Professional) is PMI’s (Project Management Institute) globally recognized certification validating the ability to lead and manage projects.
Exam details:
- 180 questions (multiple choice, drag-and-drop, matching)
- 230 minutes
- Passing score: approximately 60%+ (exact threshold not published)
- Prerequisites: 36 months (bachelor’s) or 60 months (high school) project experience + 35 hours PM education
PMBOK 7th Edition Changes
The PMBOK Guide evolved significantly from 6th to 7th edition:
6th Edition: Process-focused (5 Process Groups, 49 Processes, 10 Knowledge Areas)
7th Edition: Principles and outcomes-focused
- 12 Project Management Principles
- 8 Performance Domains
- Approach-agnostic (covers predictive, agile, and hybrid)
Exam composition: The current PMP exam is approximately 50% predictive (traditional) and 50% agile/hybrid. You must understand both approaches to pass.
The 12 PM Principles (PMBOK 7th Edition)
- Stewardship: Act responsibly and ethically
- Team: Build a collaborative team environment
- Stakeholders: Engage and manage stakeholders
- Value: Focus on delivering value
- Systems Thinking: See the whole system
- Leadership: Motivate and influence
- Tailoring: Adapt the approach to context
- Quality: Meet stakeholder expectations
- Complexity: Navigate and respond to complexity
- Risk: Optimize risk responses
- Adaptability/Resiliency: Embrace change and recover from setbacks
- Change: Enable transitions to desired future states
The 8 Performance Domains
| Domain | Core Focus |
|---|---|
| Stakeholders | Engagement, expectation management |
| Team | Team development, leadership |
| Development Approach & Life Cycle | Choose predictive/agile/hybrid |
| Planning | Schedule, budget, resource planning |
| Project Work | Execution, issue management |
| Delivery | Scope, WBS, value realization |
| Measurement | KPIs, performance tracking |
| Uncertainty | Risk and opportunity management |
Development Approaches
Predictive (Waterfall)
- Clear, stable requirements with minimal changes
- Detailed upfront planning, sequential execution
- Examples: Construction, manufacturing, regulatory compliance
Agile
- Unclear or frequently changing requirements
- Iterative, incremental development in sprints
- Examples: Software development, product development
Hybrid
- Combines elements of predictive and agile
- Example: Plan predictively, develop in agile sprints
Key Concept Cards
PMBOK 7th Edition Shift ★★★★★ : Process-focused → principles and outcomes. 12 principles + 8 domains. Agile fully integrated.
Predictive vs. Agile ★★★★★ : Stable requirements = predictive. Changing requirements = agile. Mixed = hybrid. Context-dependent choice.
Tailoring ★★★★☆ : Adjusting the approach and processes to fit the organization, project, and team. Central concept in PMBOK 7th Edition.
Practice Quiz
Q1. A software development project has requirements that change frequently. What development approach is most appropriate?
Agile. Through short iterations (sprints), agile can accommodate evolving requirements. Customer feedback after each sprint is incorporated into the next — making it optimal for unclear or changing requirements.
Q2. Why is “tailoring” so important in the PMP exam?
No two projects are identical. PMBOK 7th Edition emphasizes selecting appropriate methods based on context rather than applying a single approach universally. Tailoring involves combining predictive, agile, and hybrid elements based on organizational culture, project complexity, team capability, and stakeholder needs.
OIYO Editorial
Editorial DeskThe OIYO editorial desk researches money, law, lifestyle, and self-understanding topics against primary sources and public statistics. Every piece carries source notes and is reviewed on a regular cycle for accuracy and usefulness.