PMPilot

Start here

Practice examExam

Reading a PMP Question

5 min read

Reading a PMP Question

PMP Decision Rules gives you the rules. This page is the part nobody teaches: how you get from a wall of scenario text to the rule that applies. Knowing 200 rules is worth nothing if you cannot tell which one the question is asking about.

Every PMP question is a decision you make on a real project, compressed into four lines. Read it in two layers, in this order, and always finish with a third.

Layer 1 — Context: what situation am I in?

Before you read a single option, name the situation. The stem always tells you, usually in three or four phrases:

  • The approach. Predictive, agile, hybrid. This alone rules out whole families of answers.
  • The moment. Planning, mid-execution, at a status date, at closing.
  • The trigger. What just happened, or what has been handed to you.
  • Your position. What you own, and what you would need someone else for.

Circle those phrases. Everything else in the stem is set dressing.

The tell that you are doing this right: you can predict the shape of the right answer before you look at the options. If you cannot, you have not found the context yet, and reading the options first will just make the two plausible ones fight each other in your head.

Layer 2 — Rule: which rule fires?

The context selects the rule. Retrieve it before you look down, and state it in one line.

That line is the whole test. If you can say it, the options sort themselves. If you cannot, you are about to pick the answer that sounds most reasonable, which is exactly what the distractors are built for.

The rule is not a formula in the numeric sense. assess before you act, the risk became an issue, check the plan first are rules. So is CPI = EV/AC, and below 1.0 is bad. Both kinds do the same job: they turn a situation into a decision without requiring you to have seen this exact question before.

Layer 3 — Decision: so what do I do on Monday?

The explanation stops when it has justified the letter. Do not stop there.

Say what you would actually do with the answer on a live project. This is what makes the rule stick, because it stops being exam trivia and becomes something you have decided before. It is also the step that catches a rule you have memorised but not understood.

Worked example — a numbers question

On a predictive project the budget at completion (BAC) is 80,000**, the actual cost is 90,000. How is the project performing, and what does it imply?

  • Context. Predictive, a status date, and three of the four EVM inputs. This is a progress-evaluation question. You know that before reading any option.
  • Rule. CPI = EV/AC and SPI = EV/PV. Below 1.0 is bad, both ways. Here 0.8 and 0.89, so over budget and behind schedule. (See Earned Value Management (EVM).)
  • Decision. EAC = BAC/CPI = 50,000 forecast overrun, with the number attached.

The wrong options are each a failure of one layer. “Ahead of schedule and under budget” inverts the rule. “On budget but only slightly behind” applies it but refuses to believe a 20% overrun is real. “Not enough data” fails the context read, because EV, AC and PV are exactly the inputs the method needs.

Worked example — a behavioural question

The same three layers work when there is no arithmetic anywhere.

A key stakeholder tells you, informally, that a regulatory change next quarter may affect your scope. What should the project manager do first?

  • Context. Execution, new information, informal source, nothing confirmed yet. The trigger is information, not a problem.
  • Rule. assess before you act. Unverified information is analysed and recorded before anyone changes a plan or escalates.
  • Decision. You log it as a risk and go verify it. You do not raise a change request on a rumour, and you do not sit on it either.

Notice the distractors this rules out in advance: anything that skips straight to a change request, an escalation, or an update to the schedule. You knew those were wrong from the context alone.

How to practise it

Do not run this on questions you get right. Run it on every one you get wrong:

  1. Cover the options. Read the stem and write the context in one line.
  2. Write the rule you think fires, in one line, before looking down.
  3. Read the options and pick.
  4. Whether you were right or wrong, write the decision line — what you would do on Monday.

If step 2 came out blank, that is not a question you got wrong. That is a rule you do not have yet. Add it to your own copy of PMP Decision Rules.

Drill this

The two-layer read only becomes automatic under time pressure. ▶ 10 questions, no signup in the PMPilot exam app. Every question has a written explanation.

Graph View

Backlinks