1. The long war against the schedule
Joe Haldeman’s The Forever War is about a conflict that outlives the assumptions that started it. Soldiers return to societies they no longer recognize. The lesson for project management is that long timelines change the meaning of every decision. A schedule is not a straight line; it is a series of bets made under uncertainty.
This entry maps both possible results of the attachment test onto the programme schedule.
2. If the test passes
A passing test accelerates the schedule in these ways:
- Confidence to order long-lead items: flight connectors, rails, and latches can be procured.
- Permission to design the next test: structural or thermal-vacuum testing can be planned.
- Stakeholder credibility: a demonstrated interface is easier to show investors or partners than a paper design.
- Foundation for parallel work: other cell types can assume the interface exists.
The schedule does not collapse, but it becomes more parallel. Work that was waiting on the interface can start.
3. If the test fails
A failing test delays the schedule, but not necessarily by much:
- Failure analysis: days or weeks to understand the mode.
- Redesign: weeks or months, depending on the failure domain.
- Re-test: another build-and-test cycle.
- Total impact: likely one to three months for a localized failure, longer for an architectural failure.
The key is to fail fast and fail clearly. A six-week failure that teaches something is better than a six-month false confidence.
4. The real schedule risk
The real schedule risk is not the test result. It is the avoidance of testing. A programme that keeps designing to avoid a test will eventually face a much more expensive failure. The schedule must include time to fail and recover.
5. What this changes
- Both pass and fail outcomes have predictable schedule consequences.
- Passing enables parallel work; failing costs one to three months for localized issues.
- The schedule must reserve time for failure analysis and redesign.