how great teams get shit done

Abstract

Improving developer experience to improve developer productivity.

Developer joy:

  • dev quality: code / project quality
    • 42% of dev time used for technical debt
    • 10% of dev teams manage technical debt
    • coding guidelines
    • code reviews
    • flaky test detector
    • start with DORA
      • Change failure rate
      • Time to Restore
    • quality metrics
      • bug resolutions
      • change failure rate
      • time to restore
      • on time vulnerability resolutions
      • incident recurrence
  • dev progress: be able to push forward without roadblock
    • 3 days average from opening to merge a pull request
      • can add a bot to remind people: reduce to 1.2 days
    • instead of Quality Assurance, use Quality Assistant to help developer for manual and automated tests
    • feature test strategy
    • test automation platform
    • deployment frequency
    • lead time for change
    • internal and customer improvements
    • organization development
    • innovation time
    • reducing entropy
    • service operations
    • administrative time
  • dev value
    • get the whole picture
    • demos
      • open: everyone can join
      • outcome: show customer value
      • group thinking: challenge the solution
      • celebrate: recognize great work
    • software development is not a production line
    • measure what is important, don’t make important what you can measure