Control the maintenance burden
Frameworks, libraries, devices, and operating systems change. Document dependencies and update responsibilities so ongoing compatibility is part of the plan rather than an unexpected expense. Keep the next round of work small enough to assess clearly.
Request only necessary access and provide a useful refusal path. Test camera, storage, and location functions with permissions both allowed and denied. Keep a record of permission for any customer story used publicly.
Data and permissions
Collect only data needed for the task, document access roles, and plan deletion and recovery. Security should be considered while designing the workflow. Check access rights before giving another supplier an account login.
Document APIs, authentication, failure handling, and data ownership. Test slow responses and unavailable external systems, not just the successful path. List the required outputs before setting the delivery schedule.
- Current accounts and assets
- Verified business information
- Customer questions
- Budget and team capacity
Discuss Your Priorities