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.

getting agile Final

660 views

Published on

Published in: Technology, Design
  • Be the first to comment

  • Be the first to like this

getting agile Final

  1. 1. Getting Agile or How I learned to stop worrying and love the index cards CIPS Business Analysis SIG Event JOHN JOHNSTON ThoughtWorks
  2. 2. <ul><li>40 </li></ul>
  3. 3. <ul><li>4 </li></ul>
  4. 4. <ul><li>1 </li></ul>
  5. 5. <ul><li>100 </li></ul>
  6. 6. <ul><li>I have not always been as I appear to you now </li></ul>
  7. 8. waterfall and structured methods Web developer COBOL 12 years in IT 5 years in college
  8. 9. August 2005
  9. 10. August 2005 First exposure to agile
  10. 11. What’s changed?
  11. 12. I thought my job was to write specifications
  12. 13. Now it’s the delivery of working software into production
  13. 14. for real end users
  14. 15. Eh?
  15. 16. a change of emphasis
  16. 17. delivering business value
  17. 18. <ul><li>agile makes this easier </li></ul>
  18. 19. <ul><li>business analysis </li></ul>
  19. 21. Business Analysis
  20. 22. Business Analysis
  21. 23. delivering business value
  22. 24. not fetishising requirements on paper
  23. 25. solving business problems
  24. 26. may involve software
  25. 27. just a means to an end
  26. 28. do what you need to do to deliver
  27. 29. implementation over documentation
  28. 30. <ul><li>agile focuses on outcomes </li></ul><ul><li>not artefacts </li></ul>
  29. 31. <ul><li>1 of 4 </li></ul><ul><li>agile makes it easier to focus on </li></ul><ul><li>business value </li></ul>
  30. 32. <ul><li>getting started </li></ul>
  31. 33. <ul><li>i saw a lot of these </li></ul>
  32. 34. and people doing this
  33. 35. Where the wild things are working with stories
  34. 36. <ul><li>BAs write stories </li></ul>
  35. 37. <ul><li>developers write code </li></ul>
  36. 38. <ul><li>Therefore stories </li></ul><ul><li>are requirements , right? </li></ul>
  37. 39. WRONG!
  38. 40. (a bit) WRONG
  39. 41. (a bit) WRONG (sometimes)
  40. 42. (a bit) WRONG (sometimes) It Depends!
  41. 43. i am a consultant 
  42. 45. a unit of planning not documentation
  43. 46. agile mindset
  44. 47. implementation over documentation
  45. 48. road-map over end-state
  46. 49. <ul><li>Ron Jeffries - 3 Cs </li></ul>http://www.xprogramming.com/xpmag/expCardConversationConfirmation.htm
  47. 51. card conversation confirmation
  48. 52. <ul><li>stories have a lifecycle </li></ul>
  49. 53. become documentation at the end
  50. 54. stories are a roadmap towards implementation
  51. 55. MartinFowler.com: RollerSkateImplementation
  52. 56. <ul><li>2 of 4 </li></ul><ul><li>stories as a unit of planning helped me understand the agile mindset </li></ul>
  53. 57. <ul><li>good practice </li></ul>
  54. 58. INVEST
  55. 59. I N V E S T Independent
  56. 60. I N V E S T Negotiable
  57. 61. I N V E S T Valuable
  58. 62. I N V E S T Estimate-able
  59. 63. I N V E S T Small
  60. 64. I N V E S T Testable
  61. 65. <ul><li>effective stories define </li></ul><ul><li>user , goal and business benefit </li></ul>
  62. 66. <ul><li>As a [user] </li></ul><ul><li>I want [to do something] </li></ul><ul><li>So that [I achieve a valuable goal] </li></ul>
  63. 67. tell me what , not how
  64. 68. keep stories business focussed and implementation neutral
  65. 69. find out why that story matters
  66. 70. <ul><li>challenges </li></ul>
  67. 71. <ul><li>“ All stories should deliver business value” </li></ul>
  68. 72. <ul><li>releases deliver business value </li></ul>
  69. 73. <ul><li>“ we must do the login story first” </li></ul>
  70. 74. new dimensions
  71. 75. user centred design
  72. 76. customer proxy & user champion
  73. 77. contextual inquiry
  74. 78. “ you can observe a lot, just by watching” Yogi Berra
  75. 79. Joe – Contract Engineer <ul><li>Day to day: Supervises the construction of the new plant. Works 8 days, followed by 4 days off in a remote location. </li></ul><ul><li>TIM Usage: Grudgingly submits time reports on a weekly basis </li></ul><ul><li>Priorities: Finishing the plant construction on time and safely. Focused on his fellow engineers. </li></ul><ul><li>Needs: A simple data entry system. The computer Joe uses is shared by all site engineers. He hasn’t spent a lot of time working with computers, and doesn’t want to ‘waste his time’ learning. </li></ul>Joe is a contract engineer assisting in the construction of a new plant. He’s worked with the company for 30 years. Joe was semi-retired but had some necessary expertise; he was convinced to come back and oversee this project. “ I just want to finish this job so I can get back to building my retirement cottage.”
  76. 80. low fidelity prototyping http://www.alistapart.com/articles/paperprototyping
  77. 81. <ul><li>usability testing </li></ul>
  78. 82. <ul><li>usability testing </li></ul>“ on 10 cents a day” Steve Krug http://sensible.com Don’t Make Me Think
  79. 83. <ul><li>visual models </li></ul>
  80. 84. “ We’re agreed then?”
  81. 85. “ Ah!”
  82. 86. “ We are agreed then”
  83. 87. <ul><li>common understanding </li></ul>
  84. 88. <ul><li>3 of 4 </li></ul><ul><li>Now I consider how I can visually share what I’ve learned so I can get feedback </li></ul>
  85. 89. <ul><li>and finally </li></ul>
  86. 90. <ul><li>one french egg </li></ul>
  87. 92. just un oeuf
  88. 93. just enough
  89. 94. <ul><li>doing just enough </li></ul>
  90. 95. <ul><li>breadth then depth </li></ul>
  91. 96. <ul><li>work at the lower levels challenge assumptions made higher up </li></ul>
  92. 97. how much is just enough?
  93. 98. what do we need to know next that we don’t know at the moment?
  94. 99. 4 important points to remember <ul><li>Agile makes it easier to focus on business value </li></ul><ul><li>Understanding stories as a unit of planning helped me understand the agile mindset </li></ul><ul><li>Now I consider how I can visually share what I’ve learned so I can get feedback </li></ul>
  95. 100. 4 of 4 getting agile took good coaching and trying it out
  96. 101. Resources <ul><li>Books </li></ul><ul><ul><li>“ User Stories Applied” Mike Cohn </li></ul></ul><ul><ul><li>“ Lean Software Development” Mary & Tom Poppendieck </li></ul></ul><ul><ul><li>“ Don’t Make Me Think” Steve Krug </li></ul></ul><ul><li>Blogs </li></ul><ul><ul><li>Marc Mcneill - http://www.dancingmango.com/blog/ </li></ul></ul><ul><ul><li>Jeff Patton - http://www.agileproductdesign.com/blog/ </li></ul></ul><ul><ul><li>ThoughtBlogs – http://blogs.thoughtworks.com/ </li></ul></ul><ul><ul><li>Me! - http:// cardsahoy.wordpress.com / </li></ul></ul><ul><li>Websites </li></ul><ul><ul><li>Ask Tog (Interaction Design) - http://www.asktog.com/ </li></ul></ul><ul><ul><li>Jakob Nielsen (Web Usability) - http://www.useit.com/ </li></ul></ul>
  97. 102. Photo Credits <ul><li>The following images are used with thanks under the Creative Commons licence; </li></ul><ul><li>Important Documents from jon.t’s photostream </li></ul><ul><ul><li>http://flickr.com/photos/titusjon/1216912767/ </li></ul></ul><ul><li>Kermit from pictureclub_2000’s photo stream </li></ul><ul><li>http://flickr.com/photos/andy-germany/2047566335/ </li></ul><ul><li>Money from Tracey Olson’s photo stream </li></ul><ul><ul><li>http://flickr.com/photos/tracy_olson/61056391/ </li></ul></ul><ul><li>Butterfly from Dystopian_Optimist’s photostream </li></ul><ul><ul><li>http://www.flickr.com/photos/dystopian/37004247/ </li></ul></ul><ul><li>Rollerskates from the Flooz’s photostream </li></ul><ul><ul><li>http://flickr.com/photos/flooznyc/839704353/ </li></ul></ul><ul><li>Coach from dsanden’s photostream </li></ul><ul><ul><li>http://www.flickr.com/photos/daphid/148844023/ </li></ul></ul>
  98. 103. what questions do you have?

×