
Scrum Team Size for Scrum Masters – Part 2
Smaller Teams
Furthermore, small scrum teams tend to have less breadth of skills in them which makes losing a team member can have more of an impact. Teams that are too small tend to have less cross-skill ability so if a team member leaves, or becomes sick, a too small team may have a harder time covering the lost member’s work. This can lead to lost productivity until someone else is found to replace them.
From a Scrum Master’s point of view, small teams pose their challenges too. Collaboration is key here, as well. If there aren’t enough people on the team to effectively collaborate, bounce ideas off each other, check each other’s work, and so on, it can be difficult to effectively do the work.
Teams that have around 5 people, excluding the Scrum Master and Product Owner, tend to be more productive and efficient. Collaboration and communication tend to be easier and there is a lot less overhead than larger teams. Forming a team with fewer members is also easier. Finding 5 people who can do the job is a lot easier than finding a team of 16.
Teams with 5-7 members tend to be just as productive, or close to it, as larger teams while having a diverse set of skills that is needed to get work done efficiently. Furthermore, members often have cross-functional skills that can come in handy just in case a team member is no longer available.
Five-member teams tend to be better at communicating and collaborating with each other. Scrum Masters will often spend less time coordinating between team members and planning events when teams are kept small. Planning meetings and keeping those meetings on track can take a lot more effort with larger teams. Not only are larger team meetings harder to keep time-boxed but one tangent could throw the whole meeting off course. Keeping a team small helps you as a Scrum Master keep the team on track and productive.
Communication becomes exponentially harder and more complex as team members increase. More time and effort is spent on communications for larger teams. This is true for team members as well as the Scrum Master. Keeping communication effort down is important since this can start to eat away at productivity. If a team is too small, communication between the team may be easier, but collaboration may become harder. As a Scrum Master, you should consider the nature of the work and what is needed for the team when deciding a team size. This will allow you to keep the team and project going in a productive, efficient manner.
The ‘Agile Scrum Master Training Course With 59 Seconds Training‘ is now available for free. This free Scrum Master Certified Online Training Course provides an in-depth understanding of the Agile Scrum Master roles and responsibilities, where you find out what a Scrum Master does and how to do it. During this free course you will learn all of the tools needed to succeed as an Agile Scrum Master.
Thank you for choosing us to learn about the Agile Scrum Framework.
<– Continue Reading –>
Our Book Recommendations
We found these books great for finding out more information on Agile Scrum:
Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)
Introductory Offer: Free Course
Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)
What is this course?
This ‘Master of Agile – Agile Scrum Tester With 59 Seconds Agile (Video Training Course)’ provides an in-depth understanding of the Agile Scrum Tester roles and responsibilities
You will explore the Agile Scrum project life-cycle, including how an Agile User Story is created, to how we know when it is ‘done’
This course is aimed at those with or without prior knowledge and experience of the Agile values and principles
During this course you will learn the tools needed to succeed as an Agile Scrum Tester
What will you learn?
You will gain an in-depth understanding of the Agile Scrum Tester roles and responsibilities, and you will be able to
- Fully understand the role of the Agile Scrum Tester
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team
- Fully understand the role of the Agile Scrum Developer
- Understand the roles involved in an Agile project
- Create an effective Product Backlog
- Effectively participate in Scrum Meetings such as the Daily Stand-up, Sprint Review and Retrospective
- Identify the roles involves in the Scrum Team

What topics are covered within this course
You will cover the following topics during this course:
- An Introduction to Agile Project Management (Tester)
- The 12 Agile Principles (Tester)
- Introduction to Scrum (Tester)
- Scrum Projects (Tester)
- Scrum Project Roles (Tester)
- Quality in Agile (Tester)
- Acceptance Criteria and the Prioritised Product Backlog (Tester)
- Quality Management in Scrum (Tester)
- Epics and Personas (Tester)
- Planning in Scrum (Tester)
- Scrum Boards (Tester)
- User Stories (Tester)
- The Daily Scrum (Tester)
- The Product Backlog (Tester)
- Review and Retrospective (Tester)
- Validating a Sprint (Tester)