I tried to do this in the late 90s with a team I lead. The plan was for an A and B team. The A team (did the theme song spring into your head?) would work on

I tried to do this in the late 90s with a team I lead. The plan was for an A and B team. The A team (did the theme song spring into your head?) would work on new features and the B team would do bug fixes in existing code. The teams would switch roles back and forth each month with the idea that the team that just released something would be the logical bug fixers when it went into production. The main problem with it was cross-polination -- ideally you want the teams to mix up every iteration but that breaks the follow on bug fixing period. I think we made it 3 months before it collapsed due to conflicting outside schedule pressure I couldn't control.