Typical Size for a Scrum Team
Understanding the optimal size for a Scrum Team is crucial for effective Scrum practice. This article explores the recommended team size and its importance in the Scrum framework.
Exam Question
What is the typical size for a Scrum Team?
(choose the best answer)
A. 10 or fewer.
B. 9.
C. At least 7.
D. 7 plus or minus 3.
Correct Answer
A. 10 or fewer.
Explanation
Correct Answer
A. 10 or fewer:
The Scrum Guide suggests that a Scrum Team should typically consist of 10 or fewer members. This recommendation helps ensure effective communication, collaboration, and productivity. Smaller teams are generally more agile and can adapt quickly to changes, which is essential in a Scrum environment. There is no set minimum limit; the team should be small enough to deliver value effectively.
Incorrect Answers
B. 9: While 9 is within the recommended range, specifying an exact number does not account for the flexibility needed in team composition based on the project’s complexity and requirements.
C. At least 7: This option implies a minimum size without providing an upper limit, which could lead to overly large teams that may struggle with communication and coordination.
D. 7 plus or minus 3: This range (4 to 10 members) is close but not as precise as the Scrum Guide’s recommendation of “10 or fewer.” It’s important to note that the ideal size balances effective communication and diverse skills.
Responsibilities in Scrum
- Product Owner: The Product Owner is responsible for maximizing the value of the product and works closely with the Scrum Team to ensure they are delivering the most valuable work.
- Scrum Master: The Scrum Master facilitates Scrum events, supports the team in following Scrum practices, and helps resolve any impediments that may affect team performance.
- Developers: The Developers are responsible for turning Product Backlog items into Increments of value during each Sprint. They collaborate and self-manage to achieve the Sprint Goal.
Relevance to the PSPO I Exam
Understanding the typical size of a Scrum Team is essential for the PSPO I exam as it highlights the importance of team composition in achieving effective communication, collaboration, and productivity. Knowing this helps ensure that candidates appreciate the balance between team size and performance in a Scrum environment.
Key Takeaways
- A Scrum Team should typically consist of 10 or fewer members.
- Smaller teams facilitate better communication and collaboration.
- The recommended team size helps maintain agility and adaptability.
Conclusion
The typical size for a Scrum Team is 10 or fewer members, which helps ensure effective communication, collaboration, and productivity. Understanding this aspect of Scrum is crucial for maintaining an agile and efficient team.

Get ready for the official PSPO I exam
320 PSPO I practice questions, each with an in-depth explanation like the one above.
- Practice Mode: study at your own pace and choose the test length.
- Mock Exam Mode: 80 random questions in 60 minutes, like the real exam.
$29 is ScrumPrep's one-time price. The official PSPO I exam fee ($200) is paid separately to Scrum.org.
More PSPO I exam questions
- True or False: Sprint Reviews are an opportunity to collect stakeholder feedback.
- True or False: Dependencies could influence how the Product Owner orders Product Backlog items.
- In the middle of the Sprint, the customer decides that there are 2 new features she wants. The Product Owner could:
- A Scrum Team has been working on a product for 9 Sprints. A new Product Owner who is new to Scrum joins the team and understands she is accountable for Product Backlog. However, she is unsure about the purpose of the Product Backlog. She has read that the Product Backlog should be a list of all user features for the product. She goes to the Scrum Master asking where to put the other types of requirements that are going to be taken into account. Are all of the following types of requirements acceptable on a Product Backlog?
- Who is accountable for releasing the most valuable product possible?
