# 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. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://framework.aic.io/company-operating-manual/agile-delivery-approach.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.