This week's book giveaways are in the Refactoring and Agile forums.
We're giving away four copies each of Re-engineering Legacy Software and Docker in Action and have the authors on-line!
See this thread and this one for details.
Win a copy of Re-engineering Legacy Software this week in the Refactoring forum
or Docker in Action in the Agile forum!
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic

team size and scrum

 
Aaron Turner
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Is there recommended size (number of developers) for a team doing agile? Can the size of the team effect the productivity of a scrum?

Thanks,
Aaron
 
Pradeep bhatt
Ranch Hand
Posts: 8927
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I would say yes. Any number more than 10 is a crowd. Does anyone have patience to listen to more people in a standup meeting. How much one be able to digest ?
 
Earl Everett
Greenhorn
Posts: 1
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Scrum canon states that Team size should be seven plus or minus two. This fits well with my experience. When a team gets too large, it will tend to self-organize into sub-teams.
 
Pradeep bhatt
Ranch Hand
Posts: 8927
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Earl Everett:
Scrum canon states that Team size should be seven plus or minus two. This fits well with my experience. When a team gets too large, it will tend to self-organize into sub-teams.


Good point. How was the number 7 arrived at ?
 
Aaron Turner
Greenhorn
Posts: 7
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Should the skill set of the team members be fairly equal or does that matter?
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Pradip Bhat:


Good point. How was the number 7 arrived at ?


As far as I know, it's based on http://en.wikipedia.org/wiki/The_Magical_Number_Seven,_Plus_or_Minus_Two
 
Ilja Preuss
author
Sheriff
Posts: 14112
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
I've heard of teams of 20 to 25 developers working well, and of Daily Scrums with 50 people attending.

That certainly will change the dynamics, though. Typically you will find a technique used called "Scrum of Scrums": http://www.mountaingoatsoftware.com/scrum_team
 
Lasse Koskela
author
Sheriff
Posts: 11962
5
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Pradip Bhat:
How was the number 7 arrived at ?

If you ask Ken Schwaber, he'll start listing different specialties like "Well, you need a couple of programmers, a couple of testers, a UI designer, a database admin, [...] and there's already 7 people for your team."
 
Pradeep bhatt
Ranch Hand
Posts: 8927
Firefox Browser Java Spring
  • Mark post as helpful
  • send pies
  • Quote
  • Report post to moderator
Originally posted by Ilja Preuss:
I've heard of teams of 20 to 25 developers working well, and of Daily Scrums with 50 people attending.

That certainly will change the dynamics, though. Typically you will find a technique used called "Scrum of Scrums": http://www.mountaingoatsoftware.com/scrum_team


I am not sure how much others would have patience to listen to if it is a group of 25 people. Certainly not me.Will they find a room big enough for 20+ ? A playground maybe

Scrum of scrums is a good idea.I like it
 
  • Post Reply
  • Bookmark Topic Watch Topic
  • New Topic