------ Register to get rid of these "In Post" ads! ------


I have 10 projects I am trying to plan for a program for the rest of the
year. The team includes 15 developers. There are about 15 various skill
sets of the developers- but they are not all held by all developers. This is
to say that on certain tasks, I could swap out developers but it depends on
the task.

Right now I am assigning and switching back and forth to resource allocation
and trying to manually level. This is really time consuming. I am wondering
'Original Source: The Code Cage Forums http://www.thecodecage.com/forumz/project-formatting/101209-resource-leveling-among-multiple-projects.html#post360905
if I should be using resource leveling. If I did, should I use the actual
developers names or should I create skill sets with higher % availability.
For example, if I have 3 developers that can do Java development should I
create a "Java Developer" at 300% available and have it level against that?

One of my concerns is that I want the developer who does the development to
do the QA support as well. This is a seperate task within each project (all
projects are in the same plan right now) and I dont want Java Developer A
ultimately assigned to fix Java Developer B's code.

Does this make sense? Is my only recourse manual leveling and adjustments.
I have to run a ton of scenarios and its eatting up a lot of time.

Thanks!