My current team is quite technically young (close to all of us have less than a year presence in my company), in the software framework that my company is using.
The person who has the most experience in that framework, has one-year and half experience and has no prior work experiences, except than this one.
The rest of the team is gone or is working on different projects.
Yet we have projects to deliver.
I have discussed with my CTO but also with the team about the best way to organize this and I think honestly, this is the optimal way, having think about it again and again.
The idea is to make everyone contribute with what they know e.g the senior guy who has the techincal knowledge of the framework but not great software-work experiences and one of our new guy who has great software skills-experiences but no great knowledge of the platform. That means putting on hold until ready the idea of feature teams.
Yet someone from an other team came up with this idea, that I disagree with
- Putting our 'senior' person on the coding and asking the rest of the team to work on more minor projects work until they have the necessary skills.
As said earlier, the aim is to create feature teams, each team who will have a good/great contributor and also to train people to get them on the train. And also to deliver the projects we have at hand.
The question is the following and is more of a way to say "convince me that I'm wrong":
Has anyone tried with a new team, to create feature teams when "Putting our 'senior' person on the coding and asking the rest of the team to work on more minor projects work until they have the necessary skills." ?