The Whole Team Approach to Agile Development How

  • Slides: 12
Download presentation
The Whole Team Approach to Agile Development: How it Affects User Assistance Alyssa Fox

The Whole Team Approach to Agile Development: How it Affects User Assistance Alyssa Fox @afox 98 21 January 2016

The Old Way of Doing Scrum • Disparate visions • Dev estimates only Development

The Old Way of Doing Scrum • Disparate visions • Dev estimates only Development Flickr: Michele Massetani • Separate responsibilities QE ID • Tasks divided among sprints

Done vs. Done

Done vs. Done

The New Way of Doing Scrum • Shared vision • Dev, QE, and ID

The New Way of Doing Scrum • Shared vision • Dev, QE, and ID estimates • Shared responsibilities Flickr: Lawrence Sinclair • Tasks for all areas in same sprint

Not Done vs. Done

Not Done vs. Done

flickr: freepik. com

flickr: freepik. com

High Quality User Assistance • UI strings written correctly the first time • More

High Quality User Assistance • UI strings written correctly the first time • More thorough documentation reviews • Better usability of product through usability testing • Less documentation to write around UI issues • More content about tasks, scenarios, workflows

New Role • Help define acceptance criteria. • Include ID estimates in planning. •

New Role • Help define acceptance criteria. • Include ID estimates in planning. • Perform UI reviews and usability tests. • Volunteer to run test cases. flickr: victoriabernal • Participate in backlog grooming.

Swarming flickr: kosare “It’s better to have 80% of the features 100% done, instead

Swarming flickr: kosare “It’s better to have 80% of the features 100% done, instead of having 100% of the features 80% done. ” ~Oleksi Derkatch

Zero Bug Tolerance Flickr: Lawrence Sinclair

Zero Bug Tolerance Flickr: Lawrence Sinclair

Benefits of Whole Team Approach • Improves teamwork • Increases quality • Reduces lower-value

Benefits of Whole Team Approach • Improves teamwork • Increases quality • Reduces lower-value documentation • Gets UI strings and workflows right the first time • Allows more time for targeted user assistance • Improves understanding of users, so improves assistance when addressing their pain points

References • “Are You a Whole Team? ” http: //www. infoq. com/articles/whole-team • “Play

References • “Are You a Whole Team? ” http: //www. infoq. com/articles/whole-team • “Play Soccer, not Football: How to Foster a Whole-Team Approach by Thinking in Activities Rather than Roles, ” Matt Philip. http: //mattphilip. files. wordpress. com/2011/03/play_soccer_not_footballagile-and-beyond. pdf • Agile Testing: A Practical Guide for Testers and Agile Teams, Lisa Crispin and Janet Gregory. (http: //www. amazon. com/Agile-Testing-Practical-Guide -Testers/dp/0321534468/ref=sr_1_1? ie=UTF 8&qid=1391386425&sr=81&keywords=lisa+crispin) • Innolution Product Owner Training, Kenny Rubin. http: //innolution. com/training/product-owner-training • “How Swarming Helps Agile Teams to Deliver, ” Ben Linders. http: //www. infoq. com/news/2013/02/swarming-agile-teams-deliver • “The Whole Team Approach to Software Quality, ” Ed Spire. https: //dl. dropboxusercontent. com/u/55047326/WHOLE%20 team%20 appr oach%20 to%20 quality. pptx • “The Whole Team Approach in Practice, ” Lisa Crispin. http: //lisacrispin. com/2011/04/26/the-whole-team-approach-in-practice/