Documentation thrives in an agile methodology

700 views

Published on

This presentation shows agile newbies how to successfully incorporate accurate and complete documentation into the agile process.

Published in: Business, Technology
  • Be the first to comment

Documentation thrives in an agile methodology

  1. 1. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.DOCUMENTATION THRIVES IN AN AGILEMETHODOLOGYBY JENNA MOORE, ASSOCIATE FELLOWSENIOR TECHNICAL WRITER, SAS INSTITUTE
  2. 2. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.AGENDA• Who should be here• Define the issues• Review the options• Review Agile development• Fit the doc into the agile cycle• Learn the benefits• Learn to implement it fully
  3. 3. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.TRADITIONALPROJECTWATERFALL Documentation worktraditionally falls here
  4. 4. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.LAST MINUTEOUT OF TIME!
  5. 5. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.WHAT IS AGILE? TERMINOLOGYStory, User Story: is a software system requirement. Usually they are shortand consists of several sentences.Iteration: is a time period (2 weeks to 2 months) in which the teamimplements and delivers a set of functionality (user stories).Scrum, or Stand Up: is a status check where the team meets and shareprogress, impediments and short term assignments. Usually three questionsasked: "What did you do yesterday?", "What will you do today?" and "What isblocking progress?"Backlog: is a list of user stories, bugs, and features that need to becompleted.Theme: is a collection of user stories.
  6. 6. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.HOW DO THEY FIT?
  7. 7. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.BENEFIT 1 JUST IN TIME DOCUMENTATION• Write it during the devstory• Technical review whilefresh• Saves time later
  8. 8. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.BENEFIT 2 HIGHER ACCURACY• Review during story• Functionality andintent are fresh
  9. 9. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.BENEFIT 3BETTER SCHEDULE MANAGEMENT FOR DOC AND DEVTEAMS• Doc and dev in sync• Editors involved earlier• Long end-cycleprocesses are shortenedor eliminated
  10. 10. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.IMPLEMENTATION1SCRUMSAttend daily orweekly scrums
  11. 11. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.IMPLEMENTATION2ITERATION BACKLOGAdddocumentation tothe iterationbacklog
  12. 12. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.IMPLEMENTATION3PRODUCT BACKLOGAdd documentation only steps to the product backlog orappropriate iteration.• Technical Review• Edit• Production stepsFinaldocumentationsteps
  13. 13. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.REVIEWGetting Started• Release planning meetings• Get your stories into the backlog• Decide with development how topursue the documentation-concurrent, one iteration back, orotherKeeping Up• Assign ownership of documentationstories• Attend daily or weekly scrums• Improve processes as you go
  14. 14. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.Q&A
  15. 15. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.JENNA MOOREASSOCIATE FELLOWSlideshare.net: jcpmooreLinkedIn: www.linkedin.com/in/techwriting

×