SlideShare a Scribd company logo
1 of 14
Documentation Review: Get It Done! 1.About Today’s Session2.“Tops and Flops” Game3.“Version Madness” Game4.“Open vs. Structure Collaboration” Game5.Take-Away and Demo: The TPS Reports Case
What are we talking about today?  Today’s session is about: Technical documentation review Optimal collaboration Why is it important? Agilewords research shows optimal collaboration leads to better documentation review: Qualitatively: Less frustrations, better review Quantitatively: Docs get reviewed 50% faster  What are our objectives today? Share experiences and learn about the way we collaborate Experience collaboration best practices Have fun !
Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
Share your reviewing success story: Why is it your favorite?  How did you communicate with people?  Who coordinated feedback? How? Share your worst time waster during review: I have to chase people around for feedback via email I get feedback in many different forms and formats I spend too much time keeping track of all the versions circulating
Results from workgroups session:
Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
Part 1: Writers gives reviewers their own version  Dear Writer, you have two minutes to distribute this document to the reviewers and Subject Matter Experts of your group, and collect their feedback. Part 2: Writers share a central version  Dear Writer, you have two minutes to have your team review this document.
Results from workgroups session:
Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
Part I: Open collaboration a-la-wiki Dear documentation team and stakeholders, here is a document, feel free to take one, edit and comment, and have it reviewed in two minutes. Part II: Structured collaboration workflow Dear Manager, please mobilize your writers and reviewers and have this document reviewed in two minutes.
Results from workgroups session:
Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
Tops and Flops Doc review is at its best when the team is engaged Effective doc review can only be achieved with the right tools Doc review requires a clear process  Open vs. Structured Collaboration Reviewing docs requires a structured workflow and defined roles Open collaboration works better for crowd sourcing than project mgt Version Madness Collaboration fails when people work on separate medium Reviewing time is reduced by working on a central document
Leave your contact details in the following form and get a Free Edition of Agilewords Subscribe to Agilewords RSS feeds at http://blog.agilewords.com Follow us at http://twitter.com/Agilewords

More Related Content

Similar to Agilewords Document Collaboration - Get It Done

Being an Agile Tester
Being an Agile TesterBeing an Agile Tester
Being an Agile Testerliorf
 
Technical Communication for Unity Developers
Technical Communication for Unity DevelopersTechnical Communication for Unity Developers
Technical Communication for Unity DevelopersUnity Technologies
 
Lotus Quickr Demonstration
Lotus Quickr DemonstrationLotus Quickr Demonstration
Lotus Quickr DemonstrationChris Sparshott
 
Lessons from the Trenches of Learning Game Design
Lessons from the Trenches of Learning Game DesignLessons from the Trenches of Learning Game Design
Lessons from the Trenches of Learning Game DesignSharon Boller
 
Microsoft Teams for Leaders
Microsoft Teams for LeadersMicrosoft Teams for Leaders
Microsoft Teams for LeadersRupert Squires
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshopDavid Gracia
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshopDavid Gracia
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshopDavid Gracia
 
How to talk to your developers
How to talk to your developersHow to talk to your developers
How to talk to your developersSpin42
 
Online interactions using Liberating Structures
Online interactions using Liberating StructuresOnline interactions using Liberating Structures
Online interactions using Liberating StructuresFrederik Vannieuwenhuyse
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshopDavid Gracia
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshopDavid Gracia
 
Conflict in Agile Teams - Sydney Agile & Scrum user group Meetup
Conflict in Agile Teams - Sydney Agile & Scrum user group MeetupConflict in Agile Teams - Sydney Agile & Scrum user group Meetup
Conflict in Agile Teams - Sydney Agile & Scrum user group MeetupJeremie Benazra
 
Imagine that you are a public health nurse, and you and your colle
Imagine that you are a public health nurse, and you and your colleImagine that you are a public health nurse, and you and your colle
Imagine that you are a public health nurse, and you and your colleLizbethQuinonez813
 

Similar to Agilewords Document Collaboration - Get It Done (20)

Testers in an agile world
Testers in an agile worldTesters in an agile world
Testers in an agile world
 
Being an Agile Tester
Being an Agile TesterBeing an Agile Tester
Being an Agile Tester
 
Introduction to MeetingSphere for group problem solving
Introduction to MeetingSphere for group problem solvingIntroduction to MeetingSphere for group problem solving
Introduction to MeetingSphere for group problem solving
 
