Define completion clearly
Agree what a feature must do, how it will be tested, and what remains outside scope. Clear acceptance criteria help the team review delivery without relying on subjective impressions. Turn the findings into a short list of actions and owners.
Prepare accurate distribution information, test credentials where needed, and a support contact. Review approval cannot be treated as an automatic release date. Explain why a change was made, not just when it happened.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Keep the scope specific enough to check at each review.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Review both successful actions and errors before launch.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities