Scope and Schedule Management

PMP PMP · Process

By Abu Anns · Last updated 20 November 2026Exam version: July 2026 ECO (current since 9 July 2026)

Scope: deciding what is in and what is out

Scope management answers the most basic question about a project: what exactly are we delivering, and what are we not delivering? The July 2026 ECO gives the Process domain two tasks here: develop and manage project scope, and plan and manage schedule. Scope work begins with collecting requirements from stakeholders — through interviews, workshops, focus groups, prototypes, and observation — and then defining the scope in a scope statement that describes the product, the deliverables, the acceptance criteria, and the exclusions. The exclusions matter as much as the inclusions: a scope statement that says what is NOT part of the project prevents the arguments that arise when someone assumes a feature is included.

The scope is then decomposed into a work breakdown structure (WBS): a hierarchical breakdown of the total scope into smaller, manageable pieces, down to work packages — the lowest level of the WBS, where work can be reliably estimated, assigned, and controlled. The WBS is deliverable-oriented, not activity-oriented: it shows what will be produced, not the steps to produce it. Each work package is described in the WBS dictionary, which records its scope, responsible person, acceptance criteria, and other details. The exam tests the WBS frequently, and the key points are: it covers 100% of the scope (the 100% rule — nothing is left out, nothing extra is added), it is created by the team rather than imposed on them, and it is the basis for estimating cost and schedule.

Scope creep and gold plating

Two scope failures appear on the exam constantly. Scope creep is the uncontrolled expansion of scope without changes to time, cost, or resources — usually caused by stakeholders requesting additions that bypass change control. Gold plating is the team adding extra features that were not requested, because they think the customer will like them. Both are wrong, and the exam treats both as failures of scope management, even when the intentions are good. The correct response to a request for more scope is always the same: assess the impact and process it through change control. The correct response to a team member gold-plating is to stop the extra work and redirect the effort to the agreed scope — extra features consume time and budget, introduce untested code or unreviewed deliverables, and set expectations the project never agreed to.

Validating scope is a separate activity from controlling it, and the exam tests the distinction. Validate scope is the process of formally accepting completed deliverables with the customer or sponsor — the customer inspects the deliverable and accepts it (or requests corrections). Control scope is monitoring the scope baseline and managing changes to it. A question describing a customer reviewing a finished deliverable is about validate scope; a question describing a request to add work is about control scope (and change control).

Building the schedule

Schedule management starts from the WBS: the work packages are decomposed into activities, the activities are sequenced (which depends on which), durations are estimated, and the schedule is developed. The exam expects you to know the four dependency types: finish-to-start (the most common — B cannot start until A finishes), start-to-start, finish-to-finish, and start-to-finish (rarely used). It also expects you to know leads and lags: a lead lets a successor activity start early (for example, starting testing two days before development finishes), while a lag inserts a delay (for example, waiting three days for concrete to cure before building on it).

Duration estimating uses several techniques the exam tests by name. Analogous estimating uses the actual durations of similar past activities — fast but rough. Parametric estimating uses a statistical relationship — for example, a known rate of 50 lines of code per hour. Three-point estimating uses optimistic (O), most likely (M), and pessimistic (P) estimates; the PERT expected duration is (O + 4M + P) / 6, and the standard deviation is (P - O) / 6. Bottom-up estimating rolls up detailed estimates from the lowest level — the most accurate and the most time-consuming. The exam's formula questions often use PERT: for example, O = 4 days, M = 7 days, P = 16 days gives an expected duration of (4 + 28 + 16) / 6 = 8 days, with a standard deviation of (16 - 4) / 6 = 2 days.

The critical path method

The critical path is the longest sequence of activities through the project network, and it determines the shortest possible project duration. Activities on the critical path have zero float (also called slack): any delay to them delays the whole project. Activities not on the critical path have float — the amount of time they can be delayed without delaying the project. The exam tests critical path calculations directly, so you must be able to find the longest path through a small network and to compute float as late start minus early start (or late finish minus early finish). Our critical path calculator page lets you practise this with a worked example.

