Agile environments can be both challenging and rewarding places for technical writers. Appropriate documentation is essential to the efficient production, testing, and acceptance of software. One way to be Agile with documentation to evolve it in parallel with the system development — delivering user stories, use cases, UI designs, system tests, manuals, and even online help — with just enough detail, and just in time. Come and explore some ways that you can be Agile with your documentation. This presentation isn't intended to provide a silver bullet solution, but it may give you some ideas beyond those famous (infamous?) 3x5 index cards.

1. Being Agile with Documentation or… how technical communicators can survive (and thrive) on Agile Projects

2. Who am I, and why am I here?

3. What do you know about Agile…

4. So… What is Agile?

11. But… what does it all mean? Don’t just do Agile… Be Agile

12. Now… what does that mean for technical writers?

14. The biggest difference is the Mindset

15. Integration with the Development Team

16. No Prescription for Documentation – so we will have to write our own

18. “Typical” Agile Requirements Documentation Create a new article for publishing Publish an article to the website Delete a published article

21. Documentation and Coding should proceed in Parallel

22. Focus on Users and their Needs

23. Develop Design Patterns for your Documentation

24. Sources of Design Patterns

25. Design for Change

27. Questions? Discussion?

28. Thank You [email_address]