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.
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)
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.
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.
Thanks for sharing Ayodele 😊👍
Great insight. This video gave me heads up understanding the topic
Glad it was helpful Henry. Don't forget to subscribe for more 😊👍
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)
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.
Thanks for the comment and sharing your perspective Venkat, appreciate it 😊👍
This video soo good you explained well
Thank you Spinder 😊👍
Nice videos! Congrats
Thanks! 😊