Delivery cadence¶

This document defines the team operating rhythm for Opencomplai work. It prioritizes shipping, unblocking work quickly, and enforcing quality gates through CI.

Weekly planning (60 min, Monday)¶

Agenda:

Review last week's completed issues (5 min)
Identify blockers from last week (10 min)
Assign this week's issues — one per person, one DRI per issue (15 min)
Confirm phase gate status — are all acceptance criteria for the current phase met? (10 min)
Any scope change proposals to discuss? (10 min)
Commit to weekly goals publicly in the team Slack/Discord (10 min)

Mid-week checkpoint (30 min, Wednesday)¶

Blocked items only — no status updates
Any issue tagged status:blocked within the last 48 hours gets a resolution plan
No new scope discussion

End-of-week demo + retro (60 min, Friday)¶

Demo anything shippable — working CLI command, passing test, live deployment
Retro format: What worked? What didn't? One improvement action item for next week
Update the phase gate checklist in the relevant phase file

WIP limits¶

Max 1 issue per person in status:in-progress
Max 3 issues per area label in status:in-progress across the team

Blocked-work protocol¶

Tag status:blocked within 24 hours of the blocker being identified
Assign an escalation owner immediately
Blocked items are the first agenda item at every checkpoint

Weekly status note format (post in team channel every Friday)¶

**Week of [date] — Status**
✅ Wins: [what shipped or was completed]
⚠️ Risks: [anything that could affect next week's goals]
🚫 Blockers: [any unresolved blockers]
📌 Next week commitments: [specific deliverables with DRI names]

Phase gate process¶

Before declaring a phase complete and starting the next:

Run the acceptance criteria checklist in the phase file — every item must be green
Run the full test suite for all stacks affected by the phase
Create a GitHub issue titled Phase N complete — gate review and attach the checklist output
Both product and technical owners approve the issue before moving on