You have six teams using a traditional method to deliver a product. Your management has asked you to start using Scrum. In the initial project there were separate plans and teams for the layers of a software system, i.e. one for the frontend, one for the middle tier, one for the back-end, and one for the interfaces and services. This resembles what is known as component teams. But you have read that it’s a good idea to have teams organized by feature. What are the advantages of keeping component teams while starting Scrum?

Component teams generally have the skills needed to create a working Increment of software that provides business value. There’s less initial disruption than organizing into new teams. As they start, they will discover what works best, and how to potentially re-organize towards this. Because they have worked together for some time, they are likely able to start producing shippable Increments faster that new feature teams would. There are fewer cross-team dependencies than working in feature teams.

---