Fortnightly — Fleet Sync
| Home | Docs | Guides | Ceremonies | Templates | Setup |
Duration: 30 minutes Facilitator: Engineering leadership + Product leadership When: Every two weeks, only if you run multiple boats Attendees: One representative per boat, usually the Captain
Purpose
Surface cross-boat dependencies before they become blockers. Align on shared platform priorities. Make risks affecting multiple boats visible early.
Fleet Sync is not a status meeting and not a second Route Planning session. Boat-local shaping stays inside each boat.
Before the Meeting (Facilitator, 10 min prep)
- Ask each boat for any cross-boat dependency, shared platform request, or multi-boat risk
- Group similar platform asks together
- Carry forward any unresolved items from the previous Fleet Sync
- Remove boat-local issues that should stay in Route Planning
Script
| Time | Activity | Detail |
|---|---|---|
| 0–5 min | Review open items | What carried over from the last Fleet Sync? Anything resolved, blocked, or now irrelevant? |
| 5–15 min | Dependencies | Which boats are waiting on which other boats? Name the owner, next step, and timing risk. |
| 15–25 min | Shared platform priorities | Are multiple boats asking for the same platform capability? Decide priority, sequence, or deferral. |
| 25–30 min | Cross-boat risks | Flag risks that affect multiple boats. Name owner, mitigation, and whether leadership action is needed. |
Outputs
- Each cross-boat dependency has a requesting boat, owning boat, next step, and target date
- Shared platform asks are explicitly prioritised or deferred
- Multi-boat risks are visible with an owner and mitigation
- Any needed leadership escalations are named immediately
Key Questions to Ask
- “What is likely to block another boat in the next two weeks?”
- “Which dependencies need a named next step today?”
- “Are multiple boats asking for the same platform work?”
- “What risk would surprise more than one boat if we ignored it?”
- “Does this need leadership trade-off, or can the boats resolve it directly?”
Anti-Patterns
- Don’t turn Fleet Sync into round-robin status updates. Do discuss only items that cross boat boundaries.
- Don’t re-plan a boat’s internal work. Do keep boat-local shaping in Route Planning.
- Don’t let dependencies stay vague. Do name the requesting boat, owning boat, next step, and target date.
- Don’t treat every platform request as urgent. Do make explicit priority calls and defer openly when needed.
- Don’t leave risks implied. Do name the risk, owner, and mitigation.