I currently hold a team of 17 all of whom work on delivering single product --Admin UI. The problem with such a big team is Grooming, Standups, dividing works, scaling new team members, handling resignations --I have to do all of them.
So i divided team into 5. And assigned a set of features to each team. Each team is given 1 new guy to rampup over a months time. (Except that, Requirements Grooming happens to all of them together). So major problems are solved. Even if people resign others in the team make sure we dont stop on delivery --meaning, now team is horizontally scalable
The problem comes when requirements come in. The founder says cash dries up in 1month. The client is at the door. Now, if i divide the work by responsibility some resources are hotspotted , some are too free (because client requirements majorly focus on enhancing certain features only) If I go and delegate work to the guy who is free in other team then eventually all 5 teams are becoming one monolith team (and its happening already). Now, the team is not taking ownership of their features (because the other guy from other team did some part of it)
So the question is: How do i handle this situation. Is there a better way to handle it?