YDS: Capacity Sprint Planning vs Velocity Sprint Planning

A YouTube viewer sent in a question asking about the pros and cons of Capacity Sprint Planning vs Velocity Sprint Planning. After discussing each one, Ryan and Todd talked about each option and then gave a few different ideas to investigate as well! Check out what Todd and Ryan had to say about this situation! Want to learn more about Scrum?

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 #professional scrum

[stanislavpuhach]

And I tracked the drop in capacity after the planning to rise the discussion with the team why it’s happening and what are the consequences

[marymiller]

Velocity was somewhat helpful in a previous project, but left a lot to be desired. I couldn't tell Developers had "issues" with capacity planning due to the changes happening in the organization, people going on leave, altering the Definition of Done, etc. For whatever reason, the Scrum Master would not adjust the amount of work pulled in based on past velocity. I probably wrote this elsewhere... It also created problems with internal stakeholders in that it created a perception that the team was always behind. Many internal stakeholders didn't really understand Scrum. I couldn't really use velocity as a way to forecast or give the sponsors a sense of how the work was progressing.

[tomaszniemiec]

🛬 I'm glad you guys are back. I was hungry without my daily dosage of scrum/agile challenge to solve for breakfast, :D And with this out of the way: of course I know the law. We call it the "student law" because if you allow students six months to write a piece, you will get it after six months - either because they will overdo it or start working on it just about when the time for delivery is near. I fall into the first category, as I tend to overdo stuff, which I try to mitigate using what I know about MVP and early feedback.
🛫 Pomodoro is actually a really cool idea for individuals. While when it comes to teams I would suggest flow metrics :)

[cfbredraider]

I use the Sprint Team Capacity Calculator Chrome Extension for all of my scrum teams during sprint planning. Works great!

[neha-dx]

What should be the better approach if not capacity or velocity planning. Please emphasize on this.

[stanislavpuhach]

I use the term “capacity” to determine the availability of developers in hours. In this way I try to better understand the ratio between velocity as amount of work we deliver and capacity as the time when developers were at work let’s say

[DocThorQ]

Guys, what is your view on Story Points, especially in light of Ron Jeffries's statement. The Father of the story points "regrets" that points are still in use, saying, "I think using them to predict "when we'll be done" is at best a weak idea;". I still use them. What are your thoughts about that? What else, if not, story points can be used? Ideal time again, #NoEstimates or what else?

[JordiEilers]

Great topic. Thanx again. I'll keep watching, and just ordered the book. BTW. something is wrong with Ryans sound. It is not in sync with the vid

[sudakshinaghosh]

My team’s cycle time is not improving, especially the review and rework part. How can I improve that.

[claudiajap]

Hello guys, please so what if an organisation has to manage resources and have to spread resources across many projects. How then do they spread their resources without knowing estimating each individuals availability

[tfadams]

"Velocity is not the point, delivering value is the point". Should be repeated often.