Study PMI-SP Baseline and Milestones: key concepts, common traps, and exam decision cues.
Baseline and milestone quality decide whether the schedule can support control. PMI-SP expects you to validate major milestones against scope and contractual commitments, then establish a performance measurement baseline that can actually be used.
Milestones are not just presentation markers. They are control points that need to align with scope, contracts, agreements, and major integration logic. Strong answers also recognize inter-project dependencies and the need to test whether milestone commitments are credible before baselining.
The performance measurement baseline matters because later variance and performance interpretation depend on it. A weak baseline creates false precision. A strong baseline reflects real logic, agreed assumptions, and clear measurement intent.
Stronger answers:
Weaker answers:
A contract milestone is shown as achievable, but its delivery path depends on external project activities that have not been validated. What is the strongest next step?
A. Baseline the schedule now so the team can start tracking immediately B. Validate the inter-project dependencies and milestone logic before finalizing the performance measurement baseline C. Remove the milestone until the other project finishes D. Replace the milestone with a summary task to reduce uncertainty
Best answer: B
PMI-SP expects milestone credibility to be tested before the baseline becomes authoritative. B addresses the dependency risk directly. A baselines too early. C hides the commitment instead of analyzing it. D changes structure without solving the logic problem.