Lack of Documentation: Nightmare or Working Strategy?
summary
A QA lead from 4A Games discusses how quality assurance copes with either too many documents or none at all, comparing heavy internal wiki-style documentation to informal verbal notes. The talk examines different documentation strategies and seeks the optimal balance for QA workflows in various development circumstances.
AI-written summary · about
chapters (9)
- 0:00QA on docs
- 2:12Docs in project lifecycle
- 6:33Docs vs oral comms
- 13:40When docs aren't needed
- 16:54Balancing docs and comms
- 24:00Docs as tool
- 31:30Q&A
- 41:11AI for docs
- 45:47Key project docs
related talks
21mDevelopers vs Quality Assurance
35mQA in GameDev. How to: build outsource processes, hire right people, successfully release projects
39mWe're Agile, we don't do documentation
46mWhat can QA do and what should it not fear?
36mTo document, or not document that is the question
01h 24mWriting Documentation - Practices and Theory
15mHow we do Quality Assurance at King and How Agile Jenga Helps us With our Processes
20mOh My Docs!