how to handle redundant tasks

[claus_f]

Hi,

I'm using Project on a "beginner level" and currently face a problem
Hope I manage to express properly in english.


- The pp for a software development project was derived from
functional scope tree which we created in mindmap.
- The functional tree was clustered logical into multiple branche
and contained certain redundancies which we purposely kept in the tre
to maintain a logical "complete" view
- For example a generic library which needs to be developed once bu
is used 2-3 times in the according context of the developmen
clusters
- We did not use the "link" feature of mindmap.
- Export worked fine


For the project plan i need to find a way how to handle the redundan
tasks. To achieve a certain "readability" of the plan it would be nic
to keep one task for the library where the effort is planned once an
somehow "connect" it to redundant copies of this task not having an
effort but dependencies. I thought about creating a section fo
redundant stuff but when i just link it via dependencies, the logica
view of development cluster is not that obvious since you always need t
jump force and back in the plan to understand a logical cluster.

I hope I managed to express the problem properly and someone has a
(easy) solution

Thnx for your support

 

[JulieS]

Hello claus,

Sorry, there is no method to create multiple copies of the same task
and have them be updated automatically.

My suggestion is to create the "Generic library creation" task and
use the ability of project to add successor tasks as needed. You
can easily view a task's predecessor by splitting the screen to show
the Task Form in the lower pane or if you are using Project 2007,
you can view information in the Task Driver pane.

I hope this helps. Let us know how you get along.

Julie
Project MVP

Visit http://project.mvps.org/ for the FAQs and additional
information about Microsoft Project