# Delivery Assurance ### Purpose Delivery assurance gives confidence that work is progressing, risks are managed, and outputs are fit for purpose. ### Assurance Areas Delivery assurance covers: * scope * schedule * cost * quality * security * technical architecture * commercial obligations * supplier delivery * acceptance evidence * customer readiness ### Assurance Questions A delivery review should ask: * Are we delivering the agreed scope? * Are milestones on track? * Are risks and issues visible? * Are blockers being resolved? * Are decisions being made at the right level? * Is the customer fulfilling dependencies? * Is quality being built in? * Are security obligations being met? * Is acceptance evidence being captured? * Are changes being controlled? ### Assurance Evidence Evidence may include: * signed Statement of Work * approved delivery plan * sprint reports * backlog reports * test evidence * architecture decisions * security review records * code review records * acceptance certificates * customer approvals --- # 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/delivery-governance/delivery-assurance.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.