Surviving Agile: A Case Study in Failure (and Success)
Agile software development may work well for design teams, but the impacts to the documentation teams are usually not considered when changing methodologies. Our company moved half of its products from a 9-month Waterfall release cycle to a 1- to 4-month Agile cycle overnight and expected us to adapt our process and planning. If your company is about to make (or has already made) the switch, learn from our mistakes (and a few best practices).
In this session, you will learn:
- the challenges our team experienced moving from Waterfall to Agile development methodologies
- our successes and failures as we tried, on multiple iterations, to work within Agile
- where we are now as we continue to try to improve our processes
- how Agile design and doc would work together in a perfect world
Andy Watson has over 15 years experience in Technical Communication in the telecommunications industry. He project manages the documentation for seven programs implemented with Agile. He has a BS in Computer Science from Texas A&M University and MS in Information Design and Communication from Southern Polytechnic State University.