Create and Maintain Scrum  Documentation Effectively Alexandre Boutin Lean & Agile Coach - Scrum Master and Practitioner  ...
Objectives <ul><li>What I would like you to take out? </li></ul><ul><li>An “agile way” to look at documentation </li></ul>...
SCRUM DOCUMENTATION
Documentation Challenges <ul><li>Time and cost consuming </li></ul><ul><ul><li>To create  </li></ul></ul><ul><ul><li>To ma...
Common Guidelines <ul><li>“ Travel Light” </li></ul>Autonomation Visibility
“Travel Light” <ul><li>Principles always to keep in mind when you are writing or maintaining a document </li></ul><ul><li>...
Autonomation <ul><li>Technical Solutions </li></ul><ul><ul><li>JavaDoc, Executable Requirements… </li></ul></ul><ul><li>Pi...
Visibility <ul><li>Collaborative Wiki </li></ul><ul><ul><li>Everybody can access and update any documents </li></ul></ul><...
Agile Process <ul><li>Include documentation activities in definition of “Done” (Story, Sprint or Release) </li></ul><ul><l...
Managing Existing Documentation
Documentation Values Customer? Needs? Documentation Reuse?
Value added for Customer? <ul><li>Focus on Customers  </li></ul><ul><ul><li>Customers are users </li></ul></ul><ul><ul><li...
Evaluate value for Customer <ul><li>Create your own list of customer values </li></ul><ul><li>Assign a weight for each val...
Needs for documents <ul><li>ASK: Who is reading/using it? </li></ul>
Evaluate needs for documents <ul><li>Pragmatic </li></ul><ul><ul><li>This person reads/uses the document and provides valu...
Reuse of Documents <ul><li>A document is written for a specific purpose at a specific time </li></ul><ul><li>Do not mainta...
Evaluate reuse of documents <ul><li>Reuse Metrics </li></ul><ul><ul><li>Average time between 2 versions </li></ul></ul><ul...
Evaluate Document Values <ul><li>Define acceptance criteria </li></ul><ul><ul><li>Document meets criteria </li></ul></ul><...
A SIMPLE PRACTICE
Simplification Meeting <ul><li>All team members in a room – 1 document template </li></ul><ul><li>Objectives </li></ul><ul...
THANK YOU Alexandre Boutin Lean & Agile Coach - Scrum Master and Practitioner  Founder AgileToYou [email_address]    : +3...
Upcoming SlideShare
Loading in …5
×

Create and Maintain Scrum (Alexandre Boutin)

993 views

Published on

In this series of talks, our panel of experts present real world examples that illustrate how Lean Production concepts are being successfully applied to software development. In particular to applications that have to meet the highest levels of safety and security.

Published in: Technology
0 Comments
1 Like
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
993
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
34
Comments
0
Likes
1
Embeds 0
No embeds

