When a Predictive Approach Fits

A predictive, plan-based approach suits work where requirements are well understood up front and unlikely to change much — construction, regulatory-driven work, or anything where the cost of changing course late is very high. It also tends to fit more naturally with hierarchical or functional organizational structures, where approvals flow through defined layers, than with highly virtual, fast-moving teams — though CAPM frames this as "more suited to," not an absolute rule, since even matrix or virtual teams sometimes run predictive projects.

Within a predictive approach, work is organized into processes (such as planning, executing, and controlling), each made up of recognizable, repeatable activities — a planning process includes defining scope and building a schedule; an executing process includes directing the team's work and managing stakeholder engagement. Project components are the pieces a plan-based project plan is built from — scope statements, schedules, budgets, and similar named artifacts — and the exam expects you to tell these components apart rather than treat "the plan" as one undifferentiated document.

Study focus: expect scenarios that describe an organization's structure and project characteristics, then ask whether a predictive approach is the right fit — the test isn't memorizing a rule, it's recognizing the pattern of stable requirements plus a structure that supports top-down planning.