Governance Calendar¶
| Owner | Classification | Review Date | Status |
|---|---|---|---|
| CDO Office | Confidential | April 2027 | Active |
Governance Calendar¶
Owner: CDO Office
Last Updated: April 2026
Classification: Internal
Purpose¶
The Governance Calendar provides a single view of the recurring meetings, reviews, and planning cycles that govern the CDO division. It ensures leadership rhythms are predictable, preparation time is built in, and strategic cycles are connected.
Weekly Rhythm¶
| Day | Meeting | Owner | Duration | Attendees |
|---|---|---|---|---|
| Monday | CDO Leadership Team | CDO | 60 min | CDO + direct reports |
| Monday | Squad standups | Tech Leads | 15 min | Squad members |
| Tuesday | Digital Office check-in | Digital Office Lead | 30 min | Digital Office team |
| Wednesday | Architecture Review Board | Head of Architecture | 90 min | ARB members (bi-weekly) |
| Thursday | Engineering Leadership Sync | Acting CTO | 45 min | Tech Leads, Chapter Leads |
| Thursday | Product Prioritisation | Head of Product | 60 min | PMs, Product leadership |
| Friday | CDO/CSNO 1:1 | CDO | 45 min | CDO + CSNO (bi-weekly) |
Monthly Rhythm¶
| Week | Meeting | Owner | Duration | Purpose |
|---|---|---|---|---|
| Week 1 — Tuesday | Expansion Pipeline Sync | CSNO | 60 min | G0–G2 corridor pipeline, CDO early engagement |
| Week 2 — Thursday | Security & Risk Forum | Head of InfoSec | 60 min | Threat models, vulnerability triage, exceptions |
| Week 3 — Wednesday | Data Governance Committee | Head of Data | 60 min | Data quality, ownership, regulatory obligations |
| Week 4 — Monday | Monthly Metrics Review | CDO | 90 min | CCQ dashboard, SLO performance, delivery metrics |
| Week 4 — Friday | CDO Board Report Preparation | CDO Office | — | Input deadline for board deck items |
Quarterly Rhythm¶
| Quarter | Activity | Owner | Purpose |
|---|---|---|---|
| Q-10 weeks | OKR drafting begins | CDO + Heads | Bottom-up OKR proposals from squads and teams |
| Q-6 weeks | Roadmap alignment session | CPO + CDO | Align product roadmap with strategic priorities |
| Q-4 weeks | OKR finalisation | CDO | CDO-level OKRs locked; cascade to teams |
| Q-2 weeks | Capacity planning | Acting CTO + Heads | Squad capacity, hiring gaps, contractor needs |
| Q start | Roadmap published | Digital Office | Published to Confluence; shared with ELT |
| Q+4 weeks | Quarterly Business Review (QBR) | CDO | ELT-level delivery and strategic update |
| Q end | Retrospective | Digital Office | What worked, what didn't; process improvements |
| Q end | OKR scoring | CDO + Heads | Score completed OKRs; carry-forward decisions |
Annual Rhythm¶
| Month | Activity | Owner | Purpose |
|---|---|---|---|
| January | Annual strategic planning | CDO | Set divisional priorities for the year |
| February | Budget submission | CDO + Finance | Technology and headcount budget for board |
| April | Mid-year review | CDO | ELT review of H1 progress vs plan |
| June | H2 roadmap lock | CPO + CDO | Finalise H2 priorities; communicate to ELT |
| September | Annual performance reviews begin | Heads | All direct reports; grade calibration |
| October | Budget cycle opens (next year) | CDO + Finance | Early-stage resource planning |
| November | Grade calibration complete | CDO | Compensation decisions; promotion recommendations |
| December | Year-end retrospective | CDO | Divisional retrospective; lessons learned |
SDLC Cycle Cadence¶
Simpaisa runs 9-day delivery cycles (not 2-week sprints). Key cycle events:
| Event | When | Duration | Purpose |
|---|---|---|---|
| Cycle Planning | Day 1 | 2 hours | Backlog selection, capacity check, acceptance criteria review |
| Mid-cycle check | Day 5 | 30 min | Blocker review, scope adjustment if needed |
| Demo & Review | Day 9 (AM) | 60 min | Demonstrate completed work to stakeholders |
| Retrospective | Day 9 (PM) | 45 min | Process improvements, team health |
| Backlog Refinement | Day 8 | 60 min | Groom next cycle stories |
Cycles are not skipped for public holidays — capacity is adjusted instead.
Corridor Launch Calendar (Rolling)¶
Corridor launches (G4 entries) are scheduled as they arise. The Corridor Launch Review (see Committee Register) is convened ad hoc within 5 business days of G3 completion. The Digital Office maintains a forward view of likely launches based on the G0–G2 pipeline.
Current pipeline and expected G4 dates are maintained in the CDO 30/60/90 Day Plan and updated monthly.
Calendar Management¶
-
The CDO Office owns this calendar and coordinates scheduling conflicts.
-
All recurring meetings are in the shared CDO division calendar in Google Workspace.
-
Meeting prep materials are due 24 hours before the meeting in all cases.
-
Decisions from governance meetings are logged in the relevant committee page within 48 hours.
Next review: July 2026 | Amendments via CDO Office