The GDD's Not Dead: Tips & Tricks for Agile Design Documents
summary
Argues for keeping a single one living document GDD that grows with the project, not many scattered files; recommends the three headers method (chapter overview, feature overview, implementation detail) so different stakeholders skip to needed depth. Uses Google Docs for live collaboration, comments, links and animated GIFs, keeps a tidy change log, assigns one person to maintain the doc, treats documentation mismatches as QA issues/bugs, and warns that wikis and separate docs often slip out of sync or hide edge cases.
AI-written summary · about
chapters (10)
- 0:00Start
- 9:50Comment System
- 10:44Animated Gifts
- 11:49The Three Headers Method
- 13:37Header 2
- 14:40Heading 3
- 24:04What Works Best for a Wiki Franchisors
- 30:41Uml
- 36:53Key Features of a Game
- 40:46Overview
related talks
39mWe're Agile, we don't do documentation
26mWe're Agile, We Don't Do Documentation
40mDocumentation as User Experience
36mTo document, or not document that is the question
44mCreating a Culture of Documentation
44mPushing documentation (so it doesn't hurt anymore)
20mOh My Docs!
45mDocs or it didn't happen!