Calculate and Recover a Data-Migration Schedule
Build the network, calculate the critical path and float, test resource feasibility and evaluate a controlled recovery scenario.
30 minutes
Scenario
A company must migrate customer data before a contractual platform shutdown. The plan lists dates but does not show dependency logic, float or the effect of a scarce integration engineer.
- Your role
- Programme scheduler validating the migration forecast
- Method
- Critical Path Method
Evidence pack
A Mapping
Schema mapping takes 3 working days and starts the network.
B Extraction
Extraction takes 4 days after mapping.
C Interface
Interface build takes 6 days after mapping.
D Cleansing
Cleansing takes 5 days after extraction.
E–G
Integration test takes 3 days after interface and cleansing; UAT takes 4; cutover takes 1.
Constraint
The integration engineer supports interface build and the first two days of integration test; no overlap is possible.
Constraints
- Use working-day durations and state the date convention.
- Do not remove validation or UAT.
- Separate the contractual date from the calculated forecast.
Case steps
Work through each prompt using the evidence pack. These guided cases support self-directed practice; server-scored attempts are not available yet.
Create activity IDs, outputs, durations and predecessor logic and validate the network.
Perform forward/backward passes and identify critical and near-critical paths and float.
Test the network against the scarce-engineer constraint.
Cleansing slips two days. Evaluate schedule impact and one safe recovery option.