We're Agile, We Don't Do Documentation
summary
Argues that documentation is useful when it delivers concrete outcomes: five practical purposes are named — creating a wall of common understanding (about six or eight A4 sheets), surfacing complexity with infographics, building empathy with a widget kit for explanations, capturing rationale via decision records stored as markdown alongside code using a context decision consequences structure, and using quick whiteboard/napkin sketches for creative problem solving; warns against heavyweight auto‑generated diagrams and recommends lightweight visible artefacts groomed in team rituals.
AI-written summary · about
chapters (9)
- 0:00Intro
- 1:10Documentation
- 2:58Software Documentation
- 4:00How Much Documentation
- 5:26Use Documentation to Create a Common Understanding
- 8:04Use Documentation to Surface Complexity
- 14:41Use Documentation to Make Better Decisions
- 17:32Creative Problem Solving
- 20:40How to keep documentation up to date
related talks
39mWe're Agile, we don't do documentation
36mTo document, or not document that is the question
38mThe Stuff You Don't Want to Write... Documentation
34mDocumentation Thinking Beyond the Docs: Lessons from Decision-Facing Technical Writing
37mHumanising Your Documentation
29mHumanizing Your Documentation
40mDocumentation as User Experience
34mHumanizing Your Documentation