YDS: Is the Scrum Team's Velocity a Sprint Review Topic?

preview_player
Показать описание
Is the Scrum Team's Velocity a Sprint Review Topic? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.

What do you think? Let us know in the comments!

Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -

Join Ryan and Todd in a Professional Scrum Master course:

And make sure you subscribe to the channel!

DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week!

FTC DISCLAIMER: This video is not sponsored by anyone.

Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems.

#scrum #agile #scrummaster
Рекомендации по теме
Комментарии
Автор

Right on guys, you are giving your viewers quality. Agree, we need more Value than targeting the scrum team.

derekwright
Автор

Finally people who know what they are talking about ..No BS!!
Thanks 🙏🏼 guys

b.a
Автор

I took over a team where the previous Scrum Master always started the Sprint Review with completed points : committed points and the velocity chart. I’ve been planning to switch to focus on value, and now it’s more urgent. Thanks!

robertfeldbruegge
Автор

Thanks guys! Another great episode!

May I suggest you make videos on the Scrum events, their inputs, participants and outcomes? Just like you had a week of Values.

Timaz
Автор

Thanks for a great episode👍🏼.. Couldn't agree more that Velocity doesn't give any insights on whether we are delivering Value or not.

Looking forward for the EBM episodes.

abhishekdixit
Автор

Excellent question.
Totally agree RR+TM, outcomes, not output, EBM is really shining through as a "must have" knowledge.
Thanks and ... Stay Amazing 🌟

MarkBurville
Автор

This episode was helpful in focusing on the true purpose of the Sprint Review as a Scrum event. Thanks TM & RR

MrAkkim
Автор

As always, it's a good episode. Like that music better-- from Eminem's song. Yes, Velocity is like burn-down chart, owned by Developers. They should not be talked about during Sprint Review.

I am looking forward to seeing your new episodes about EBM. Thanks D.J. R.R. and "Party Word Guy" or PWG Todd LOL.

supergirls
Автор

BTW, the jingle on 1.25 speed is even better 🤣

MarkBurville
Автор

I agree with you... but I think depending of the maturity of your stakeholders it can be something that you will be forced to use for projection. When you have stakeholders that is asking for due date all the time. To help them understand that due date depends of many thing and that you can't know what will happen in few weeks for sure, I found usefull to show release burndown chart (thus associated to velocity) so we can have discussion around those estimated due date of release.
I totally agree that outcome are more valuable and you should focus on that, but output on a low maturity agile context will find their place to have discussion... else you will end up with stakeholders asking for date X, pressuring the scrum team, conducting to neglect quality without a metric to show them the reality.

flowmizer
Автор

They used velocity in my previous organization. If we there had been customers or the sponsor, they would have had no idea what the software developers were talking about. Project Managers and others who didn’t understand Scrum used velocity and the incomplete work (that was “promised” for the sprint) to complain that the software developers were chronically late in delivering on what they said they would do. Although those complaints were not brought up in a Sprint Review. I guess the software developers liked the metrics. I honestly was more interested in when it would be done (flow metrics) so I could start to report better forecasts to the sponsor. EBM would have been interesting, and I think it would have been eye opening for the organization if they had been open to other ways of thinking.

vkxcqsn
join shbcf.ru