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. Use the findings to update the brief for the next stage.
Prepare accurate distribution information, test credentials where needed, and a support contact. Review approval cannot be treated as an automatic release date. Record the date, reason, and owner of important changes.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. A written brief should explain what will change and what will stay.
Test representative devices, permissions, interrupted connections, and failed inputs. Define acceptance checks with the people who will use the product. Confirm that forms, phone links, and replies reach the right person.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities