The Scrum Team

PSM I PSM I · Scrum Team & Accountabilities

By Abu Anns · Last updated 20 November 2026Exam version: PSM I (Scrum Guide 2020)

The fundamental unit of Scrum is a small team of people: the Scrum Team. It consists of one Scrum Master, one Product Owner, and Developers. That is the whole list. There are no sub-teams and no hierarchies inside a Scrum Team — it is a cohesive unit of professionals focused on one objective at a time, the Product Goal. This matters more than it sounds. In many organizations, teams are assembled from separate departments — developers here, testers there, a business analyst somewhere else — each reporting to a different manager. Scrum rejects that structure. One team, one goal, one shared accountability for the outcome. When the exam asks who is in the Scrum Team, the answer is always these three accountabilities and nothing else: stakeholders, managers, and customers work with the team but are not part of it.

Scrum Teams have two defining properties: they are cross-functional and self-managing. Cross-functional means the members have all the skills necessary to create value each Sprint — the team does not depend on people outside itself to finish the work. If a team must wait for an external database group or an external test team before an Increment is usable, it is not truly cross-functional, and its ability to deliver value each Sprint is compromised. Self-managing means the team internally decides who does what, when, and how. Nobody outside the team assigns tasks to Developers, and nobody inside the team has authority over the others — not even the Scrum Master. This is the property the exam tests most often, because it conflicts with the habits of traditional management. A manager who tells Developers which items to pick up, or a Scrum Master who directs the daily work, is breaking self-management even with good intentions.

The Scrum Team is responsible for all product-related activities: stakeholder collaboration, verification, maintenance, operation, experimentation, research and development, and anything else that might be required. That is a deliberately wide list. There is no handoff to another group for testing, deployment, or support — the team owns the product end to end. The entire Scrum Team is accountable for creating a valuable, useful Increment every Sprint. Notice the word entire: the Increment is not the Developers' responsibility alone. The Product Owner shapes what is valuable, the Developers build it, and the Scrum Master makes sure the team can work effectively — but the accountability for a valuable Increment each Sprint belongs to the team as a whole. The organization, for its part, structures and empowers the team to manage its own work, and working in Sprints at a sustainable pace improves the team's focus and consistency.

Size and structure

The Scrum Team is small enough to remain nimble and large enough to complete significant work within a Sprint — typically 10 or fewer people. Smaller teams, the Guide observes, communicate better and are more productive. This is a guideline with a specific action attached: if a Scrum Team becomes too large, it should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Those teams then share the same Product Goal, the same Product Backlog, and the same Product Owner. The exam likes this rule because it has a precise structure — one Product Backlog and one Product Owner across the teams, not one backlog per team. It also likes the boundary: 10 or fewer is typical, not a hard maximum, so a question claiming that an 11-person team is forbidden by the Guide is wrong. What the Guide requires is that oversized teams consider splitting, not that they must split at exactly 11.

One objective at a time

The Scrum Team focuses on one objective at a time: the Product Goal. This single focus is what makes the team's work coherent. Without it, a team pulled between competing priorities cannot make good trade-offs, because there is no shared definition of what matters most. The Product Goal gives the team a long-term target to plan against, and the Sprint Goal gives each Sprint its own single objective within that larger aim. When stakeholders ask the team to work on three unrelated initiatives at once, the Scrum framework's answer is not to multitask harder — it is to order the work in one Product Backlog against one Product Goal and let the Product Owner make the trade-offs visible. The exam tests this through scenarios where a team is scattered: the correct response almost always involves restoring a single focus rather than adding process to manage the scatter.

Worked scenario

Imagine a 14-person Scrum Team building a banking app. Communication is slow, the Daily Scrum runs long, and half the team feels disconnected from decisions. The Scrum Guide's answer is structural: the team should consider reorganizing into two cohesive Scrum Teams, both working from the same Product Backlog toward the same Product Goal, with the same Product Owner. Each team would have its own Scrum Master and its own Developers, and each would run its own Sprints. What the Guide does not suggest is adding a coordinator, splitting the backlog into two products, or appointing a lead developer to direct the work — all of those break either the single-product structure or self-management. The same logic applies at smaller scale: when a team of eight adds four specialists and starts to struggle, the first question is whether the team is still small enough to communicate well, not whether it needs more meetings.

The organization plays a part in making the Scrum Team work. The Guide says Scrum Teams are structured and empowered by the organization to manage their own work — empowerment is not something the team grants itself, it is something the organization provides by removing the structures that get in the way: approval chains, status reporting, and resource allocation by managers. When an organization says it wants self-managing teams but keeps every decision with management, the contradiction shows up quickly: the team cannot adapt, the Daily Scrum becomes a reporting channel, and the Sprint Goal becomes a management target. Working in Sprints at a sustainable pace improves the team's focus and consistency, which is another organizational responsibility: a team that is permanently overloaded cannot inspect honestly or adapt thoughtfully, because it has no slack to think. The exam sometimes tests this through scenarios where the organization, not the team, is the problem — and the correct response involves the Scrum Master coaching the organization, not blaming the team.

Advertisement

Exam traps to watch for

Practice questions

Test yourself on this guide. Answers are checked instantly, with a full explanation for each question.

Q1.Which of the following correctly describes the membership of a Scrum Team?

Report an error

Q2.A Scrum Team has grown to 15 people and communication has become slow and difficult. According to the Scrum Guide, what should the team consider?

Report an error

Q3.A Scrum Team is described as self-managing. What does this mean?

Report an error

Q4.Who is accountable for creating a valuable, useful Increment every Sprint?

Report an error

Q5.Which statement about the structure of a Scrum Team is TRUE?

Report an error

Q6.A department manager starts assigning specific Product Backlog items to individual Developers each morning. What Scrum principle does this MOST directly violate?

Report an error

Q7.A Scrum Team is described as cross-functional. What does this mean?

Report an error

Q8.Which of the following is the Scrum Team responsible for?

Report an error

Q9.Two Scrum Teams work on the same product. According to the Scrum Guide, what do they share?

Report an error