Planning Poker Estimation Technique

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

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

  • @ayodelebamgbose9900
    @ayodelebamgbose9900 2 года назад +2

    As the scrum master, when the scrum team cannot agree on a story point value after lots of explanations and individual estimations, we'll go by the higher estimates.

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

      Thanks for sharing Ayodele 😊👍

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

    Great insight. This video gave me heads up understanding the topic

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

      Glad it was helpful Henry. Don't forget to subscribe for more 😊👍

  • @kitthekat6844
    @kitthekat6844 2 года назад +1

    You mentionned that each member of the team should be estimating the user story, but what about multi-disciplinary teams? I don't see myself forcing my artists or designers to estimate techincal work! They won't be able to estimate properly the work done, and will end up slowing down the team or copying their technical collegues. (and same for the opposite as well)

  • @VVHFX
    @VVHFX 2 года назад +1

    Team needs to follow the rules for compromising & see if they would like to go with an average or median if outliers are being included. Also, for understanding the uncertainty better, the team could break a user story down to have a spike on the unclear part.

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

      Thanks for the comment and sharing your perspective Venkat, appreciate it 😊👍

  • @spindersingh1888
    @spindersingh1888 2 года назад +1

    This video soo good you explained well

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

      Thank you Spinder 😊👍

  • @pescaearmas
    @pescaearmas 2 года назад +1

    Nice videos! Congrats