Skip to content

AIOPS-05] Run DORA team archetype self-assessment and document targeted roadmap #79

Description

@paruff

[AIOPS-05] Run DORA team archetype self-assessment and document targeted roadmap

Labels: ai-ops, process, p1-critical, effort-small
Assignee: 👤 Human
Phase: Phase 1 — AI Foundation
DORA 2025 Source: “Seven team archetypes” chapter; “Diagnosing your team profile” guidance
Effort: Small (2–3 hours)
Prerequisites: VSM-01


Why This Matters (2025 DORA Finding)

The 2025 DORA report replaces the old Elite/High/Medium/Low performance tiers with seven team archetypes derived from cluster analysis. The insight: different archetypes experience AI adoption differently and require different interventions. A “Legacy Bottleneck” team and a “Pragmatic Performer” team both benefit from AI — but at completely different points of their workflow.

“Without accurate team-level measurement mapped to these archetypes, teams misallocate AI investment.” — Faros AI analysis of 2025 DORA data

For Goald, identifying which archetype the team most closely resembles determines which issues in this backlog should be elevated and which can wait.


The Seven Archetypes

# Archetype Characteristics AI Risk
1 Foundational Challenges Survival mode, process gaps, high burnout AI accelerates chaos
2 Legacy Bottleneck Unstable systems, constant firefighting AI speeds code, broken deploy swamps gains
3 Constrained by Process Slow, bureaucratic workflows AI creates friction with process overhead
4 High Impact, Low Cadence Quality work, slow delivery, low stability Need automation to unlock cadence
5 Stable and Methodical Deliberate, high quality, consistent AI can safely accelerate here
6 Pragmatic Performers Fast, functional, effective AI creates PR review backlog at scale
7 Harmonious High-Achievers Virtuous cycle: well-being + performance AI multiplies advantages

Acceptance Criteria

Self-Assessment Document

  • docs/TEAM_ARCHETYPE.md created with:
    • The team’s current archetype (or closest match) with reasoning
    • Evidence from the last 30 days: deployment frequency, rework rate (METRICS-02), PR cycle time, team friction observations
    • The two or three capabilities from the DORA AI Capabilities Model that are weakest for this archetype
    • A targeted 4-week improvement focus based on the archetype

Archetype-Specific Issue Priority Adjustments

Based on the self-assessment, adjust the implementation order in the master index:

If Foundational Challenges or Legacy Bottleneck:

  • Elevate: DEVOPS-01 (CI), PERF-01 (indexes), SEC-03 (Firestore rules), OBS-01 (Sentry)
  • Rationale: Fix stability before accelerating throughput

If Constrained by Process:

  • Elevate: PROCESS-01 (small batches), VSM-02 (bottleneck removal), GITOPS-01 (streamline PR process)
  • Rationale: Reduce friction first; AI will amplify the remaining friction otherwise

If High Impact, Low Cadence:

  • Elevate: DEVOPS-01, DEVOPS-02, DEVOPS-03 (EAS Build), GITOPS-02 (environment promotion)
  • Rationale: Automation to unlock deployment frequency

If Stable and Methodical or Pragmatic Performers:

  • Current order is appropriate — proceed as planned
  • Watch for: AIOPS-03 (issue templates) and AIOPS-04 (prompt library) becoming bottlenecks as PR volume grows

If Harmonious High-Achievers:

  • Accelerate Phase 3 user features; the foundation is sound
  • Focus on METRICS-01/02 to maintain visibility as velocity increases

Quarterly Re-assessment

  • PROCESS-02 monthly tuning updated to include: “Has the team archetype shifted? Re-read TEAM_ARCHETYPE.md and update if needed.”
  • Archetype review is a standing agenda item in the monthly retrospective

Files to Create

  • docs/TEAM_ARCHETYPE.md
  • Update docs/RUNBOOKS.md — add quarterly archetype re-assessment
  • Update MASTER-IMPLEMENTATION-INDEX.md — note any priority adjustments from archetype assessment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions