✦ For everyone, free.

Practical knowledge for real and everyday life

Home

Schedule Maintenance and Replanning

Schedule Maintenance and Replanning keeps software projects on track by adjusting timelines and plans as goals evolve.

Schedule Maintenance and Replanning involve the ongoing processes required to keep a software project schedule accurate, relevant, and aligned with project objectives throughout the project lifecycle. Schedule maintenance focuses on updating the project schedule to reflect actual progress, changes in project scope, resources, risks, and dependencies, while schedule replanning is a more substantial revision that may involve resetting the baseline schedule to accommodate significant changes or obsolescence.


Definition and Purpose

Schedule Maintenance is the continuous activity of monitoring and updating the project schedule to incorporate new information, ensure alignment with project realities, and support effective decision-making. It includes routine updates such as progress tracking, incorporation of change requests, resource adjustments, and risk responses.

Schedule Replanning, often triggered by major deviations or unforeseen events, involves revising the schedule to accommodate significant changes that render the current plan obsolete or ineffective. This may require re-estimating tasks, redefining dependencies, reallocating resources, and establishing a new baseline schedule.

Together, these processes ensure that project scheduling remains a useful and reliable tool for managing time, cost, and scope trade-offs.


Components of Schedule Maintenance

Project Schedule Update Triggers

Schedule updates are initiated by various triggers, including:

  • Scope Changes: Addition, removal, or modification of project deliverables.
  • Estimate Revisions: Updated task durations or effort estimates based on actual performance or new information.
  • Dependency Adjustments: Changes in task sequencing or external constraints.
  • Resource Availability: Fluctuations in resource assignments, availability, or productivity.
  • Risk Events: Realization of risks or new risks requiring schedule impact assessment.

Types of Schedule Updates

  1. Scope-Driven Updates: Reflect changes in project scope, requiring adjustments in tasks, durations, and dependencies.
  2. Estimate-Driven Updates: Occur when actual progress reveals discrepancies in initial task duration or effort estimates.
  3. Dependency-Driven Updates: Result from changes in task relationships or external factors impacting sequencing.
  4. Resource-Driven Updates: Arise from changes in resource assignments, availability, or productivity.
  5. Risk-Driven Updates: Triggered by the occurrence or mitigation of risks impacting schedule.

Update Process

The process typically includes:

  • Collecting actual progress and status data.
  • Identifying variances between planned and actual performance.
  • Analyzing causes of variances and assessing impact.
  • Updating task data, dependencies, and resource assignments.
  • Communicating changes to stakeholders.

Schedule Replanning

When to Replan

Replanning is necessary when:

  • The schedule baseline is no longer valid due to accumulated deviations.
  • Significant scope changes occur that fundamentally alter the project.
  • Resource constraints or availability change drastically.
  • Risk events cause major disruptions.
  • Stakeholders require a new, realistic plan to guide future work.

Replanning Activities

  • Reassessing project objectives and constraints.
  • Re-estimating tasks based on current information.
  • Revising dependencies and sequencing.
  • Reallocating resources to optimize schedule.
  • Establishing a new baseline for tracking future progress.

Project Schedule Rebaseline Criteria

A schedule rebaseline is justified when:

  • Actual progress diverges beyond acceptable thresholds.
  • Changes in scope, resources, or risks are significant.
  • The existing plan no longer supports effective control.
  • Management or stakeholders require a formally updated plan.

Managing Schedule Obsolescence

Schedule obsolescence occurs when the project schedule becomes outdated due to cumulative changes and deviations. Preventing obsolescence requires:

  • Frequent updates and reviews.
  • Timely identification of triggers.
  • Incorporation of lessons learned from schedule performance.
  • Effective communication and stakeholder engagement.

Scheduling Effectiveness Review and Lessons Learned

Periodic evaluation of scheduling effectiveness helps improve future schedule maintenance and replanning by:

  • Analyzing causes of schedule variances.
  • Assessing the accuracy of estimates and assumptions.
  • Reviewing the adequacy of update and replanning processes.
  • Documenting lessons learned to refine scheduling practices.

Collect Progress Data Identify Variances & Triggers Update Schedule or Replan Communicate & Review
Schedule Variance = Actual Completion Date Planned Completion Date
Replanning Threshold = Sum of Schedule Variances Total Project Duration > Predefined Limit

These formulas guide decision-making about when to trigger replanning activities based on deviations from the planned schedule.


Schedule maintenance and replanning are essential to managing dynamic project environments, enabling timely adjustments that preserve project objectives, optimize resource utilization, and enhance stakeholder confidence in schedule reliability.