PMI-SP Domain 1: Schedule Strategy (14%)

Overview

Schedule Strategy covers the decisions a scheduler makes before planning starts: how schedule files and baselines are stored, versioned and changed; which approach (CPM, critical chain, rolling wave, agile release planning) fits this project; which tool, update cycle, thresholds and earned value rules apply; and how those choices are written into the schedule management plan and the other subsidiary plans.

The domain also asks you to explain all of this to the team, because a schedule policy nobody follows is a document, not a control. Expect questions where the right answer is to set or fix a rule rather than edit a date. Domain 2 builds the model under these rules, Domain 3 enforces them through status cycles and change control, and Domain 4 archives under the retention rules you defined.

Why it matters on the exam

At 14% this is a smaller domain, but its decisions resurface throughout the exam. A Domain 3 question about an unexplained baseline change is really asking whether configuration control existed; a Domain 4 question about missing files depends on archiving rules set here. Candidates struggle because Schedule Strategy questions describe a problem that looks technical, such as a slipping date or a tool conflict, when the root cause is a missing policy. Experienced schedulers also tend to reach for the approach they always use rather than tailoring it to contract type, life cycle and organizational process assets. Weak understanding here costs points twice: once in this domain, and again whenever a later scenario hinges on whether the right governance was already in place.

How it's tested

Questions in this domain are mostly situational: a new project, a merger of two scheduling cultures, a contract with reporting clauses, or a team ignoring update rules. You choose the BEST policy, the FIRST thing to establish, or the most appropriate scheduling approach. Few calculations appear here; the skill tested is matching governance decisions to project characteristics.

Policy before action

A problem such as conflicting file versions or unexplained baseline edits appears, and the answer is to establish or enforce a configuration or change-control rule rather than fix the symptom.
Tailor the approach

Project traits (contract type, uncertainty, life cycle, resource scarcity) are listed, and you pick the scheduling method or level of detail that fits them.
Plan component placement

You decide which plan should hold a scheduling rule, for example update frequency in the schedule management plan versus baseline change approval in the change management plan.

Reasoning it through

A government contract requires monthly earned value reporting, but the organization has no defined percent-complete rules. The team asks which tool to buy. Reasoning: the tool is secondary; the gap is a policy. Define earned value methods and measurement rules in the schedule management plan first, then select a tool that can produce the required reports. Answers that start with software or with a re-baseline skip the governance step.

Tasks 5

Official tasks from the PMI outline, in outline order.

1.1 Establish project schedule configuration management policies and proceduresRules for storing, accessing, versioning and changing schedule files and baselines.

What it means: You define where the schedule model lives, who can edit it, how versions are named, and how a baseline can be changed, drawing on best practice, regulation and contract terms.
What to understand: Configuration management protects the integrity of the schedule as an artifact: the approved baseline must be reproducible, and every working version must be traceable to a status date and change record.
How it shows up: Two teams report different finish dates from 'the schedule', or a baseline was overwritten during an update; the correct response creates or enforces version and access control.
Common confusion: Candidates equate configuration management with change control. Change control decides whether a change is approved; configuration management controls the files and versions that record it.

1.2 Develop schedule approach based on the unique characteristics of the projectChoose method, detail level and planning horizon to fit the project.

What it means: You select how the schedule will be built, for example CPM with rolling wave detail, critical chain with buffers, or agile release planning, based on size, risk, contract and organizational process assets.
What to understand: The approach follows from project traits: high uncertainty favors rolling wave or iterative planning, scarce shared resources favor resource-constrained or critical chain methods, and fixed-price contracts with milestone payments need detailed, logic-driven networks.
How it shows up: A scenario lists traits such as long duration, unclear later phases and a firm first milestone; the best answer is near-term detail with planning packages for later work.
Common confusion: Choosing the most detailed approach for every project. Excess detail in uncertain future phases creates false precision and constant re-planning.

1.3 Establish scheduling policies and procedures regarding methodology and selection of a scheduling toolMethodology, tool, thresholds and earned value rules for the schedule management plan.

What it means: You set the scheduling methodology, select the tool, define update cycles, units, calendars, variance thresholds and earned value measurement methods, and record them in the schedule management plan.
What to understand: Thresholds (for example, SPI below 0.95 or a 10-day finish variance) trigger action, so they must be defined before execution; earned value rules such as 0/100, 50/50 or weighted milestones must be chosen per work type.
How it shows up: Reports show variances but nobody acts on them; the answer is that control thresholds and escalation rules were never set in the schedule management plan.
Common confusion: Selecting the tool before the methodology. The tool must support the chosen method and reporting obligations, not dictate them.

