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. Record the decision as well as the numbers behind it.
Agree supported devices and operating systems, then test representative combinations. Include update and support responsibilities. Leave the team with a decision, an owner, and a review date.
Integration boundaries
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. Define the deliverables and exclusions before work starts.
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