Skip to main content

Scrum team of 17? Is that possible?

Last post 07:49 am October 6, 2016 by Olivier Ledru
6 replies
08:10 am September 25, 2016

Hi, I would like the opinion of Scrum experts on Scrum team sizes.

Following a re-organization within my company, two Scrum teams have been merged and are now a unique team of 17 members, with 3-4 PO/PMs and 1 scrum master. We've been operating like this for about 5 sprints now.

Unfortunately, it is pretty dysfunctional. The daily's and grooming sessions are lengthly, we systematically run out of time on retro and planning.

I read here and there that the maximum SCRUM team size should be 9 (i.e. 6 +/- 3).

Do you think we should split again? Is there any way Scrum would allow or even recommend such big teams?

Thanks !!!



03:24 pm September 26, 2016

s there any way Scrum would allow or even recommend such big teams?



Recommended or allowed? No.

That doesn't means it doesn't take place in many organizations. I have had a similarly-sized team work for a single Product Owner. That was quite cumbersome, but the Scrum Team was focused around sprint work and Sprint Goals. This dynamic can still technically follow Scrum, although team size will remain an issue.

I have also had a large team serving multiple Product Owners, similar to your situation. Unfortunately this creates a fragmented view of work, and simply isn't Scrum. There are benefits to visually identifying and tracking work, but with multiple PO's, it is near impossible to create any sense of team ownership of sprint stories, or identify a Sprint Goal.

Look to the 5 Scrum values (Focus, Openness, Respect, Courage, Commitment) and see how your setup either supports these values, or contradicts these values. Use your observations as a good starting point for discussion if things are not working.

Good luck.


06:12 pm September 26, 2016

You need to sort out who the product owner is first. If there is a single product, or a composite one with a clear value stream, then you may need a Nexus of teams with one PO. The act of combining the teams might have been a bodged attempt at doing something along those lines, but which left product ownership unresolved.

If your current POs represent separate products and unrelated value streams then we should expect separate and unrelated teams, but if that was the case then (I suppose) they would not have been combined in the first place.


12:05 pm September 27, 2016

Always go to the source: http://scrumguides.org/scrum-guide.html

Having three to four Product Owners is a violation.

There is no rule that there can only be three to nine Development Team members. Some reasons are given for each of these recommended size constraints.

The biggest problems I've encountered with a large team were communication, coordination, and knowledge sharing.


02:58 pm October 5, 2016

Sounds to me whoever had input into the reorg were not aware or concerned with Scrum at all. That is usually the case when there is not top down understanding and buy in. If "the team" truly wants to implement scrum they may have to revisit roles if possible and organize a team(s) with in the team but my guess is there are large issues here that will always cause a problem unless resolved by those who own the problems.


07:50 pm October 5, 2016

Just a thoughts...

If there are 3-4 product owners, why not to break team based on some functionality into 3-4 cross functional teams? Each team will have single PO, single sprint goal, separate SBI while share PBI, DOD and even SM.


07:49 am October 6, 2016

Maybe they choose to have only one big Scrum Team to help priotitize at the product-portefolio level, in order to focus at one time on the more valuable product ?

But if each Sprint is made of a mix of tasks from the 4 products, your suggestion really make sense to me.


By posting on our forums you are agreeing to our Terms of Use.

Please note that the first and last name from your Scrum.org member profile will be displayed next to any topic or comment you post on the forums. For privacy concerns, we cannot allow you to post email addresses. All user-submitted content on our Forums may be subject to deletion if it is found to be in violation of our Terms of Use. Scrum.org does not endorse user-submitted content or the content of links to any third-party websites.

Terms of Use

Scrum.org may, at its discretion, remove any post that it deems unsuitable for these forums. Unsuitable post content includes, but is not limited to, Scrum.org Professional-level assessment questions and answers, profanity, insults, racism or sexually explicit content. Using our forum as a platform for the marketing and solicitation of products or services is also prohibited. Forum members who post content deemed unsuitable by Scrum.org may have their access revoked at any time, without warning. Scrum.org may, but is not obliged to, monitor submissions.