Process: Scope and Schedule Management

When a task is delayed, the project manager should first update the schedule with the new estimated completion date to reflect current reality. The manager then determines whether the delay impacts the overall project timeline, for example by checking whether the task is on the critical path or whether the slip exceeds its float. Finally, the manager must analyze downstream dependencies to understand how this delay cascades to other activities. This approach follows the Project Management Institute's best practices for schedule management and allows for informed decision-making about whether escalation, mitigation, or resource reallocation is necessary. A two-day delay on a non-critical task may not warrant sponsor escalation, but impact assessment is always required.

The scope baseline consists of the approved project scope statement, the WBS, and the WBS dictionary. The WBS itself is a hierarchical decomposition of the total scope of work into deliverables and work packages, but the graphical or outline structure only shows names and identifiers; it does not explain what each element actually entails. The WBS dictionary fills this gap: for each WBS element it provides a detailed description of the work, the deliverables, acceptance criteria, assumptions and constraints, responsible organization, associated milestones, quality requirements, and technical references. In this way the dictionary translates the structural view of the WBS into the concrete execution requirements that teams need to perform and verify the work, and it supports scope control by making clear what is (and is not) included in each element. It does not define the hierarchy or numbering scheme (that is the WBS structure itself), it does not establish sequencing and logical dependencies (that belongs to schedule development and the network diagram), and it is not a formal approval or sign-off log (that is handled through change control processes). Therefore, the primary relationship is that the dictionary provides the detailed descriptive and acceptance information for each element of the WBS structure, linking scope definition to project execution.

The scenario describes a project manager who regularly reviews the schedule, compares actual task completion dates against planned dates, identifies delays (variances), updates the schedule accordingly, and communicates these changes to stakeholders. This is the definition of schedule monitoring and control through variance tracking. Variance tracking involves measuring the difference between planned performance and actual performance, then taking corrective actions. The manager is not developing the schedule (which occurs during planning), not performing resource leveling (which addresses resource constraints), and not using earned value management forecasting (which requires integrated scope, schedule, and cost data). This activity directly exemplifies the monitoring and controlling process group where variances are identified and managed.