Metrics 📈 For Measuring The Scrum Team's Effectiveness [Don’t Use Velocity]

แชร์
ฝัง
  • เผยแพร่เมื่อ 1 ต.ค. 2024

ความคิดเห็น • 31

  • @wowaschneider9181
    @wowaschneider9181 2 ปีที่แล้ว +2

    Important topic👍!
    Impact and the real value delivered is crucial; how is it helping and what change have we made with our shipped increment.
    Are users using „it“? And how, and what’s helping them or what problem have we solved? … agility & value is about the organization, not only the team. …

  • @osnyzinho
    @osnyzinho ปีที่แล้ว +2

    I tried to give 2 likes, but was not possible.

  • @TheAgileLeanGardener
    @TheAgileLeanGardener ปีที่แล้ว +2

    Great video, totally agree and anything that helps us move away from story points and velocity is a good thing in my opinion! I like EBM and a focus on ‘actual’ customer value rather than ‘perceived’ customer value.

  • @francescotiberi1608
    @francescotiberi1608 2 ปีที่แล้ว +2

    Very clear and useful, thank you so much. We are currently struggling exactly with this topic, how to make ourselves measurable without driving the wrong behaviors.

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว

      Good to know that you found the video useful. All the best @Francesco.

  • @EmpySoul
    @EmpySoul 2 ปีที่แล้ว +1

    Amazing video! The moment you mentioned the team may not be capable to deliver at the end of sprint because of PROD Issues, I felt very related. My product has so many tech debt and very tight release dates that is kinda impossible to pay down the tech debt, but showing some of these metric might help to get my bosses are of the price to prefer on-time release over quality products. Thanks always for you knowledge.

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว

      Thanks you for the your kind word. All the best for pushing change at your current workplace.

  • @mustofin
    @mustofin ปีที่แล้ว +1

    this is what i've been looking for. Thanks coach.
    Stay healthy & stay handsome

    • @scrummasterinblack
      @scrummasterinblack  ปีที่แล้ว

      You are welcome. Thank you for the support. :)

    • @mustofin
      @mustofin ปีที่แล้ว

      ​@@scrummasterinblack It's my pleasure

  • @TheAgileLeanGardener
    @TheAgileLeanGardener 2 ปีที่แล้ว

    Hehe yes couldn’t agree more, velocity shouldn’t be used to measure a team! Love the frequency of releasing to help measure and I think the sprint goal, which in my experience is underused so often, can really help create the focus needed to achieve this.

  • @pranshugupta2607
    @pranshugupta2607 2 ปีที่แล้ว +1

    As always, inspiring and right on 👍

  • @JouleDoc
    @JouleDoc 2 ปีที่แล้ว +1

    Nice topik bro

  • @Rkajian4388
    @Rkajian4388 2 ปีที่แล้ว +1

    Awesome video, what is state of effectiveness level for the blue color “top one”? ;)

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว +1

      Good one that you noticed that part 😁. I leave that out to the team to figure out how can they level up their game. Probably like Amazon's team who release to production environment every 11 seconds. I saw a presentation video about it once.

    • @Rkajian4388
      @Rkajian4388 2 ปีที่แล้ว +1

      @@scrummasterinblack ah good answer, so we can figure outs, “awesome” state for our team self, not necessary to copy paste the other company, as long as it’s “effective” for us, what other company did can be a knowledge and reference, is’n it? anyway thanks coach

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว

      @@Rkajian4388 yes. The point is to keep levelling up the level of awesomeness :) because you can always be more awesome than yesterday.

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว

      @@Rkajian4388 as long as they deliver at least 1 releasable increment every Sprint.

    • @Rkajian4388
      @Rkajian4388 2 ปีที่แล้ว

      @@scrummasterinblack well noted and thanks, I was told by a Certified scrum master that our company does not implement scrum well, because our timebox is 1 month instead of 2 weeks like most other companies, they said it is not effective or even our agility is worst, is it paradox? maybe next video can clarify some of paradox things in scrum world ;)

  • @alec823
    @alec823 2 ปีที่แล้ว +1

    Thank you for this amazing video 🙌

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว +1

      You're so welcome! Thank you for watching. :)

    • @alec823
      @alec823 2 ปีที่แล้ว

      @@scrummasterinblack Would be interesting to know your vision of working with distributed teams through the time zones. How do conduct and schedule events in this case. And what kind of tools do you use in this situation :)

    • @scrummasterinblack
      @scrummasterinblack  2 ปีที่แล้ว

      @@alec823 There isn't one size fits all approach. It depends how distributed is the whole team members. If it's spread between two timezones, it is often times not as complex if each team member is spread accross more than three timezones. I usually facilitate the discussion with the team on how to deal with the circumstances. Miro or Mural is my favorite tool for facilitating the discussion.

    • @alec823
      @alec823 2 ปีที่แล้ว +1

      @@scrummasterinblack Thank you for a quick and comprehensive reply 🤝