A sample text widget

Etiam pulvinar consectetur dolor sed malesuada. Ut convallis euismod dolor nec pretium. Nunc ut tristique massa.

Nam sodales mi vitae dolor ullamcorper et vulputate enim accumsan. Morbi orci magna, tincidunt vitae molestie nec, molestie at mi. Nulla nulla lorem, suscipit in posuere in, interdum non magna.

Scrum: Smaller size makes a team that works together and more capable of self-organizing

Scrum teams are typically kept at a size of around 6-9 team members, and it is recommended that if the number of people in the team grows larger, then the team need to be split into multiple teams. This was a topic of discussion within the Scrum Masters in the team. We had read about this in almost all the articles and books that we had read about Srum and even the training had emphasized this. But when we asked the trainer about the reasons about why a Scrum team should not have say 10 people, the reasons were not very clear. The basic reason given was that the team would become unmanageable, and also, the Daily Scrum meeting would become much larger since there would be more people to provide an updates and increase the chance that the Daily Scrum meeting would become longer and longer. Now, this did make sense. When you increase the number of people in a Scrum team, there will be more people speaking, and the chances that what one person talks about has absolutely no relevance to the other people in the meeting, and when you combine this with the fact that the meeting will become longer, starts to increase the feeling of team members that the meeting is not fully relevant to them, or that only parts of the meeting are relevant to them. This would still be fine if the meeting was held maybe once in a week, but when the meeting happens on a Daily Basis, you certainly don’t want people to feel disenchantment with the meeting.
The other reason that we could figure out related to group dynamics. As the number of people in the meeting increases, the chances that you will have disruptive elements in the team increases and also increases the fact that the group will stop working as a whole, as a self-organizing group. In a smaller group, people tend to have a feeling of collective ownership, which means that they will try to figure out solutions if things are not going as per plan, and even in cases where a team members is lagging, will suggest solutions; if somebody has to go off on leave, people would even try to cover up in cases where the teams really have a feeling of ownership. However, there is research to show that if the group size becomes larger, then the self-organizing nature of the team reduces, and this also hampers the ability of the team to cover for each other and point out improvement areas for each other. Once you have a group with a larger number of people, the ability of people to work with each other is hampered by the feeling of some members of the team to try as a leader of the team even though there is no such position in terms of hierarchy within the group, and this affects the efficiency of the team.
This problems in terms of the team not being able to self-organize also manifests itself in the team taking more time to become an effective Scrum team. With more people in the team, the personal connections between the team members also take more time to happen, and there is a higher chance that some negative relationships can also form.

Leave a Reply

You can use these HTML tags

<a href="" title=""> <abbr title=""> <acronym title=""> <b> <blockquote cite=""> <cite> <code> <del datetime=""> <em> <i> <q cite=""> <s> <strike> <strong>