On the importance of Done <ul><li>Ezra Gildesgame, Rob Purdie </li></ul>20 25 aug 13:30
Who are we? <ul><li>Ezra Gildesgame, GVS </li></ul><ul><ul><ul><li>@ezrabg </li></ul></ul></ul><ul><li>Rob Purdie, The Eco...
Why are we here? <ul><li>To share how three teams at The Economist online, in three locations, all working on the same cod...
Session outline <ul><li>Background / preamble (10 mins) </li></ul><ul><li>What Done means (10 mins) </li></ul><ul><li>Why ...
Background / preamble <ul><li>We've been doing Scrum for 2 years now </li></ul><ul><li>Started when we decided to move to ...
Background / preamble <ul><li>Incrementally means bit-by-bit, released as soon as bits are Done </li></ul><ul><li>Iterativ...
Background / preamble <ul><li>We've taken this approach in order to benefit from Drupal sooner </li></ul><ul><li>To maximi...
Background / preamble <ul><li>The important things to grok here are: </li></ul><ul><ul><ul><li>Small bits </li></ul></ul><...
Background / preamble <ul><li>Small bits: </li></ul><ul><ul><ul><li>We deliver increments of working software that can be ...
Background / preamble <ul><li>Benefit / ROI: </li></ul><ul><ul><ul><li>Increments of software are implemented and delivere...
Background / preamble <ul><li>Done: </li></ul><ul><ul><ul><li>Increments of software have value only IF and WHEN they are ...
Background / preamble <ul><li>In this session we want to talk about: </li></ul><ul><ul><ul><li>What Done means </li></ul><...
What Done means <ul><li>There is no concept of partial completion in Scrum </li></ul><ul><li>Work is either 0% complete or...
What Done means <ul><li>Given this, and given we work in short, timeboxed iterations, we deliver &quot;thin vertical slice...
What Done means <ul><li>It's important to have a shared definition of Done, especially when working on projects involving ...
What Done means <ul><li>For us, a story is Done when it has been: </li></ul><ul><ul><ul><li>Implemented </li></ul></ul></u...
What Done means <ul><li>Implemented: </li></ul><ul><ul><ul><li>Code developed </li></ul></ul></ul><ul><ul><ul><li>Peer rev...
What Done means <ul><li>Verified: </li></ul><ul><ul><ul><li>Human (manual) tests performed; passing </li></ul></ul></ul>
What Done means <ul><li>Validated: </li></ul><ul><ul><ul><li>Accepted by the Product Owner; feature can be used as intende...
Why Done is important <ul><li>Focusing on Done increases productivity </li></ul><ul><li>Small bits Done and delivered mean...
Why Done is important <ul><li>Done provides ability to stop even successful projects and still benefit </li></ul><ul><li>T...
How we get stuff Done <ul><li>We use Bazaar for source control  </li></ul><ul><li>We use Launchpad to manage the workflow ...
How we get stuff Done <ul><li>We use Hudson and EC2 to create &quot;human test instances&quot; for each story </li></ul><u...
How we get stuff Done
Thank you! / Questions <ul><li>? </li></ul>
<ul><li>http://cph2010.drupal.org/node/add/eval/15068 </li></ul>
Upcoming SlideShare
Loading in …5
×

On the importance of done

1,732 views
1,686 views

Published on

A presentation on what "done" means at The Economist online

Published in: Technology
1 Comment
4 Likes
Statistics
Notes
No Downloads
Views
Total views
1,732
On SlideShare
0
From Embeds
0
Number of Embeds
2
Actions
Shares
0
Downloads
31
Comments
1
Likes
4
Embeds 0
No embeds

