How to Calculate Team Capacity for the Upcoming Sprint + Capacity Template
How many user stories can be picked for the upcoming sprint?
Welcome to the 🔒 subscriber-only edition 🔒 of my weekly newsletter, the “Winning Strategy.” Every week, I answer one reader question about agile, product, roles, skills, job interviews, frameworks, working with humans, and anything else that you need answered about your career growth. You can send me your questions here.
Note: If you enjoy reading this post, would you mind showing your support by clicking the little gray heart below the title above? It would really mean a lot and help spread the word about this growing newsletter. 😍
On to this week’s question!
Q: My team always struggles while deciding to pick user stories for the upcoming Sprint. I have two questions. (1) How to calculate the team’s capacity? (2) How to use the team’s capacity to pick user stories? Given the capacity is in hours, and user stories are estimated in story points.
Thanks for reaching out with such a relatable question!
Years ago, I've been in those exact shoes, in the midst of Sprint Planning, scratching my head and wondering just how many user stories our team can realistically commit to. Velocity is not the whole story. It’s just one piece of the puzzle. And let me tell you, it’s a common puzzle many of us face in the Scrum world.
It's like selecting the right gear for a hiking trip – you want to pack enough to be prepared but not so much that it slows you down.
Understanding your team’s capacity in Scrum is essential, almost as crucial as knowing your backpack's limit. It not only ensures we deliver value efficiently but also keeps the team's well-being in check.
In this newsletter, I'll be walking you through the ins and outs of understanding and calculating your team’s capacity in Scrum.
But that’s not all!
I'll also share a handy template to make this process smoother for you.
So, grab your favourite drink, settle in, and let’s demystify the magic behind successful Sprint Planning together! 📖☕