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.

Empathy from Agility

825 views

Published on

A big part of the Agile manifesto and history of it coming together has to do with the need and desire to respond to change, adaptability being achieved by replacing project phases with short iterations, a strong quality foundation enabling teams to change direction and adjust to customer feedback.

We've come a long way and now realise that making software softer isn't enough, software development is complex and systemic. This talk is a reflection on the frontiers of agility, at its outer bounds. It's about further softening the edges and improving the effectiveness of software by truly empathising with those whose lives it touches.

Published in: Software
  • Be the first to comment

Empathy from Agility

  1. 1. Empathyfrom Agility marcelloduarte @_md
  2. 2. https://en.wikipedia.org/wiki/Vrindavan#/media/File:Madanmohan_Mandir_Vrindavan.JPG @_md
  3. 3. softwareisaboutpeople
  4. 4. it’speoplewho useit { @_md
  5. 5. it’speoplewho useit developit { @_md
  6. 6. it’speoplewho useit developit orderit { @_md
  7. 7. it’speoplewho { useit developit orderit acceptit ... @_md
  8. 8. Muchsoftwareisdesignedandbuilt withlittleconsiderationforhowitwill beusedandhowitcanbestsupportthe workitsuserswillbedoing. “ —Constantin&Lockwood,1999
  9. 9. empathy |ˈɛmpəәθi| the ability to understand and share the feelings of another. noun [ mass noun ]
  10. 10. empathyisatypeofattention
  11. 11. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  12. 12. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer through early and continuous delivery of valuable software. Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage. Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale. Business people and developers must work together daily throughout the project. Build projects around motivated individuals. Give them the environment and support they need, and trust them to get the job done.
  13. 13. The most efficient and effective method of conveying information to and within a development team is face-to-face conversation. Working software is the primary measure of progress. Agile processes promote sustainable development. The sponsors, developers, and users should be able to maintain a constant pace indefinitely. Continuous attention to technical excellence and good design enhances agility. Simplicity--the art of maximizing the amount of work not done--is essential. The best architectures, requirements, and designs emerge from self-organizing teams. At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behavior accordingly.
  14. 14. valuelisten
  15. 15. agile { value adapt deliver,adapt&repeat changeenablingquality @_md
  16. 16. @_md
  17. 17. https://www.flickr.com/photos/samhames/4699360569 @_md
  18. 18. productbacklogsand
 expectationsaroundrequirements @_md
  19. 19. mostagileprojectsusescrum “54% said they use Scrum in combination with other practices, while 42% reported exclusive use of Scrum.” — The 2015 State of Scrum Report
  20. 20. scrum {inspect adapt transparency @_md
  21. 21. xp {tdd refactoring continuousintegration @_md
  22. 22. agilepracticeshashelpedmakesoftwaresofter @_md
  23. 23. scrum { @_md
  24. 24. scrum { commitment @_md
  25. 25. scrum { commitment estimation @_md
  26. 26. scrum { commitment estimation acceptancecriteria @_md
  27. 27. scrum { commitment estimation acceptancecriteria independentstories @_md
  28. 28. scrum { commitment estimation acceptancecriteria independentstories productownership @_md
  29. 29. scrum { commitment estimation acceptancecriteria independentstories productownership engineeringpractice @_md
  30. 30. valuesmotivateprocesses, thenweforgetthevalues... @_md
  31. 31. managedagility coachedagility ownedagility @_md
  32. 32. managed
 agility { @_md
  33. 33. managed
 agility {wiifm,formaltraining @_md
  34. 34. managed
 agility {wiifm,formaltraining newprocesses @_md
  35. 35. managed
 agility {wiifm,formaltraining newprocesses champions @_md
  36. 36. managed
 agility {wiifm,formaltraining newprocesses champions “justtelluswhattodo” @_md
  37. 37. coached
 agility { @_md
  38. 38. coached
 agility {show,don’ttell @_md
  39. 39. coached
 agility {show,don’ttell focusonconfidence @_md
  40. 40. coached
 agility {show,don’ttell focusonconfidence principlesoverprocesses @_md
  41. 41. coached
 agility {show,don’ttell focusonconfidence principlesoverprocesses askinggoodquestions @_md
  42. 42. owned
 agility { @_md
  43. 43. owned
 agility {empathy @_md
  44. 44. owned
 agility {empathy challengeprocesses @_md
  45. 45. owned
 agility {empathy challengeprocesses contextualise @_md
  46. 46. owned
 agility {empathy challengeprocesses contextualise systemic @_md
  47. 47. softwaredevelopmentdrivingforces @_md
  48. 48. softwaredevelopmentdrivingforces @_md
  49. 49. softwaredevelopmentdrivingforces I WANT EVERYTHING I WANT IT CHEAP! I WANT IT NOW! @_md
  50. 50. softwaredevelopmentdrivingforces WE NEED DOCKER SYNTAX SUGAAAR! WE NEED DDD
  51. 51. softwaredevelopmentdrivingforces SUSTAINABILITY MAINTAINABILITY WE NEED QUALITY @_md
  52. 52. empathy @_md
  53. 53. usersusers @_md
  54. 54. empathy customers users sales developers maintainers @_md
  55. 55. usecases @_md
  56. 56. releasemission usecases { @_md
  57. 57. developersempathytowardsbusiness
  58. 58. https://www.flickr.com/photos/hdptcar/2530986852
  59. 59. usecases releasemission {thebusiness:techratio @_md
  60. 60. businessempathytowardsdevelopers
  61. 61. releasemission thebusiness:techratiousecases { @_md
  62. 62. releasemission thebusiness:techratiousecases { @_md
  63. 63. releasemission thebusiness:techratio 3:1 usecases { @_md
  64. 64. releasemission thebusiness:techratio TDD/DDD/BDD,butno££ usecases { @_md
  65. 65. releasemission thebusiness:techratio TDD/DDD/BDD,butno££ usecases { ModellingbyexampleBusinessworkshops @_md
  66. 66. challengeprocesses @_md
  67. 67. isitpossibletodeliversoftwarewithoutestimation?
  68. 68. challengethevalue estimation requirements planning acceptancecriteria lessonslearned @_md
  69. 69. estimation==costidentificationtechnique @_md
  70. 70. estimation==costidentificationtechnique forecast empirical PERT historical #noestimates cycletime planningpoker @_md
  71. 71. requirements @_md
  72. 72. @_md
  73. 73. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer! through early and continuous delivery! of valuable software. @_md
  74. 74. Principles behind the Agile Manifesto We follow these principles: Our highest priority is to satisfy the customer! through early and continuous delivery! of valuable software. @_md
  75. 75. @_md
  76. 76. products @_md
  77. 77. products experiments @_md
  78. 78. requirements @_md
  79. 79. requirements hypothesis @_md
  80. 80. Examples:Eliminatingofficewaste andunnecessarycosts @_md
  81. 81. usinghypothesisinsteadofuserstories @_md[Jeffrey L. Taylor, 2011]
  82. 82. Hypothesis I believe [target market]! will [behave some way]! because [this reason]! UserStory In order to [some business goal]! As a [user]! I’d like [behaviour]! @_md
  83. 83. Motivation:Eliminatingofficewaste andunnecessarycosts Experiment:Getemployeestodotheirowntravelrequest @_md
  84. 84. Motivation:Eliminatingofficewaste andunnecessarycosts Experiment:Getemployeestodotheirowntravelrequest Ibelieveouremployeeswillbehappytodotheirowntraveland accommodationarrangementswithinbudgetbecausetheywillhave morefreedomofchoiceandwinloyaltypointswiththeircards. @_md
  85. 85. measure! @_md
  86. 86. Test:
 -Chooseasubsetofemployees
 -Agreethebudgetwithrelevantstakeholders
 -Gatherfeedbackaftertheengagement @_md
  87. 87. empathise measure learn build @_md
  88. 88. bitstrips.com
  89. 89. requirements MoSCoW backlog WBS candidate queue justintime canonical RFPsexperiments @_md
  90. 90. contextualise @_md
  91. 91. contextualise Whatestimationapproaches? Howmuchrequirements? Howmuchplanning? Howmuchconversationoverfeatures? Whatrolesdoweneed? Whatprocessesandtoolscanweuse?{ @_md
  92. 92. agilityhasopenedupsoftwaredevelopment @_md
  93. 93. ithelpedmakesoftwaresofter @_md
  94. 94. butsoftwareisn’taboutcode @_md
  95. 95. ittouchespeople’slife @_md
  96. 96. there’sempathyinagile @_md
  97. 97. weforgetvaluesveryquickly @_md
  98. 98. let’sownouragility @_md
  99. 99. andconnectwiththerealneeds @_md
  100. 100. @_md marcelloduarte
  101. 101. thankyou! @_md

×