Digital Office
| Field | Detail |
|---|---|
| Owner | Arsalan Pervez, Delivery Manager - Digital Office |
| Sponsor | Daniel O'Reilly, Chief Digital Officer |
| Date | 14 April 2026 |
| Status | Active |
| Classification | Internal - Restricted |
| Review Cycle | Monthly |
The Digital Office is the CDO's primary execution arm, responsible for ensuring Simpaisa's seven delivery tribes operate with rigour, consistency, and measurable velocity. This plan covers the first 90 days from 14 April 2026 through 13 July 2026, structured across three phases: assess and establish (Days 1-30), build and implement (Days 31-60), and optimise and prove (Days 61-90).
Team Overview¶
| Name | Role |
|---|---|
| Arsalan Pervez | Delivery Manager (Team Lead) |
| Wajih Aslam | Digital Delivery Lead |
| Muhammad Ahsan | Delivery Analyst |
| Annus Ahmed | Delivery Analyst |
Mission: Embed delivery discipline across all seven Simpaisa tribes by driving SDLC v2.0 adoption, establishing PMO governance, maintaining architecture integrity through ADR governance, and tracking AI adoption as a strategic metric.
Scope of accountability: - SDLC v2.0 rollout and compliance monitoring across all tribes - Jira Kanban board configuration and hygiene standards - PMO governance enforcement (portfolio reviews, dependency tracking, escalation paths) - Definition of Done (DoD) adoption and audit - Architecture Decision Record (ADR) governance in Confluence - AI-native engineering adoption metrics and reporting
Milestone Overview¶
gantt
title Digital Office - 90-Day Delivery Plan
dateFormat YYYY-MM-DD
axisFormat %d %b
section Phase 1 - Assess and Establish
Tribe delivery assessments :a1, 2026-04-14, 14d
Jira board configuration (all tribes) :a2, 2026-04-21, 14d
SDLC v2.0 onboarding sessions :a3, 2026-04-28, 14d
PMO governance framework drafted :a4, 2026-04-14, 30d
Weekly portfolio review cadence live :a5, 2026-04-21, 7d
section Phase 2 - Build and Implement
DoD audit across all tribes :b1, 2026-05-15, 21d
ADR template and Confluence space :b2, 2026-05-15, 14d
Dependency tracking board live :b3, 2026-05-22, 14d
AI adoption baseline established :b4, 2026-05-15, 30d
SDLC compliance dashboard published :b5, 2026-06-01, 12d
section Phase 3 - Optimise and Prove
First DORA metrics report :c1, 2026-06-14, 14d
PMO governance audit (90-day) :c2, 2026-06-28, 14d
AI adoption report to leadership :c3, 2026-07-01, 12d
Continuous improvement backlog live :c4, 2026-06-14, 30dPhase 1 - Assess and Establish (Days 1-30, 14 April - 13 May 2026)¶
Objective: Understand the current delivery state across all seven tribes, establish baseline measurements, and put foundational governance structures in place.
Deliverables¶
| # | Deliverable | Owner | Due | Success Metric |
|---|---|---|---|---|
| 1.1 | Conduct structured delivery assessment for each of the seven tribes - document Jira usage, sprint cadence, Definition of Done compliance, and backlog hygiene | Wajih Aslam + Annus Ahmed | 28 Apr 2026 | Assessment report completed for all 7 tribes with RAG status per dimension |
| 1.2 | Configure Jira Kanban boards for all seven tribes to SDLC v2.0 standard - including columns (Backlog, In Progress, In Review, Done), WIP limits, and DoD checklist integration | Muhammad Ahsan | 5 May 2026 | All 7 tribe boards live in Jira with SDLC v2.0 column structure and DoD checklist visible |
| 1.3 | Deliver SDLC v2.0 onboarding sessions to all tribe leads and senior engineers - covering the 10-point Definition of Done, gate structure, and Jira workflow requirements | Arsalan Pervez | 9 May 2026 | Sessions delivered to all 7 tribes; attendance recorded; follow-up Q&A log maintained |
| 1.4 | Establish weekly portfolio review cadence - standing agenda, attendee list, Jira dashboard, and escalation path documented and agreed with CSNO and COO | Arsalan Pervez | 21 Apr 2026 | First portfolio review held by 21 April 2026; cadence is recurring in shared calendar |
| 1.5 | Draft the Digital Office PMO Governance Framework - defining enforcement mechanisms, exception handling, reporting lines to CSNO, and escalation thresholds | Arsalan Pervez + Wajih Aslam | 13 May 2026 | Framework document published to Confluence Digital space; reviewed and signed off by CDO |
Key Risks (Phase 1)¶
- Tribe leads may be resistant to Jira board reconfiguration if it disrupts existing workflows. Mitigation: frame as supporting, not policing; run sessions collaboratively.
- Incomplete visibility into tribe tooling (some may not be using Jira actively). Mitigation: discovery call with each tribe lead in Week 1.
Phase 2 - Build and Implement (Days 31-60, 14 May - 12 June 2026)¶
Objective: Move from assessment to implementation - enforce the governance structures established in Phase 1, build the measurement infrastructure, and embed the Definition of Done across active delivery.
Deliverables¶
| # | Deliverable | Owner | Due | Success Metric |
|---|---|---|---|---|
| 2.1 | Conduct a Definition of Done audit across all seven tribes - review completed tickets against the 10-point DoD; produce a compliance heat map | Muhammad Ahsan + Annus Ahmed | 5 Jun 2026 | DoD compliance heat map published; tribes below 60% compliance placed on improvement plan |
| 2.2 | Publish the Architecture Decision Record (ADR) governance standard - Confluence template, naming convention, mandatory fields, and tribe owner assignment; seed with the first five cross-tribe ADRs | Wajih Aslam | 29 May 2026 | ADR Confluence page structure live; at least 5 ADRs published; tribe architects assigned as owners |
| 2.3 | Implement cross-tribe dependency tracking in Jira - using issue links, a dedicated dependency board, and a weekly dependency review slot within the portfolio review | Muhammad Ahsan | 5 Jun 2026 | Dependency board live with at least 80% of known cross-tribe dependencies mapped; reviewed weekly |
| 2.4 | Establish the AI adoption baseline - define the measurement framework (tools in use, engineers with active licences, commits touching AI-generated code, review coverage), collect Week 1 data | Wajih Aslam + Annus Ahmed | 13 Jun 2026 | Baseline report published with data from at least 5 of 7 tribes; framework agreed with CDO |
| 2.5 | Publish the SDLC v2.0 compliance dashboard in Confluence - showing per-tribe adoption rate (DoD compliance, Jira hygiene score, ADR coverage), updated weekly | Muhammad Ahsan | 12 Jun 2026 | Dashboard live and publicly accessible in Digital space; updated for at least two consecutive weeks |
| 2.6 | Introduce a fortnightly dependency and blocker review - separate from the portfolio review - with tribe leads and engineering leads, producing a written output each cycle | Arsalan Pervez | 20 May 2026 | Two fortnightly reviews completed by end of Phase 2; outputs published to Confluence |
Key Risks (Phase 2)¶
- ADR adoption may be low if tribe architects are not engaged early. Mitigation: Wajih to run a 30-minute ADR clinic per tribe before the framework is published.
- AI adoption data may be difficult to collect without instrumentation. Mitigation: use proxy measures (Copilot seat usage, AI commit tags) and agree on methodology with CDO before launch.
Phase 3 - Optimise and Prove (Days 61-90, 13 June - 13 July 2026)¶
Objective: Demonstrate measurable improvement against the baselines established in Phases 1 and 2, publish the first leadership-level metrics report, and institutionalise the governance cadence so it is self-sustaining.
Deliverables¶
| # | Deliverable | Owner | Due | Success Metric |
|---|---|---|---|---|
| 3.1 | Publish the first DORA metrics report across all tribes - covering deployment frequency, lead time for change, change failure rate, and mean time to restore; compare to Phase 1 baseline | Wajih Aslam + Muhammad Ahsan | 28 Jun 2026 | Report published to CDO and CSNO; at least 5 of 7 tribes have measurable data across all four DORA dimensions |
| 3.2 | Conduct the 90-day PMO governance audit - review portfolio review attendance, escalation resolution times, DoD compliance trend, and ADR publication rate; produce a written findings report | Arsalan Pervez | 7 Jul 2026 | Audit report completed; findings presented to CDO; at least 3 improvement actions captured in Jira |
| 3.3 | Publish the AI adoption progress report to the leadership team - showing adoption trend from baseline to Day 90, identifying leading tribes, lagging tribes, and recommended incentives | Annus Ahmed + Wajih Aslam | 4 Jul 2026 | Report presented at leadership review; AI adoption rate across Digital Office tribes documented at tribe level |
| 3.4 | Establish the Digital Office continuous improvement backlog in Jira - a rolling backlog of process improvement items, owned by the Digital Office, reviewed monthly with the CDO | Arsalan Pervez | 13 Jun 2026 | Backlog created; at least 10 items captured from Phase 1 and 2 findings; first monthly review completed |
| 3.5 | Transition portfolio review to a fully self-service model - tribe leads update Jira boards ahead of each review; Digital Office role shifts from data collection to facilitation and escalation | Arsalan Pervez | 13 Jul 2026 | Three consecutive portfolio reviews completed with tribe-led updates; Digital Office preparation time below 1 hour per review |
Key Risks (Phase 3)¶
- DORA metrics may be incomplete if CI/CD pipelines are not instrumented. Mitigation: escalate to Engineering leads in Phase 2 if pipeline data is not accessible.
- Leadership report on AI adoption may face scepticism without quantitative methodology. Mitigation: agree measurement methodology with CDO by end of Phase 2.
Success Metrics (90-Day Targets)¶
These are the headline metrics the Digital Office will be held to at the 90-day review with the CDO and CSNO.
| Metric | Baseline (Day 1) | Target (Day 90) | Measurement Method |
|---|---|---|---|
| SDLC v2.0 adoption rate (% of tribes with compliant Jira boards and active DoD) | 0% (not yet assessed) | 85% (6 of 7 tribes) | SDLC compliance dashboard |
| Definition of Done compliance (% of completed tickets passing all 10 DoD criteria) | Unknown | 70% across all tribes | DoD audit in Jira |
| Deployment frequency (DORA) | Unknown | Measured and baselined for all tribes | DORA metrics report |
| Lead time for change (DORA) | Unknown | Measured and baselined for all tribes | DORA metrics report |
| AI adoption rate (% of engineers with active AI tooling licence and measurable usage) | Unknown | Baseline established; target set for Q3 | AI adoption report |
| ADR coverage (% of significant architectural decisions captured as ADRs in Confluence) | 0 | At least 10 ADRs published across tribes | Confluence ADR index |
| Portfolio review cadence (% of weeks where review was held with tribe-led updates) | 0% | 90% (missing at most 1 in 10 weeks) | Meeting log |
| Cross-tribe dependency visibility (% of known dependencies tracked in Jira) | 0% | 80% | Dependency board |
Operating Rhythm¶
The Digital Office will operate on the following recurring cadences from Week 1:
| Cadence | Frequency | Format | Owner |
|---|---|---|---|
| Portfolio review | Weekly (Monday) | 60-minute structured review, Jira dashboard | Arsalan Pervez |
| Dependency and blocker review | Fortnightly (Wednesday) | 45-minute focused session, written output | Wajih Aslam |
| SDLC compliance dashboard update | Weekly (Friday) | Automated where possible, manual fallback | Muhammad Ahsan |
| CDO 1:1 (Arsalan) | Weekly | Standing agenda: metrics, blockers, decisions needed | Arsalan Pervez |
| AI adoption data collection | Monthly | Survey plus tooling data pull | Annus Ahmed |
| Continuous improvement backlog review | Monthly | Digital Office internal review | Arsalan Pervez |
Dependencies and Escalation¶
Upstream dependencies: - SDLC v2.0 document published and accessible (complete - April 2026) - CDO sponsorship and active participation in portfolio reviews - CSNO (Bachir Njeim) engagement on PMO governance enforcement - Tribe leads granted Jira admin rights for board configuration assistance
Escalation path: - Tribe-level blockers: Arsalan Pervez escalates to tribe lead directly, then to CDO if unresolved within 5 business days - Governance non-compliance: Documented in audit log, escalated to CSNO and CDO jointly - Tooling blockers (Jira access, Confluence permissions): Muhammad Ahsan escalates to IT Operations with 48-hour SLA target