Schedule Performance Domain Fundamentals

Purpose of Scheduling

A project schedule translates scope into a timeline for delivery. It serves as a communication tool, sets stakeholder expectations, and provides a baseline for performance tracking. A well-maintained schedule helps detect delays early, allowing corrective actions before issues escalate.

Key Schedule Concepts

• Project schedule – a model of linked activities with planned dates, durations, milestones, and resource assignments.
• Estimate – a quantitative assessment of effort (labor units) or duration (work periods). Both are refined as more details emerge.
• Schedule baseline – the approved version of the schedule, changed only through formal change control (more rigid in predictive projects, more flexible in adaptive ones).
• Flexibility – essential for adapting to changes, managing risks, and optimizing resources. It supports incremental delivery and team morale.
• Forecasts – predictions of future timeline performance based on current progress and trends. Updated regularly with actual work data.
• Actual duration – calendar time from an activity’s actual start to its finish (or to the data date if still in progress).
• Network diagram – a graphical representation of logical dependencies (e.g., finish-to-start) among activities.

The Schedule Management Plan

This plan defines policies and procedures for developing, maintaining, and controlling the schedule. It includes rules for accuracy, units of measure, iteration length, control thresholds, performance measurement, and reporting formats. It is established during the Plan Schedule Management process.

Developing the Schedule (Four Steps)

1. Define activities – Decompose work packages into specific actions. Artifacts include the activity list, attributes, and milestones.

2. Determine sequence – Identify logical dependencies among activities (e.g., finish-to-start, start-to-start). Every activity (except the first and last) should have at least one predecessor and one successor. Leads and lags may be added to create a realistic sequence.

3. Estimate effort and duration – Use techniques like expert judgment, analogous/parametric estimating, PERT, planning poker, story points, or T-shirt sizing. Factors influencing duration include resource availability, skill levels, constraints (fixed duration vs. fixed effort), technology advances, and the law of diminishing returns. Document all assumptions and avoid common cognitive biases (e.g., planning fallacy).

4. Adjust – Review the draft schedule. If unacceptable, apply techniques such as schedule compression, resource leveling, or alternative sequencing. After setting start/end dates, team members confirm that assignments align with resource calendars. The final schedule becomes the baseline once approved.

Monitoring and Controlling the Schedule

This ongoing process keeps the schedule realistic. Key activities:

• Determine current schedule status.
• Influence factors that cause schedule changes.
• Reassess needed reserves.
• Detect whether the overall timeline has shifted.
• Manage approved changes.

In predictive projects, changes to the baseline require formal integrated change control.

In adaptive projects, monitoring focuses on comparing delivered work against estimates per iteration, using velocity and burnup/burndown charts. Retrospectives improve processes. Backlog reprioritization keeps the plan aligned with evolving priorities.

For contracted work, regular status reviews with suppliers help ensure schedule control.

Tailoring the Schedule Approach

The development life cycle strongly shapes scheduling:

• Predictive – detailed upfront planning, formal change management, clear critical path.
• Adaptive – timeboxed iterations, short planning horizons, flexible adjustments.
• Hybrid – high-level predictive milestones combined with adaptive sprints for uncertain components.

Other tailoring considerations:

• Product attributes – high-criticality or innovative deliverables may need more detailed, frequent updates.
• Team attributes – large/dispersed teams require robust tools; experienced teams can work with high-level plans.
• Culture – risk-averse organizations prefer fixed schedules; adaptive cultures embrace fluid plans.
• Project environment – megaprojects or aggressive deadlines call for rigorous scheduling.
• Scheduling methods – choose from critical path, critical chain, location-based scheduling, lean scheduling (pull-planning, limiting queues), Gantt charts, or Kanban. Ensure schedule detail matches WBS detail.

Interactions with Other Domains

The schedule is tightly linked to Scope, Finance, Resources, Risk, Stakeholders, and Governance. Changes in scope, cost, or resources directly affect duration. Conversely, schedule adjustments impact resource allocation and budget. The schedule must balance with all domains to deliver project outcomes.

Checking Schedule Outcomes

A successful schedule delivers these results:

• Scheduling approach aligns with deliverable type (predictive, adaptive, or hybrid).
• Project phases connect from launch to close with appropriate exit criteria.
• A holistic delivery plan with no gaps or misalignment.
• Complete documentation (dependencies, durations, resources, milestones).
• Appropriate tools and techniques are used (e.g., critical path method, PM software).
• Stakeholders are actively involved in schedule development.
• Sufficient buffers (float, contingency reserves, or alternate strategies) are built in for known unknowns.