arckit roadmap

​

Overview

​

Command Syntax

arckit roadmap "<project ID or initiative>"

​

Arguments

​

What It Creates

• File: projects/{NNN}-{project-name}/ARC-{PROJECT_ID}-ROAD-v1.0.md
• Document ID: ARC-{PROJECT_ID}-ROAD-v1.0
• Content: Strategic roadmap with timeline, themes, capability evolution, investment, governance (typically 400-600 lines)

​

Prerequisites

​

Interactive Configuration

​

Question 1: Time Horizon

“What time horizon should the roadmap cover?”

​

Question 2: Year Format

“Which year notation should the roadmap use?”

​

Roadmap Structure

​

1. Executive Summary

• Strategic Vision: What transformation is being enabled? (1-2 paragraphs)
• Investment Summary: Total investment, CAPEX/OPEX split, ROI, payback period
• Expected Outcomes: 3-5 measurable business outcomes
• Timeline at a Glance: Duration, major phases, key milestones, governance gates

​

2. Strategic Context

• Vision & Strategic Drivers: Link to stakeholder drivers, architecture principles alignment
• Current State Assessment: Technology landscape, capability maturity baseline, technical debt, risk exposure
• Future State Vision: Target architecture, capability maturity targets, technology evolution (reference Wardley Maps if available)

​

3. Roadmap Timeline

• Use financial year notation: FY 2024/25, FY 2025/26, etc. (if UK Government) OR calendar years
• Show 4 major phases: Foundation, Migration, Transformation, Optimization
• Include governance gates as milestones

​

4. Roadmap Themes & Initiatives

• Strategic objective
• Timeline by financial year (what happens in FY 2024/25, FY 2025/26, etc.)
• Initiatives within each year
• Milestones and investment
• Success criteria

​

5. Capability Delivery Matrix

• L1: Initial: Ad-hoc, unpredictable, reactive
• L2: Repeatable: Basic discipline, some processes
• L3: Defined: Documented standards, proactive
• L4: Managed: Measured, controlled, predictable
• L5: Optimized: Continuous improvement, innovative

​

6. Dependencies & Sequencing

​

7. Investment & Resource Planning

• Investment Summary by Financial Year: Table showing CAPEX, OPEX, total by year
• Resource Requirements: FTE needed, key roles, recruitment timeline, training budget
• Investment by Theme: Budget allocation across themes
• Cost Savings & Benefits Realization: Operational savings, efficiency gains, revenue enablement

​

8. Risks, Assumptions & Constraints

• Key Risks: Strategic risks impacting roadmap (link to risk register if available)
• Critical Assumptions: Funding, skills, vendor support, executive sponsorship
• Constraints: Budget caps, regulatory requirements, timeline mandates

​

9. Governance & Decision Gates

• Governance Structure: ARB (monthly), Programme Board (monthly), Steering Committee (quarterly)
• Review Cycles: Weekly progress, monthly ARB, quarterly business review, annual strategic review
• Service Standard Assessment Gates (if UK Government): Alpha, Beta, Live assessments with dates
• Decision Gates: Go/No-Go gates at major phase transitions

​

10. Success Metrics & KPIs

• Strategic KPIs: Cloud adoption %, technical debt reduction, security incidents, MTTR, deployment frequency
• Capability Maturity Metrics: Maturity levels by year
• Technical Metrics: API availability, page load time, IaC %, automated testing coverage
• Business Outcome Metrics: User satisfaction, cost reduction, revenue enablement, productivity gains

​

11. Traceability

• Stakeholder Drivers → Roadmap Themes
• Architecture Principles → Compliance Timeline
• Requirements → Capability Delivery
• Wardley Maps → Technology Evolution
• Risk Register → Mitigation Timeline

​

UK Government Specifics

​

Included for UK Gov:

• Financial Year Notation: Use “FY 2024/25”, “FY 2025/26” format (not calendar years)
• Spending Review Alignment: Mention SR periods and budget cycles
• Service Standard Assessment Gates: Include Alpha, Beta, Live assessment milestones
• TCoP (Technology Code of Practice): Reference compliance with 13 points
• NCSC CAF: Include security baseline progression
• Cyber Essentials/ISO 27001: Security certification timeline
• Digital Marketplace: If procurement involved, reference G-Cloud/DOS
• Cross-Government Services: Reference GOV.UK Pay, Notify, Design System integration

​

MOD Specifics

​

Real-World Timeline Example

• Foundation phase: 3-6 months (strategy, baseline, security framework)
• Migration phase: 6-18 months (legacy analysis, data migration, app modernization)
• Transformation phase: 12-24 months (cloud-native platform, API platform, DevOps maturity)
• Optimization phase: 6-12 months (performance, scale, continuous improvement)
• Total typical roadmap: 2-5 years

​

Command Handoffs

​

Create Detailed Project Plan for Phase 1

arckit plan

​

Generate Product Backlog

arckit backlog

​

Roadmap vs Plan

​

Important Notes

​

Key Concepts

• Strategic vs Tactical: Roadmap is multi-year strategic, Plan is single-project tactical
• Capability Maturity: Use 5-level model (L1: Initial → L5: Optimized)
• Governance: Roadmaps require heavier governance than project plans (ARB, Programme Board, Steering Committee, Quarterly reviews)
• Integration: Roadmap feeds into arckit plan, arckit sobc, arckit backlog, arckit traceability
• Realistic Timelines: Show investment increasing in middle years (migration/transformation), then decreasing in optimization phase
• Traceability: Link every roadmap theme back to stakeholder drivers and architecture principles

​

Related Guides

• Roadmap Development
• Capability Maturity Models
• Technology Evolution
• Investment Planning