No notes for slide
  • Create and Maintain Scrum (Alexandre Boutin)

    1. 1. Create and Maintain Scrum Documentation Effectively Alexandre Boutin Lean & Agile Coach - Scrum Master and Practitioner “ Process Strategy for Yahoo International Engineering” [email_address]  : +33 (0)6 45 40 23 17
    2. 2. Objectives <ul><li>What I would like you to take out? </li></ul><ul><li>An “agile way” to look at documentation </li></ul><ul><li>Effective ideas and practices </li></ul>
    3. 3. SCRUM DOCUMENTATION
    4. 4. Documentation Challenges <ul><li>Time and cost consuming </li></ul><ul><ul><li>To create </li></ul></ul><ul><ul><li>To maintain (more!) </li></ul></ul><ul><li>Monitoring </li></ul><ul><ul><li>Versions </li></ul></ul><ul><ul><li>Accessibility </li></ul></ul><ul><li>Delivery </li></ul><ul><ul><li>Validation </li></ul></ul><ul><ul><li>Ownership </li></ul></ul>“ Don’t confuse documentation with understanding” Jim Highsmith
    5. 5. Common Guidelines <ul><li>“ Travel Light” </li></ul>Autonomation Visibility
    6. 6. “Travel Light” <ul><li>Principles always to keep in mind when you are writing or maintaining a document </li></ul><ul><li>K.I.S.S. </li></ul><ul><ul><li>Keep It Small & Simple </li></ul></ul><ul><ul><li>Simplicity, the art of maximizing the work you will not have to do </li></ul></ul><ul><li>Y.A.G.N.I. </li></ul><ul><ul><li>You aren’t Gonna Need It </li></ul></ul><ul><ul><li>Reviewing draft document is not WASTE! </li></ul></ul><ul><li>2 A4 pages </li></ul>
    7. 7. Autonomation <ul><li>Technical Solutions </li></ul><ul><ul><li>JavaDoc, Executable Requirements… </li></ul></ul><ul><li>Pictures </li></ul><ul><ul><li>“ A Picture is worth a thousand words” </li></ul></ul><ul><ul><li>Capture technical design on dashboard and include the photo in the document </li></ul></ul><ul><li>“ In” the product </li></ul><ul><ul><li>User Manual integrated in final product </li></ul></ul>
    8. 8. Visibility <ul><li>Collaborative Wiki </li></ul><ul><ul><li>Everybody can access and update any documents </li></ul></ul><ul><li>Dashboard </li></ul><ul><ul><li>Much more effective than traditional reporting </li></ul></ul><ul><li>Demo </li></ul><ul><ul><li>“ Working product” rather than “Documentation” </li></ul></ul>
    9. 9. Agile Process <ul><li>Include documentation activities in definition of “Done” (Story, Sprint or Release) </li></ul><ul><li>Consider documentation writer as a member of the team </li></ul><ul><li>Be as inventive as possible about ways to not produce documentation </li></ul>“ The primary goal is to deliver software; the secondary goal is to set up for the following game” Alistair Cockburn
    10. 10. Managing Existing Documentation
    11. 11. Documentation Values Customer? Needs? Documentation Reuse?
    12. 12. Value added for Customer? <ul><li>Focus on Customers </li></ul><ul><ul><li>Customers are users </li></ul></ul><ul><ul><li>Customers have money </li></ul></ul><ul><ul><li>Customers do promotion </li></ul></ul><ul><li>Put on customers glasses </li></ul><ul><ul><li>Evaluate how much each document adds value for customers </li></ul></ul>
    13. 13. Evaluate value for Customer <ul><li>Create your own list of customer values </li></ul><ul><li>Assign a weight for each value </li></ul><ul><li>Evaluate each document </li></ul>1 0 1 5% Deploy. 1 0 1 10% Stability 1 0 0 5% Scalability 1 0 0 5% Maint. 0 1 0 30% Usability 0 1 0 25% Certif. 20% 0 Document C … … 55% 0 Document B 15% 0 Document A 100% 20% Value Fit for Purpose
    14. 14. Needs for documents <ul><li>ASK: Who is reading/using it? </li></ul>
    15. 15. Evaluate needs for documents <ul><li>Pragmatic </li></ul><ul><ul><li>This person reads/uses the document and provides valuable feedback to the team </li></ul></ul><ul><li>Mandatory </li></ul><ul><ul><li>We have to deliver this document (by contract, according to the norm …) </li></ul></ul><ul><li>Disillusion </li></ul><ul><ul><li>Nobody is reading it, but you know, it’s in our quality process </li></ul></ul><ul><li>Foolish </li></ul><ul><ul><li>I wrote it and someone should read it for sure. I’m saying this for years now, will someone start doing things right in this company </li></ul></ul>Keep this document Ok, let’s try to reduce it to a minimum Stop doing it that way! I can help you, who is the quality director?
    16. 16. Reuse of Documents <ul><li>A document is written for a specific purpose at a specific time </li></ul><ul><li>Do not maintain all existing documentation just because it exists </li></ul><ul><li>Communicate rather than document </li></ul>
    17. 17. Evaluate reuse of documents <ul><li>Reuse Metrics </li></ul><ul><ul><li>Average time between 2 versions </li></ul></ul><ul><ul><li>Longevity of last version </li></ul></ul><ul><ul><li>Number of time the document is downloaded </li></ul></ul><ul><ul><li>Number of time the document is really used by the team </li></ul></ul><ul><ul><li>Number of time the document is reused by other teams </li></ul></ul><ul><li>At Yahoo, most documents are in a Wiki and employees accesses are collected </li></ul>
    18. 18. Evaluate Document Values <ul><li>Define acceptance criteria </li></ul><ul><ul><li>Document meets criteria </li></ul></ul><ul><ul><ul><li>Keep it </li></ul></ul></ul><ul><ul><ul><li>Simplify it </li></ul></ul></ul><ul><ul><ul><li>Evaluate alternative options for producing same information </li></ul></ul></ul><ul><ul><li>Document does not meet criteria </li></ul></ul><ul><ul><ul><li>Stop producing this document </li></ul></ul></ul><ul><ul><ul><li>Change your process </li></ul></ul></ul>
    19. 19. A SIMPLE PRACTICE
    20. 20. Simplification Meeting <ul><li>All team members in a room – 1 document template </li></ul><ul><li>Objectives </li></ul><ul><ul><li>Keep all sections </li></ul></ul><ul><ul><li>Remove all information that does not add value </li></ul></ul><ul><ul><ul><li>Duplication of information </li></ul></ul></ul><ul><ul><ul><li>Reduce long text </li></ul></ul></ul><ul><ul><li>Find better ways for producing information </li></ul></ul><ul><ul><ul><li>Screenshots or photos </li></ul></ul></ul><ul><li>Benefits </li></ul><ul><ul><li>Document is simpler </li></ul></ul><ul><ul><li>Team shares a common definition of the content </li></ul></ul><ul><ul><li>Later document production will be faster </li></ul></ul>
    21. 21. THANK YOU Alexandre Boutin Lean & Agile Coach - Scrum Master and Practitioner Founder AgileToYou [email_address]  : +33 (0)6 45 40 23 17

    ×