How many concurrent projects can a senior handle?
I am trying to find sensible resource-allocation models for developers. The department will have many different projects for different external customers, so I need to make some guidelines in order to avoid people getting angry due to lack of focus, not working on things they want to, etc. 

Currently I have suggestion for a model: 

- Junior developers – will only work on one project at a time (reason: mainly that they are unable to control their own time use)
- Intermediate developers – will mostly work one project at a time for 50 % or more, but might be 50-50 on two projects
- Senior developers – will work at the most on 3 projects at a time; percentage can be e.g. 50 %, 30 % and 20 %. 

It’s the seniors that I am worried about. As the customers might want to buy a junior-group only, I need to provide them with a mentor (senior) to make sure they have the knowledgeprogress and the aid that they need (someone with experience and knowledge about their project). A group of 5 juniors will get a senior at 50 % of the time. 

The question is – can a senior handle 3 projects at a time (he will be hired with this in mind – I will not trick someone to believe that they will write code 100 % of the time and end up with 20 %), or is this too much? 

I have a feeling that 2 projects is way better that 3? Or? What if the senior is needed 50 % on the “junior-project” and 30 % on analysis and design on another project. Can he handle one more project with the last 20 %? 

(And no – time for training, coffee, etc. will not be part of the 100 %. I have already reduced the “real” amount of working hours with that in mind). 

How many concurrent projects can a senior handle?
===

I am trying to find sensible resource-allocation models for developers. The department will have many different projects for different external customers, so I need to make some guidelines in order to avoid people getting angry due to lack of focus, not working on things they want to, etc. 

Currently I have suggestion for a model: 

- Junior developers – will only work on one project at a time (reason: mainly that they are unable to control their own time use)
- Intermediate developers – will mostly work one project at a time for 50 % or more, but might be 50-50 on two projects
- Senior developers – will work at the most on 3 projects at a time; percentage can be e.g. 50 %, 30 % and 20 %. 

It’s the seniors that I am worried about. As the customers might want to buy a junior-group only, I need to provide them with a mentor (senior) to make sure they have the knowledgeprogress and the aid that they need (someone with experience and knowledge about their project). A group of 5 juniors will get a senior at 50 % of the time. 

The question is – can a senior handle 3 projects at a time (he will be hired with this in mind – I will not trick someone to believe that they will write code 100 % of the time and end up with 20 %), or is this too much? 

I have a feeling that 2 projects is way better that 3? Or? What if the senior is needed 50 % on the “junior-project” and 30 % on analysis and design on another project. Can he handle one more project with the last 20 %? 

(And no – time for training, coffee, etc. will not be part of the 100 %. I have already reduced the “real” amount of working hours with that in mind). 