1.4 Develop the scheduling-related components for project management plansScheduling content inside integration, scope, cost, risk, resource and communication plans.

What it means: You contribute scheduling content to other subsidiary plans, such as baseline change routes in integrated change control, reporting cadence in the communications plan, and schedule reserve rules in the risk plan.
What to understand: The schedule management plan cannot work alone; its rules must be consistent with how scope is decomposed, how cost is time-phased, and how risks are funded with time contingency.
How it shows up: A question asks which plan should document how schedule contingency is released, or where the WBS dictionary links to activities; pick the plan that owns that decision.
Common confusion: Placing every scheduling rule only in the schedule management plan and missing that integrated change control in the overall project management plan governs baseline changes.

1.5 Provide information about project scheduling objectives and goals, the role of the scheduler, and proceduresOrient the team on scheduling goals, roles and procedures.

What it means: You brief team members and activity owners on why the schedule exists, what the scheduler does and does not own, and how and when to give status.
What to understand: Activity owners provide status and estimates; the scheduler maintains the model, analyzes it and reports. Clear roles prevent owners from editing logic directly or scheduler-invented progress.
How it shows up: Status is late or inconsistent soon after kickoff; the best first action is to explain the update procedure and owner responsibilities, not to escalate or replace staff.
Common confusion: Assuming the scheduler should estimate durations alone. The ECO expects estimates from people doing the work, with the scheduler facilitating.

High-yield concepts

The terms, rules and formulas this domain turns into questions most often.

Schedule management plan

The subsidiary plan that states the scheduling methodology, tool, level of accuracy, units, update cycle, control thresholds, performance measurement rules and reporting formats for the project.

Remember
If a scenario reveals inconsistent units, update timing or variance responses, the missing or ignored element belongs in the schedule management plan.

Tested as
It is the default answer for 'where should this scheduling rule be defined' questions in Domain 1.

Trap
Treating the schedule management plan as the schedule itself; it governs the model and contains no activity dates.
Schedule configuration management

Version naming, storage, access rights and baseline protection rules that let anyone reproduce the approved baseline and every reported update.

Remember
A baseline must never be overwritten; each update is saved as a new version tied to a status date.

Tested as
Appears when files conflict, data is lost, or an auditor cannot trace a date change to its source.

Trap
Choosing 'restrict tool licenses' as the fix when the real gap is undefined version and baseline control procedures.
Control threshold

A predefined variance limit, such as SPI below 0.95 or a milestone slipping more than five working days, beyond which the scheduler must analyze and escalate.

Remember
Thresholds are set in planning and trigger action during execution; a variance inside the threshold is reported, not escalated.

Tested as
Scenarios test whether a variance requires escalation or corrective action under the agreed limits.

Trap
Escalating every variance; that floods sponsors and ignores the agreed tolerance.
Rolling wave planning

Detailing near-term work into activities while keeping later work at work-package or planning-package level, refined as information arrives.

Remember
It is a deliberate approach chosen in strategy, with a defined horizon (for example, detail the next 90 days) and refinement cycle.

Tested as
The best-fit approach for long projects with uncertain later phases.

Trap
Mistaking rolling wave for a lack of planning; the later packages still carry budget and duration in the baseline.
Critical chain method

A resource-constrained scheduling method that strips safety from activity estimates and pools it into project and feeding buffers, then manages by buffer consumption.

Remember
Buffers protect the finish date; the critical chain accounts for resource dependencies, not only logic.

Tested as
Chosen in strategy when shared, scarce resources and multitasking drive delay.

Trap
Calling the critical chain the same as the critical path; the critical path ignores resource limits.
Earned value measurement methods

Rules for crediting earned value, such as 0/100 for short tasks, 50/50 for tasks spanning two periods, weighted milestones for long tasks, percent complete for measurable work, and level of effort for support work.

Remember
The method is chosen per work package type during planning and recorded in policy, not invented at reporting time.

Tested as
Strategy questions ask which method fits a described task type.

Trap
Using subjective percent complete for long, hard-to-measure tasks, which inflates early progress.
Level of detail and accuracy

The planned granularity of activities (for example, durations of one to two reporting periods) and acceptable estimate ranges for each phase.

Remember
Detail should let progress be measured within a status cycle; activities far longer than the cycle hide slippage.

Tested as
Shows up in approach and policy questions about update frequency and measurability.

Trap
Believing more activities always means better control; too many tiny activities make updating unreliable.
Organizational process assets (OPAs)

Templates, calendars, historical durations, scheduling standards and lessons learned that the organization already holds.

Remember
Check OPAs before building new policy; tailoring starts from what exists.

