---
title: "Grow your \"feature teams\" into just \"teams\""
url: "https://www.5whys.com/articles/grow-your-feature-teams-into-just-teams.md"
canonical: "https://www.5whys.com/articles/grow-your-feature-teams-into-just-teams.html"
published: "2012-05-01T09:36:33+00:00"
updated: "2012-05-01T09:42:21.747000+00:00"
tags: ["Growing People", "Learning Phase"]
author: "Roy Osherove"
description: "Why feature teams built from specialists carry a bad bus factor, and why team leaders should grow them into teams where everyone can do each other's work."
usage: "Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page)."
license: "https://creativecommons.org/licenses/by/4.0/"
---

# Grow your "feature teams" into just "teams"

A feature team, as I see it, is a team consisting of all the people needed to accomplish a released specific feature. So on such a team you might have an architect, a DBA, a coder, a UI guy, a frontend guy etc.. In that case it's important to notice that a team consisting of different specialists is also a team with [a very bad bus factor](https://www.5whys.com/articles/the-bus-factor-why-your-best-developer-is-your-biggest-probl.html).  The team can stop being productive as soon as even one person on the team gets sick for a couple of days. Knowledge is not shared. That's why, in the learning phase, it's important to have a goal to turn feature teams into just "teams" of people who work together, each with the minimal skills to do the work of the others. It takes a lot of time, but growing people, taking them out of their comfort zone, and teaching them new skills, is part of your job as a team leader. As a team leader, you should view feature teams of different specialists as something to grow out of. To be left with only teams of people who can self organize and do the work and have the skills needed to overcome problems such as a person on the team missing. Most organizations don't even have feature teams yet, but as a leader, your vision should strive to have "feature teams" be just a mid-point on the way to teams that share knowledge.

## Read next

- [The architect as a leader, and other specialists](https://www.5whys.com/articles/the-architect-as-a-leader-and-other-specialists.html): Why an architect or any specialist on a team is a bottleneck, and should act as a coaching leader who spreads knowledge until they are no longer needed.
- [The 3 maturity stages of a software team and how scrum fails to identify them](https://www.5whys.com/articles/the-3-maturity-stages-of-a-software-team-and-how-scrum-fails.html): The chaotic, mid-life and mature stages of a software team, the leadership each one needs, from dictator to coach, and why Scrum Masters miss them.
- [Should you grow even a short-term consultant in your team?](https://www.5whys.com/articles/should-you-grow-even-a-short-term-consultant-in-your-team.html): Why a team leader should still grow short-term consultants and temporary team members, treating everyone they lead as if they would stay forever.

## Topic

- [Learning Mode](https://www.5whys.com/topics/learning-mode)


---

## About the author

**Roy Osherove**: Senior Solutions Architect at AWS working on AI for production and AI-driven development; author of The Art of Unit Testing and Elastic Leadership, with about 20 years of consulting and training on unit testing, TDD, team leadership and continuous delivery.

### Sites

- [RobotPaper](https://robotpaper.ai/): This blog: AI patterns and anti-patterns, AI and coding agents, and engineering leadership.
- [osherove.com](https://osherove.com): Roy's personal site. Author of The Art of Unit Testing and Elastic Leadership; consulting and training on unit testing, TDD, team leadership and continuous delivery, plus about 20 years of blog posts.
- [The Art of Unit Testing](https://www.artofunittesting.com): The Art of Unit Testing, 3rd Edition (Manning): readable, maintainable, trustworthy unit tests, plus TDD workshops in C#, JavaScript, Java and Kotlin.
- [5whys.com](https://www.5whys.com): Roy's writing on software team leadership: self-organizing teams, surviving chaos, learning mode and the Elastic Leadership model.
- [Pipeline Driven](https://pipelinedriven.org): Continuous delivery and DevOps practices: build patterns, pipeline-friendly testing, DevOps metrics and enterprise DevOps.
- [Elastic Leadership](https://www.elasticleadership.com): Elastic Leadership, Roy's framework for software team leaders (survival, learning and self-organizing modes).

### Social

- X: https://x.com/royosherove
- LinkedIn: https://www.linkedin.com/in/osherove/

### Contact

- Contact form: https://forms.gle/jQSx5KoXvrVA1JCK7

### License

Licensed under CC BY 4.0 — reuse, quote and adapt with attribution (Roy Osherove, link to the original page). License: https://creativecommons.org/licenses/by/4.0/
