# Glossary ### Agile An iterative approach to delivery that focuses on user needs, frequent learning, visible progress and continuous improvement. ### Alpha A phase used to test possible solutions and risky assumptions before committing to full build. ### Acceptance Criteria The agreed conditions that must be met for a deliverable, story or milestone to be accepted. ### Backlog A prioritised list of work items to be delivered or investigated by the team. ### Background IP Pre-existing intellectual property owned by the company or a third party before the project starts. ### Beta A phase where the preferred solution is built and tested with real users before live operation. ### Change Control The process for assessing and approving material changes to scope, cost, time, risk, acceptance, security, data or IP. ### Definition of Done The agreed standard that must be met before work is considered complete. ### Definition of Ready The agreed standard that must be met before work is ready for delivery planning. ### Discovery A phase used to understand the problem, users, constraints and opportunities before committing to a solution. ### Foreground IP Intellectual property created during and for a specific project. ### Live The phase where a service is operated, monitored, supported and continuously improved. ### Prototype A test artifact used to learn. A prototype is not automatically production-ready. ### RAID Risks, Assumptions, Issues and Dependencies. ### Roadmap A planning artifact that shows direction, expected phases, key outcomes, dependencies and decision points. ### Statement of Work The document that defines the authorised work package, including scope, deliverables, milestones, acceptance criteria and commercial terms. ### Technical Spike A time-boxed investigation used to answer a technical question or reduce uncertainty. ### User Need A statement of what a user needs to achieve and why it matters. --- # 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/glossary.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.