AI Delivery Governance

Appearance

1. Epic template ​

Use this when the work is large, spans multiple tickets, and represents a meaningful business or technical objective.

Epic: [Clear Name of the Initiative] ​

1. Executive Summary ​

We want to [describe the desired outcome] because [describe the business, user, operational, or technical reason].

This epic exists to solve: [describe the real problem].

It does not exist to merely produce code, tickets, documentation, or AI-generated artifacts.

2. Strategic Intent ​

The intent of this epic is:

[Write the core intention in 1–3 sentences.]

A person must be able to explain this intent verbally without reading this document.

3. Problem Statement ​

Currently:

  • [Current pain/problem 1]
  • [Current pain/problem 2]
  • [Current pain/problem 3]

This causes:

  • [Impact on users/customers]
  • [Impact on developers/operations]
  • [Impact on business/security/compliance]

4. Desired Outcome ​

When this epic is complete:

  • [Outcome 1]
  • [Outcome 2]
  • [Outcome 3]

Success means that [describe observable improvement].

5. Scope ​

In Scope ​

  • [Item clearly included]
  • [Item clearly included]
  • [Item clearly included]

Out of Scope ​

  • [Item explicitly excluded]
  • [Item explicitly excluded]
  • [Item explicitly excluded]

Anything not listed in scope must be clarified before implementation.

6. Source of Truth ​

The following sources define the real intent of this epic:

  • Product decision: [link]
  • Customer request / stakeholder input: [link]
  • Incident / bug / operational evidence: [link]
  • Architecture decision record: [link]
  • Design / mockup: [link]
  • Compliance / security requirement: [link]

If no source of truth exists, this epic is not ready.

7. Stakeholders ​

RoleNameResponsibility
Product Owner[Name]Owns product intent and priority
Technical Lead[Name]Owns architecture and technical direction
Delivery Owner[Name]Owns planning and coordination
Security / Compliance[Name]Owns risk constraints
Engineering Team[Team]Owns implementation and verification

8. Key Assumptions ​

We currently assume that:

  • [Assumption 1]
  • [Assumption 2]
  • [Assumption 3]

Each assumption must be validated, rejected, or converted into a risk before delivery.

9. Constraints ​

We must respect:

  • Technical constraints: [details]
  • Security constraints: [details]
  • Compliance constraints: [details]
  • Timeline constraints: [details]
  • Dependency constraints: [details]
  • Operational constraints: [details]

10. Risks ​

RiskProbabilityImpactMitigation
[Risk 1]Low / Medium / HighLow / Medium / High[Mitigation]
[Risk 2]Low / Medium / HighLow / Medium / High[Mitigation]
[Risk 3]Low / Medium / HighLow / Medium / High[Mitigation]

11. Non-Functional Requirements ​

This epic must consider:

  • Performance: [expectation]
  • Security: [expectation]
  • Reliability: [expectation]
  • Observability: [logs, metrics, traces]
  • Maintainability: [expectation]
  • Accessibility: [if applicable]
  • Data privacy: [if applicable]

12. Success Metrics ​

We will know this epic succeeded if:

MetricCurrent ValueTarget ValueMeasurement Source
[Metric 1][x][y][source]
[Metric 2][x][y][source]
[Metric 3][x][y][source]

Avoid vanity metrics. Measure outcomes, not activity.

13. Child User Stories ​

  • [ ] [Story 1]
  • [ ] [Story 2]
  • [ ] [Story 3]
  • [ ] [Story 4]

Each child story must have its own acceptance criteria and verification evidence.

14. AI Usage Declaration ​

AI was used for:

  • [ ] Drafting
  • [ ] Summarization
  • [ ] Research
  • [ ] Ticket decomposition
  • [ ] Technical proposal
  • [ ] Not used

Human verification completed:

  • [ ] Intent checked against source of truth
  • [ ] Scope reviewed by Product Owner
  • [ ] Technical feasibility reviewed by Technical Lead
  • [ ] Risks reviewed
  • [ ] Acceptance criteria reviewed
  • [ ] No unverified AI claim remains

Human accountable owner: [Name]

15. Definition of Ready ​

This epic is ready only when:

  • [ ] The strategic intent is clear
  • [ ] Scope and out-of-scope are explicit
  • [ ] Source of truth is linked
  • [ ] Stakeholders are identified
  • [ ] Major risks are documented
  • [ ] Success metrics are defined
  • [ ] Child stories are identified or planned
  • [ ] Human owner has reviewed all AI-generated content

16. Definition of Done ​

This epic is done only when:

  • [ ] All child stories are completed
  • [ ] Acceptance criteria are satisfied
  • [ ] Success metrics have been measured or scheduled for measurement
  • [ ] Documentation is updated
  • [ ] Operational impact is reviewed
  • [ ] Security/compliance impact is reviewed
  • [ ] Stakeholders have accepted the result
  • [ ] Lessons learned are documented