FAANG Incremental Delivery
Ship Fast, Learn Fast, Optimize Fast
xOps follows FAANG incremental delivery principles: working software every 2 weeks, evidence-based quality gates, autonomous PDCA cycles targeting ≥99.5% validated accuracy, and DORA metrics for continuous improvement.
Delivery Cadence
| Cadence | Activities | Deliverable (Git-Tracked) |
|---|---|---|
| Daily | Code commits with tests, agent coordination | Passing CI pipeline + coordination logs |
| Sprint (2 weeks) | Working software increment, HITL review, retrospective | Tagged release + PDCA validation report |
| Release (per phase) | Production deployment, customer validation, metrics baseline | Terraform state + 4-way cross-validation evidence |
DORA Metrics: Measuring Delivery Excellence
xOps tracks all 4 DORA metrics as git-tracked deliverables:
| DORA Metric | BC1 Target | How Measured | Git Artifact |
|---|---|---|---|
| Deployment Frequency | 1/sprint (2 weeks) | git tag count per sprint | Release tags: v0.1.0-phase1 through v1.0.0 |
| Lead Time for Changes | <2 days | First commit → deployment | git log --first-parent delta |
| Change Failure Rate | <5% | Failed deploys / total deploys | CI workflow conclusion status in .github/workflows/ |
| Mean Time to Restore | <1 hour | Incident open → resolution | Incident log in docs/docs/operations/incidents.md |
Why DORA for xOps
DORA metrics are the industry standard (Google, FAANG, DORA State of DevOps Report) for measuring software delivery performance. For ANZ FSI enterprise buyers, DORA provides:
- Benchmarking: Compare xOps delivery against industry elite performers
- Predictability: Sprint-over-sprint trend lines for capacity planning
- Trust: Evidence-based claims about delivery velocity, not opinions
Evidence Architecture: Git-Tracked vs Agent Workspace
Critical Distinction
tmp/ is ephemeral agent workspace — not permanent evidence. Git-tracked deliverables are the real evidence.
| Evidence Type | Location | Lifecycle | Purpose |
|---|---|---|---|
| Git-tracked deliverables | Repository (src/, docs/, terraform/, .github/) | Permanent, versioned, auditable | Production evidence — what was shipped |
Agent workspace (tmp/) | tmp/<project>/ | Ephemeral, session-scoped, gitignored | Agent coordination scratch space — how decisions were made |
| CI/CD artifacts | GitHub Actions, Terraform Cloud | Retention-policy governed | Build evidence — how it was validated |
| DORA metrics | Release tags, CI logs, incident docs | Derived from git history | Delivery performance — how well we're shipping |
What Goes Where
| Artifact | Goes In | Why |
|---|---|---|
| Terraform modules, source code | src/, modules/ (git) | Permanent, versioned, reviewable |
| Test results, coverage reports | CI artifacts + docs/ summary | Reproducible from git |
| Architecture Decision Records | docs/docs/adrs/ (git) | Permanent architectural knowledge |
| PDCA validation reports | docs/ or release notes (git) | Sprint-level quality evidence |
| Agent coordination logs | tmp/ (gitignored) | Ephemeral — informs decisions, not the decision itself |
| Cross-validation raw data | tmp/ during session, summary in docs/ | Raw data is transient; conclusions are permanent |
| FinOps FOCUS reports | docs/ or S3 (git-tracked reference) | Business deliverable, must survive sessions |
PDCA Cycle: How Quality is Measured
Every deliverable goes through autonomous Plan-Do-Check-Act cycles before HITL review:
PLAN → DO → CHECK → ACT
↑ |
└────────────────────┘
(max 3 cycles before HITL escalation)
| Phase | Who | What | Git Deliverable |
|---|---|---|---|
| PLAN | PO + CA | Score requirements, design architecture | ADR + INVEST stories committed to docs/ |
| DO | Specialist agents | Implement, test, collect evidence | Code + tests committed to feature branch |
| CHECK | 4-way cross-validation | Validate across boto3, MCP, Runbooks, Console | Validation summary in PR description |
| ACT | All agents | Fix gaps, re-score, iterate | Fix commits on same branch |
Targets:
- Cross-validated accuracy: ≥99.5%
- Agent consensus: ≥95% across PO, CA, MEE, IE
- Max autonomous cycles: 3 (then HITL escalation)
Enterprise Coordination Protocol
Every feature follows the ADLC coordination chain — no exceptions:
HITL Manager Directive
↓
1. product-owner (BLOCKING) → INVEST stories, acceptance criteria
↓
2. cloud-architect (BLOCKING) → Architecture ADR, deployment target
↓
3. Specialists (PARALLEL) → IE + QA + SCE + OE + FDE
↓
4. Evidence collection → Git-tracked deliverables + tmp/ workspace
↓
5. PDCA cycles until ≥99.5%
↓
6. HITL review → Merge to main → Release tag
Anti-patterns prevented: 25 documented patterns blocked by 5 governance hooks. See PR/FAQ Q19 for the full hook reference.
HITL Gates per Phase
| Phase | HITL Role | Time Investment | Gate Criteria | Git Artifact |
|---|---|---|---|---|
| PLAN (Wk 1-2) | Give directive | 15 min | Agent scores ≥90% | ADR + stories in docs/ |
| BUILD (Wk 3-4) | Review code | 30 min | Linting PASSED, tests GREEN | Feature branch merged |
| TEST (Wk 5-6) | Approve evidence | 15 min | 4-way cross-val ≤0.5% | Test report in CI |
| DEPLOY (Wk 7-8) | SNS approve | 5 min | checkov 0 FAILED, infracost ≤+5% | terraform apply state |
| MONITOR (Wk 9-10) | Review SLOs | 15 min | Baselines established | SLO definitions in docs/ |
Total HITL time per sprint: ~80 minutes. Agents handle the remaining ~80 hours of execution.
xOps BC1 Delivery Timeline with DORA Tracking
| Phase | Sprint | Deliverable | PDCA Target | DORA: Deploy Freq |
|---|---|---|---|---|
| 1 | Wk 1-2 | docker-compose + CLAUDE.md + Playwright | ≥90% | v0.1.0-phase1 |
| 2 | Wk 3-4 | CloudOps-Runbooks MCP + Open WebUI pipeline | ≥95% | v0.2.0-phase2 |
| 3 | Wk 5-6 | FinOps FOCUS 1.2+ + 4-way cross-validation | ≥95% | v0.3.0-phase3 |
| 4 | Wk 7-8 | Terraform M3 + CI gates (checkov+trivy+infracost) | ≥99% | v0.4.0-phase4 |
| 5 | Wk 9-10 | AWS deploy + 4-layer evidence + PDCA closure | ≥99.5% | v1.0.0 |
Evidence
- PDCA validation log: PR/FAQ Section 8
- Cross-validation pattern:
.claude/skills/finops/cross-validation.md - Anti-pattern list:
.claude/rules/adlc-governance.md(25 patterns) - Coordination:
tmp/adlc-framework/coordination-logs/product-owner-2026-03-11-docs-expansion.json