Skip to content

Backlog Epics

This document defines how catalog categories become backlogs ready for Azure DevOps. It is written for product owners and tech leads.

Hierarchy

Epic -> Capability -> Feature -> Service Candidate (CS-SVC-XXXX) -> User Stories -> Acceptance Criteria

Standard Epics Per Category

Each of the 30 categories gets at least:

  1. Platform Epic - build/extend the bounded-context service(s).
  2. Documentation Epic - deep-dive, contracts, runbooks.
  3. Architecture Epic - bounded-context definition, ADRs, contracts, events.
  4. MVP Implementation Epic - Tier 0-1 services for the category.
  5. Future Expansion Epic - Tier 4-5 items.

Example: Category 2 (Identity & Access)

Epic: Identity & Access Platform
  Capability: Authentication
    Feature: OIDC/OAuth2 provider
      Service Candidate: CS-SVC-0051 Identity Server (Live)
      Service Candidate: CS-SVC-0052 OpenID Connect Provider
        Story: As a tenant admin, I can configure SSO...
          AC: SAML and OIDC supported; audited; multi-tenant.
  Capability: Authorization
    Feature: RBAC/ABAC
      Service Candidate: CS-SVC-0084 RBAC Policy Service
      Service Candidate: CS-SVC-0085 ABAC Policy Service

Generating Backlogs From The Catalog

The machine-readable catalog (.csv) is the seed: each row is a candidate Feature/Service with tier, wave, and status. A future generator step can emit work items per phase.