Tagged “documentation”
4 articles
6 min read
Acknowledgement Tickets and Sprint Closure Notes Clients Read
An acknowledgement ticket needs three sections: what was delivered, how to verify it, and how to report issues. Sprint closure notes need three more.
- client-communication
- documentation
- agile-delivery
7 min read
BRD vs PRD: What Actually Belongs in Each Document
BRD vs PRD: the BRD holds business justification, scope and sign-off. The PRD holds features, user stories and acceptance criteria.
- requirements
- documentation
- scope-management
5 min read
Client-Facing Tickets: The Template I Use to Stop Scope Creep
Client-facing tickets need five sections: summary, business justification, acceptance criteria, out of scope, and timeline. Here is the template.
- client-communication
- documentation
- scope-management
7 min read
Why a Living Outstanding-Items Register Beats a RAID Log
A Living Outstanding-Items Register beats a RAID log by tracking requirement status, absorbed change requests, and ad-hoc items in one place.
- project-management
- raid-log
- change-management