I thought of doing exactly what Dale suggested and have in the past). While
it is a practical way to do it, there is one MAJOR flaw. If the multiple
task items are not the same duration (in the real world they probably would
not be) you will have allocation problems when one of the task it complete
and the others are still being worked on. For example, if you have 5 task
and assign each task at 20% allocation, then if task “A†is done first, the
other 4 tasks should be now allocated at 25% (in theory), but Project will
not do this for you automatically, so you end up having to manually re-adjust
the allocations. This can be a maintenance nightmare for large projects.
Using resource leveling or even setting up dependencies is far more easier to
manage.
Dale - I understand you were answering the question and not necessarily
recommending this as a solution. So I am not disagreeing with you, just
warning the person who asked that if you do use this method, be aware of the
issues.
Dale - I understand you were answering the question and not necessaerily
recomending your solution. So I am not disagreeing with you, just warning the
person to asked that if you do use this method.