Scrum Team Size for Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum Teams need to be big enough to get things done, but small enough to allow for communication and move quickly.

The Scrum Team has three roles that make up the structure of the team, the Scrum Master, Product Owner, and Development Team. When deciding how large a team should be, the development team is where the numbers will increase or decrease. There will always be one Scrum Master and one Product Owner – teams shouldn’t have more than one Product Owner.

Choosing how many people are needed for a scrum team can seem like a daunting task for Scrum Masters. Scrum Masters guide the team in using Scrum and ensure that the team is working in its best way by serving the team. There isn’t any rigid template that you have to follow when creating a Scrum Team, however, there is some general advice to help out.

A common recommendation is that Scrum Teams should be seven people, plus or minus two. While recommendations allow for flexibility in building your team, they can be hard to implement when deciding how many people to include. As a Scrum Master, you will be tasked with ensuring the team performs at its peak. If a team is too big or too small it can affect the way you do your job.  So what size should a Scrum Team be?

Larger Teams

As a scrum team gets larger, so does the amount of communication needed to ensure collaboration. As a Scrum Master, you should consider what is needed for the team and how complex the project working on is. Larger teams tend to be necessary for larger, more complex work.

59 Seconds Agile - The Scrum Team Size

59 Seconds Agile – The Scrum Team Size

Larger Teams

Teams need to be big enough to allow the work to be done. Sometimes if a project is larger and more complex, it will require more developers. Larger companies also tend to have larger teams since there will often be larger, more complex projects. However, teams can get too large. If a Product Owner comes to you and wants a 16-man team, a Scrum Master should consider whether it is necessary and how it will affect the use of Scrum.
 
Scrum Masters should consider how many development team members are needed to effectively get the work done while allowing for effective communication and efficient collaboration. When teams are too large, it can be harder to keep meetings time-boxed, communication becomes harder and more time and effort will be needed on the Scrum Master’s part to keep the team working effectively. Essentially, from a Scrum Master’s point of view, larger teams tend to require too much coordination between the team to keep things running smoothly and effectively. The larger the team becomes; the more time is needed to keep the team on track and working efficiently.

Scrum Masters should consider the ramifications and pitfalls that can happen when teams get too large and complex. If a Product Owner comes to you and insists on a team size that seems too large to effectively handle, suggesting that the team split into two teams that work parallel to each other can help alleviate some of the problems associated with large teams.

Smaller Teams

So what happens if teams are too small?

Teams should be big enough to handle the work effectively and efficiently. Having only a couple developers can affect the amount of work that is able to be done on the project. Even with this, collaboration becomes a problem since there will be fewer people available to check each other’s work or test solutions.

Prev <— Continue Reading —> Next

Our Favourite Agile Books

Read Our Reviews

The History of Agile For Scrum Masters

Prior to the 1990’s software development was very slow, often taking years to complete development and release the product to market. The industry was following a very formal methodology for products and software development…

Read More

What is Agile to the Scrum Master?

While traditional project management is still widely used, the benefits of an Agile approach to running a project are becoming more and more recognized. Where Agile has a distinct advantage over classic project management is the development of new products…

Read More

Why Use Agile as a Scrum Master?

When determining if a move to Agile is right, a PESTLE can be used to simplify what factors should be considered. While Agile is sometimes thought of as a software development project management method, it isn’t just for these types of technology-centric companies…

Read More

The Agile Manifesto For Scrum Masters

Agile is a quick, simple, lightweight and effective way of managing projects. In traditional project management models…

Read More

The Agile Principles For Scrum Masters

When the Agile Manifesto was drawn up in 2001, it embodied four values and twelve principles that signaled a new approach to…

Read More

The Agile Fundamentals For Scrum Masters

Thinking of becoming a Scrum Master? Or are you already one, but you’re still new to the job? No matter what level of experience…

Read More

The Declaration of Interdependence For Scrum Masters

The Declaration of Interdependence establishes that all members, stakeholders, and customers are interdependent and…

Read More

The Agile Frameworks For Scrum Masters

