Free templates for software teams

Every doc a team writes between an idea and a release, in the order they're written. Each one is the shape Releavo itself uses, with how to fill it in and a worked example. The examples follow one feature, bulk orders for a wholesaler, from the brief to the release notes. They're markdown: copy them into any tool.

1. 1Product brief templateOne page that says what you're building, for whom, and how you'll know it worked.Signed off by the product owner
2. 2PRD templateThe product requirements document says what the product must do, in requirements you can test.Signed off by the product owner
3. 3UX spec templateThe UX spec turns the PRD's requirements into flows and screens, including the states designs usually forget: empty, loading, partial and error.Signed off by the product owner or the designer
4. 4Architecture doc templateThe architecture doc says how the system will meet the PRD and the UX spec: what the parts are, what data they own, how they talk, and why you chose this design over the alternatives..Signed off by the tech lead
5. 5Epic templateAn epic is a body of work that delivers one outcome a user would notice and takes more than a sprint.Signed off by the product owner
6. 6User story templateA user story is a slice of an epic that fits in a sprint and delivers something a user can see.Signed off by the product owner
7. 7Readiness check templateA readiness check answers one question before development starts: is everything the team needs to build this decided, consistent and approved? It ends in a verdict and a list of what blocks it..Signed off by the tech lead
8. 8Test plan templateTest cases come straight from a story's acceptance criteria: at least one per criterion, plus the negative and edge cases from the PRD and UX spec.Signed off by QA
9. 9Change request templateA change request is how a change to already-approved scope, behaviour or dates gets decided instead of just happening.Signed off by the product owner
10. 10Release notes templateRelease notes tell users what they can do now that they couldn't before.Signed off by the product owner