Can the first training site still go live?
You are interviewing for a civilian program delivery role on a fictional training calendar rollout.
The question
Work starts on working day 1. The target is the end of day 6. A dependent task starts on the next working day after all its predecessors finish. The program owner approves scope changes and releases.
| Working days | Starts after | |
|---|---|---|
| Data import | 2 | Project start |
| Dry run | 2 | Data import |
| Prepare materials | 3 | Project start |
| Readiness review | 1 | Dry run and materials |
Import and materials start on day 1 in parallel.
“Explain the original plan, the revised forecast and what the first site can deliver.”
Not saved by this site. Your browser may restore text when you navigate back.
A strong answer, step by step
Open each step in turn. This is one strong answer, not the only one.
Step 1: When can the review finish?
What would you do here? Open the move you’d make.
Day 5, with one working day of margin
The strong move. The review follows the later of the two paths.
Day 8, because the four task durations add up to eight
Tempting, but it misses something. That treats parallel work as if every task followed the previous one.
Day 4, when the dry run ends
Tempting, but it misses something. The one-day review follows the dry run and materials.
See how a strong candidate says it
“Import finishes on day 2, the dry run on day 4 and materials on day 3. The readiness review finishes on day 5. That leaves one working day before the target.”
Why it works: The dry run controls the start of the review because it ends later than materials.
Step 2: What should your update show?
What would you do here? Open the move you’d make.
Report the controlling chain and the available margin
The strong move. The owner can see which risk matters to the finish date.
Report only that two tasks are in progress
Tempting, but it misses something. A task count does not explain the effect on the final milestone.
Flag materials as the controlling task because it takes three days
Tempting, but it misses something. Materials finish before the dry run under the opening plan.
See how a strong candidate says it
“I would report that import, dry run and readiness review determine the finish. The approved plan gives them one working day of margin. I would check the import finish date first.”
Why it works: This explains which dependency can move the milestone and how much delay it can absorb.
Step 3: When do you now expect to finish?
The source files need a second check. The import now takes four working days in total. Other durations and dependencies are unchanged.
What would you do here? Open the move you’d make.
Forecast day 7 and show the one-day variance
The strong move. The revised import uses the margin and moves the forecast beyond the target.
Keep day 6 because the approved target did not change
Tempting, but it misses something. The target is still day 6. The unchanged target does not change the predicted finish.
Forecast day 6 because the dry run ends then
Tempting, but it misses something. The readiness review still takes another day.
See how a strong candidate says it
“With import ending on day 4, the dry run ends on day 6 and the readiness review on day 7. The full-scope forecast is one working day later than the target.”
Why it works: The forecast reflects the changed dependency while the approved target stays visible.
Step 4: What can the owner commit to?
The program owner approves a first-site release using a verified subset of the imported data. After the same four-day import, its dry run takes one working day and its readiness review takes one more. Remaining sites keep a two-day dry run and separate acceptance.
What would you do here? Open the move you’d make.
Forecast the first site for day 6 subject to review
The strong move. The revised first-site scope fits the target and keeps the review in the plan.
Report all sites on track for day 6
Tempting, but it misses something. The one-day dry run applies only to the first site. The remaining sites retain separate checks.
Launch on day 5 after the dry run
Tempting, but it misses something. The first site still needs the one-day readiness review before release.
See how a strong candidate says it
“The first site can finish its dry run on day 5 and readiness review on day 6. I would forecast a first-site launch on day 6 if those checks pass and report the other sites separately.”
Why it works: The owner approved a smaller first release and the readiness review still gates it.
The answer, in short
- Decision
- Update the forecast when a dependent task changes.
- Because
- Each release scope still needs its own acceptance checks.
- What would change it
- A verified change to a task or approved release scope would change the forecast.
Common traps
- Track the path that determines the finish.
- Give dates with the scope and checks they depend on.
Check your answer
- I calculated the original forecast.
- I showed the dependency and margin.
- I reported the revised finish.
- I scoped the first-site forecast.
Last reviewed Nov 11, 2026