A common exam point is that the critical path can change. As the project progresses and activities finish early or late, a different path may become the longest. The project manager must monitor the critical path continuously, not just at the start. Another exam point is that the critical path determines the project duration, but it does not determine which activities are most important — a non-critical activity can still be vital to quality or to stakeholder satisfaction. The exam also tests near-critical paths: a path with very little float can become critical with the smallest delay, and it deserves almost as much attention as the critical path itself.

Schedule compression: crashing and fast tracking

When a project is behind schedule, the exam offers two compression techniques, and knowing the difference between them is essential. Crashing adds resources to critical path activities to shorten them — it costs more money (overtime, extra people, faster equipment) but does not add risk to the sequence of work. Fast tracking takes activities that were planned in sequence and does them in parallel — it costs little or no extra money but adds risk, because work starts before its predecessor is complete and may need rework if the predecessor changes. The exam's rule of thumb: fast track first (it is cheaper), then crash if more compression is needed. Both techniques apply only to the critical path — compressing a non-critical activity does not shorten the project.

Resource optimization is the related idea. Resource leveling adjusts the schedule to resolve resource over-allocation, and it can change the critical path and extend the project duration. Resource smoothing adjusts activities within their available float, so it does not change the critical path or the end date. A question that asks how to fix over-allocated resources without changing the project end date is asking for smoothing; a question that accepts a longer schedule to fix overallocation is asking for leveling.

Agile scheduling

In agile projects, scheduling works differently: the team plans in iterations, estimates in relative units (story points) rather than hours, and measures progress by velocity — the amount of work completed per iteration. The schedule is not a fixed network of dates but a forecast based on the backlog and the team's measured velocity. The exam tests this through scenarios: a team whose velocity is stable can forecast how many iterations a given backlog will take; a team that is asked to commit to a fixed date for a fixed scope is being asked for something agile explicitly avoids (fixed scope plus fixed date plus fixed resources is impossible to guarantee). Burndown and burnup charts show progress against the iteration or release plan, and the exam expects you to read them: a burndown line above the ideal line means the team is behind.

Exam mindset for scope and schedule

For scope and schedule questions, the pattern is: define clearly, decompose fully, sequence logically, estimate honestly, and control changes formally. Scope creep and gold plating are always wrong. The critical path determines the project duration, and only critical path compression shortens it. Fast tracking adds risk; crashing adds cost. And when the situation is agile, think in iterations, velocity, and forecasts rather than in fixed dates and detailed networks.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.A developer adds an extra reporting feature to a deliverable because they believe the customer will appreciate it. The feature was not requested and is not in the scope statement. What is this an example of, and what should the project manager do?

Report an error

Q2.A project network has three paths from start to finish: Path A-B-D-F takes 14 days, Path A-C-D-F takes 12 days, and Path A-C-E-F takes 13 days. What is the critical path, and what is the float on activity E?

Report an error

Q3.An activity has an optimistic duration estimate of 4 days, a most likely estimate of 7 days, and a pessimistic estimate of 16 days. What is the PERT expected duration and the standard deviation?

Report an error

Q4.A project is two weeks behind schedule and the sponsor will not approve additional budget. The project manager wants to recover the schedule without spending more money. Which technique should the project manager try FIRST?

Report an error

Q5.A customer has reviewed a completed deliverable and found that it does not meet one of the agreed acceptance criteria. What should the project manager do?

Report an error

Q6.A project manager is creating the work breakdown structure (WBS) for a new project. Which approach is BEST?

Report an error

Q7.A key resource is over-allocated: they are assigned to two activities that overlap in the same week. The project manager must resolve the over-allocation without changing the project end date. Which technique should be used?

Report an error

Q8.An agile team's velocity has been stable at 20 story points per sprint for the last four sprints. The remaining product backlog is estimated at 100 story points. How many more sprints should the project manager forecast to complete the backlog?

Report an error