When Agile Doesn't Work Anymore: Managing a Large Documentation Project
C2 | Tue 22 Jan | 5:10 p.m.–5:30 p.m.
Lana Brindley has been playing with technology since that summer in the 80s when she got eaten by a grue. She has been writing since she could hold a pencil, and is currently writing technical documentation for SUSE after spending many years hanging around in the OpenStack community and generally making a pest of herself. Lana enjoys going to technical conferences to talk about stuff that has been buzzing around in her brain for too long, and also to make sure she leaves the house from time to time. While she isn't generally a technical pessimist, she read _IBM and the Holocaust_ recently, and has been looking at technical development with a wary eye ever since. She's fairly certain the future robot overlords will be benign. Mostly.
We all age. Some more gracefully than others. Our documentation ages, too, and sadly it's not always glamorous. Docs that start out as a thing of sartorial elegance can, many years and patches later, become tired and sad and badly in need of retirement. Sometimes the content is so out of date and incorrect, the format so anachronistic that it needs to be consigned to a recycling bin. But not all documentation should be euthanised. Sometimes, it just needs a face lift. Agile documentation is, by its very nature, piecemeal, which can make it difficult to maintain a large documentation suite, and almost impossible to perform a large project that requires meticulous planning and extensive testing. In this talk I'll cover situations that require a complete documentation overhaul, how to go about planning for and undertaking such a project, and (perhaps most importantly) how to sell a Waterfall-style project to your Agile Product Owner.