September 7, 2026 · 6 min read
TL;DR: Milestones appear in 45 of the bank's answer options: 9 keyed, 36 wrong. The keyed ones rest on what a milestone is, a zero-duration marker, or on who a milestone report is for. The wrong ones use a milestone as a governance venue, a payment trigger, or a progress measure, none of which a moment in time can do.
A milestone is the simplest object in scheduling and one of the more reliably mishandled. Its whole definition is that it takes no time, and almost every wrong answer in this set quietly assumes it takes some.
A significant point in time with zero duration, used to mark an achievement. One bank item tests only that.
Colleagues tell you they are planning, executing, and monitoring their project using only milestones, each given a duration of one to four weeks. The options let you approve the approach under three different conditions, or call it flawed. Keyed: the approach is flawed, because a milestone is a significant point in time with zero duration used to mark an achievement.
Assigning it a one-to-four-week duration confuses a milestone with an activity or a work package. And the item is deliberately built so the conditions do not save it. It is not fine if the milestones reflect only imposed dates. It is not fine if they are used only for phase reviews. It is not fine because it spares the team from measuring progress on activities. The approach is wrong regardless of how the milestones are used, because the objects themselves have been misdefined.
That is unusual for this bank, which mostly tests judgment. Here it tests one line of doctrine, which makes it free marks if you hold the definition precisely.
Nine times, and the two clearest cases are both about communication rather than scheduling mechanics. The rest sit alongside them: milestones estimated from historical data when priorities are uncertain, common milestones shared across two teams, milestones gathered for a charter, and milestone trend analysis as a forecasting technique.
When the audience is senior. A project manager in a large organisation running many similar projects must report status to senior management in a form that gives them what they need quickly. The options are project management plans, detailed schedules, Gantt charts, and milestone reports. Keyed is the milestone report, as the only choice fitting a need for a quick high-level view. The others carry redundant or overly detailed information for that purpose.
When drift is the threat. A public aquatic centre needs to open quickly. The crew is skilled, stakeholders are engaged, the community is enthusiastic. Keyed is building a milestone-based plan with regular stakeholder involvement and communication.
The reasoning there is the best argument for milestones anywhere in the bank. This project has the ingredients that usually make delay avoidable, so the threat is not capability but drift: an opening date slipping a little at a time because nobody sees the slippage until it is large. Milestones prevent exactly that, because they are binary and public. One is either met on its date or it is not, and reviewing them regularly makes a slip visible to everyone who could help while there is still room to recover.
Common trap: using a milestone as a governance event or a payment trigger. Both are offered and both lose. In one item, an experimental machine learning product with no stable specification needs quality assurance, and stage-gate milestone reviews at which the sponsor decides whether the project continues are offered. Keyed is pair programming with customer feedback sessions, because with no stable specification to inspect against, quality has to be built into how the work is done rather than inspected in afterwards. In another, a subcontractor demands immediate payment for out-of-scope work, and initiating a change to add the payment milestone is offered. Keyed is raising a change request and reviewing the contract to evaluate payment options first, because agreeing a payment milestone commits to terms nobody has approved. A milestone marks that something happened. It does not decide anything and it does not pay anyone.
A milestone reports that a moment arrived. When the stem wants a decision, a payment, or a quantity, the exam keys something else.
| The stem wants | Milestone option offered | Keyed |
|---|---|---|
| A quick high-level view for senior management | Milestone reports | Milestone reports |
| To prevent slow schedule drift on a well-resourced project | Milestone-based plan with stakeholder reviews | Milestone-based plan |
| Quality on an experimental product with no spec | Stage-gate milestone reviews | Pair programming plus customer feedback |
| To respond to a subcontractor's payment demand | Add the payment milestone | Change request and contract review first |
| Progress and remaining work across agile projects | Progress milestone review | Sprint burn-up chart |
That last row is worth reading closely, because it is the one where a milestone almost works. Executives ask for progress and remaining work across ongoing agile projects. A progress milestone review is offered and loses to a sprint burn-up chart. The burn-up plots both things the executives asked for as separate lines: cumulative work completed rising from the bottom, total scope drawn as its own line above it, with the gap between them showing what remains. Movement in the scope line stays visible, which matters because efficiency directives tend to change scope. A burndown chart, with its single descending line, would make added scope look like a team that has stopped progressing.
A milestone tells you a moment arrived. When the question asks how much is left, you need a measure with a quantity in it.
What is a milestone on the PMP exam? A significant point in time with zero duration, used to mark an achievement. One bank item is keyed entirely on that definition: planning with milestones given one-to-four-week durations is flawed because it confuses milestones with activities or work packages.
Why is a milestone report the right format for senior management? Because it gives a high-level view quickly. The bank keys it over project management plans, detailed schedules and Gantt charts, all of which carry redundant or overly detailed information for that audience.
Is a milestone-based plan ever the keyed answer? Yes, when the risk is schedule drift rather than capability. Milestones are binary and public, so a slip becomes visible to everyone who could help while there is still room to recover.
Can a milestone have a duration if it represents a phase? No. A phase has duration; the gate at its end is the milestone. The bank rejects one-to-four-week milestones outright, including when they are used only for reviews between consecutive phases.
PMP Practice's 2,141 questions are certified against PMBOK 8 and the July 2026 ECO, with every wrong answer explained rather than just marked wrong. Start the free 20-question sample — no card, no signup required to try it.
Related reading: Building the Schedule: Which Estimating Technique the Exam Wants and Critical Path Method (CPM) & Float. Schedule tasks are mapped on the Process domain study page.
What is a milestone on the PMP exam?
A significant point in time with zero duration, used to mark an achievement. One bank item is keyed entirely on that definition: planning with milestones given one-to-four-week durations is flawed because it confuses milestones with activities or work packages.
Why is a milestone report the right format for senior management?
Because it gives a high-level view quickly. The bank keys it over project management plans, detailed schedules and Gantt charts, all of which carry redundant or overly detailed information for that audience.
Is a milestone-based plan ever the keyed answer?
Yes, when the risk is schedule drift rather than capability. Milestones are binary and public, so a slip becomes visible to everyone who could help while there is still room to recover.