LETTER99 SOFTWARE PROJECT REVIEW CHECKLIST letter99.com | info@letter99.com | (303) 810-5788 Use this guide to discuss a software project, review working increments, and prepare for delivery. Adapt the checks to the project. Scope, commercial commitments, ownership, and support are agreed in the proposal. 1. THE USEFUL OUTCOME [ ] Describe the problem and the people who need to solve it. [ ] Map the current workflow and systems involved. [ ] Define the smallest useful first release. [ ] Agree what is in scope, what is excluded, and the assumptions. [ ] Identify dependencies, decision makers, and access requirements. 2. ACCEPTANCE CRITERIA [ ] Write down the important user journeys and expected results. [ ] Define access roles and permitted actions. [ ] Identify missing, invalid, or duplicate information scenarios. [ ] Agree behavior when a connection or external service fails. [ ] Specify relevant devices, browsers, and accessibility requirements. [ ] Agree relevant data volumes and operating conditions. 3. WORKING REVIEWS [ ] Agree a review cadence and who can accept completed work. [ ] Walk through working software against the agreed criteria. [ ] Record accepted behavior and unresolved questions. [ ] Distinguish defects, decisions, and new scope requests. [ ] Agree the cost, timing, and priority effect of a requested change. [ ] Keep the next priorities visible. 4. RELEASE READINESS [ ] Complete the relevant workflow and regression checks. [ ] Review permissions, configuration, and deployment environments. [ ] Prepare and check any migration or data import. [ ] Record known limitations and acceptance of outstanding items. [ ] Agree the launch window and operating responsibilities. [ ] Define monitoring, recovery, and the rollback procedure. 5. HANDOVER [ ] Confirm repository access, code ownership, and relevant licenses. [ ] Confirm account ownership and access responsibilities. [ ] Review setup instructions and configuration requirements. [ ] Walk through build, deployment, and release instructions. [ ] Document important architectural choices and dependencies. [ ] Review relevant backup, recovery, and integration operating notes. [ ] Record unresolved items and agreed next steps. [ ] Confirm support coverage, channels, and responsibilities. NOTES AND DECISIONS Project: Useful first outcome: Decisions required: Owner for each decision: Next review: CONTACT Letter99 Software 300 S Jackson St, Suite 415 Denver, CO 80209 info@letter99.com (303) 810-5788 https://letter99.com/contact