Your Personal Tech-Writing Agile Manifesto (or: Scrum is not a 4-character word)
summary
Argues concrete ways for documentation to fit agile: use definition of done for tasks, aim to write sprint+1 so UI and tasks publish quickly, and track progress on a Kanban board (mentions Jira, Confluence, SharePoint, Hangouts/IRC). Gives timing specifics — sprints 1–4 weeks (two common), releases sometimes every six months, Chrome every six weeks — and reports these methods reduce rework and surface blockers, claiming they actually improved integration of docs with development.
AI-written summary · about
chapters (14)
- 0:00Intro
- 0:30Who am I
- 4:19Who are the volunteers
- 5:31Cultural references
- 7:55Background
- 13:55Agile Manifesto
- 18:07Working Software over Comprehensive Documentation
- 20:35Customer Collaboration over Contract Negotiation
- 23:45Respond to Change Over
- 27:29Scrum
- 34:25Kanban
- 36:31Lean Development
- 38:13Criticism
- 40:05Overkill
related talks
26mWe're Agile, We Don't Do Documentation
39mWhen Agile Fails: Working on Large Documentation Projects
25mAgile: The Bad Parts - Matt Parker, Martina Hodges-Schell
49mAgile is a Dirty Word
34mLeadership Lessons from the Agile Manifesto
01h 01mLeadership Lessons from the Agile Manifesto
26mIs Agile still the answer?
49mBaking Boards: Tweak the Recipe for Agile Development