Painting the Night Sky at Noon: Putting the "Doc" in DevDocTest
summary
DevDocTest (DDT) claims that writing user docs and test plans synchronously with code cuts the end-of-cycle crunch and the “hockey stick” workload by letting writers and QEs scope stories early, shape UX, and validate docs during development. It uses trackers like Jira, sprint priority ordering rather than strict sprint deadlines, and hands-on test bashes/hackathons to catch mismatches. Reality: transition often creates temporary front-loaded spikes and abandoned features force rewrites, but practiced tenets—early involvement, priority sorting, frequent syncs—regularly reduce late rework.
AI-written summary · about
chapters (9)
- 0:00Introduction
- 0:26Overview
- 1:24Teamwork
- 2:16Coordination
- 3:51Project Complexity
- 4:53Waterfall
- 7:54Agile
- 15:28Core tenets
- 19:28Outro
related talks
31mTDD: Are you sure about that?
35mFrom Code to Clarity: Collaboration with Devels when Writing Product Documentation
39mThe Documentation Dream: One Team, No Silos, Shared Goal
24mWho Writes the Docs?
20mDo Docs Better: Practical Tips on Delivering...
44mTesting Documentation: Why So Technical?
37mTaking a step back: Analysing your documentation
32mTDD – Trust Driven Development