Introduction to MeetingSphere for group problem solving
Introduction to MeetingSphere for group problem solvingIntroduction to MeetingSphere for group problem solving
Introduction to MeetingSphere for group problem solving
 
Technical Communication for Unity Developers
Technical Communication for Unity DevelopersTechnical Communication for Unity Developers
Technical Communication for Unity Developers
 
Lotus Quickr Demonstration
Lotus Quickr DemonstrationLotus Quickr Demonstration
Lotus Quickr Demonstration
 
Lessons from the Trenches of Learning Game Design
Lessons from the Trenches of Learning Game DesignLessons from the Trenches of Learning Game Design
Lessons from the Trenches of Learning Game Design
 
Microsoft Teams for Leaders
Microsoft Teams for LeadersMicrosoft Teams for Leaders
Microsoft Teams for Leaders
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshop
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshop
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshop
 
How productive are your meetings with Microsoft Lync?
How productive are your meetings with Microsoft Lync?How productive are your meetings with Microsoft Lync?
How productive are your meetings with Microsoft Lync?
 
How to talk to your developers
How to talk to your developersHow to talk to your developers
How to talk to your developers
 
Online interactions using Liberating Structures
Online interactions using Liberating StructuresOnline interactions using Liberating Structures
Online interactions using Liberating Structures
 
Scrum à la Pablo (English)
Scrum à la Pablo (English)Scrum à la Pablo (English)
Scrum à la Pablo (English)
 
402 w2
402 w2402 w2
402 w2
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshop
 
Collaborative tool workshop
Collaborative tool workshopCollaborative tool workshop
Collaborative tool workshop
 
Conflict in Agile Teams - Sydney Agile & Scrum user group Meetup
Conflict in Agile Teams - Sydney Agile & Scrum user group MeetupConflict in Agile Teams - Sydney Agile & Scrum user group Meetup
Conflict in Agile Teams - Sydney Agile & Scrum user group Meetup
 
Imagine that you are a public health nurse, and you and your colle
Imagine that you are a public health nurse, and you and your colleImagine that you are a public health nurse, and you and your colle
Imagine that you are a public health nurse, and you and your colle
 

Agilewords Document Collaboration - Get It Done

  • 1. Documentation Review: Get It Done! 1.About Today’s Session2.“Tops and Flops” Game3.“Version Madness” Game4.“Open vs. Structure Collaboration” Game5.Take-Away and Demo: The TPS Reports Case
  • 2. What are we talking about today? Today’s session is about: Technical documentation review Optimal collaboration Why is it important? Agilewords research shows optimal collaboration leads to better documentation review: Qualitatively: Less frustrations, better review Quantitatively: Docs get reviewed 50% faster What are our objectives today? Share experiences and learn about the way we collaborate Experience collaboration best practices Have fun !
  • 3. Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
  • 4. Share your reviewing success story: Why is it your favorite? How did you communicate with people? Who coordinated feedback? How? Share your worst time waster during review: I have to chase people around for feedback via email I get feedback in many different forms and formats I spend too much time keeping track of all the versions circulating
  • 6. Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
  • 7. Part 1: Writers gives reviewers their own version Dear Writer, you have two minutes to distribute this document to the reviewers and Subject Matter Experts of your group, and collect their feedback. Part 2: Writers share a central version Dear Writer, you have two minutes to have your team review this document.
  • 9. Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
  • 10. Part I: Open collaboration a-la-wiki Dear documentation team and stakeholders, here is a document, feel free to take one, edit and comment, and have it reviewed in two minutes. Part II: Structured collaboration workflow Dear Manager, please mobilize your writers and reviewers and have this document reviewed in two minutes.
  • 12. Documentation Review: Get It Done! 1.About Today’s Session 2.“Tops and Flops” Game 3.“Version Madness” Game 4.“Open vs. Structured Collaboration” Game 5.Take-Away and Demo: The TPS Reports Case
  • 13. Tops and Flops Doc review is at its best when the team is engaged Effective doc review can only be achieved with the right tools Doc review requires a clear process Open vs. Structured Collaboration Reviewing docs requires a structured workflow and defined roles Open collaboration works better for crowd sourcing than project mgt Version Madness Collaboration fails when people work on separate medium Reviewing time is reduced by working on a central document
  • 14. Leave your contact details in the following form and get a Free Edition of Agilewords Subscribe to Agilewords RSS feeds at http://blog.agilewords.com Follow us at http://twitter.com/Agilewords