In Search of… An Agile Documentation Process

Even though we didn’t follow any of the practices that have become synonymous with Agile, we were still being Agile…

Don’t Do Agile… Be Agile! Being quick, resourceful, and adaptable What does “being” Agile mean… Moving quickly and lightly Thinking quickly and clearly

Our Challenge Keeping requirements current for the development team Maintaining synchronization between documentation and software Having concurrent delivery of software, online help, and manuals

What results did we achieve? Reduced design time Fewer bug reported Faster development time No waiting for documentation Manuals and software ready at same time Less refactoring of code Fewer integration problems

User Focus The Secret? Communication Teamwork

The original process has been modified and refined through six more years of experience The process is not dependant on any specific tool or product Follow the “ KIS & KIL ” principle… keep it simple and keep it light

The impact of writing things down

The Model

GUI-driven process based on user stories Delivers just enough information just in time to be necessary and sufficient for getting the job done Involves both marketing and engineering Provides a strong framework for communication Generates as many or as few artifacts as necessary

Of techniques and Tools