Tested as
Often the correct FIRST step when establishing a schedule approach.

Trap
Writing policy from scratch and ignoring mandated corporate scheduling standards.
Integrated change control

The project-level process that reviews and approves changes to any baseline, including the schedule baseline, through a defined authority such as a change control board.

Remember
The scheduler can model a proposed change but cannot approve a baseline change alone.

Tested as
Strategy questions ask you to define this route before execution.

Trap
Letting the project manager informally re-baseline because a date slipped.
Scheduler role

The scheduler builds and maintains the model, collects and validates status, analyzes performance and forecasts; activity owners provide estimates and progress.

Remember
Ownership of estimates and progress sits with the people doing the work.

Tested as
Appears in orientation and status-quality questions.

Trap
Choosing an answer where the scheduler sets durations unilaterally to meet a target.

Side by side

Concepts candidates mix up, compared on the point that decides the answer.

Configuration management vs. change control vs. version control

Concept	Meaning	Key difference	Common trap
Configuration management	Policies for identifying, storing, accessing and protecting schedule artifacts and baselines	Governs the integrity and traceability of files	Assuming it approves changes
Change control	Process to evaluate and approve or reject changes to baselines	Governs decisions about content	Assuming it tracks file versions
Version control	Naming and saving each schedule update as a distinct, dated version	A mechanism inside configuration management	Overwriting the working file each cycle and losing the history needed for forensic analysis

Critical path method vs. critical chain vs. rolling wave

Concept	Meaning	Key difference	Common trap
Critical path method (CPM)	Logic-driven network that finds the longest path and total float	Assumes resources are available unless leveled separately	Applying it to resource-starved projects without leveling
Critical chain	Resource-constrained path with aggregated project and feeding buffers	Manages by buffer consumption, not float	Keeping padded estimates and adding buffers too, which double-counts safety
Rolling wave	Progressive elaboration of near-term work in detail	A detailing strategy usable with either method	Treating it as an alternative to CPM rather than a planning horizon technique

Schedule management plan vs. schedule baseline vs. schedule model

Concept	Meaning	Key difference	Common trap
Schedule management plan	Rules for building and controlling the schedule	Contains policy, not dates	Updating it every status cycle
Schedule model	The working network of activities, logic, durations and resources in the tool	Changes every update	Reporting the model as if it were the baseline
Schedule baseline	The approved version of the model used to measure performance	Changes only through formal change control	Re-baselining to make variances disappear

Exam traps

Each trap is an answer that looks right. Learn the clue that should change your mind.

Fixing the symptom instead of the policy

What candidates pick
Manually reconciling two conflicting schedule files and redistributing the result.

Why it looks right
It solves the immediate confusion quickly and looks helpful.

Why it's wrong
The conflict will recur because no version or access procedure exists; Domain 1 rewards establishing the control.

Clue to watch for Words like 'again', 'different versions' or 'no one knows which file is current' point to configuration management.
Tool-first thinking

What candidates pick
Purchase or standardize on a new enterprise scheduling tool.

Why it looks right
Tools feel like a concrete, visible fix and vendors promise integrated reporting.

Why it's wrong
Without methodology, thresholds and earned value rules, a new tool reproduces the same inconsistency.

Clue to watch for The scenario mentions inconsistent methods or reporting rules, not tool capability limits.
Maximum detail everywhere

What candidates pick
Decompose the entire multi-year project into daily activities at the start.

Why it looks right
More detail sounds more rigorous and controllable.

Why it's wrong
Later phases lack the information to support that detail, so estimates are guesses that force constant re-planning.

Clue to watch for Statements such as 'design for phase 3 is not yet defined' signal rolling wave planning.
Scheduler as estimator

What candidates pick
The scheduler sets durations from experience to save time.

Why it looks right
Experienced schedulers often know typical durations.

Why it's wrong
Estimates lose ownership and credibility; the ECO expects subject matter experts and activity owners to provide them.

Clue to watch for Look for activity owners who later dispute dates they never estimated.
Escalate every variance

What candidates pick
Report a three-day slip to the sponsor immediately.

Why it looks right
Transparency seems always correct.

Why it's wrong
If the variance is inside the threshold in the schedule management plan, the agreed response is to monitor and report routinely.

Clue to watch for The scenario gives both the variance size and a stated threshold; compare them before acting.
Plan placement confusion

What candidates pick
Record baseline change approval authority only in the schedule management plan.

Why it looks right
It is a schedule baseline, so the schedule plan seems the natural home.

Why it's wrong
Approval of any baseline change runs through integrated change control in the project management plan; the schedule plan references it.

