# Agile Delivery

Agile delivery in MCAF is lightweight and outcome-driven.

## Goals

- keep the backlog visible and current
- turn work into small reviewable increments
- keep feedback loops short
- convert repeated process pain into durable repo guidance

## Default Operating Model

- Maintain one shared backlog that the whole delivery team can see.
- Keep work items small enough to review, test, and ship without hidden side work.
- Define readiness before implementation and completion before closure.
- Use short planning and feedback loops instead of large ceremony-heavy process.
- Record lasting process rules in the repo, not only in chat or meetings.

## Backlog Rules

- backlog items describe a user or system outcome, not just a task label
- scope, acceptance, and constraints are visible before implementation starts
- if an item is too large to review coherently, split it before coding

## Team Cadence

- planning chooses the next smallest meaningful slice of value
- standups or async updates surface blockers and PR review needs
- retrospectives or equivalent feedback loops must produce concrete follow-up actions

## Durable Artifacts

- work agreements and recurring rules belong in docs or `AGENTS.md`
- feature behaviour belongs in feature specs
- architecture decisions belong in ADRs
- repo workflow rules belong in skills only when they are reusable
