Upgrade to Pro — share decks privately, control downloads, hide ads and more …

Agile: A Challenge From the Trenches

Agile: A Challenge From the Trenches

We want to do our best work, and yet often cannot manage to do so. Circumstances conspire to impede progress, impair communications, and prevent success. Organizations want to know how much software will cost, and when it will be delivered. Developers want to be proud their work, and they want it to have meaning. However, my view from the trenches indicates that many times these desires are not fulfilled.

I teach classes in Object-Oriented Design, but the most common question I receive is not technical. Students want advice about how to do good work in organizations which profess to be Agile but seem to actively resist their efforts. Bright, committed, and highly motivated programmers feel prevented from acting in the best interests of their organizations. In the short-term they despair, and in the long, they depart.

Agile hasn't failed them, but we might be failing Agile. It's time to take an honest look at the problem and get practical about solutions.

Sandi Metz

April 01, 2016
Tweet

More Decks by Sandi Metz

Other Decks in Technology

Transcript

  1. Apr 2016
    @sandimetz
    Sandi Metz
    a
    Challenge
    from the
    Trenches

    View Slide

  2. @sandimetz Apr 2016

    View Slide

  3. @sandimetz Apr 2016

    View Slide

  4. @sandimetz Apr 2016

    View Slide

  5. @sandimetz Apr 2016

    View Slide

  6. @sandimetz Apr 2016

    View Slide

  7. @sandimetz Apr 2016
    Agile
    2016

    View Slide

  8. @sandimetz Apr 2016

    View Slide

  9. @sandimetz Apr 2016
    95%
    Some Agile

    View Slide

  10. @sandimetz Apr 2016
    43%
    Mostly Agile

    View Slide

  11. @sandimetz Apr 2016
    Wanted

    View Slide

  12. @sandimetz Apr 2016

    View Slide

  13. @sandimetz Apr 2016
    Got

    View Slide

  14. @sandimetz Apr 2016

    View Slide

  15. @sandimetz Apr 2016
    Accelerate product delivery
    Enhance ability to manage changing priorities
    Increase productivity
    Enhance software quality
    Enhance delivery predictability
    Improve business/IT alignment
    Improve project visibility
    Reduce project risk
    Improve team morale
    Improve engineering discipline
    Reduce project cost
    Increase software maintainability
    Better manage distributed teams
    Ability to manage changing priorities
    Increased team productivity
    Improved project visibility
    Increased team morale/motivation
    Better delivery predictability
    Faster time to market
    Enhanced software quality
    Reduced project risk
    Improved business/IT alignment
    Improved engineering discipline
    Enhanced software maintainability
    Better manage distributed teams
    87
    85
    84
    81
    81
    80
    79
    78
    77
    73
    70
    62
    62
    56
    55
    47
    44
    44
    40
    40
    29
    24
    23
    22
    21
    Wanted Got
    %
    %

    View Slide

  16. @sandimetz Apr 2016
    Software
    2016

    View Slide

  17. @sandimetz Apr 2016

    View Slide

  18. @sandimetz Apr 2016

    View Slide

  19. @sandimetz Apr 2016
    Modern Resolution of All Projects
    15%
    30%
    45%
    60%
    2011 2012 2013 2014 2015
    22%
    17%
    19%
    17%
    19%
    49%
    56%
    50%
    55%
    52%
    29%
    27%
    31%
    28% 29%
    Successful Challenged Failed

    View Slide

  20. @sandimetz Apr 2016
    Resolution by Project Size
    0%
    10%
    20%
    30%
    40%
    50%
    60%
    70%
    Grand Large Medium Moderate Small
    Successful Challenged Failed

    View Slide

  21. @sandimetz Apr 2016
    Agile
    0%
    10%
    20%
    30%
    40%
    50%
    60%
    70%
    Large Medium Small
    Successful Challenged Failed
    Waterfall
    Large Medium Small
    Resolution by Project Size

    View Slide

  22. @sandimetz Apr 2016
    Resolution: Agile vs Waterfall
    0%
    10%
    20%
    30%
    40%
    50%
    60%
    70%
    Agile Waterfall
    Successful Challenged Failed

    View Slide

  23. @sandimetz Apr 2016

    View Slide

  24. @sandimetz Apr 2016
    1

    View Slide

  25. @sandimetz Apr 2016
    Attributions

    View Slide

  26. @sandimetz Apr 2016
    What a jerk

    View Slide

  27. @sandimetz Apr 2016
    I'm in a hurry

    View Slide

  28. @sandimetz Apr 2016
    Fundamental
    Attribution
    Error

    View Slide

  29. @sandimetz Apr 2016
    2

    View Slide

  30. @sandimetz Apr 2016
    Teamwork

    View Slide

  31. @sandimetz Apr 2016
    Project Aristotle

    View Slide

  32. @sandimetz Apr 2016
    Project Aristotle

    View Slide

  33. @sandimetz Apr 2016
    Emotional Intelligence
    of
    Groups

    View Slide

  34. @sandimetz Apr 2016
    "equality in distribution of
    conversational turn-taking"

    View Slide

  35. @sandimetz Apr 2016
    "average social sensitivity"

    View Slide

  36. @sandimetz Apr 2016
    Psychological Safety

    View Slide

  37. @sandimetz Apr 2016
    3

    View Slide

  38. @sandimetz Apr 2016
    Motivation

    View Slide

  39. @sandimetz Apr 2016

    View Slide

  40. @sandimetz Apr 2016
    Autonomy
    Mastery
    Purpose

    View Slide

  41. @sandimetz Apr 2016
    Advice

    View Slide

  42. @sandimetz Apr 2016
    Dear Programmers

    View Slide

  43. @sandimetz Apr 2016
    Dear Programmers
    re: Programmers

    View Slide

  44. @sandimetz Apr 2016
    Experiment

    View Slide

  45. @sandimetz Apr 2016
    Isolate

    View Slide

  46. @sandimetz Apr 2016
    Depart

    View Slide

  47. @sandimetz Apr 2016
    Dear Programmers
    re: Managers

    View Slide

  48. @sandimetz Apr 2016
    Say "Yes"

    View Slide

  49. @sandimetz Apr 2016
    Dear Managers

    View Slide

  50. @sandimetz Apr 2016
    Don't Settle

    View Slide

  51. @sandimetz Apr 2016
    Own the Human

    View Slide

  52. @sandimetz
    Thanks
    Apr 2016

    View Slide

  53. @sandimetz Apr 2016
    References
    VersionOne, The 10th Annual State of Agile™ Report
    http://www.infoq.com/articles/standish-chaos-2015
    https://hbr.org/2016/01/collaborative-overload Harvard Business Review
    http://www.nytimes.com/2016/02/28/magazine/what-google-learned-from-its-quest-to-build-the-perfect-team.html
    https://www.youtube.com/watch?v=u6XAPnuFjJc Daniel Pink RSA Animate "Drive"

    View Slide

  54. @sandimetz
    http://poodr.com
    Apr 2016

    View Slide

  55. @sandimetz
    http://99bottlesbook.com
    Apr 2016

    View Slide

  56. @sandimetz
    Sandi Metz
    @sandimetz
    http://sandimetz.com
    Apr 2016

    View Slide