1. How Writers Can Thrive in Agile Gavin Austin 2013 Agile Conference 16/05/27 104522027 徐逢均 修訂

2. O utline Problems Solutions Daily best practices Team best practices Benefits 2

3. P ROBLEM 3

4. Problems 4 Terminology Product Owner? Scrum Master? Daily Scrum? Meetings Sprint planning, Sprint review, Sprint retrospective, and Daily “stand up”. Time Spend more time on Agile and less time writing documentation.

5. Problems 5 Product Specifications product managers they no longer needed to write specifications for their products Estimates provide hourly, daily, or weekly estimates for their documentation tasks Time Tracking Tools track the accuracy of estimates generated additional work

6. Problems 6 Multiple Teams writers worked for multiple product teams and were considered a “shared service.” Team Loyalties Writers found it difficult to prioritize tasks. Context Switching Switching tasks, teams, priorities, or business requirements

7. Problems 7 Fiction writers produced documentation for nonexisting products based on evolving sketches, prototypes, business cases, or hearsay

8. S OLUTION 8

9. Solutions Encourage Patience No one expected a perfect transition. Provide Training Every new employee in product development is required to attend Agile training. Learn to Adapt It’s easier to adapt to an Agile environment when writers review its benefits instead of its challenges. 9

10. Solutions Build Templates Writing, updating, and organizing documentation plans Standardize Tracking Tools Working in an Agile environment became easier for writers Pad Estimates Give your team estimates that are a little longer than what you think is necessary to complete a task. 10

11. Solutions Provide Clear Definitions Hire More Writers Switching to Agile immediately exposed the need to hire more writers to ensure quality documentation Learn to Adapt It’s easier to adapt to an Agile environment when writers review its benefits instead of its challenges. Extend Documentation Deadlines Writing in an Agile environment is less stressful when documentation deadlines are extended slightly beyond the product development deadline. 11

12. D AILY BEST PRACTICES 12

13. DAILY BEST PRACTICES Ask Questions Email Your Team Write Fiction Revise Fiction Skip Meetings Schedule Office Hours Organize Documentation“Blitzes” Write Bottom-Up as well as Top-Down Learn What to Ignore 13

14. T EAM BEST PRACTICES 14

15. TEAM BEST PRACTICES Volunteer Be Wrong Speak Up Barter Self Organize Be a Shared Service Claim the Last Line of Defense 15

16. B ENEFITS 16

17. B ENEFITS Personable Environment People get to know who they’re working with. Clearer Communication Team members meet daily and are encouraged to ask questions and voice concerns. Fixed Deadlines People can plan their lives outside of work (and finally take that vacation!) without wondering if a work schedule will interfere. 17

18. B ENEFITS Writers Have More Impact Writers have more impact because they’re considered an equal member of a scrum team that’s working together to complete a product. Writers Are More Visible Writers participate in most of the same meetings as their teammates and their daily, weekly, and monthly tasks are discussed and posted for everyone to see. 18

19. B ENEFITS Learn What to Expect Writers work with a team of various personalities, processes, and time frames in which to complete tasks. Retrospectives Solve Problems Writers notice positive results from retrospective meetings Self Determining Writers like the idea of determining what it is they need to do to complete tasks instead of relying on management to point them in the right direction. 19

20. B ENEFITS Team Spirit Writers share in the collective successes and failures of their teams Sense of Ownership Writers sense that they have ownership and influence over a product because their feedback is considered as valuable as their teammates’. Features Are Less Complex Writers notice that Agile removes unnecessary complexities from products Know Who Does What Writers learn in planning meetings which developers and quality engineers are responsible for completing specific tasks 20