YDS: How Do You Increase the Velocity of a Scrum Team?

How Do You Increase the Velocity of a Scrum Team? 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!

Take a Professional Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti!

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

[TheSebabaez]

Loved the video, when I saw the snippet came right in expecting Todd to go on a rant, wasn't disappointed 😂. Now seriously, couldn't agree more on the topic

[madzero]

Is it me or is there just a little bit of emotion in Todd's voice? 😉

[tomaszgrygoruk]

One the best episodes, ever !! :) When I had seen the question I knew the the answer.
From my point of view let's increase the understanding what needs to be done. This might be valuable and can increase effectiveness.

[limitlesspotential]

I love when he said "can we get rid of the velocity completely?" Its totally true and I completely agree with it. Velocity is just a measure of number of story points delivered and does not show anything about what value is delivered and scrum always focuses on value delivered. The focus should shift from measuring outcomes and instead of output.

[robertlegatie]

Todd is 🔥🔥🔥. Love it.
We are all Todd on this subject.

[jasonlea]

Focusing on 'flow of work', optimising the system, reducing cycle time and monte carlo simulation are valuable areas to explore.

[ankhayratv]

Great video.

Can be used to show to people who think Velocity is useful. In fact, I'm going to share it with someone right now!

[masterinuse]

There is even a Cost of Delay...WTH. Great episode guys, thank you.

[tfadams]

In addition to what others said about Todd's emotion, which I heartily agree with, there are great references in here from both Ryan and Todd on books and classes. I seem to have the V word conversation at least every few weeks and I definitely sound like a broken record. But I remain optimistic that someone will listen and actually hear me 😃.

[MrAkkim]

Love this topic. Please create a few more segments on why this is no longer the best way or method of going about delivering tangible value.

[ঘুরিফিরিযখনতখন]

Love it. Thanks Todd and Ryans for the great explanation.

[MarkBurville]

Absolutely passionate subject, love it, don't change Todd. Very funny 🤣 Stay Amazing 🌟 see you next year answering this one again :P

[AgileforHumans]

*BETTER WAYS TO ESTIMATE, FORECAST, and MEASURE:*

[osnyzinho]

Todd is nervous! Yeah!!!! That was funny!

[TechBroNina]

agreed!! velocity is such an arbitrary number subjectively tied to how a team measures ITSELF for personal growth, NOT for evm tracking metrics to juxtapose teams!

[FlyyGuyVision]

yesss yess & yesss Velocity is what it is PERIOD end of story‼️

[fernandoroldanrojas]

If it is not much to ask, can you please share an implementation of a better metric and explain it with real world scenarios? Unfortunately where I work velocity is all that matters.

[TechBroNina]

i hope you folks open up with the fact that velocity isn’t everything :) and that it takes time to improve a team’s efficiency, and velocity is truly a subjective per-team basis arbitrary number!!

[davidh]

Most metrics will be gamed if required. EBM is really difficult to collect and nearly impossible to game. Thanks for this vid.

[Rekettyelovag]

Well... blame the names. Velocity suggests speed. High speed of a (performance) car, how fast it can go from 0-60, how fast can you do your job? It's kinda logical to a person who doesn't do deep research.
I said it multiple times that the one thing in Scrum that I don't like is the name of the iteration: Sprint (however, I understand y they chose that). The Wikipedia definition of a sprint is: "Sprinting is running over a short distance at the top-most speed of the body in a limited period of time. It is used in many sports that incorporate running, typically as a way of quickly reaching a target or goal, or avoiding or catching an opponent. " Needless to say, this implies speed and quickness, which is not what Scrum is about. But if you ask around, most management and devs say Scrum/Agile is about fast delivery. So don't be surprised when people ask this question and they try to make sense of it.
Also it is really hard to talk these people off of this topic as they don't know how or can't do meaningful metrics. They want v=s/t.

I wanted to write an article about this but never found enough time to do a proper research around it...so this is the quick and fast version. :D