No notes for slide
  • Stranger in a Strange Land : Grok means to understand so thoroughly that the observer becomes a part of the observed—to merge, blend, intermarry, lose identity in group experience.
  • We prioritize our work based on perceived ROI
  • How we get stuff DONE and release it every week, coordinating the efforts of three teams in three locations running different sprint schedules using Bazaar and Launchpad
  • Verified: Human (manual) tests performed; passing (i.e. story meets &amp;quot;how to demo&amp;quot; description)
  • Validated: Accepted by the Product Owner (according to &amp;quot;how to demo&amp;quot; description); feature can be used as intended Feature is ready to be released into the live environment (i.e. no further development work required)
  • On the importance of done

    1. 1. On the importance of Done <ul><li>Ezra Gildesgame, Rob Purdie </li></ul>20 25 aug 13:30
    2. 2. Who are we? <ul><li>Ezra Gildesgame, GVS </li></ul><ul><ul><ul><li>@ezrabg </li></ul></ul></ul><ul><li>Rob Purdie, The Economist online </li></ul><ul><ul><ul><li>@robpurdie </li></ul></ul></ul>
    3. 3. Why are we here? <ul><li>To share how three teams at The Economist online, in three locations, all working on the same codebase, make incremental improvements to the site, released every Tuesday </li></ul>
    4. 4. Session outline <ul><li>Background / preamble (10 mins) </li></ul><ul><li>What Done means (10 mins) </li></ul><ul><li>Why Done is important; the value of Done (10 mins) </li></ul><ul><li>How we get stuff Done (15 mins) </li></ul><ul><li>Questions (15 mins) </li></ul>
    5. 5. Background / preamble <ul><li>We've been doing Scrum for 2 years now </li></ul><ul><li>Started when we decided to move to Drupal </li></ul><ul><li>We are moving to Drupal incrementally and iteratively </li></ul>
    6. 6. Background / preamble <ul><li>Incrementally means bit-by-bit, released as soon as bits are Done </li></ul><ul><li>Iteratively means improving each bit as it is implemented </li></ul>
    7. 7. Background / preamble <ul><li>We've taken this approach in order to benefit from Drupal sooner </li></ul><ul><li>To maximize benefit-sooner, we always implement /release the increment with the highest business value / ROI next </li></ul><ul><li>This approach has introduced short-term complexity – but it's been worth it </li></ul>
    8. 8. Background / preamble <ul><li>The important things to grok here are: </li></ul><ul><ul><ul><li>Small bits </li></ul></ul></ul><ul><ul><ul><li>Business value / ROI </li></ul></ul></ul><ul><ul><ul><li>Done </li></ul></ul></ul>
    9. 9. Background / preamble <ul><li>Small bits: </li></ul><ul><ul><ul><li>We deliver increments of working software that can be used by our customers at the end of every timeboxed iteration </li></ul></ul></ul>
    10. 10. Background / preamble <ul><li>Benefit / ROI: </li></ul><ul><ul><ul><li>Increments of software are implemented and delivered in order of business value </li></ul></ul></ul>
    11. 11. Background / preamble <ul><li>Done: </li></ul><ul><ul><ul><li>Increments of software have value only IF and WHEN they are Done </li></ul></ul></ul>
    12. 12. Background / preamble <ul><li>In this session we want to talk about: </li></ul><ul><ul><ul><li>What Done means </li></ul></ul></ul><ul><ul><ul><li>Why Done is important / the value of Done </li></ul></ul></ul><ul><ul><ul><li>How we get stuff Done </li></ul></ul></ul>
    13. 13. What Done means <ul><li>There is no concept of partial completion in Scrum </li></ul><ul><li>Work is either 0% complete or 100% complete </li></ul><ul><li>Done means potentially shippable </li></ul><ul><li>Done means usable by the customer </li></ul>
    14. 14. What Done means <ul><li>Given this, and given we work in short, timeboxed iterations, we deliver &quot;thin vertical slices&quot; of functionality </li></ul><ul><li>These are (usually) specified as user stories </li></ul><ul><li>User stories have corresponding acceptance criteria </li></ul>
    15. 15. What Done means <ul><li>It's important to have a shared definition of Done, especially when working on projects involving multiple teams </li></ul>
    16. 16. What Done means <ul><li>For us, a story is Done when it has been: </li></ul><ul><ul><ul><li>Implemented </li></ul></ul></ul><ul><ul><ul><li>Verified </li></ul></ul></ul><ul><ul><ul><li>Validated </li></ul></ul></ul>
    17. 17. What Done means <ul><li>Implemented: </li></ul><ul><ul><ul><li>Code developed </li></ul></ul></ul><ul><ul><ul><li>Peer reviewed and refactored </li></ul></ul></ul><ul><ul><ul><li>Tested </li></ul></ul></ul><ul><ul><ul><li>Bug free – all known bugs resolved </li></ul></ul></ul><ul><ul><ul><li>Documented </li></ul></ul></ul>
    18. 18. What Done means <ul><li>Verified: </li></ul><ul><ul><ul><li>Human (manual) tests performed; passing </li></ul></ul></ul>
    19. 19. What Done means <ul><li>Validated: </li></ul><ul><ul><ul><li>Accepted by the Product Owner; feature can be used as intended </li></ul></ul></ul><ul><ul><ul><li>Feature is ready to be released into the live environment </li></ul></ul></ul>
    20. 20. Why Done is important <ul><li>Focusing on Done increases productivity </li></ul><ul><li>Small bits Done and delivered means business value sooner </li></ul><ul><li>Small bits Done results in more feedback sooner </li></ul>
    21. 21. Why Done is important <ul><li>Done provides ability to stop even successful projects and still benefit </li></ul><ul><li>There are accounting benefits too! </li></ul>
    22. 22. How we get stuff Done <ul><li>We use Bazaar for source control </li></ul><ul><li>We use Launchpad to manage the workflow around branching and merging </li></ul><ul><li>We create &quot;feature branches&quot; for each story </li></ul>
    23. 23. How we get stuff Done <ul><li>We use Hudson and EC2 to create &quot;human test instances&quot; for each story </li></ul><ul><li>We have adopted core committer model for merge proposal approvals </li></ul>
    24. 24. How we get stuff Done
    25. 25. Thank you! / Questions <ul><li>? </li></ul>
    26. 26. <ul><li>http://cph2010.drupal.org/node/add/eval/15068 </li></ul>

    ×