Basic Set Up Question

[spondee]

Am new to really using Project (2000).

I have a number of 'small' tasks with sub-tasks. Each 'set' could be
'projects' in themselves.

Is it better to set up a separate file for each, or to put them all on
one (they do fall under same 'topic'.

(Is there a way to enter a TOPIC/HEADER in a Project file WITHOUT it
being a task???)

If I create a number of different files, is there some way to compare,
consolidate, etc without merging?

Is there someway to insert multiple Project files on the same
calendar? For Tracking or Comparison???

In my 'trials', it does seem 'easier' to manage a small Project file
rather than an intricate, multi-layered, one.

I want to do this 'right' from the get go so I don't run into probs
down the line!

Thanks,

 

[John]

Spondee,
See replies/comments to your individual questions.

I have a number of 'small' tasks with sub-tasks. Each 'set' could be
'projects' in themselves.

What is 'small' in your mind? It is not unusual to have several hundred
or even a few thousand lines (tasks and summary lines) in a single,
manageable project file.

Is it better to set up a separate file for each, or to put them all on
one (they do fall under same 'topic'.

This is really a matter of preference. Some prefer to work with a single
file while others like the idea of several small files that are
consolidated into a master file. Each method has it pros and cons. For
someone new to Project, it is probably a little easier to use a single
project file (again, depending on your definition of 'samll')
particularly if the tasks are all interrelated. If the single file gets
unweildy, it can be broken into two or more individual files at a later
time.

(Is there a way to enter a TOPIC/HEADER in a Project file WITHOUT it
being a task???)

Normally the top level summary line whether manually created (indent all
other tasks under it) or automatically created (Tools/Options/View tab -
check "Project summary task" at the bottom of the Options window).
Summary lines are not normally thought of as "tasks" but rather as
"headers" for the working subtasks under them. However, if you want
additonal text information, you can use the Notes field or any one of
the spare Text fields. You can also go to File/Properties/Summary tab
and enter information about the file.

If I create a number of different files, is there some way to compare,
consolidate, etc without merging?

Yes. You can use the Compare Project versions add-in (see FAQ 36 -
Compare Project versions) at:
http://www.mvps.org/project/faqs.htm
Building a dynamically consolidated master (Insert/Project) does not
merge the subproject files, it simply sets up a series of pointers to
the subproject files and lets you see the subprojects all together.

Is there someway to insert multiple Project files on the same
calendar? For Tracking or Comparison???

Unless otherwise modified, all new projects start with the same default
calendar. If each individual project file has a different calendar there
are probably several ways to track and compare them. It depends on what
you are looking for.

In my 'trials', it does seem 'easier' to manage a small Project file
rather than an intricate, multi-layered, one.

Again, this is mostly a matter of preference.

I want to do this 'right' from the get go so I don't run into probs
down the line!

There is no one 'right' way to create a file structure and don't worry
about getting everything just right. One thing that is constant with a
project plan - it will need to be changed/updated on a regular basis
because nothing ever quite works as planned.

Hope this helps.

John

 

[spondee]

Hope this helps.

Tremendously! Thank you! I'll play w/this for a couple of days, then
probably will be back!!!

 

[John Beamish]

The only problem I can see with putting all projects into a separate file is
that it is then difficult to generate meaningful EV reports. Of course, if
the projects are small then EV reports might not be of much value.

As for the indentation you described, that should work well. A judicious
use of "Insert | Page break" will -- generally -- let Spondee start new
project reports on a new page.

 

[John]

spondee,
Great, that'w what the newsgroup is all about.

John