
Acceptance and support
Use task-based checks for the release and agree responsibility for later operating-system changes. Maintenance belongs in the project budget. Identify the most useful correction before adding another feature.
Document what existing apps fail to provide and which custom steps are essential. Build around the user task rather than novelty. Keep the next round of work small enough to assess clearly.
- A written brief
- Named responsibilities
- Agreed review points




