In this blog post I’d like to share some of our experiences with fitting the Scrum workflow into a process that has more products than teams.
As with many companies introducing Scrum to their existing teams, implementing the process involves introducing a lot of new concepts and changing the way the team works together. One of the problems we had was that we didn’t have teams aligned with products in a way that allowed us to naturally turn them into agile teams. This is the story about how those teams have evolved since we started out with Scrum.
At KeyIdentity our development team is tasked with managing a lot of separate products. A quick look in our product archive reveals 100 repositories! Thankfully those are not all active, but we regularly commit to about 15 of those. With a team of 10, that does not fit exactly with the concept of self contained agile teams, where each team is working on one product.
We started gradually introducing Scrum in product development a couple of years ago. If you have not heard of Scrum itself, you might want to head over to the Scrum Guide to have a look at what it is all about.
The question that we had to ask ourselves is whether to split the team, and if so, how? We tried a number of approaches: Continue reading 5 ways to organize multi-product Scrum teams