
Acceptance and support
Use task-based checks for the release and agree responsibility for later operating-system changes. Maintenance belongs in the project budget. Use the findings to update the brief for the next stage.
Document what existing apps fail to provide and which custom steps are essential. Build around the user task rather than novelty. Choose the next task from the review rather than repeating the calendar.
- A written brief
- Named responsibilities
- Agreed review points




