Hi Mike. Thanks for sharing these helpful videos. I noticed this with my team. We are a new team working on an existing project. We work in a 3 week sprint and depending on the scope and expertise of the team. My team can complete around 2 stories per sprint. So, one member can work on 2 stories with 5sp, another 2 stories with 8sp.. ect. In the end we end up with the same speed.
Thanks Mike. The info is great. I work as a SM/Coach in a very large company and have access to reports where I can get the number of stories completed by each member in almost every team. I didn't calculate a specific single number as a median, but looked at the range, per person, per sprint over a year. Every person was almost always between 2 and 4 stories per sprint. Same as you, sprint length didn't matter. There were a few outliers, but just looking at the trend, I think our numbers agree. Thanks for the continued coaching!
Does number of team members include scrum master and product owner along with the developers? If the SM/PO on the team is not actively developing then I would think we wouldn’t include them as having two items each.
Good clarifying question! In this case the two items per team member guideline should only be for those who are doing the work (developers). While the SM and PO are part of the Scrum Team, if they aren't working on backlog items, the team should bring in about 2 items per developer.
In the video I say that the number is essentially the same regardless of sprint length, meaning teams doing longer sprints tend to work on larger items.
![[Mythbusting] What Happens To The Sprint Backlog Items That Are Not Done?](http://i.ytimg.com/vi/_o5_Gw0ZeJA/mqdefault.jpg)
Hi Mike.
Thanks for sharing these helpful videos.
I noticed this with my team.
We are a new team working on an existing project. We work in a 3 week sprint and depending on the scope and expertise of the team. My team can complete around 2 stories per sprint.
So, one member can work on 2 stories with 5sp, another 2 stories with 8sp.. ect. In the end we end up with the same speed.
Great stuff as usual. I really prefer the YT videos over the blog as an audio learner. Thank you.
Thanks. That's good to know as I start to plan how to spend my time for the coming year.
Thanks Mike. The info is great. I work as a SM/Coach in a very large company and have access to reports where I can get the number of stories completed by each member in almost every team. I didn't calculate a specific single number as a median, but looked at the range, per person, per sprint over a year. Every person was almost always between 2 and 4 stories per sprint. Same as you, sprint length didn't matter. There were a few outliers, but just looking at the trend, I think our numbers agree. Thanks for the continued coaching!
You're welcome!
Does number of team members include scrum master and product owner along with the developers? If the SM/PO on the team is not actively developing then I would think we wouldn’t include them as having two items each.
Good clarifying question! In this case the two items per team member guideline should only be for those who are doing the work (developers). While the SM and PO are part of the Scrum Team, if they aren't working on backlog items, the team should bring in about 2 items per developer.
What’s the length of sprint in your recommendation?
In the video I say that the number is essentially the same regardless of sprint length, meaning teams doing longer sprints tend to work on larger items.