Predictive, Plan-Based Methodologies · Topic 1 of 3
When to Use a Predictive Approach
When a predictive, plan-based approach fits for CAPM: suitable conditions and structures, activities in each process group and key project components.
- 3 min
- Predictive suits clear, stable requirements and a high cost of change.
- Scope, schedule and cost are planned early and baselined.
- Changes go through formal change control.
What it is
A predictive (plan-based, often called waterfall) approach defines scope, schedule and cost as early as possible, then delivers the work in planned phases. Changes are controlled carefully against approved baselines.
It works best when the requirements are clear and stable, and when changing course late would be expensive or unsafe.
How it works
When predictive fits
| Condition | Why predictive fits |
|---|---|
| Requirements are well known and unlikely to change | Detailed upfront planning stays valid |
| High cost of change late in the project | Getting it right first avoids rework, as in construction |
| Regulatory or contractual need for detailed plans | Approvals and documentation are required up front |
| The technology and method are proven | Little experimentation is needed |
| Value can only be used when everything is finished | Partial delivery has little use, such as a bridge |
When requirements are uncertain or customers need early feedback, an adaptive or hybrid approach usually fits better.
Organizational structure
| Structure | Effect on a predictive project |
|---|---|
| Hierarchical or functional | Clear lines of authority and formal approvals match plan-based control |
| Matrix | Team members report to a functional manager and a project manager; plans and agreed resource commitments help manage shared people |
| Colocated | Easier coordination, but predictive projects do not depend on it |
| Virtual | Clear written plans, schedules and communication plans help distributed teams work to the same baseline |
Predictive methods suit organizations that value formal documentation, defined roles and phase approvals.
Activities in each process group
| Process group | Typical predictive activities |
|---|---|
| Initiating | Develop the charter; identify stakeholders |
| Planning | Collect requirements; define scope; create the WBS; build the schedule and budget; plan quality, risk, communications and procurement |
| Executing | Direct the work; manage the team; manage quality; conduct procurements; manage communications |
| Monitoring and Controlling | Track performance; perform integrated change control; validate and control scope; control schedule and cost; control quality; monitor risks |
| Closing | Close the project or phase; obtain final acceptance; archive records; release resources |
Project components
| Component | Meaning |
|---|---|
| Phase | A collection of related activities ending in one or more deliverables |
| Deliverable | A unique, verifiable product, result or capability produced to complete a process, phase or project |
| Milestone | A significant point or event, zero duration |
| Activity | A scheduled piece of work with a duration |
| Work package | The lowest level of the WBS, where cost and duration are estimated and managed |
| Baseline | The approved version of scope, schedule or cost, used for comparison |
If a question describes a construction or manufacturing project with fixed specifications and regulatory approvals, predictive is almost always the intended answer.
How the exam asks about this
- "Requirements are fixed and the cost of late change is high. Which approach?" Predictive.
- "In which process group is the WBS created?" Planning.
- "What is the lowest level of the WBS?" The work package.
What to remember for the exam
- Predictive suits clear, stable requirements and a high cost of change.
- Scope, schedule and cost are planned early and baselined.
- Changes go through formal change control.
- Functional and hierarchical structures fit predictive control well.
- Know which activities belong to each process group.
Predictive does not mean "no change". Change happens, but through a formal change control process.
Common mistakes
Choosing predictive when requirements are unclear. Uncertainty points to adaptive or hybrid.
Calling a milestone an activity. A milestone has no duration.
Putting scope validation in Executing. It is a Monitoring and Controlling activity.
Check yourself
When is a predictive approach most appropriate?
When requirements are clear and stable and the cost of change late in the project is high.
What is a deliverable?
A unique, verifiable product, result or capability produced to complete a process, phase or project.
In which process group does integrated change control happen?
Monitoring and Controlling.
Topic 1 of 3 in Predictive, Plan-Based Methodologies
Test yourself on Predictive, Plan-Based Methodologies
The full PMI CAPM question bank has 1,049 questions, with timed practice exams and an explanation for every answer.
This study guide is independent and is not affiliated with, endorsed by, or sponsored by PMI. Vendor names, certification names and exam codes are trademarks of their respective owners and are used for identification only.