Introducing Developer Velocity Lab to improve developers’ work and well-being

Поделиться
HTML-код
  • Опубликовано: 12 сен 2024

Комментарии • 8

  • @condor83
    @condor83 2 года назад

    One of the best video I've ever seen!!!.
    Truly, in less than 25 you receive metrics to start to look at that are not MTTR, Lead Time, etc...
    AWESOME.

  • @jimblizzard9725
    @jimblizzard9725 Год назад

    Excellent video!

  • @l_combo
    @l_combo 11 месяцев назад

    Love this overall, except the use of the term velocity and the example referencing story points which are relative to a team and not to be used more broadly.
    I'd welcome the use of the term throughput instead of velocity so that is generic to work with teams using any approach to ways of working and not be tied to the often-misused story points.
    Do you also have an product or value stream type example that is composed of many deployment points.

  • @kaiimgenberg3030
    @kaiimgenberg3030 Год назад

    I'm missing robustness and security of code in this video. I would expect that MS Research would emphasize code quality especially on the security dimension after all this research. Why didn't they? What about reduction of technical debt and finding/fixing vulnerabilities as a simple measure of better code?

  • @JoelBondurant
    @JoelBondurant 3 года назад

    USA brand corporation objects can use military robots with lasers to zap human capital tax cattle objects to enforce maximal developer performance compliance.

    • @cobertos_6455
      @cobertos_6455 3 года назад +2

      Ow, don't zap the developers. They don't like it