1. Creating User Documentation in an Agile World
Jane Wilson

2. You say Scrum, I say Agile…
“Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.”
Adapt and Iterate (sprints)–
Work continuously with customer
Agile Manifesto
Scrum Ceremonies:
Planning
Daily Scrum Meetings
Sprint Reiews
Retrospectives
Transparency and Simplicity
Self-organizing Teams – create and point stories
Fail Fast

4. (this space intentionally left blank)

6. Scrum Team Where does the Technical Writer fit in? Scrum Master
Product
Owner
Team Members

7. Technical Writer Specialized member of the scrum team
Works with the PO and team to create doc stories
Participates in scrum stand-up meetings
Participates in planning and demo meetings
Maintains content plan

8. Friendly Reminder… Writers cover multiple scrum teams!
Teams need to be mindful of meeting times and frequency, story load.

9. Stories or Tasks?

10. Documentation Stories
Documentation user stories should reflect all work done by a Technical Writer as part of the scrum team.

11. Documentation Stories
Stories to document functionality being created by the development team.
Stories relating to documentation-specific work. (These stories are much less common.)

12. Documentation Stories
The big question – Story Points?

13. Documentation Stories
Tips:
Divide work into multiple stories (not a single catch-all story)
Link a doc story to the related dev features 

14. Review Time Quality Process (InfoDev)
Review for completeness and flow (scrum team)
End-to-end review and sign-off by PMs

17. Your mileage may vary...

18. Participate in scrum ceremonies!
Planning
Daily Stand-ups
Sprint Review
Retrospective

19. , Learn about Agile,

20. Handy Phrases….
Don’t be afraid to throw the “B” word!

21. Handy Phrases….
“That’s not really Agile…”

22. Jane Wilson jwilson.stc@gmail.com jane.wilson@ge.com