Your SlideShare is downloading. ×
Adapting to Agile Development for Software 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

Adapting to Agile Development for Software Documentation

161
views

Published on

Speaker presentation at WritersUA West 2014 Conference, Palm Springs, CA on March 4, 2014. …

Speaker presentation at WritersUA West 2014 Conference, Palm Springs, CA on March 4, 2014.

Presenter: Zohra Mutabanna

A case study on how documentation teams successfully adapt to an Agile (Scrum) process. Includes ideas and strategies for those who may be transitioning or already working in an Agile environment.

Published in: Software, Technology, Business

0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
161
On Slideshare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
3
Comments
0
Likes
0
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
  • Source of Images: With permission from Andrew Kazreyvich, http://www.Codevanced.net.
  • Image Source: Adapted from http://neurontesting.blogspot.com/
  • Image Source: http://www.mprti.com
  • Image Source: http://www.nci.co.uk
  • Source: http://www.solutionsiq.com
  • Transcript

    • 1. Zohra Mutabanna zmutabanna@courion.com Lead Technical Writer WritersUA West 2014 Conference March 4, 2014 Palm Springs, CA
    • 2.  The Agile Manifesto  The Scrum Process  Documenting in Scrum  Benefits and Challenges in Scrum  Strategies for Success
    • 3.  Scrum Roles  Scrum Artefacts and Workflow
    • 4.  Track tasks in Sprint Backlog  Begin when functionality is available  Create iterative content in a sprint  Attend weekly Scrum of Scrums with Scrum Masters Writer
    • 5. Tasks in Sprint Backlog
    • 6.  An empowered team player  Members collaborate through a backlog and daily scrum  Documentation priority follows PBI priority  Delta tracked across sprints
    • 7.  Scrum format may vary from one team to another  Documentation adapts to Scrum like a development team  Different deliverables for different teams  Minimal documentation may require more updates
    • 8.  Communicate, Connect, Collaborate ◦ Update Sprint Backlog with documentation tasks ◦ Proactively communicate documentation needs ◦ Leverage technology for distributed teams ◦ Attend meetings – as needed
    • 9.  Managing Time as a Shared Resource ◦ Track your overhead - ideally 20% for non-sprint activities ◦ Be flexible about Scrum practices and processes
    • 10.  Rethink Deliverables: ◦ Context Sensitive Help ◦ Videos ◦ eBooks  Transition from Static to Dynamic Authoring with: ◦ Structured Authoring ◦ Single Sourcing ◦ Reusability
    • 11.  The Agile Manifesto: Kazreyvich, Andrew. The Agile Manifesto . Web. 1 March 2014. <http://www.codevanced.net>  The Scrum Process: Adapted. Web. 1 March 2014.  Benefits: Web. 1 March 2014 <http://www.mprti.com>  Challenges: Web. 1 March 2014 <http://www.nci.co.uk>  Scrum Cloud: Web. 1 March 2014. <http://www.solutionsiq.com>