3. Even though we didn’t follow any of the practices that have become synonymous with Agile, we were still being Agile…
4. Don’t Do Agile… Be Agile! Being quick, resourceful, and adaptable What does “being” Agile mean… Moving quickly and lightly Thinking quickly and clearly
5. Our Challenge Keeping requirements current for the development team Maintaining synchronization between documentation and software Having concurrent delivery of software, online help, and manuals
6. 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
8. 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
12. 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
How many of you are here hoping to learn something about documentation? And how many are here just for the networking? And how many are here because I put the word “Agile” in the topic title? So… before we raise the curtain, let’s set the scene: - It’s 2001, half way through the Dot.com crash - Extreme Programming is starting to make noise - The Agile Manifesto is being written - Development is being done at “Internet” speed