K
Kevin
I am using Project for scheduling and time tracking using the timesheets
feature. As such, there are project tasks and non-project tasks that need to
be tracked using timesheets. For non-project tasks, I've done the following,
as has been addressed in several posts:
1. Add the non-project tasks.
2. Enter an estimated Duration for each task, such as 90 days.
3. Make each task Fixed Duration and non-Effort Driven.
4. Enter an Actual Start date on each task to "lock" the Start date.
5. Add resources to the project team.
6. Assign resources at a Units value that approximates the amount of time
spent in an average day or week on each task (DO NOT enter 0% Units).
7. Publish the project.
The problem that I have with this is that it affects resource leveling. For
example, if I assign a 5-day task for "John Doe" called "Generate Design
Document" from 7/21 to 7/25, but I add a non-project task as described above
for "Ad-hoc Meetings" during the 7/21 to 7/25 week, John will be
overallocated. Resource leveling will push the original task out.
How can I add non-project related tasks to the schedule which are viewable
in the resources timesheet but do not cause over-allocation of resources?
(Keeping in mind that these non-project activities are not 100% predictable,
and so cannot be inserted with fixed dates ahead of time. In the above
example, John Doe will generate the design document in 5 days, regardless of
whether he spends 0, 1, or 2 hours during the week in ad-hoc meetings.)
Thanks,
feature. As such, there are project tasks and non-project tasks that need to
be tracked using timesheets. For non-project tasks, I've done the following,
as has been addressed in several posts:
1. Add the non-project tasks.
2. Enter an estimated Duration for each task, such as 90 days.
3. Make each task Fixed Duration and non-Effort Driven.
4. Enter an Actual Start date on each task to "lock" the Start date.
5. Add resources to the project team.
6. Assign resources at a Units value that approximates the amount of time
spent in an average day or week on each task (DO NOT enter 0% Units).
7. Publish the project.
The problem that I have with this is that it affects resource leveling. For
example, if I assign a 5-day task for "John Doe" called "Generate Design
Document" from 7/21 to 7/25, but I add a non-project task as described above
for "Ad-hoc Meetings" during the 7/21 to 7/25 week, John will be
overallocated. Resource leveling will push the original task out.
How can I add non-project related tasks to the schedule which are viewable
in the resources timesheet but do not cause over-allocation of resources?
(Keeping in mind that these non-project activities are not 100% predictable,
and so cannot be inserted with fixed dates ahead of time. In the above
example, John Doe will generate the design document in 5 days, regardless of
whether he spends 0, 1, or 2 hours during the week in ad-hoc meetings.)
Thanks,