Guides for software teams.
Short, practical guides for software teams, from the first spec to the release.
- Specs · 4 min readWhat is a PRD? How to write one, step by step
- Specs · 4 min readHow to write a product spec your team will read
- Specs · 3 min readHow to write acceptance criteria, with examples
- Specs · 3 min readHow to write a technical design doc
- Specs · 3 min readWhat is an architecture decision record (ADR)?
- Boards · 4 min readWhat is a kanban board? A guide for software teams
- Boards · 3 min readHow to set up a kanban board for a software team
- Boards · 3 min readHow to run a bug tracking board that stays tidy
- Boards · 3 min readThe MoSCoW method: Must, Should, Could explained
- Boards · 3 min readDefinition of done vs acceptance criteria
- Releases · 3 min readHow to plan a software release, step by step
- Releases · 3 min readA software launch checklist, step by step
- Releases · 3 min readHow to write release notes people read
- Team practice · 3 min readHow to run a retrospective that changes something
- Team practice · 3 min readHow to write a blameless incident postmortem
- Team practice · 3 min readHow to plan a sprint without overcommitting
- Team practice · 3 min readHow to take meeting notes your team will use
- Teams and tools · 3 min readChoosing project management software for a dev team
- Teams and tools · 4 min readProject management for large software teams
- Teams and tools · 3 min readProject management for growing software teams
- Teams and tools · 3 min readHow remote software teams stay in sync
- Teams and tools · 3 min readWhy team chat should link to the work
- Teams and tools · 3 min readHow to plan your week around your tasks
- Teams and tools · 3 min readA checklist for onboarding a new engineer
Put a guide to work.
Every guide ends in Kanso. Free does not expire.