What if your team could choose not only how to work, but also who to work with? Scrum’s approach to team structure makes this a possibility—helping teams move faster, collaborate more deeply, and create higher-quality products. Let’s explore how optimized team structures empower agile teams to thrive.
Google’s landmark “Project Aristotle” found that psychological safety—not seniority, education, or even experience—was the most important factor for high-performing teams. Self-managed Scrum teams can create this safety by choosing teammates and work styles that fit.
Self-management puts decisions normally made by a manager or the organization into scrum team members’ hands. Because of the limited size of teams—which consist of less than ten people—agile product development efforts can have multiple scrum teams, if necessary. Self-management and size-limiting mean that agile product development can provide unique opportunities to customize team structures and work environments. Here are a few examples:
-
Developers may organize their team structure around people with specific work styles and personalities. Organization around work styles provides these benefits:
- Allows team members to work the way they want to work
- Encourages team members to expand their skills to fit into teams they like
- Helps increase team performance because people who do good work like to work together and naturally gravitate toward one another
- Scrum teams can make tailored decisions to balance team members’ professional and personal lives.
- Even technical issues benefit greatly from decentralized, self-managed decision-making.
- Because teams estimate their work, product owners can determine how many scrum teams may be required to accomplish the items on a product backlog.
- Ultimately, scrum teams can make their own rules about whom they work with and how they work.
In what ways might letting your team choose work styles and teammates change outcomes on your next project?
The practice of empowering team members to make decisions and set rules about their work, rather than relying on top-down management.
The ability for Scrum teams to design their own working structures, processes, and groupings based on their unique strengths and preferences.
How might decentralized, self-managed decision-making help teams handle even highly technical challenges?
In fast-changing industries like software or design, teams that are empowered to self-organize often find clever solutions to new problems—because they’re closest to the work and can adapt quickly.
Want to go deeper? The science behind smaller teams
Research consistently shows that smaller teams (usually fewer than ten members) collaborate more effectively. Communication overhead drops, responsibility is clearer, and trust builds more rapidly. In Scrum, this size limit isn’t arbitrary—it’s backed by decades of organizational science and is key to agile success.
At a tech startup, product teams adopted Scrum and were allowed to form groups based on shared work styles. Within months, cross-functional groups naturally emerged, increasing both productivity and job satisfaction. Team members reported greater autonomy and lower turnover—direct results of team customization.
The idea of team customization allows agile workplaces to have more diversity. Organizations with traditional management styles tend to have monolithic teams where everyone follows the same rules. Agile work environments are much like the old salad bowl analogy. Just like salads can have ingredients with wildly different tastes that make a delicious dish, agile product development can have people on teams with very diverse strengths that fit in to make great products.
Think of a time when your team was able—or unable—to set its own rules. How did it impact your work experience?
All high-performing teams need to be managed from the top and follow identical processes.
Scrum teams thrive by customizing their structure and rules, which leads to greater diversity and performance.
- Scrum enables teams to self-manage and make decisions traditionally reserved for managers.
- Team customization and size limits foster autonomy and adaptability.
Reflect on your current or past team experiences and design your “ideal” Scrum team structure.
- List the top three work styles or strengths you value in teammates.
- Describe how you would group people or set team rules to maximize performance.
- Consider how your design would handle both professional and personal needs.
How could the “salad bowl” analogy for agile teams transform your organization’s approach to diversity, skillsets, and collaboration?
What is the primary advantage of self-managed Scrum teams?
Tap to revealThey empower team members to make decisions and set their own rules, increasing autonomy and performance.
How does team customization impact diversity in agile workplaces?
Tap to revealIt allows teams to include members with varied strengths and backgrounds, enhancing creativity and outcomes.
What is the recommended maximum size for a Scrum team?
Tap to revealLess than ten people.
Optimized team structures in Scrum empower teams to self-manage, customize their work environment, and maximize both diversity and performance.
Limiting Scrum teams to fewer than ten people encourages effective collaboration and enhances adaptability in agile product development.
“Just like salads can have ingredients with wildly different tastes that make a delicious dish, agile product development can have people on teams with very diverse strengths that fit in to make great products.”
Which of the following best describes the impact of self-management in Scrum teams?
The Shift
- Self-managed Scrum teams can customize their structure and rules for higher performance and job satisfaction.
- Team customization enhances diversity, enabling teams to leverage varied strengths and perspectives.
- Keeping team sizes small ensures effective communication, adaptability, and trust among members.