> For the complete documentation index, see [llms.txt](https://framework.aic.io/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://framework.aic.io/company-operating-manual/agile-delivery-approach.md).

# Agile Delivery Approach

### Overview

We follow an agile delivery approach based on user needs, iterative delivery, continuous learning, and evidence-based governance.

Agile delivery helps us reduce risk by learning early, delivering in increments, and adapting plans as new information becomes available.

### Our Agile Lifecycle

We use the following agile lifecycle:

1. Discovery
2. Alpha
3. Beta
4. Live
5. Retirement or transition

### Why We Use Agile

We use agile delivery to:

* understand user and customer needs before committing to solutions
* test assumptions early
* deliver value incrementally
* reduce delivery risk
* improve transparency
* enable faster feedback
* support better governance
* avoid large late-stage failures

### Agile Within Commercial Control

Agile does not mean uncontrolled delivery.

We use agile methods within a structured commercial framework.

The Statement of Work defines the commercial boundary.

The backlog defines the delivery detail.

Change control manages material changes.

Governance ensures visibility, assurance, and decision-making.