Clue to watch for Words such as 'approve', 'authority' or 'change control board' point to the change management process.

Answer framework

Use this sequence when a Schedule Strategy question asks what to establish or do first.

Identify whether the problem is a missing rule, an unenforced rule, or a genuine technical issue inside the schedule model itself.
Check organizational process assets, contract clauses and regulations for mandated scheduling standards before inventing new policy.
Match the scheduling approach and detail level to project traits such as uncertainty, resource scarcity, life cycle and contract type.
Write the rule into the correct plan: methodology, tools, thresholds and earned value methods in the schedule management plan; baseline approval in integrated change control.
Communicate the rule and the division of roles to activity owners, then confirm compliance at the first status cycle and correct any drift early.

Practice question

Midway through a program, an auditor cannot reconcile last quarter's reported finish date with any saved schedule file. The scheduler overwrites the master file after each weekly update. What should the scheduler do FIRST?

Re-baseline the schedule so future reports start from a clean reference Establish version control and baseline storage procedures and apply them from the next update Ask activity owners to re-submit last quarter's status so the file can be rebuilt Switch to a scheduling tool with automatic audit logging

Show the answer

Answer B. The root cause is the absence of configuration management: updates overwrite history, so reported dates cannot be traced. Establishing version and baseline storage procedures stops further loss and supports later forensic analysis. Re-baselining is the strongest distractor, but it needs formal change control and does nothing to preserve traceability. A new tool also skips the missing policy.

Want more like this? The PMI-SP practice test has questions for every domain.

Checklist

0 of 11

Tick each one you can do without notes. Your ticks stay in this browser.

Study strategy

Start with the schedule management plan, because every other task in this domain feeds it. Write a one-page outline from memory covering methodology, tool, units, calendars, update cycle, thresholds, earned value methods and reporting, then compare it with the PMBOK Guide and the Practice Standard for Scheduling.

Next, study configuration management and integrated change control side by side until you can say in one sentence which governs files and which governs decisions. Then work through approach selection using short project profiles: for each, choose CPM or critical chain, decide the rolling wave horizon, and justify the detail level.

Candidates underestimate the plan-placement questions and the earned value measurement methods, which look like Domain 3 topics but are set here. Practice afterwards with situational questions that ask what to do FIRST, and check that your answer creates or enforces a rule before it touches dates. Then move to Domain 2, where these rules shape how the model is built.

FAQ

How much of the PMI-SP exam covers Schedule Strategy?

PMI weights the domain at 14%. Applied to the 170-item exam, that is roughly 24 questions as a planning estimate; PMI does not publish per-domain counts.

Are there calculations in Domain 1?

Very few. You may need to read an SPI against a threshold, but most items test which policy, approach or plan component fits a scenario.

What is the difference between the schedule management plan and the schedule baseline?

The plan holds the rules for building and controlling the schedule. The baseline is an approved version of the schedule model, with dates, used to measure performance.

Do I need to know a specific scheduling tool?

No specific product is required. You need to know what a tool must support, such as baselines, calendars, resource loading and earned value reporting, and why methodology comes first.

How does this domain relate to Schedule Monitoring and Controlling?

Domain 3 enforces what Domain 1 defines. Thresholds, update cycles and change routes you set here decide what counts as a reportable variance and how baseline changes happen later.

Is critical chain tested as a strategy decision or a calculation?

Both appear across the exam. In this domain it is a strategy choice for resource-constrained projects; buffer sizing and buffer consumption show up in planning and control questions.

How long should I study this domain?

A planning estimate is 15 to 25 hours, more if you have never written a schedule management plan or worked under formal configuration control.

Related domains

Other Project Management certifications

Where the same subject shows up in other exams. Cards marked "Same subject" open the matching domain.

PMI-SP Domain 1: Schedule Strategy

Overview

How it's tested

Policy before action

Tailor the approach

Plan component placement

Tasks 5

High-yield concepts

Schedule management plan

Schedule configuration management

Control threshold

Rolling wave planning

Critical chain method

Earned value measurement methods

Level of detail and accuracy

Organizational process assets (OPAs)

Integrated change control

Scheduler role

Side by side

Configuration management vs. change control vs. version control

Critical path method vs. critical chain vs. rolling wave

Schedule management plan vs. schedule baseline vs. schedule model

Exam traps

Fixing the symptom instead of the policy

Tool-first thinking

Maximum detail everywhere

Scheduler as estimator

Escalate every variance

Plan placement confusion

Answer framework

Practice question

Checklist

Study strategy

FAQ

Other Project Management certifications

Test your Domain 1 knowledge

Keep going