
Acceptance and support
Use task-based checks for the release and agree responsibility for later operating-system changes. Maintenance belongs in the project budget. End each review with a named next step.
Document what existing apps fail to provide and which custom steps are essential. Build around the user task rather than novelty. Leave the team with a decision, an owner, and a review date.
- A written brief
- Named responsibilities
- Agreed review points




