Successfully reported this slideshow.
Your SlideShare is downloading. ×

The Next Decade (of Agile Software Development)

Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Ad
Loading in …3
×

Check these out next

1 of 110 Ad

The Next Decade (of Agile Software Development)

Download to read offline

(As presented at Agile Testing Days, October 2013, Potsdam DE) Two years ago, I looked back at over a decade of progress in the community of Agile software development practitioners. I talked about some alarming trends in our attitudes, our practices and what we teach, but also described the ways in which I believe we’d really advanced the art of software development. Now, I explore a more interesting question: Where do we go from here? Those alarming trends haven’t all gone away. In fact, some have got worse, and I want to highlight some of things that I think we really need to stop before they destroy all the credibility we’ve built. Of course, the picture is not bleak: we’ve helped make software development better for so many people, and I’ll talk about where I’d like us to focus our considerable energy to help make the coming decade even better for our field and the lives of our colleagues.

(As presented at Agile Testing Days, October 2013, Potsdam DE) Two years ago, I looked back at over a decade of progress in the community of Agile software development practitioners. I talked about some alarming trends in our attitudes, our practices and what we teach, but also described the ways in which I believe we’d really advanced the art of software development. Now, I explore a more interesting question: Where do we go from here? Those alarming trends haven’t all gone away. In fact, some have got worse, and I want to highlight some of things that I think we really need to stop before they destroy all the credibility we’ve built. Of course, the picture is not bleak: we’ve helped make software development better for so many people, and I’ll talk about where I’d like us to focus our considerable energy to help make the coming decade even better for our field and the lives of our colleagues.

Advertisement
Advertisement

More Related Content

Similar to The Next Decade (of Agile Software Development) (20)

Recently uploaded (20)

Advertisement

