W7 / Library
Templates you are welcome to borrow.
Plain, practical documents for running software work well, whoever builds it.
The one-page scope
- Outcome. One sentence: who can do what, by when.
- In. The features or pages in this phase.
- Out. What is deliberately excluded, and why.
- Later. Good ideas parked for a future phase.
- Assumptions. What must be true for the estimate to hold.
- Estimate. A range, with the assumptions above.
- Decision-makers. Who signs off scope, design and launch.
Keeping a RAID log useful
RAID stands for risks, assumptions, issues and dependencies. Keep it under twenty live entries. Review it weekly, in five minutes, not monthly in an hour. Every entry needs an owner and a next action with a date. Close entries promptly; a log full of stale items is ignored. Risks that are both likely and serious deserve a line in the status report until they are resolved.
The four-line status report
Status: Amber, because user testing moved by three days. Done: Payment screens built and demonstrated. Next: Fix testing issues; begin admin exports. Needed from you: Approve refund wording by Thursday.
What a proper handover contains
- Repository access and a readme a new developer can follow
- Hosting, domain and store account ownership confirmed
- Environment variables and secrets documented securely
- Decision log and outstanding risk register
- Accessibility statement with known issues
- Backup and restore steps, tested once
- Support arrangement agreed or explicitly declined