There are many different Agile frameworks – all of them share the same philosophy and are built around the Agile Manifesto and Principles. But they vastly differ in their approaches, values, and structure. …

Read More

The Scrum Framework For Scrum Masters

The Agile Scrum framework is designed to deliver products and projects of any size. This includes projects, programs, and portfolios. Scrum provides guidelines on delivery techniques, events, and roles. Many of the same ceremonies are held within both a standard Agile scrum project and an Agile Scrum…

Read More

The Scrum Roles For Scrum Masters

Scrum is a useful tool for the creation, maintenance, plan, and execution of diverse products and services. The tool consists of…

Read More

The Scrum Team Size For Scrum Masters

The basics of Scrum can be easy but implementing them and succeeding with Scrum can be infinitely harder. Scrum …

Read More

The Agile Project Vision For Scrum Masters

At the heart of any great product is a great vision. It describes the primary goal or goals of a product and creates a focus that…

Read More

Forming the Scrum Team For Scrum Masters

Scrum is a framework that encourages delivery of potentially shippable product increments every 2-6 weeks. The work is…

Read More

Developing Epics For Scrum Masters

The term ‘epic’ in agile refers to a large user story that has not yet been defined in detail. Typically, an epic will cover a single…

Read More

The Agile Product Backlog For Scrum Masters

A Product Backlog is an organized collection of the existing User Stories (aka Wants and Needs) for an explicit business endeavor. Think of a shopping catalog of User Stories, ordered by urgency, that can be perused and selected from to determine what will be worked on during the current…

Read More

Release Planning For Scrum Masters

Although flexibility and adaptability are part and parcel of an agile methodology, this does not mean that no planning is required when…

Read More

Creating User Stories For Scrum Masters

User Stories are an integral part of the agile development process. They are an important agile technique that is used to frame…

Read More

Estimating User Stories For Scrum Masters

One of the principles of self-managing teams in Agile Scrum is working collaboratively with the Product Owner to effectively deliver…

Read More

Creating Tasks For Scrum Masters

According to The Agile Manifesto: “The best architectures, requirements, and designs emerge from self-organizing teams.” As a…

Read More

Estimating Agile Tasks For Scrum Masters

In Scrum, a list of user stories is produced and put together to form a product backlog, and each of these user stories will need to…

Read More

Creating the Sprint Backlog For Scrum Masters

The Sprint Backlog is defined as a group of user stories that are grouped together during the Sprint Planning Meeting.  This…

Read More

Creating the Deliverables For Scrum Masters

Agile Scrum provides the framework for delivery of the vision of an organization. Execution of the vision includes processes, ceremonies and project deliverables that are also known as artifacts…

Read More

The Daily Stand-Up For Scrum Masters

The daily scrum is an opportunity for developers or anyone committed to working in the sprint to talk to each other to make sure the…

Read More

Product Backlog Prioritisation For Scrum Masters

The product backlog is a key element of Agile software development. It facilitates a development environment that creates valuable features and products for stakeholders…

Read More

The Sprint Review Meeting For Scrum Masters

The Sprint Review meeting comes at the end of the sprint and the goal of this meeting is to have key people in the room to be able …

Read More

Demonstrating and Validating the Sprint For Scrum Masters

As organizations migrate to Agile principles, there may be questions about how the organization can prove that there is value…

Read More

The Sprint Retrospective For Scrum Masters

A very simple step by step guide to help you choose the appropriate product development methodology from…

Read More

Releasing the Product For Scrum Masters

One of the most important milestones any project will ever have is finally releasing their product and putting it out there. It’s the…

Read More

Regression Testing For Scrum Masters

In companies using agile development, it is common to introduce changes in a product incrementally. Along with the new changes, unexpected issues may arise, testing whether the existing functionality is broken or not becomes very important…

Read More

Product Owners

Find out more about the Agile and the Product Owner Role

Read More

Developers

Find out more about the Agile and the Developer Role

Read More

More Articles

Read More

Chicken Appreciation Society

Share
Translate »