# Evolution of a resource assigned on a task

• ### Question

• Hi everybody,

I'm working on a project on Office Project 2010 right now and I would like to do something but I can't find the solution. Here's the thing :

Example : I'd like to be able to say that a resource is working at 20% on a task for the first seven days, then working at 80% on this same task for few days, and finally at 40% for the last seven days.

I would like to do that because my resources have to work on different tasks at the same time and when a task has ended, I would like to put the potential of working of that ended task on the new one.

Example :

First week : A is working at 40% on task A. A is working at 40% on task B. A is working at 20% on task C.

Second week : The task A ends. I want that A works at 60% on task B and 40% on task C.

Third week : The task B ends. I want that A works at 100% on task C.

I hope you've understood my problem.

Thanks,

Yours faithfully,

Baptiste.

Thursday, November 8, 2012 7:04 PM

• HI,

You can do that in Project, but it's totally manual and you absolutely don't benefit of any calculation from Project.

Asign the resources to the appropriate tasks (at 100%, manual correction follows)

Here you can enter work day by day, resource per resource, task by task.

If I were you, I'd let people always work at 100% at one task till it's finished: you willl see that eveything will end sooner, but if you insist, it's possible.

Greetings,

Thursday, November 8, 2012 9:12 PM
• You have explained what you want to do quite well, and it can be done easily enough, but you have to also consider whether it's worth it and whether the extra trouble has any real payoff, and also whether it is really what you want to do or should be doing for the sake of the project. Projects go faster if a person works on one job at a time until it is finished, as Jan says. If you spread your person across A, B and C, then it must increase the duration of A, or make it take longer than it should/could, so this just delays the point at which person can give full attention to B and C.

I would not do the assignment as percentages. If you are going that far then you may as well input the specific number of hours for each day (task usage view), and if you are doing that then the next step is to specify which particular hours (and minutes) in the day they are going to be. As Jan says, "resource per resource, task by task" and also hour by hour and minute by minute. It's all manual and the more manual it becomes the less automatic calculation you can take advantage of, and the maintenance requirement goes up. Remember, you have to track this later. It also creates problems for leveling.

Thursday, November 8, 2012 10:02 PM

### All replies

• HI,

You can do that in Project, but it's totally manual and you absolutely don't benefit of any calculation from Project.

Asign the resources to the appropriate tasks (at 100%, manual correction follows)

Here you can enter work day by day, resource per resource, task by task.

If I were you, I'd let people always work at 100% at one task till it's finished: you willl see that eveything will end sooner, but if you insist, it's possible.

Greetings,

Thursday, November 8, 2012 9:12 PM
• You have explained what you want to do quite well, and it can be done easily enough, but you have to also consider whether it's worth it and whether the extra trouble has any real payoff, and also whether it is really what you want to do or should be doing for the sake of the project. Projects go faster if a person works on one job at a time until it is finished, as Jan says. If you spread your person across A, B and C, then it must increase the duration of A, or make it take longer than it should/could, so this just delays the point at which person can give full attention to B and C.

I would not do the assignment as percentages. If you are going that far then you may as well input the specific number of hours for each day (task usage view), and if you are doing that then the next step is to specify which particular hours (and minutes) in the day they are going to be. As Jan says, "resource per resource, task by task" and also hour by hour and minute by minute. It's all manual and the more manual it becomes the less automatic calculation you can take advantage of, and the maintenance requirement goes up. Remember, you have to track this later. It also creates problems for leveling.

Thursday, November 8, 2012 10:02 PM