Plan and Manage Schedule: Execution
Not sure you’re ready?
Take the ~3-minute readiness diagnostic and see where you stand.
A project schedule in its planning phase is a frictionless, perfect mathematical simulation of the future. The moment execution begins, that simulation collides with organizational physics. Dependencies overlap unexpectedly, resource constraints emerge like sudden traffic jams, and work expansions expose hidden risks. The transition from planning to execution is the transition from theory to reality. Your role as a project manager shifts from architecting the ideal path to navigating the actual one. This requires a relentless focus on measuring empirical truth against expectations, diagnosing variations, and manipulating project variables to protect the final delivery date.
How you manage schedule execution depends entirely on the fundamental rules of your project's methodology. We cannot manage time unless we understand how our environment consumes it.
The Predictive Engine
In a predictive (Waterfall) environment, we are beholden to a rigid, deterministic path. Executing a predictive schedule management plan requires recording the actual start dates of project activities and, subsequently, recording the actual finish dates of project activities.
But binary "started" or "finished" states are not enough to manage complex delivery. The space between those two points is where schedules bleed time. Therefore, updating the project schedule requires calculating the percentage of work completed for in-progress activities and simultaneously estimating the remaining duration for unfinished activities. This continuous feed of empirical data is what keeps the schedule alive.
Crucially, while you continually update these actuals, the initial promise you made to stakeholders remains locked. The approved schedule baseline can only be modified through the Perform Integrated Change Control process. This protects the integrity of the project; without a locked baseline, "late" becomes an undefinable concept.
The Agile Ecosystem
Agile frameworks abandon the monolithic predictive timeline for a dynamic flow of value. Here, agile schedule execution relies on iterative timeboxed cycles known as sprints. Rather than adhering to long-term task assignments, agile teams pull work items from the iteration backlog based on the available capacity of the team members. This pull system ensures that work is never shoved onto a team member who is already a bottleneck.
To maintain visibility over this rapid cadence, teams utilize specific tools and ceremonies:
- Kanban Boards: These tools visually represent the flow of work to manage task execution in agile and hybrid schedules. They make invisible knowledge work visible.
- Daily Standups: These are agile ceremonies used to track daily schedule progress and identify immediate impediments. They are not status meetings for the manager; they are daily recalibrations of the team's micro-schedule.
When actual execution deviates from the plan, we must measure the gap. Variance analysis compares target schedule baseline performance against the actual schedule performance. By looking at the delta between what we promised and what we delivered, we understand our present state. But the present state is only half the picture. Trend analysis examines project performance metrics over time to determine if schedule execution is improving or deteriorating. It tells us our velocity and our trajectory.
The Mathematics of Reality: Earned Value Management (EVM)
To objectively measure schedule performance without relying on subjective gut feelings, we use Earned Value Management. We translate time and work into a unified currency.
Schedule Variance (SV)
Schedule Variance is calculated by subtracting Planned Value from Earned Value. (SV=EV−PV)
Look at the logic here. If the value of the work we actually accomplished (EV) is greater than the work we planned to accomplish by today (PV), the result is a positive number.
- A positive Schedule Variance mathematically indicates the project is currently ahead of schedule.
- Conversely, if EV is less than PV, we have a negative number. A negative Schedule Variance mathematically indicates the project is currently behind schedule.
- If they match perfectly, a Schedule Variance of exactly zero indicates the project is performing exactly on schedule.
We can express this same relationship as a ratio of efficiency:
Schedule Performance Index (SPI)
The Schedule Performance Index is calculated by dividing Earned Value by Planned Value. (SPI=EV/PV)
- A Schedule Performance Index greater than 1.0 signifies that more work was completed than initially planned.
- A Schedule Performance Index less than 1.0 signifies that less work was completed than initially planned.
- A Schedule Performance Index equal to 1.0 signifies that the completed work exactly matches the planned work.
The Critical Path and Network Threats
Not all delays are created equal. To know if a schedule variance actually threatens your delivery date, you must analyze the network logic.
Critical path method (CPM) analysis assesses progress along the critical path to identify direct threats to the project finish date. The critical path has zero float. Therefore, a delay on the critical path directly delays the final project finish date unless corrective schedule compression is applied.
What about the other tasks? Delays on non-critical paths only affect the project finish date if the specific delay exceeds the activity's total float. If an activity has 10 days of float, and it runs 4 days late, the project finish date does not move. The mathematical flexibility absorbs the blow.
If you suspect severe disruptions are on the horizon, you employ what-if scenario analysis. This technique evaluates multiple possible project schedules to predict the impact of specific adverse events (e.g., "What if our primary supplier strikes in October?").
Because agile environments don't utilize a traditional critical path, they require unique telemetry to monitor execution and predict completion.
Tracking Work and Scope
- Agile burndown charts display the remaining amount of work over the duration of an iteration or release. They are highly effective for visualizing whether a sprint is on track to finish on time.
- Agile burnup charts track the total amount of work completed toward the total planned project scope. Because burnup charts show both the completed work line and the total scope line, they are invaluable for exposing scope creep that burndown charts might hide.
Measuring Speed and Flow
- Velocity tracks the total number of story points successfully completed by an agile team in a single iteration.
- By tracking how velocity fluctuates, we perform velocity variance analysis, which allows agile teams to adjust their capacity commitments for future iterations. If historical velocity is 40 points, but the variance shows a downward trend to 30, the team must commit to less in the next sprint to remain predictable.
- Lead time measures the total elapsed time from a customer request to the delivery of the final product. This is the customer's perspective of time.
- Cycle time measures the exact amount of time an agile team spends actively working on a specific task. This is the team's perspective of time.
Diagnosing the Agile System
When flow breaks down, agile practitioners use advanced visual tools to find the root cause:
- Control charts visualize cycle time variations in agile and Kanban environments to identify process instability. If task cycle times bounce wildly outside control limits, your execution process is unstable and unpredictable.
- Cumulative Flow Diagrams highlight bottlenecks in agile schedule execution by showing the distribution of work across process states. If the "In Testing" band on the diagram violently widens, you know immediately where work is piling up.
When execution analysis reveals you are behind schedule, or when resources clash, you must intervene.
Schedule Compression
When the critical path slips, you must apply force. Schedule compression shortens the project schedule duration without reducing the project scope. There are two primary levers you can pull, each with a distinct penalty:
| Technique | Definition | Trade-off |
|---|---|---|
| Crashing | A schedule compression technique that assigns additional resources to critical path activities. (e.g., approving overtime, hiring a second crew). | Applying the crashing technique typically results in increased overall project costs. You are buying time with money. |
| Fast-Tracking | A schedule compression technique that overlaps activities originally planned to occur in sequence. (e.g., laying a building's foundation while architectural drawings are still being finalized). | Applying the fast-tracking technique typically increases overall project risk. Because dependencies are overlapped, the fast-tracking technique often leads to rework due to executing dependent tasks in parallel. |
Resource Optimization
Sometimes the schedule is mathematically perfect, but physically impossible because of human limitations. If the schedule requires your lead engineer to work 60 hours in a 40-hour week, the schedule must be optimized.
- Resource leveling modifies schedule dates to address resource constraints and prevent resource overallocation. If a resource is double-booked, leveling pushes one of those tasks into the future. Because it alters the network logic to accommodate reality, applying resource leveling to a project schedule often increases the total project duration.
- Resource smoothing adjusts activities within their free and total float limits without delaying the critical path. It is a less invasive technique. It optimizes resource usage only where the schedule's existing flexibility allows it. Because it respects float, the project end date remains intact.
Mastering schedule execution is the art of balancing these physical laws of project management. By relentlessly tracking empirical data, applying the rigorous math of variance analysis, and skillfully deploying compression and optimization techniques, you transform the chaotic reality of execution back into predictable delivery.