Meetings and cadence
Purpose: This is the checkpoint chapter for delivery. These meetings and cadences exist to enforce the standards through a small number of strong forcing functions.
Templates stay in standards/ where they exist. This folder defines the delivery-layer checkpoint model.
1. What this section covers
This section defines:
- which checkpoints exist
- what each checkpoint is meant to force
- what should be sync vs async
- which recurring meetings are worth keeping
The goal is not more rhythm. The goal is better control.
2. Core checkpoints
The main delivery checkpoints are:
- Project Review Meeting — plan before promise
- Weekly leadership sync — portfolio risk and escalation visibility
- Client weekly touchpoint — visible value, confidence, and decisions
- CSO-SL alignment — story matches build
- Engagement technical standup — optional daily unblock
- Re-gate on material change — change control
- Linear truth review — board reflects reality
Canonical checkpoint chapter:
3. Checkpoint philosophy
Checkpoints should:
- force clarity
- make risk visible
- create decision points
- prevent drift between the plan, the board, and the client story
What they should not do:
- create status theater
- replicate the same conversation in multiple places
- become recurring meetings with no forcing function
4. Most important gate
The Project Review Meeting is the main gate in this system.
Use it to:
- pressure-test the plan
- review dependencies and risks
- validate dates before hard commitment
- approve or send back
Supporting docs:
5. Supporting docs in this section
| Resource | Purpose |
|---|---|
| weekly-leadership-sync.md | Portfolio-level sync |
| templates | Lightweight agenda / notes shells |
Last updated: 2026-03-24