High-Level PMP Topics Breakdown:
People (42%):
o Conflict Management: Interpreting and resolving team
conflict.
o Leading Teams: Supporting, mentoring, and motivating team
members.
o Virtual Teams: Managing distributed teams.
o Collaboration: Building shared understanding and fostering
trust.
o Empowerment: Supporting team performance and
empowering members.
o Training & Mentoring: Ensuring knowledge transfer.
Process (50%):
o Methodologies: Agile, Scrum, Waterfall (predictive), and
hybrid approaches.
o Scope Management: Defining requirements, creating Work
Breakdown Structures (WBS).
o Schedule & Budget Management: Estimation tools,
forecasting, and controlling costs.
o Risk Management: Identifying, analyzing, and responding to
threats/opportunities.
o Quality Management: Planning, assuring, and controlling
deliverables.
o Procurement & Vendor Management: Contract
management and vendor relations.
o Closing: Project or phase closure, including knowledge
transfer.
Business Environment (8%):
o Compliance & Governance: Ensuring regulatory and
organizational compliance.
o Value Delivery: Evaluating project benefits, ROI, and
organizational value.
o Strategy Alignment: Supporting organizational change and
strategic goals.
o Sustainability: Managing environmental impacts and
sustainability factors.
PMP Perspective: Key People & Leadership
Competencies
1. Conflict Management: Interpreting and Resolving Team Conflict
Conflict in projects is normal and often healthy if managed constructively.
A PMP-aligned leader must identify the source, assess the intensity, and
use the right technique based on the context.
Common Sources of Conflict
Task priorities
Resource constraints
Technical opinions
Interpersonal issues
Roles & responsibilities (RACI gaps)
Cultural or communication differences
PMI-Recognized Conflict Resolution Techniques
1. Collaborate / Problem-Solve
o Win–win approach.
o Most effective for long-term relationships and complex issues.
2. Compromise / Reconcile
o Everyone gives up something.
o Useful for time-sensitive resolution.
3. Smooth / Accommodate
o Emphasizes common ground, downplays differences.
o Good for maintaining harmony.
4. Force / Direct
o Useful only in emergencies or authority-based decisions.
5. Withdraw / Avoid
o Appropriate when conflict is trivial or emotions are high.
PMP Viewpoint
Address conflict early and in private.
Remain neutral, focus on issues—not personalities.
Apply emotional intelligence (EI) to understand feelings, triggers,
biases.
Document resolutions when needed (especially in distributed
teams).
2. Leading Teams: Supporting, Mentoring, and Motivating Team
Members
Effective leadership in PMP is servant leadership combined with situational
leadership depending on team maturity.
Key Leadership Responsibilities
Set a clear vision and connect it to organizational strategy.
Remove blockers, provide resources, and eliminate bureaucracy.
Mentor and coach team members to improve competence.
Recognize achievements to reinforce positive behaviors.
Promote psychological safety—allowing open communication and
experimentation.
Motivation Techniques
Intrinsic motivation: autonomy, mastery, purpose.
Extrinsic motivation: rewards, recognition, career development.
Use Maslow, Herzberg, McClelland theories where appropriate.
PMP Emphasis
High-performing teams are built through trust, transparency, and
empowerment.
Leaders adapt their style to team needs—directing, coaching,
supporting, or delegating.
3. Virtual Teams: Managing Distributed Teams
Virtual or geographically dispersed teams are common in today’s global
project environments.
Challenges
Time zone differences
Communication delays
Cultural disparities
Lack of social connection
Difficulty in monitoring progress
PMBOK-Based Best Practices
Establish clear working agreements (SLAs for communication,
availability windows).
Use collaboration tools (Teams, Zoom, Jira, Confluence).
Schedule regular check-ins, daily standups, virtual retros.
Encourage video interactions to humanize communication.
Promote asynchronous communication where possible.
Create a culture of documentation to avoid information loss.
What PMP Expects
Reduce ambiguity with overcommunication.
Build rapport intentionally (virtual team-building).
Measure outcomes—not physical presence.
4. Collaboration: Building Shared Understanding and Fostering
Trust
Collaboration is the backbone of both Agile and Predictive methodologies.
How to Build Shared Understanding
Conduct requirement workshops, backlog refinement, WBS sessions.
Create information radiators (dashboards, kanban boards).
Encourage open feedback loops: reviews, retrospectives, demos.
Document decisions in a central repository.
Fostering Trust
Transparency in decisions.
Consistency in actions.
Respect for diverse perspectives.
Deliver commitments reliably.
Practice active listening.
PMP Mindset
The PM acts as a facilitator and integrator—bridging gaps across
teams, functions, and vendors.
Trust leads to reduced conflict, increased creativity, and better
performance.
5. Empowerment: Supporting Team Performance and Empowering
Members
Empowered teams take ownership and deliver higher-quality
results.
PMBOK Empowerment Techniques
Delegate authority genuinely (not just tasks).
Allow teams to self-organize (widely used in Agile).
Encourage decision-making at the lowest responsible level.
Provide visibility into goals and their impact.
Recognize and reward initiative.
Supporting Performance
Provide continuous feedback and coaching.
Address impediments quickly.
Ensure resource availability and skill alignment.
Use team charters to clarify norms and responsibilities.
PMP View
Empowerment reduces micromanagement and increases
accountability.
The PM becomes a leader rather than a controller.
6. Training & Mentoring: Ensuring Knowledge Transfer
Continuous learning is a core element of PMBOK philosophy and
organizational maturity.
Types of Training
On-the-job learning
Formal classroom or online courses
Role-specific skill training (technical/domain)
Process and methodology training (Agile, PMI standards)
Tool-based workshops (Jira, MS Project, Maximo)
Knowledge Transfer Mechanisms
Pairing senior and junior members (mentoring)
Shadowing
Internal demos and brown-bag sessions
Documenting SOPs, runbooks, and lessons learned
Maintaining a knowledge repository (Confluence, SharePoint)
Conducting transition-to-support sessions in closure phase
PMP Emphasis
The PM ensures proper onboarding, continuous improvement, and
transition planning.
Knowledge transfer is critical for project sustainability and
operational success.
PMP Perspective Breakdown of Key Project
Management Areas
1. Methodologies: Agile, Scrum, Waterfall (Predictive), Hybrid
Predictive (Waterfall)
Follows a sequential lifecycle: Initiation → Planning → Execution →
Monitoring/Controlling → Closing.
Best for projects with stable, well-defined requirements (e.g.,
construction, infrastructure).
Emphasizes extensive upfront planning, baseline creation
(scope, schedule, cost), and strict change control.
Agile
Best for projects with emerging or evolving requirements.
Uses incremental and iterative delivery, enabling customer
collaboration and flexibility.
Values working product > documentation, and embraces
frequent inspection and adaptation.
Roles include Product Owner, Agile Team, and Agile Coach.
Scrum (specific Agile framework)
Work is delivered in time-boxed iterations called Sprints
(usually 2–4 weeks).
Includes structured events: Sprint Planning, Daily Scrum, Sprint
Review, Sprint Retrospective.
Artifacts include Product Backlog, Sprint Backlog, Increment.
Empowers self-organizing, cross-functional teams.
Hybrid
A combination of Agile and Predictive practices.
Common scenarios:
o Predictive planning for scope, cost, compliance.
o Agile execution for development or solution delivery.
Especially suitable for large enterprise programs, regulated
industries, and ERP/Maximo implementations.
2. Scope Management
Requirements Gathering
Includes capturing stakeholder needs via:
o Interviews, workshops, focus groups
o Prototypes, use cases, user stories
o Document analysis and observations
Result: Requirements Documentation + Requirements
Traceability Matrix (RTM).
Creating the Work Breakdown Structure (WBS)
A hierarchical decomposition of the project scope.
Breaks the project into:
o Deliverables
o Work packages
o Activities (in detailed schedule planning)
The WBS forms the basis for:
o Cost estimation
o Scheduling
o Resource allocation
o Risk identification
3. Schedule & Budget Management
Estimation Tools
Top-down / Analogous: Based on historical data or expert
judgment.
Bottom-up: Activity-level estimates aggregated upward.
Three-point estimating: Optimistic (O), Most likely (M),
Pessimistic (P).
Parametric: Mathematical models (e.g., cost per meter, hours per
ticket).
Schedule Management
Develop a schedule baseline using methods like:
o Critical Path Method (CPM)
o Gantt charts
o Network diagrams
Tools: MS Project, Primavera, Jira (for Agile velocity-based planning)
Budget Management
Establishing a cost baseline.
Using Earned Value Management (EVM) for forecasting and
control:
o Schedule Variance (SV), Cost Variance (CV)
o Schedule Performance Index (SPI)
o Cost Performance Index (CPI)
o Estimate at Completion (EAC)
4. Risk Management
Risk Identification
Techniques: brainstorming, SWOT, expert interviews, assumption
analysis.
Output: Risk Register.
Risk Analysis
Qualitative: probability × impact rating.
Quantitative: Monte Carlo, decision trees, expected monetary
value (EMV).
Risk Response Strategies
Threats: Avoid, Transfer, Mitigate, Accept
Opportunities: Exploit, Enhance, Share, Accept
Risk Monitoring
Track risk triggers and implement contingency/reserve strategies.
5. Quality Management
Quality Planning
Define quality standards, metrics, acceptance criteria.
Choose tools like control charts, Pareto, cause-effect diagrams.
Quality Assurance
Process-oriented: audits, process improvements, compliance checks.
Quality Control
Product-oriented: inspections, testing, reviews, defect tracking.
Ensures deliverables meet defined standards.
6. Procurement & Vendor Management
Procurement Planning
Decide what to buy, when, and from where.
Prepare RFIs, RFPs, RFQs.
Contract Types
Fixed-price: predictable but high vendor risk.
Time & Material (T&M): flexible but cost-volatile.
Cost-plus: transparent but less cost control.
Vendor Management
Establish SLAs, KPIs, and performance reporting.
Manage relationship, negotiate terms, ensure compliance.
Control procurement: contract changes, dispute resolution, delivery
verification.
7. Closing: Project or Phase Closure
Administrative Closure
Ensure all deliverables are formally accepted.
Update project documents and archive records.
Contract Closure
Confirm all procurement obligations are fulfilled.
Release contractors and finalize payments.
Knowledge Transfer & Lessons Learned
Conduct lessons learned sessions.
Document best practices and improvement areas.
Transition support/maintenance to operations teams.
PMP Perspective: Compliance, Value
Delivery, Strategy, and Sustainability
1. Compliance & Governance: Ensuring Regulatory and
Organizational Compliance
Compliance is a key responsibility for a Project Manager, especially in
regulated industries (Utilities, Oil & Gas, BFSI, Government Programs).
PMP emphasizes predictability, transparency, documentation, and
adherence to standards.
Core Areas of Compliance
Regulatory compliance:
Health & Safety (HSE), environmental laws, data privacy (GDPR),
industry-specific regulations.
Organizational compliance:
Internal policies, security standards, procurement rules, financial
controls.
Contractual compliance:
Ensuring both the project team and vendors meet contractually
defined obligations.
Governance in PMP
Project governance ensures consistent decision-making,
accountability, and oversight. It includes:
Governance frameworks (e.g., Steering Committees, PMO
standards).
Approval gates (concept approval, design approval, release
approval).
Audit trails and quality compliance documentation.
Key PM Responsibilities
Identify applicable regulations early during planning.
Conduct compliance risk assessments.
Maintain documentation for audits.
Ensure team awareness of rules and procedures.
Facilitate internal/external audits and respond to findings.
2. Value Delivery: Evaluating Project Benefits, ROI, and
Organizational Value
PMI now strongly focuses on value delivery, not just completing scope. A
successful project = delivering measurable benefits.
Types of Project Value
Tangible:
Cost savings, improved efficiency, revenue increase, reduced
downtime.
Intangible:
Customer satisfaction, brand value, regulatory adherence, employee
engagement.
Strategic value:
Supporting transformations like digitalization, automation, ESG
goals.
Benefits Management (PMBOK 7th Edition)
Define Benefits: What value the project will create.
Align Benefits: Ensure executive and stakeholder agreement.
Track Benefits: Monitoring during and after the project.
Validate Benefits: Confirm actual ROI post-implementation.
Tools for Value and ROI Assessment
Cost–benefit analysis
Business case review
NPV (Net Present Value), IRR (Internal Rate of Return)
Earned Value Management for performance tracking
KPI dashboards and balanced scorecards
PMP Emphasis
A PM must ensure that outcomes are not just delivered, but also useful
and sustainable.
3. Strategy Alignment: Supporting Organizational Change and
Strategic Goals
Projects exist to deliver organizational strategy. PMP expects the PM
to understand strategic objectives and ensure the project contributes to
them.
How Projects Support Strategy
Executing the company’s multi-year roadmap.
Facilitating operational improvements (e.g., Asset Management
transformation using Maximo).
Enabling regulatory readiness (e.g., compliance tracking systems).
Modernizing operations through IT and digital solutions.
Enabling organizational growth or market expansion.
What Strategic Alignment Looks Like
Ensuring project outcomes directly support strategic KPIs.
Maintaining alignment through change management techniques.
Adapting project plans when organizational priorities shift.
Ensuring stakeholders understand how the project supports larger
goals.
PM’s Role in Organizational Change Management (OCM)
Communicate vision and purpose.
Prepare stakeholders for process and system changes.
Manage resistance and ensure smooth adoption.
Coordinate training and transition activities.
Ensure benefits realization through sustained usage.
4. Sustainability: Managing Environmental Impacts and
Sustainability Factors
Modern PMP practices emphasize sustainable project management —
ensuring that the project minimizes harm and contributes positively to
environmental, social, and economic factors.
Sustainability Domains (Aligned with PMI and ESG Principles)
Environmental Sustainability
Reducing waste, energy use, or emissions.
Using eco-friendly materials or greener technologies.
Ensuring compliance with environmental regulations.
Designing solutions that minimize environmental footprint.
Social Sustainability
Ensuring worker health & safety.
Ethical labor practices.
Diversity and fair access to opportunities.
Positive impact on communities involved.
Economic Sustainability
Ensuring the project is financially sound.
Delivering long-term value and not just short-term savings.
Optimizing resources to avoid wastage.
PM Responsibilities in Sustainability
Incorporate sustainability objectives into project charters.
Validate environmental requirements during planning.
Monitor sustainable practices during execution.
Ensure vendors follow sustainability standards.
Report sustainability metrics to stakeholders.
Examples
Utilities/energy project reducing carbon footprint.
IT project implementing efficient data centers.
Infrastructure project using recycled materials.
Asset management project enabling predictive maintenance to
reduce waste.