Sprint 3: Roadmap, risk & the go/no-go
Your initiative: _______________________ Group: __________
Now turn your scope, stakeholders and checkpoints into a delivery plan, then defend it when the staff push back and a crisis hits. Remember Difference 2: progress is illusory, so your gates exist to catch the demo-to-production gap before it reaches a customer or the board.
1. Delivery roadmap with go/no-go gates
| Phase | What happens | Go/no-go gate: what must be true to proceed? |
|---|---|---|
| Pilot (narrow) | ||
| Evaluate | ||
| Scale / Pivot / Kill | ||
| Production |
2. Risk register
| Risk | AI-specific? (non-determinism / data / demo-gap / verification) | Likelihood | Impact | Mitigation |
|---|---|---|---|---|
3. Crisis response (DDCD)
Your facilitator will hand your group a crisis. Respond:
- Diagnose: is this technical, people, leadership, or ethical? ______________
- Decide: your call under uncertainty: ______________
- Communicate: who, and what do you say? ______________
- Document: the decision and the reason: ______________
4. The gate-1 decision
At your first evaluation gate, the data is ambiguous. Make the call and defend it with evidence:
SCALE / PIVOT / KILL (circle one), because: ______________________________________________
Killing a project that isn’t working, early, is success, not failure. The cost of wrongly scaling is far higher than the cost of wrongly killing.
Leave Sprint 3 with: a roadmap with gates, a risk register, a documented crisis response, and a defended go/no-go decision. Together with Sprints 1–2, that’s your delivery design.