The Next Decade (of Agile Software Development)

  1. 1. The Next Decade Where do we go from here?
  2. 2. Watch the video at http://link.jbrains.ca/1aJLeBd (4 minutes)
  3. 3. “Why aren’t we rich yet?” Kent Beck
  4. 4. “Why aren’t we rich yet?” Kent Beck ...in 2003
  5. 5. We fancy “Agile” as a mindset...
  6. 6. I don’t think our message is quite getting through... http://blog.brodzinski.com/2010/03/you-must-be-agile.html
  7. 7. We use awesome Zen-like phrases that we understand, but the rest of the world doesn’t
  8. 8. Bill Caputo
  9. 9. Ron Jeffries: “We Tried Baseball and It Didn’t Work” http://xprogramming.com/articles/jatbaseball/
  10. 10. Community: “They’re Just Rules” http://c2.com/cgi/wiki?TheyreJustRules
  11. 11. Energised Work / Gus Power http://link.jbrains.ca/Tghs02
  12. 12. Where does all this leave us?
  13. 13. worked my ass off to transform the way we all build software
  14. 14. Chip and Dan Heath Switch: How to Change Things When Change is Hard
  15. 15. James Shore: “Études for Excellence” http://www.jamesshore.com/Blog/Etudes-for-Excellence.html
  16. 16. “Why aren’t we rich yet?”
  17. 17. David Anderson Diana Larsen Olav Maassen Chris Matts Ron Jeffries Chet Hendrickson David Snowden Aslak Hellesøy Eric Ries Uncle Bob
  18. 18. We’ve scripted the critical moves, but we’ve failed to convey the vision
  19. 19. “They” have no real reason to change, so “they” work to rule...
  20. 20. Steven Baker http://stevenrbaker.com/ A year ago, this guy moved in down the street from me...
  21. 21. Heiman, Tuleja, Miller: “The New Strategic Selling” This model helps me “sell” practices to people
  22. 22. ...so while we believe this...
  23. 23. Simple, clear purpose and principles give rise to complex, intelligent behavior. Complex rules and regulations give rise to simple, stupid behavior. Dee Hock, Birth of the Chaordic Age
  24. 24. ...we get this...
  25. 25. People appear to really want to buy rules, processes, templates...
  26. 26. Training companies are taking advantage of this trend...
  27. 27. There, there...
  28. 28. What happened?!
  29. 29. I don’t think this attitude has helped much over the years...
  30. 30. Steve McConnell: “Code Complete” “Grandma’s Ham”, page 43
  31. 31. Watch the video at http://link.jbrains.ca/bob-newhart-stop-it (6 minutes)
  32. 32. Let’s look at our most well-advertised, popular practices
  33. 33. http://martinfowler.com/articles/itsNotJustStandingUp.html photo: Karthik Chandrasekarial
  34. 34. Travelogue Face Time 80% done
  35. 35. Now’s your chance to complain... get it out of your system.
  36. 36. What’s missing?
  37. 37. Risks!
  38. 38. Chapter 2, Risk Management is Product Management for Adults http://link.jbrains.ca/S2jyPY
  39. 39. These folks look like they’re “doing it right”!
  40. 40. A place to put those quick things that come to mind...
  41. 41. Liz Keogh, “Behavior-Driven Development” http://www.slideshare.net/lunivore/behavior-driven-development-11754474
  42. 42. How different are your Cucumber scenarios from this?
  43. 43. What’s missing?
  44. 44. Involving the Customer
  45. 45. Talking in Examples
  46. 46. Liz Keogh, “Behavior-Driven Development” http://www.slideshare.net/lunivore/behavior-driven-development-11754474
  47. 47. I still believe that this is a great place to start...
  48. 48. I need my story next!
  49. 49. What’s missing?
  50. 50. Negotiating scope: not “which stories?” but “how much of each story?”
  51. 51. Gus Power, “Extreme Pair Programming” http://energizedwork.com/weblog/2009/05/extreme-pair-programming
  52. 52. ;
  53. 53. What’s missing?
  54. 54. Arlo Belshee, “Promiscuous Pairing and Beginner’s Mind” http://link.jbrains.ca/V4bQsW
  55. 55. Watch the video at http://link.jbrains.ca/angela-harms-excerpt (1 minute)
  56. 56. http://www.industrialxp.org/retrospectives.html
  57. 57. What’s missing?
  58. 58. As always, trust remains the principal ingredient...
  59. 59. It all seems so simple...
  60. 60. I’m sorry, Dave... but I can’t let you change that.
  61. 61. What’s missing?
  62. 62. I know it’s very old advice, but it remains just as true today.
  63. 63. Uh... yeah... I’m going to need you to go ahead and get 12 more points done this sprint...
  64. 64. What’s missing?
  65. 65. Negotiating scope: not “which stories?” but “how much of each story?”
  66. 66. Even Jenkins can’t integrate all those features at once!
  67. 67. What’s missing?
  68. 68. James Shore: “Continuous Integration is an Attitude, Not a Tool” http://link.jbrains.ca/TePNKE
  69. 69. http://link.jbrains.ca/R8rBxx
  70. 70. What’s missing?
  71. 71. How do your Scrum Masters answer this question? Office Space. http://www.imdb.com/title/tt0151804/
  72. 72. What’s in the way?
  73. 73. Ego
  74. 74. What do you think practitioners miss when they try to follow our advice?
  75. 75. I like to focus on these ideas both when I teach and when I practice...
  76. 76. Josh Gough http://tech.groups.yahoo.com/group/scrumdevelopment/message/48820
  77. 77. http://link.jbrains.ca/product-sashimi
  78. 78. The “Contract, then Expand” technique http://www.jbrains.ca/permalink/three-steps-to-a-useful-minimal-feature
  79. 79. http://www.jbrains.ca/permalink/becoming-an-accomplished-softwaredesigner
  80. 80. The Five Dysfunctions of a Team http://link.jbrains.ca/T7HCPC
  81. 81. J. B. Rainsberger, “Integrated Tests Are a Scam: Part 1” http://blog.thecodewhisperer.com/2010/10/16/integrated-tests-are-a-scam/
  82. 82. Converging towards a common design standard http://link.jbrains.ca/TlE3JH
  83. 83. Vi ses i Stockholm! http://www.legacycoderetreat.org http://www.coderetreat.org
  84. 84. Will you join me?
  85. 85. me@jbrains.ca The Next Decade More mindful practice http://link.jbrains.ca/next-decade

×