# Phase Entry and Exit Checklists ### Discovery Entry Checklist * Sponsor identified * Problem or opportunity described * Discovery timebox agreed * Commercial authority confirmed * Stakeholder access agreed * Research access agreed * Security constraints identified * Evidence repository created ### Discovery Exit Checklist * Problem statement completed * User needs identified * Current state mapped * Constraints recorded * Risks and assumptions recorded * Options assessed * Recommendation prepared * Alpha or next-phase scope drafted * Decision recorded ### Alpha Entry Checklist * Discovery recommendation approved * Alpha questions agreed * Riskiest assumptions ranked * Team roles confirmed * Prototype approach agreed * Technical spike plan created * Security and data constraints understood * Commercial authority confirmed ### Alpha Exit Checklist * Prototypes tested * User feedback captured * Technical feasibility assessed * Security and data implications understood * Preferred option selected * Beta backlog created * Beta roadmap drafted * Commercial assumptions updated * Proceed, stop or reshape decision recorded ### Beta Entry Checklist * Beta Statement of Work agreed * Backlog prioritised * Acceptance criteria agreed * Environments planned * Engineering standards confirmed * Security approach confirmed * Release approach agreed * Support model design started ### Beta Exit Checklist * Critical journeys tested * Service or product working for real users * Security evidence complete or risk-accepted * Accessibility evidence complete where required * Performance evidence reviewed * Support model ready * Monitoring in place * Live readiness approved * Acceptance recorded ### Live Entry Checklist * Service owner confirmed * Support process live * Monitoring active * Incident process agreed * Access controls reviewed * Operational documentation complete * Release process agreed * Service metrics agreed ### Live Review Checklist * Service performance reviewed * User feedback reviewed * Support tickets reviewed * Incidents reviewed * Security vulnerabilities reviewed * Improvement backlog prioritised * Technical debt reviewed * Roadmap updated ### Retirement Entry Checklist * Retirement trigger identified * Service owner engaged * User impact assessed * Data impact assessed * Supplier impact assessed * Contractual exit obligations reviewed * Retirement approval route agreed ### Retirement Exit Checklist * Users informed or transitioned * Data retained, migrated, archived or deleted * Access removed * Integrations closed * Suppliers exited * Redirects implemented where required * Service decommissioned * Closure evidence stored * Final approval recorded --- # 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/templates-and-checklists/phase-entry-and-exit-checklists.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.