PMP Exam Prep: The Basics Most Candidates Get Wrong

Here's something I noticed after years of coaching and mentoring project managers one-on-one for the PMP exam: the candidates who failed — almost without exception — didn't fail because the exam was too hard.

They failed because they never truly locked in the foundation. They jumped straight into the complex stuff — risk quantification, earned value, procurement strategy — without building a solid base. And when the exam threw a foundational concept at them dressed up in a complex scenario, they got it wrong every time.

This article covers the basics — the concepts that appear in every single section of the PMP exam. Get these right and everything else gets easier.

What Is a Project? (And What It's NOT)

This is the first concept PMI tests — and the first one candidates take for granted.

A project is a temporary endeavor undertaken to create a unique product, service, or result. Two words carry all the weight there: temporary and unique.

Temporary

Every project has a defined beginning and a defined end. If there is no end in sight — it's not a project. It's operations.

Unique

No two projects produce exactly the same result. Even if you build the same type of infrastructure twice, the context, team, risks, and constraints will differ.

Project vs. Operations — Know the Line

This distinction will appear on your PMP exam, guaranteed:

Temporary Does NOT Mean Short

A project can run for a week or for seven years. Duration is irrelevant. What makes it a project is that it ends.

Projects end for several reasons — and PMI expects you to know all of them:

• Objectives met — the scope, deadline, or budget goal is achieved
• Deadline passed — the opportunity tied to the project no longer exists
• Funds depleted — the team does as much as possible within available budget
• Need no longer exists — better technology or a change in strategy makes the project obsolete
• Legal or regulatory change — a new law or regulation makes the project non-compliant
• Resources unavailable — a key team member, skill set, or material is no longer accessible

Any of these can appear as answer choices on a PMP exam question. Know them cold.

Projects Drive Change: The MACD Framework

Every project drives change — specifically, it moves an organization from its current state to a desired future state. There are only four ways a project achieves that:

• M — Move — relocate data, systems, or teams
• A — Add — build a new capability or feature
• C — Change — modify a workflow, system, or process
• D — Delete — retire a legacy system or remove a process

This is called the MACD framework — Move, Add, Change, Delete.

The Transition State — Don't Ignore It

Between the current state and the desired future state, there's often a period where both the old and new systems run in parallel. This is called the transition state.

For example: a company migrating from on-premise servers to the cloud can't flip the switch overnight. For weeks or months, both systems run simultaneously. That dual-running period introduces risk, resource pressure, and complexity that has to be planned for.

The exam will test whether you understand that the transition state exists and must be actively managed — not just acknowledged.

Business Value: The Reason Every Project Exists

Business valueis the benefit — the return — that a project delivers to the organization, its stakeholders, or its customers. No business value. No project. It's that simple.

Tangible Business Value

• Increased revenue or profit
• New equipment or infrastructure
• Market share gained
• Cost savings from automation
• Software that eliminates manual hours

Intangible Business Value

• Brand reputation
• Customer trust and loyalty
• Strategic alignment
• Regulatory compliance
• Goodwill and public benefit

The Business Case

Business value is formally documented in the Business Case — the document that answers one question: Why is this project worth investing in?

If an organization can't articulate the business value of a project — it shouldn't be doing the project. On your exam, whenever you see a question about why a project was initiated or why it should be continued, think business value first.

Why Projects Get Initiated: The 4 Triggers

PMI defines four reasons why organizations start projects. Know all four — they appear in exam questions regularly.

1. Regulatory, Legal, or Social Requirements

A new law passes. A regulation changes. The organization must run a project to stay compliant. The business value is clear even if the project wasn't wanted: avoid fines, avoid shutdown, stay operational.

2. Stakeholder Requests

A client needs a custom solution. An internal team needs a system upgrade. An executive wants a new capability. Projects are initiated in response to someone who has authority and need.

3. Technology Advancement

AI is forcing organizations to run projects they didn't plan for two years ago. In construction, a new material changes what's possible. In manufacturing, new equipment changes production capacity. When technology moves forward, projects follow.

4. Creating, Improving, or Fixing Existing Products, Processes, or Services

Your onboarding process takes three weeks — run a project to cut it to five days. Your product has a critical defect — run a project to fix it. Your reporting process is manual — run a project to automate it. This is the most common trigger for projects in established organizations.

What Is Project Management?

The official PMI definition: Project management is the application of knowledge, skills, tools, and techniques to meet project requirements.

The practical version: project management is what makes change happen — in an organized, controlled, and accountable way. Without it, you get scope creep, budget overruns, missed deadlines, and angry stakeholders. With it, you have structure, predictability, and a plan.

What a PM Actually Does

• Gathering requirements — understanding what stakeholders need, not just what they say they want
• Communicating constantly — this is 80% of the job
• Managing stakeholders — anyone who affects or is affected by the project
• Balancing constraints — scope, schedule, cost, quality, resources, and risk
• Tailoring processes — using only what the project actually needs from the PMBOK's 49 processes
• Delivering business value — connecting every decision back to why the project exists

The Iron Triangle

The three primary constraints — Time, Cost, and Scope — form the Iron Triangle. Pull one side, and the other two are affected. Your job as a PM is to keep all three in balance while managing quality, resources, and risk around them.

Two Life Cycles — Know the Difference

This is a concept the PMP exam tests directly, and many candidates confuse the two.

Project Management Life Cycle

Universal. Every project, in every industry, follows the same five process groups:

1. Initiating
2. Planning
3. Executing
4. Monitoring & Controlling
5. Closing

Project Life Cycle

Unique to each type of project. It describes the specific phases your project goes through based on the type of work being done. Each phase produces a deliverable. The end of each phase creates a milestone — a significant checkpoint.

Progressive Elaboration: Why Your Early Estimates Are Supposed to Be Rough

Progressive elaboration means you start broad and get more specific as you gather more information. Your plan sharpens over time. Your estimates become more accurate as requirements become clearer.

Early in a project: "This will probably take 3 to 6 months."
Four weeks later, after requirements gathering: "14 weeks, $180,000, three engineers."

Same project. More information. Better estimate. This is not a flaw in your planning — it's how professional project management works. PMI expects you to understand that early estimates carry more uncertainty, and that this uncertainty decreases as the project progresses.

Your 7 Exam Anchors from This Lesson

Before you move on, make sure you can explain each of these out loud without looking at your notes: