Successfully reported this slideshow.
We use your LinkedIn profile and activity data to personalize ads and to show you more relevant ads. You can change your ad preferences anytime.

On the importance of done


Published on

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

Published in: Technology

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> </li></ul>