Transcript
Page 1: Adapting to Agile Development for Software Documentation

Adapting to Agile Development for Software

Documentation

Zohra [email protected] Technical Writer

WritersUA West 2014 ConferenceMarch 4, 2014

Palm Springs, CA

Page 2: Adapting to Agile Development for Software Documentation

The Agile Manifesto The Scrum Process Documenting in Scrum Benefits and Challenges in Scrum Strategies for Success

Agenda

Page 3: Adapting to Agile Development for Software Documentation
Page 4: Adapting to Agile Development for Software Documentation

The Agile Manifesto

Page 5: Adapting to Agile Development for Software Documentation

The Scrum Process

Scrum Roles

Scrum Artefacts and Workflow

Page 6: Adapting to Agile Development for Software Documentation

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

Page 7: Adapting to Agile Development for Software Documentation

Product Backlog Item (PBI) Definition

Page 8: Adapting to Agile Development for Software Documentation

Tasks in Sprint Backlog

Page 9: Adapting to Agile Development for Software Documentation

Task Attributes

Page 10: Adapting to Agile Development for Software Documentation

BenefitsAn empowered team player

Members collaborate through a backlog and daily scrum

Documentation priority follows PBI priority

Delta tracked across sprints

Page 11: Adapting to Agile Development for Software Documentation

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

Page 12: Adapting to Agile Development for Software Documentation

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

Page 13: Adapting to Agile Development for Software Documentation

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

Page 14: Adapting to Agile Development for Software Documentation

Rethink Deliverables:

◦ Context Sensitive Help

◦ Videos

◦ eBooks

Transition from Static to Dynamic Authoring with:

◦ Structured Authoring

◦ Single Sourcing

◦ Reusability

Strategies for Success

Page 15: Adapting to Agile Development for Software Documentation
Page 16: Adapting to Agile Development for Software Documentation

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