Running Effective Delivery Governance Cadences

What Delivery Governance Actually Is

Governance is not control. It's the framework of cadences, forums, and decision rights that ensures the right people make the right decisions at the right time with the right information. Good governance is invisible when things go well and invaluable when things go wrong.

For a Delivery Manager, governance answers three questions: 1. Are we delivering what we committed to? (Progress) 2. What could prevent us from delivering? (Risk) 3. What decisions are needed to keep delivery on track? (Action)

The Governance Pyramid

Design governance as a pyramid — frequent, lightweight checks at the base; infrequent, strategic reviews at the top:

Daily: Team-Level Sync (15 min)

Purpose: Surface blockers and coordinate within teams Attendees: Development team + Scrum Master Format: Walk the board, flag blockers, align on today's priorities DM involvement: Not required. Attend occasionally to observe, not to participate.

Daily: Cross-Team Sync / Scrum of Scrums (15 min)

Purpose: Surface cross-team blockers and dependency issues Attendees: One representative per team + Delivery Manager Format: Each rep shares: (1) What might block another team, (2) What we need from another team, (3) Any escalation needed Output: Immediate actions assigned for blocker resolution

Weekly: Delivery Review (45-60 min)

Purpose: Assess delivery health across all teams and drive decisions Attendees: Delivery Manager + Scrum Masters + Tech Leads Format: 1. Dashboard walk-through (10 min) — RAG status, metrics trends 2. Blocker triage (15 min) — anything older than 48 hours gets an owner and deadline 3. Dependency review (10 min) — any at risk? What's the mitigation? 4. Risk review (10 min) — new risks, changed risks, mitigations due 5. Decisions and escalations (5 min) — what needs to go up?

Output: Updated dashboard, resolved blockers, escalation items for steering

Fortnightly: Stakeholder Update (30 min)

Purpose: Keep sponsors and stakeholders informed and aligned Attendees: Delivery Manager + key stakeholders + Product Owner Format: Progress / Risk / Ask structure

• Progress: what was delivered, what's on track
• Risk: what could derail delivery, what's being done about it
• Ask: decisions needed, resources required, blockers that need leadership help

Output: Decisions made, resources committed, expectations aligned

Monthly: Delivery Health Review (90 min)

Purpose: Deeper analysis of delivery trends and systemic issues Attendees: Delivery Manager + Engineering Lead + Product Lead + SM community Format: 1. DORA metrics trend analysis (20 min) 2. Quality trend (escaped defects, rework rate) (15 min) 3. Team health pulse results (15 min) 4. Systemic impediments discussion (20 min) 5. Improvement investments for next month (20 min)

Output: Improvement backlog prioritised, investments agreed

Quarterly: Strategic Delivery Review (half day)

Purpose: Assess delivery capability and plan strategic improvements Attendees: Senior leadership + Delivery Manager + Engineering Lead Format: 1. Quarter in review: what was delivered vs planned (30 min) 2. Delivery performance: DORA trends, predictability, quality (30 min) 3. Capability assessment: team maturity, tooling, process (30 min) 4. Next quarter plan: delivery targets, investments, hiring (60 min)

Output: Quarterly delivery plan, investment decisions, hiring approvals

Designing Effective Meetings

The "No Surprises" Rule

Governance meetings should never surface information for the first time. If a risk is Red, the DM should already know before the meeting. Governance forums confirm and decide — they don't discover.

The Pre-Read

For any meeting longer than 30 minutes, send a pre-read 24 hours in advance. This shifts the meeting from "presenting information" to "discussing decisions." The pre-read contains the data; the meeting contains the conversation.

The Decision Log

Every governance meeting produces decisions. Log them: what was decided, by whom, when, and what action follows. Decisions without a log get forgotten and re-debated.

The Escalation Path

Clear escalation criteria prevent both under-escalation (problems fester) and over-escalation (leadership is overwhelmed with noise):

• Team level: Blocker < 24 hours, within team's control → SM resolves
• Delivery level: Blocker > 48 hours, cross-team, or needs resource → DM resolves
• Steering level: Blocker > 5 days, budget impact, scope change, or strategic risk → Leadership decides

Anti-Patterns in Governance

Meeting overload: So many governance meetings that teams have no time to deliver. Fix: audit meeting load quarterly. If teams spend >20% of time in governance meetings, consolidate or eliminate.

Status theatre: Meetings where everyone reports Green to avoid difficult conversations. Fix: create psychological safety. Reward early risk reporting. Punish surprises, not problems.

Decision avoidance: Meetings that discuss endlessly but never decide. Fix: every meeting has a decision owner. If a decision can't be made in the meeting, set a deadline and owner for offline resolution.

Governance without teeth: Decisions are made but not followed through. Fix: track decision completion. Review outstanding decisions at the start of every governance meeting.

One-size-fits-all: Applying the same governance to a 3-person team and a 50-person programme. Fix: scale governance to complexity. Small teams need less; large programmes need more.

Measuring Governance Effectiveness

• Decision cycle time: How long from "decision needed" to "decision made"? Target: <5 business days for routine decisions.
• Escalation resolution time: How long from escalation to resolution? Target: <3 business days.
• Meeting ROI: Ask attendees quarterly: "Is this meeting worth the time?" If >30% say no, redesign it.
• Surprise rate: How often do problems surface in steering that weren't flagged earlier? Target: never. If it happens, the lower-level governance failed.

---

Download the [Delivery Dashboard template](/templates) for a governance-ready delivery health reporting format.