Overview
Predictive, Plan-Based Methodologies is 17% of the CAPM exam, the smallest domain, covering the traditional, upfront-planning approach to projects. It has three tasks. Explaining when to use a predictive approach covers its suitability for different organizational structures, the activities within each process, and distinguishing project components. The project management plan and schedule covers applying critical path methods, calculating schedule variance, and explaining work breakdown structures and work packages, plus quality and integration management plans. Documenting project controls covers identifying the artifacts used in predictive projects and calculating cost and schedule variances.
As the smallest domain, it is focused but concept-rich, including some calculation. The exam rewards knowing when predictive fits, understanding the schedule and the critical path, decomposing work into a work breakdown structure, and computing basic variances. These predictive fundamentals complement the agile domain and build on the core concepts from Domain 1.
How it's tested
CAPM questions in this domain describe a predictive project situation and ask when predictive fits, how the schedule or critical path works, or a variance calculation. CAPM questions test understanding of fundamentals through knowledge and short scenario items, so read for the precise concept or technique being tested and choose the textbook-correct answer.
-
When to use predictive
A project or structure is described, and you judge whether a predictive, plan-based approach fits.
-
Schedule and critical path
A scheduling need is described, and you apply the critical path, WBS or work packages.
-
Controls and variances
A control or performance need is described, and you identify the artifact or calculate a variance.
A project has stable, well-understood requirements, a fixed scope, and a client who needs a detailed plan and schedule agreed upfront. These conditions suit a predictive, plan-based approach, which defines scope, schedule and cost in detail at the start and manages against that baseline, rather than an adaptive approach that iterates on evolving requirements. Recognizing that stable, well-defined requirements favor predictive delivery is the judgment the exam expects.
Domains 3
Official domains from the PMI outline, in outline order.
2.1 Explain when it is appropriate to use a predictive, plan-based approachSuitability by structure, process activities, and project components.
- What it means
- This covers identifying when a predictive, plan-based approach suits the organizational structure (virtual, colocated, matrix, hierarchical), determining the activities within each process, giving examples of typical process activities, and distinguishing the different project components.
- What to understand
- Predictive approaches suit projects with stable, well-defined requirements where scope, schedule and cost can be planned upfront and managed against a baseline. The organizational structure and the nature of the work influence suitability. Knowing when predictive fits, versus when an adaptive approach is better, is the core judgment.
- How it shows up
- A project's characteristics are described, and you must judge whether a predictive approach is appropriate.
- Common confusion
- Choosing predictive for evolving, uncertain requirements where an adaptive approach fits better.
2.2 Demonstrate an understanding of a project management plan scheduleCritical path, schedule variance, WBS, work packages, and quality and integration plans.
- What it means
- This covers applying critical path methods, calculating schedule variance, explaining work breakdown structures and work packages, and applying quality and integration management plans within the predictive schedule and plan.
- What to understand
- The critical path is the longest sequence of dependent activities, determining the shortest project duration; activities on it have no float. A work breakdown structure decomposes the scope into deliverables and work packages. Schedule variance compares planned to actual progress. These scheduling fundamentals are central to predictive planning.
- How it shows up
- A scheduling or planning need is described, and you must apply the critical path, WBS, or a schedule calculation.
- Common confusion
- Confusing the critical path (longest path, zero float) with the shortest path, or a WBS with a schedule.
2.3 Determine how to document project controls of predictive, plan-based projectsPredictive artifacts and cost and schedule variance.
- What it means
- This covers identifying the artifacts used in predictive, plan-based projects, and calculating cost and schedule variances to measure performance against the plan.
- What to understand
- Predictive projects use artifacts such as baselines, status reports and change logs to document and control the work. Performance is measured with variances: schedule variance and cost variance compare actual progress and spending to the plan, where negative values signal being behind or over budget. Knowing the artifacts and computing variances is the control skill.
- How it shows up
- A control or performance situation is described, and you must identify the artifact or calculate the variance.
- Common confusion
- Misinterpreting variance signs, where negative indicates behind schedule or over budget.
High-yield concepts
The terms, rules and formulas this domain turns into questions most often.
-
Predictive approach
Upfront planning against a baseline.
- Remember
- Suits stable, defined requirements.
- Tested as
- Approach questions.
- Trap
- Using it for evolving requirements.
-
Critical path
Longest path of dependent activities.
- Remember
- Determines the shortest duration; zero float.
- Tested as
- Schedule questions.
- Trap
- Confusing with the shortest path.
-
Float (slack)
Time an activity can slip without delay.
- Remember
- Critical path activities have zero float.
- Tested as
- Schedule questions.
- Trap
- Thinking critical activities have float.
-
Work breakdown structure
Hierarchical decomposition of scope.
- Remember
- Breaks work into deliverables and packages.
- Tested as
- Planning questions.
- Trap
- Confusing a WBS with a schedule.
-
Work package
The lowest level of the WBS.
- Remember
- A manageable unit of work.
- Tested as
- Planning questions.
- Trap
- Confusing it with a task list.
-
Schedule variance
Planned versus actual schedule progress.
- Remember
- Negative means behind schedule.
- Tested as
- Control questions.
- Trap
- Misreading the sign.
-
Cost variance
Planned versus actual cost.
- Remember
- Negative means over budget.
- Tested as
- Control questions.
- Trap
- Misreading the sign.
-
Baseline
The approved plan for comparison.
- Remember
- Measure performance against it.
- Tested as
- Control questions.
- Trap
- Not comparing to the baseline.
-
Quality and integration plans
Plans for quality and coordination.
- Remember
- Applied within the predictive plan.
- Tested as
- Planning questions.
- Trap
- Overlooking integration.
-
Predictive artifacts
Baselines, reports, change logs.
- Remember
- Document and control the project.
- Tested as
- Control questions.
- Trap
- Not using control artifacts.
Side by side
Concepts candidates mix up, compared on the point that decides the answer.
Predictive vs. adaptive suitability
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Predictive | Plan upfront, baseline | Stable, defined requirements | Using for uncertain work |
| Adaptive | Iterate and adjust | Evolving requirements | Using for fixed, stable scope |
Critical path vs. float
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| Critical path | Longest dependent path | Zero float, sets duration | Confusing with shortest path |
| Float | Allowable slip | Non-critical activities have it | Thinking critical activities have float |
WBS vs. schedule
| Concept | Meaning | Key difference | Common trap |
|---|---|---|---|
| WBS | Decomposition of scope | What the work is | Confusing with a schedule |
| Schedule | Timing of the work | When the work happens | Confusing with a WBS |
Exam traps
Each trap is an answer that looks right. Learn the clue that should change your mind.
-
Predictive for uncertainty
- What candidates pick
- Recommend a predictive, plan-based approach for a project with highly uncertain, evolving requirements.
- Why it looks right
- Upfront planning feels thorough.
- Why it's wrong
- Uncertain, evolving requirements suit an adaptive approach; predictive fits stable, well-defined requirements.
Clue to watch for Requirements are unclear and likely to change.
-
Critical path is shortest
- What candidates pick
- Identify the shortest sequence of activities as the critical path.
- Why it looks right
- Shortest sounds efficient.
- Why it's wrong
- The critical path is the longest path of dependent activities, which determines the shortest possible project duration.
Clue to watch for The question asks which path drives the project duration.
-
Critical activity has float
- What candidates pick
- Assume an activity on the critical path has float to spare.
- Why it looks right
- Most activities have some slack.
- Why it's wrong
- Critical path activities have zero float; any delay to them delays the whole project.
Clue to watch for The activity is on the critical path.
-
WBS is a schedule
- What candidates pick
- Treat the work breakdown structure as the project schedule.
- Why it looks right
- Both organize the work.
- Why it's wrong
- A WBS decomposes what the work is; the schedule shows when it happens.
Clue to watch for The need is timing versus scope decomposition.
-
Positive variance is bad
- What candidates pick
- Interpret a negative schedule or cost variance as good performance.
- Why it looks right
- Numbers can be confusing.
- Why it's wrong
- A negative schedule variance means behind schedule and a negative cost variance means over budget.
Clue to watch for The variance value's sign indicates performance.
Answer framework
For any Domain 2 scenario, use these steps to find the answer the CAPM expects.
- Judge whether the project suits a predictive approach: stable, well-defined requirements favor predictive over adaptive, since stable, well-defined requirements and a need for upfront planning favor predictive delivery.
- Build and understand the schedule, identifying the critical path (longest dependent path, zero float) and decomposing scope with a WBS into work packages.
- Apply the quality and integration management plans within the overall project plan.
- Document and control the project with predictive artifacts such as baselines and reports.
- Measure performance with schedule and cost variances, remembering negative values indicate behind schedule or over budget. Where two options seem to fit, choose the one that most precisely matches the textbook definition the question is testing.
Practice question
Want more like this? The CAPM practice test has questions for every domain.
Checklist
0 of 10
Tick each one you can do without notes. Your ticks stay in this browser.
Study strategy
Approach this smaller domain as the traditional, plan-based side of project management, and do not skip it despite its 17% weight. Start with judging when predictive fits: stable, well-defined requirements and a need for upfront planning favor predictive over adaptive. Then master the schedule fundamentals, especially the critical path (the longest dependent path with zero float) and the work breakdown structure that decomposes scope into work packages.
Because this domain includes the exam's main calculations, practice schedule and cost variance, and make sure you interpret the signs correctly, negative means behind schedule or over budget. Learn the predictive control artifacts and the quality and integration plans.
Since the CAPM is a knowledge exam, drilling the critical path concept and variance calculations with practice questions is the most effective preparation. Because the CAPM is a knowledge exam for entry-level candidates, flashcards on the key definitions and plenty of practice questions are highly effective, and reviewing missed questions by domain shows where to focus. Afterwards, move to Domain 3, Agile Frameworks and Methodologies.
FAQ
How much of the CAPM is Domain 2?
Predictive, Plan-Based Methodologies is 17% of the exam, the smallest domain, covering the traditional upfront-planning approach.
When is a predictive approach appropriate?
When requirements are stable and well defined, the scope is fixed, and detailed scope, schedule and cost can be planned upfront and managed against a baseline. Uncertain, evolving requirements favor an adaptive approach instead.
What is the critical path?
The longest sequence of dependent activities through a project, which determines the shortest possible project duration. Activities on the critical path have zero float, so delaying any of them delays the whole project.
What is a work breakdown structure?
A hierarchical decomposition of the project scope into smaller deliverables and work packages. It defines what the work is, distinct from the schedule, which defines when the work happens.
How do I interpret schedule and cost variance?
A negative schedule variance means the project is behind schedule, and a negative cost variance means it is over budget. Positive values mean ahead of schedule or under budget.
What artifacts do predictive projects use?
Baselines for scope, schedule and cost, along with status reports, change logs and other control documents used to measure and manage performance against the plan.
How does Domain 2 connect to the rest of the exam?
It applies the fundamentals from Domain 1 to predictive delivery, complements the agile approach in Domain 3, and relates to the requirements and delivery concepts in Domain 4.
Other Project Management certifications
Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.
- PRINCE2 7 Practitioner Study guide
- PMI Risk Management Professional Study guide
- PMI Scheduling Professional Study guide
- Project Management Professional Study guide
- CompTIA Project+ Study guide
- PRINCE2 7 Foundation Study guide
- Portfolio Management Professional Study guide
- Program Management Professional Study guide
- Agile Project Management Study guide
- PMI Agile Certified Practitioner Study guide
- Project Management Professional (PMBOK 7) Study guide
- Disciplined Agile Scrum Master Study guide
Test your Domain 2 knowledge
You have covered when to use predictive, the schedule and critical path, and project controls. Test whether you can apply predictive methods and variances under exam conditions.