Size of scrum Team_2020 Scrum Guide
What to be size of developer (previously called as "Development Team") in case of shared Product owner in multiple teams??
Shall we count same product owner in each team ???
Scrum guide says,
"The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive. If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner."
Rupesh,
My understanding is that every Scrum team should have one (and only one) Product Owner and one Scrum Master. Thus every Scrum Team can have a maximum of 8 Developers. (since Scrum Team max is 10). Even if the same Product Owner works across multiple Products, he would reserve the Product Owner space as each Scrum Team can have only one Product Owner. So regardless of the Product Owner or Scrum Master being shared, there can be a max of 8 developers.
If the Product Owner and Scrum Master both work actively on the Product Backlog items in resolving them, one can count them as Developers bringing the Maximum to 10.
Sid.
The most important part of that quote is that:
The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint (...)
the rest is only a personal hint or clue for you to spark reflection. For example, if you have a "team" of 30 developers, is it allows them to remain nimble? You should not be focussed on the max cap for developers, maybe if you will have 11 devs it will be good or even best in your context, or maybe if you will have 8 devs it will be too much to handle in your situation.
Should we count PO in each Scrum Team? IMO Yes, from each ST local perspective, they have one PO.
There is one team, the Scrum Team, in which the Scrum Master and Product Owner are members, as well as Developers.
If establishing an exact size for the team seems to be important, ask yourself why. What problems would numerical precision on this matter solve or create for a team, which the judicious interpretation of a guideline would not?
I agree with @Piotr Górajek and want to add a little. He quoted the first part of sentence. I'm going to share the entire sentence and the one following.
The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint, typically 10 or fewer people. In general, we have found that smaller teams communicate better and are more productive.
Notice the words I bolded. Those words indicate that there is no prescribed or set limit. The authors are just providing some insights that they have discovered over the years. As Piotr said, the first part of that sentence is the most important.
I'm also going to give @Ian Mitchell credit for doing what he does so well. The question isn't how many is allowed. The question is why do we care so much about a set number.
Thank you for highlighting the words @Daniel Wilhite. It helps us all understand better. No prescribed or set limit for a Scrum Team. Small, Nimble and 10 is a guideline. Got it!
Thank you Sidharth Bathia ; Ian Mitchell ; Daniel Wilhite for replies. Not only this query get clarified but I understand that scrum guide not rigid by setting rules but providing some insights based on years of experience for implementating on various industries.