We're Agile, we don't do documentation
summary
Argues that documentation adds concrete value and gives practical forms: create a wall of common understanding (six A4 sheets, updated by a developer every two weeks) for high‑level maps; use infographics and paper “widget” cards to explain an offline‑first data flow and tricky state transitions; capture decisions as architecture decision records (context → decision → consequences) stored with code. Recommends visible artifacts, short rituals (weekly huddle, biannual tech day), and keeping docs minimal and frequently pruned.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 5:30Common understanding
- 8:28Complexity
- 15:40Decision records
- 18:37Creative problem solving
- 23:15Keeping documentation up to date
- 25:28Recap
- 29:05Thoughtworks
- 33:00Visual presentation
related talks
26mWe're Agile, We Don't Do Documentation
36mTo document, or not document that is the question
47mMaking architecture decisions, the Agile Way
38mThe Stuff You Don't Want to Write... Documentation
29mMove Fast and Document Things: Writing internal docs at fast-moving organizations
51mDocumenting and Communicating Modern Software Architectures
42mThe GDD's Not Dead: Tips & Tricks for Agile Design Documents
40mDocumentation as User Experience