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

1. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
DOCUMENTATION THRIVES IN AN AGILE
METHODOLOGY
BY JENNA MOORE, ASSOCIATE FELLOW
SENIOR TECHNICAL WRITER, SAS INSTITUTE

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. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
TRADITIONAL
PROJECT
WATERFALL Documentation work
traditionally falls here

4. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
LAST MINUTE
OUT OF TIME!

5. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
WHAT IS AGILE? TERMINOLOGY
Story, User Story: is a software system requirement. Usually they are short
and consists of several sentences.
Iteration: is a time period (2 weeks to 2 months) in which the team
implements and delivers a set of functionality (user stories).
Scrum, or Stand Up: is a status check where the team meets and share
progress, impediments and short term assignments. Usually three questions
asked: "What did you do yesterday?", "What will you do today?" and "What is
blocking progress?"
Backlog: is a list of user stories, bugs, and features that need to be
completed.
Theme: is a collection of user stories.

6. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
HOW DO THEY FIT?

7. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
BENEFIT 1 JUST IN TIME DOCUMENTATION
• Write it during the dev
story
• Technical review while
fresh
• Saves time later

8. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
BENEFIT 2 HIGHER ACCURACY
• Review during story
• Functionality and
intent are fresh

9. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
BENEFIT 3
BETTER SCHEDULE MANAGEMENT FOR DOC AND DEV
TEAMS
• Doc and dev in sync
• Editors involved earlier
• Long end-cycle
processes are shortened
or eliminated

10. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
IMPLEMENTATION
1
SCRUMS
Attend daily or
weekly scrums

11. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
IMPLEMENTATION
2
ITERATION BACKLOG
Add
documentation to
the iteration
backlog

12. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
IMPLEMENTATION
3
PRODUCT BACKLOG
Add documentation only steps to the product backlog or
appropriate iteration.
• Technical Review
• Edit
• Production steps
Final
documentation
steps

13. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
REVIEW
Getting Started
• Release planning meetings
• Get your stories into the backlog
• Decide with development how to
pursue the documentation-
concurrent, one iteration back, or
other
Keeping Up
• Assign ownership of documentation
stories
• Attend daily or weekly scrums
• Improve processes as you go

14. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
Q&A

15. Copyr ight © 2013, SAS Institute Inc. All rights reser ved.
JENNA MOORE
ASSOCIATE FELLOW
Slideshare.net: jcpmoore
LinkedIn: www.linkedin.com/in/techwriting