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.

Agility ≠ Speed

231 views

Published on

Keynote present at Agile Tour Vienna (2018-10-06)

Velocity. Sprints. More points, more speed. An obsession with speed often overtakes the core values of agile software development. It’s not just development of software; it’s development of working software. Sprints are not about sprinting; they’re about sustainable pace. Time to market is less important than time in market. Full-stack development is normally a statement about technology, but it also applies to individuals and interactions. The full stack touches both the code and the world outside the code, and with that view comes responsibility and pause for thought. Doing the wrong thing smarter is not smart. The point of a team is its group intelligence not its numbers. Is scaling up the challenge, or is scaling down the real challenge? The distraction and misuse of speed, velocity, point-based systems, time, team size, scale, etc. is not the accelerant of agile development. Agility lies in experimentation, responsiveness and team intelligence.

Published in: Software
  • Be the first to comment

  • Be the first to like this

Agility ≠ Speed

  1. 1. Agility ≠ Speed @KevlinHenney
  2. 2. agile, adjective ▪ able to move quickly and easily Concise Oxford English Dictionary
  3. 3. agile, adjective ▪ able to move quickly Concise Oxford English Dictionary
  4. 4. I have made this [letter] longer than usual because I have not had time to make it shorter. Blaise Pascal
  5. 5. Je n'ai fait celle-ci plus longue que parce que je n'ai pas eu le loisir de la faire plus courte. Blaise Pascal
  6. 6. I have made this [letter] longer than usual because I have not had time to make it shorter. Blaise Pascal
  7. 7. time
  8. 8. I spent a lot of money on booze, birds and fast cars. The rest I just squandered. George Best
  9. 9. https://twitter.com/KevlinHenney/status/922803893167427584
  10. 10. Move fast and break things
  11. 11. speed
  12. 12. velocity
  13. 13. v = vx + vy
  14. 14. v = |v|
  15. 15. v = s'
  16. 16. v = ds dt __
  17. 17. v = s t _
  18. 18. t s
  19. 19. t s
  20. 20. t s [T] [T]
  21. 21. utilisation
  22. 22. quality of estimation
  23. 23. Observe Gather information from a range of sources Orient Understand where you're at and where you want to be Decide Develop a plan for action Act Carry out the plan Boyd's OODA Loop
  24. 24. Decide Develop a plan for action Act Carry out the plan Observe Gather information from a range of sources Orient Understand where you're at and where you want to be Boyd's OODA Loop
  25. 25. Plan Establish hypothesis, goal or work tasks Do Carry out the plan Study Review what has been done against plan (a.k.a. Check) Act Revise approach or artefacts based on study Deming/Shewhart Cycle
  26. 26. The design process is an iterative one. Andy Kinslow
  27. 27. You have to finish things — that's what you learn from, you learn by finishing things. Neil Gaiman
  28. 28. code tests scripts
  29. 29. codified knowledge
  30. 30. knowledge acquisition
  31. 31. learning
  32. 32. communication
  33. 33. social negotiation
  34. 34. model of participation
  35. 35. The biggest advantage of autonomously working teams is risk reduction through increased group intelligence. Kevlin Henney https://jaxlondon.com/blog/java-core-languages/the-error-of-our-ways-kevlin-henney/
  36. 36. There’s little correlation between a group’s collective intelligence and the IQs of its individual members. But if a group includes more women, its collective intelligence rises. "What Makes a Team Smarter? More Women" Anita Woolley & Thomas W Malone http://hbr.org/2011/06/defend-your-research-what-makes-a-team-smarter-more-women/
  37. 37. People from diverse backgrounds might actually alter the behavior of a group’s social majority in ways that lead to improved and more accurate group thinking. "Why Diverse Teams Are Smarter" David Rock & Heidi Grant https://hbr.org/2016/11/why-diverse-teams-are-smarter
  38. 38. Diverse teams are more likely to constantly reexamine facts and remain objective. "Why Diverse Teams Are Smarter" David Rock & Heidi Grant https://hbr.org/2016/11/why-diverse-teams-are-smarter
  39. 39. The four conditions that characterize wise crowds: diversity of opinion, independence, decentralization, and aggregation.
  40. 40. speed
  41. 41. size
  42. 42. scale
  43. 43. Software development does not have economies of scale. Development has diseconomies of scale. Allan Kelly Beyond Projects http://www.slideshare.net/allankellynet/no-prokects-beyond-projects-refreshed-version
  44. 44. completion time for one person 𝑡 = 𝑡1
  45. 45. division of labour 𝑡 = 𝑡1 𝑛
  46. 46. 𝑡 = 𝑡1 1 − 𝑝 𝑛 − 1 𝑛 portion in parallel Amdahl's law
  47. 47. communication overhead (typical) connections (worst case) 𝑡 = 𝑡1 1 − 𝑝 𝑛 − 1 𝑛 + 𝑘 𝑛 𝑛 − 1 2
  48. 48. 𝑡 = 𝑡1 1 − 𝑝 𝑛 − 1 𝑛 + 𝑘 𝑛 𝑛 − 1 2t n
  49. 49. The Facebook iOS app has over 18,000 Objective-C classes, and in a single week 429 people contributing to it. Facebook's code quality problem Graham King http://www.darkcoding.net/software/facebooks-code-quality-problem/
  50. 50. For every activity there is a certain appropriate scale.
  51. 51. Your customers do not buy your software by the line. David Evans
  52. 52. We may therefore picture the process of form-making as the action of a series of subsystems, all interlinked, yet sufficiently free of one another to adjust independently in a feasible amount of time. Christopher Alexander Notes on the Synthesis of Form
  53. 53. It works, because the cycles of correction and recorrection, which occur during adaptation, are restricted to one subsystem at a time. Christopher Alexander Notes on the Synthesis of Form
  54. 54. The basic thesis [...] is that organizations which design systems [...] are constrained to produce designs which are copies of the communication structures of these organizations. Melvin Conway How Do Committees Invent?
  55. 55. We have seen that this fact has important implications for the management of system design. [...] A design effort should be organized according to the need for communication. Melvin Conway How Do Committees Invent?
  56. 56. thrustdrag liftgravity
  57. 57. designdebt practiceconway
  58. 58. F = ma
  59. 59. µονόλιθος
  60. 60. Why do cars have brakes?
  61. 61. Cars have brakes so you can slow down.
  62. 62. Cars have brakes so you can go fast.

×