Your SlideShare is downloading. ×
Being Agile With Documentation
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Being Agile With Documentation

6,578
views

Published on

Agile environments can be both challenging and rewarding places for technical writers. Appropriate documentation is essential to the efficient production, testing, and acceptance of software. One …

Agile environments can be both challenging and rewarding places for technical writers. Appropriate documentation is essential to the efficient production, testing, and acceptance of software. One way to be Agile with documentation to evolve it in parallel with the system development — delivering user stories, use cases, UI designs, system tests, manuals, and even online help — with just enough detail, and just in time. Come and explore some ways that you can be Agile with your documentation. This presentation isn't intended to provide a silver bullet solution, but it may give you some ideas beyond those famous (infamous?) 3x5 index cards.

Published in: Technology, Business

1 Comment
9 Likes
Statistics
Notes
No Downloads
Views
Total Views
6,578
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
171
Comments
1
Likes
9
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Feel free to ask questions as we are going along
  • Transcript

    • 1. Being Agile with Documentation or… how technical communicators can survive (and thrive) on Agile Projects
    • 2. Who am I, and why am I here?
    • 3. What do you know about Agile…
    • 4. So… What is Agile?
    • 5. Individuals and Interactions
      • over processes and tools
    • 6. Working Software
      • over comprehensive documentation
    • 7. Customer Collaboration
      • over contract negotiation
    • 8. Responding to Change
      • over following a plan
    • 9. Sustainable Pace
      • Continuous attention to technical excellence and good design
    • 10. Simplicity
      • Self-Organizing Teams Reflection and Improvement
    • 11. But… what does it all mean? Don’t just do Agile… Be Agile
    • 12. Now… what does that mean for technical writers?
    • 13.
      • writing and editing
      • document design
      • using language effectively to please or persuade (rhetoric)
      • problem solving
      • collaboration and teamwork
      • interpersonal and oral communication
      • facility with, and ability to learn, technologies
      Adapt your Core Competencies
    • 14. The biggest difference is the Mindset
    • 15. Integration with the Development Team
    • 16. No Prescription for Documentation – so we will have to write our own
    • 17. Whiteboards…
      • and Markers… and Cameras… oh my!
    • 18. “Typical” Agile Requirements Documentation Create a new article for publishing Publish an article to the website Delete a published article
    • 19.  
    • 20. KIS and KIL
      • and a dollop of Horse Sense
    • 21. Documentation and Coding should proceed in Parallel
    • 22. Focus on Users and their Needs
    • 23. Develop Design Patterns for your Documentation
    • 24. Sources of Design Patterns
    • 25. Design for Change
    • 26. Some resources to check out
      • Manifesto for Agile Software Development www.agilemanifesto.org
      • Scott Ambler – Agile Modeling website http:// www.agilemodeling.com
      • WritersUS – Agile Technical Documentation www.writersua.com
    • 27. Questions? Discussion?
    • 28. Thank You [email_address]

    ×