Choose schedule recovery using current impacts and risk

ReasonSpan™. Project Management Professional. Schedule recovery and risk.

A predictive service-rollout project must complete security approval, data migration, and operations preparation before integrated readiness testing can begin. Testing takes two working days, followed by one day for release. The approved finish is day twenty-three. The project manager must evaluate a recovery proposal after a delay. The question is whether the proposal improves the current project finish while respecting cost, quality, and risk constraints.

The updated schedule shows security approval finishing on day eighteen, data migration on day twenty-two, and operations preparation on day seventeen. All three are required before readiness testing. The latest finish is day twenty-two, so testing and release move the forecast finish to day twenty-five. Data migration currently controls that merge.

One manager proposes overtime that moves security approval from day eighteen to day sixteen. Migration still finishes on day twenty-two, so the project still finishes on day twenty-five. The proposal buys no project time under the stated dependencies. A second proposal adds qualified migration analysts for six thousand dollars and is forecast to finish migration on day twenty. If that forecast is achievable, testing and release can finish on day twenty-three. A third proposal skips mandatory readiness testing. That would violate the stated release criteria and is not an acceptable recovery option.

The team has not yet validated analyst availability or assessed the additional reconciliation risk. The project manager cannot authorize the added spending under this project's governance. What should the project manager do next? Approve security overtime because it shortens an activity? Commit to the extra analysts and report the original date as guaranteed? Validate the migration recovery plan with the team, assess cost and risk, and take the recommendation to the authorized approver? Or omit readiness testing to recover two days?

Validate the migration recovery plan and seek the required authorization. Confirm resource availability, dependency logic, the duration estimate, quality checks, and risk responses with the people doing the work. Present the supported forecast, uncertainty, cost, and alternatives. Activity savings are useful only when they improve the project result or serve another justified objective. Do not promise the original date from an unvalidated estimate, and do not remove a mandatory quality gate to make a schedule look better.

After approval, coordinate the additional resources, update the forecast and affected plans, and communicate the decision. Follow the project's change process if a baseline change is needed; a revised forecast does not erase the approved baseline. Monitor the controlling branch and the other required branches as the recovery proceeds. If the assumptions fail, reassess the options and communicate the impact promptly. Schedule recovery is a management decision supported by current schedule logic, cost, risk, and delivery requirements.

The finish remains day 23: max(20, 19, 17) + 2 + 1 = 23. Security now controls the merge, so the additional migration-only reduction yields no project-finish improvement under the supplied assumptions. Reassess all current required branches and weigh any other claimed benefit against its cost and risk. If an earlier release is justified, evaluate feasible options affecting the current constraint, preserve mandatory quality requirements, and obtain any required authorization.