Superior task, where start date and end date defines the earliest start and the latest date of subor

[Ebbe]

I am trying again. Now WITH a subject


Hi

I have some tasks that has to be executed within a time span defined by a
start date and an end date.

I want to see a superior (Level 1) task, where start date and end date
defines the earliest start date and the latest end date of all subordinate
(Level 2) tasks. If I accidentally go beyond the bound dates given by the
superior task the tasks should be marked specially or a warning should pop
up.

Have anyone "out there" an idea how I solve this problem?

In the very end I am going to write a VBA-macro, that create both the
superior task and the subordinate tasks.
Then it is only manual work to push and pull the subordinate tasks to fit in
the superior time span.

Using: MS Project prof 2003
Ebbe

 

[John]

I am trying again. Now WITH a subject


Hi

I have some tasks that has to be executed within a time span defined by a
start date and an end date.

I want to see a superior (Level 1) task, where start date and end date
defines the earliest start date and the latest end date of all subordinate
(Level 2) tasks. If I accidentally go beyond the bound dates given by the
superior task the tasks should be marked specially or a warning should pop
up.

Have anyone "out there" an idea how I solve this problem?

In the very end I am going to write a VBA-macro, that create both the
superior task and the subordinate tasks.
Then it is only manual work to push and pull the subordinate tasks to fit in
the superior time span.

Using: MS Project prof 2003
Ebbe

Ebbe,
Well, I personally think you are going about it wrong but then, that's
just my opinion. It sounds like you are trying to "force" Project to act
the way you want instead of allowing it to be an application that
facilitates the planning and scheduling of a project. The "superior"
task you describe is exactly what a summary line is in Project, but,
Project summary lines only reflect the subtasks, they do not drive them.
You are trying to drive them by imposing a duration limit on the summary
line and Project just doesn't work that way.

I suggest you let Project do what it is best at and that is to help plan
and maintain a dynamic schedule. Virtually every plan has limits as far
as how much time is available, when certain things need to be done and
how much money is available to execute the plan. The best plan structure
is one that describes the tasks in a realistic timeframe (estimated
duration) and logical sequence of performance (linked schedule).
Deadlines can be set (Deadline field) and baselines can be set
(baselines fields) to help monitor how the scheduling is doing - is it
on track or not. If it is, great. If it is not, analysis can be
performed to determine where the problems are so they can be address by
revising the plan (e.g. re-plan the effort, assign more resources, etc.).

Project has multiple tools for analyzing schedule performance. Earned
value metrics can be used. Critical path analysis can be used. Graphical
indicators can be used. If necessary, analysis can be performed with
formulas in custom fields or with VBA.

I don't know if this helps, but I wanted to at least attempt to direct
you toward a more conventional approach to planning and executing a
schedule.

John
Project MVP