ManagementPMP

PMP Project Management Fundamentals: Frameworks, Lifecycles, and the PMI Mindset

Project management is not about filling in Gantt charts — it is about delivering the right outcome for the right stakeholders at the right cost and time. The PMP exam tests whether you think like a project manager first and a process follower second. That means understanding WHY each process exists before memorising WHAT it does. This guide walks you through the frameworks, lifecycle models, and performance domains that PMI expects you to apply under exam pressure.

14 min
6 sections · 10 exam key points

PMBOK 7 vs PMBOK 6: What Changed and Why It Matters

PMI shifted PMBOK 7 from a process-based standard to a principle-based one. Where PMBOK 6 gave you 49 processes in five process groups, PMBOK 7 gives you 12 principles and eight performance domains. The exam still tests process knowledge from PMBOK 6 through the Examination Content Outline (ECO), but it layered agile mindset and the new principles on top. Think of PMBOK 6 knowledge as the 'what to do' and PMBOK 7 principles as the 'why you do it that way'. The twelve principles include stewardship, collaboration, value, holistic thinking, quality, complexity, risk, adaptability, resilience, change, and leadership. The eight performance domains — stakeholders, team, development approach, planning, project work, delivery, measurement, and uncertainty — describe the areas of focus rather than prescribing step-by-step methods.

Development Approaches: Predictive, Agile, and Hybrid

The single biggest shift in the current PMP exam is the expectation that you can choose the right development approach for a given project. Predictive (waterfall) works when requirements are stable and well-understood — think constructing a bridge or migrating a legacy system with a fixed scope. Agile works when requirements are expected to change and fast feedback loops reduce risk — think building a new mobile app where users discover what they want through prototypes. Hybrid combines both: you might use predictive phases for contracting, procurement, and hardware delivery while using Sprints for the software layer. About half of PMP exam questions are agile or hybrid in nature, so if you trained purely on PMBOK 6 waterfall, you will struggle. Understand when Scrum, Kanban, XP, or SAFe is the right fit and why.

Process Groups and Knowledge Areas (PMBOK 6 Foundation)

Even in the PMBOK 7 era, the five process groups remain the backbone of how most exam questions are framed: Initiating (define and authorise the project), Planning (establish the approach, schedule, budget, and risk plan), Executing (deliver the work), Monitoring and Controlling (compare actuals to plan and manage change), and Closing (formally complete the project or phase). The ten knowledge areas cut across all process groups: Integration, Scope, Schedule, Cost, Quality, Resource, Communications, Risk, Procurement, and Stakeholder Management. Integration Management is the most important — the Project Manager integrates all other areas through the Project Management Plan and Change Control. The Change Control Board (CCB) approves or rejects changes; the project manager never approves changes unilaterally.

Key Formulas and Earned Value Management

EVM (Earned Value Management) questions appear on every PMP exam. The three baseline values are PV (Planned Value — the budgeted cost of work scheduled), EV (Earned Value — the budgeted cost of work actually completed), and AC (Actual Cost — what you really spent). From these you derive: SV = EV - PV (Schedule Variance; negative means behind), CV = EV - AC (Cost Variance; negative means over budget), SPI = EV / PV (Schedule Performance Index; below 1.0 means behind), CPI = EV / AC (Cost Performance Index; below 1.0 means over budget). Forecasting: EAC = BAC / CPI (Estimate At Completion using current performance), ETC = EAC - AC (cost to finish), VAC = BAC - EAC (variance at completion). Critical Path Method: the longest path through the network = project duration. Float = LS - ES or LF - EF; activities on the critical path have zero float.

Stakeholder and Communications Management

PMI treats stakeholder management as a continuous engagement activity, not a one-time identification exercise. You identify stakeholders, analyse their power and interest using a Power/Interest or Salience grid, plan how to engage each group, and then actively manage their engagement throughout the project. The communications management formula — N(N-1)/2 channels where N is the number of stakeholders — appears on exams to illustrate why communication complexity grows non-linearly with team size. Push communication (email, reports) is one-directional and works for status updates. Pull communication (shared portals, document repositories) works for large audiences who need information on demand. Interactive communication (meetings, calls) is best for complex issues requiring immediate feedback.

Risk Management: Identify, Analyse, Respond, Monitor

Risk management is one of the highest-weighted areas on the PMP exam. The process flows: Plan Risk Management (how will you approach risk?) > Identify Risks (what could go wrong?) > Qualitative Analysis (rank by probability and impact) > Quantitative Analysis (model financial impact using Monte Carlo simulation or decision trees) > Plan Risk Responses > Implement Risk Responses > Monitor Risks. Response strategies for threats: Avoid (eliminate the risk), Transfer (insurance, contracts), Mitigate (reduce probability or impact), Accept (passive or active with contingency reserves). Response strategies for opportunities: Exploit, Share, Enhance, Accept. A risk owner is assigned to each risk and is responsible for executing the response. Residual risks remain after responses; secondary risks are created by the responses themselves.

Key exam facts — PMP

  • PMBOK 7 has 12 principles and 8 performance domains; PMBOK 6 had 49 processes in 5 process groups
  • EVM: CPI = EV/AC, SPI = EV/PV — values below 1.0 indicate problems
  • EAC = BAC/CPI when current performance is expected to continue
  • Critical path activities have zero float; shortening the critical path compresses schedule
  • Change requests must go through Change Control Board — PM never self-approves scope changes
  • About 50% of PMP exam questions are agile or hybrid
  • Risk response strategies for threats: Avoid, Transfer, Mitigate, Accept
  • Communications channels formula: N(N-1)/2
  • Project Charter formally authorises the project and names the Project Manager
  • Lessons Learned are captured throughout the project, not just at closing

Common exam traps

The PMP exam is all about PMBOK 6 processes

Roughly half the questions test agile or hybrid project management. You need Scrum, Kanban, and servant leadership knowledge alongside the traditional process groups.

Float and slack mean the same thing in all contexts

Total float is shared across a path; free float belongs to a single activity. An activity can have free float only if total float exceeds what the next activity needs.

Qualitative and quantitative risk analysis are always both required

Qualitative analysis (probability x impact) is done on all projects. Quantitative analysis (Monte Carlo, decision trees) is optional and only done on large or complex projects where the cost of analysis is justified.

The project manager approves changes when they are small

All changes must go through the integrated change control process. The PM evaluates impact and presents to the CCB; only the CCB has approval authority (unless explicitly delegated).

Practice this topic

Test yourself on PMP Fundamentals

JT Exams routes you to questions in your exact weak areas — automatically, after every session.

No credit card · Cancel anytime

Related certification topics