Short and Long period Tasks or Projects

[Dip]

Hello,

I have a schedule that has about 20 short term projects summaries (1-2
weeks), and about 10 long term projects (2-4 months). From a planning point
of view, is it better to put all these together on the same sheet or to
separate into 2 different files ?

Any comment would be appreciated.

Dip

 

[John]

Hello,

I have a schedule that has about 20 short term projects summaries (1-2
weeks), and about 10 long term projects (2-4 months). From a planning point
of view, is it better to put all these together on the same sheet or to
separate into 2 different files ?

Any comment would be appreciated.

Dip

Dip,
Are the tasks related in a logical sequence? If so, then they should all
be in the same file. If the tasks are not related logically, then it's
up to the user to structure the file in whatever format is easiest to
track and maintain.

John
Project MVP

 

[Dip]

Hi John,

Thank you! Most of the projects are unrelated except that some of them have
a finish-to-start predecessor. I could arrange them in a ascending or
descending order by date, I suppose! But is there are any preferred way as to
know who would be out of work (90% job completion) soon ?

Dip

 

[John]

Hi John,

Thank you! Most of the projects are unrelated except that some of them have
a finish-to-start predecessor. I could arrange them in a ascending or
descending order by date, I suppose! But is there are any preferred way as to
know who would be out of work (90% job completion) soon ?

Dip

Dip,
You're welcome. We're getting into a bit of semantics here. You talk
about "projects" and "projects summaries", when I think you really mean
"tasks". A "project" is an overall plan. It normally contains many
summary lines under which are grouped performance tasks that describe
the detail of the work to be done to complete the plan.

Task relationships (i.e. predecessors/successors) should only be between
performance tasks, not between summary lines. It's not clear exactly
what you have.

As far as seeing which resources will be "out of work soon", you can
look at the Remaining Work field on the Resource Usage view.

Hope this helps.
John
Project MVP

 

[Jan De Messemaeker]

Hi,

John no doubt meant the remaining availability field.

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
+32 495 300 620
For availability check:
http://users.online.be/prom-ade/Calendar.pdf

 

[John]

Hi,

John no doubt meant the remaining availability field.

Jan,
No, I in fact meant the Remaining Work field. I guess the Remaining
Availability field (timescaled data only) could be used depending on how
the user wants to view the "out of work" parameter.

John
Project MVP

 

[Dip]

Hi John,

That is pretty much how it is here. My projects are actually tasks. I have
added a column in both the gantt and the resource usage to view the
"remaining work" so that I would know in advance when a resource would "run
out" of work.

Thanks a lot.

Jan, I tried to add the "available from" column as well but it does not show
anything ("N/A").

Thanks.
Dip