Adapting to Agile Development for Software
Documentation
Zohra [email protected] Technical Writer
WritersUA West 2014 ConferenceMarch 4, 2014
Palm Springs, CA
The Agile Manifesto The Scrum Process Documenting in Scrum Benefits and Challenges in Scrum Strategies for Success
Agenda
The Agile Manifesto
The Scrum Process
Scrum Roles
Scrum Artefacts and Workflow
Documenting in Scrum 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
Product Backlog Item (PBI) Definition
Tasks in Sprint Backlog
Task Attributes
BenefitsAn empowered team player
Members collaborate through a backlog and daily scrum
Documentation priority follows PBI priority
Delta tracked across sprints
Challenges
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
Communicate, Connect, Collaborate
◦ Update Sprint Backlog with documentation tasks
◦ Proactively communicate documentation needs
◦ Leverage technology for distributed teams
◦ Attend meetings – as needed
Strategies for Success
Managing Time as a Shared Resource
◦ Track your overhead - ideally 20% for non-sprint activities
◦ Be flexible about Scrum practices and processes
Strategies for Success
Rethink Deliverables:
◦ Context Sensitive Help
◦ Videos
◦ eBooks
Transition from Static to Dynamic Authoring with:
◦ Structured Authoring
◦ Single Sourcing
◦ Reusability
Strategies for Success
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>
Citations
Recommended
