# Foundations ### Overview We use agile delivery to reduce uncertainty, increase transparency and deliver useful outcomes earlier. Agile is not a lack of structure. It is a disciplined way of learning, prioritising and delivering in controlled increments. Our agile model is designed for real customer environments where delivery must satisfy multiple needs at once: * users need services that work * customers need confidence and visibility * commercial teams need scope and payment control * technical teams need clear standards * security teams need assurance evidence * suppliers need clear responsibilities * leadership needs decision points and risk visibility ### The Agile Contract Boundary In our model, agile delivery operates inside an agreed commercial boundary. The Statement of Work defines: * the authorised work package * the phase being delivered * the outcomes expected * the deliverables * the milestones * the acceptance criteria * the customer responsibilities * the assumptions and exclusions * the commercial model * the IP position * the governance cadence The backlog then defines the day-to-day and sprint-by-sprint delivery detail. This means we can be flexible in how we solve the problem without losing control of scope, risk, cost or acceptance. ### What Agile Means for Customers For customers, agile delivery means: * seeing progress regularly * receiving early evidence rather than late surprises * making prioritisation decisions throughout delivery * validating assumptions before major spend * shaping the product or service using real feedback * understanding trade-offs between time, scope, cost and quality * receiving clearer evidence for acceptance and assurance ### What Agile Means for Delivery Teams For delivery teams, agile delivery means: * working from a prioritised backlog * delivering in short increments * demonstrating progress frequently * making blockers visible early * testing assumptions quickly * improving ways of working continuously * keeping technical, security and delivery evidence current ### What Agile Does Not Mean Agile does not mean: * uncontrolled scope * unclear responsibilities * no documentation * no plan * no commercial discipline * no acceptance criteria * unlimited change * building without evidence * bypassing security or assurance ### Our Delivery Promise We commit to making work visible, learning early, delivering in increments, managing risk actively and protecting both customer outcomes and our commercial position. ### Practical Operating Rules * Every engagement has a defined delivery phase. * Every phase has entry and exit criteria. * Every sprint or iteration has a clear objective. * Every deliverable has acceptance criteria. * Every material decision is recorded. * Every material change is controlled. * Every reusable IP asset is checked before use. * Every project maintains evidence as it delivers. * Every team reviews and improves how it works. --- # 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/agile-delivery-playbook/foundations.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.