Re: Linked tasks - LOST LEVELS!!!

Hi John;

sorry for the delay, things got a little hairry here....
I've responded to select portions of your reply:

John wrote:
> In article <1112369659.289438.124700@xxxxxxxxxxxxxxxxxxxxxxxxxxxx>,
> hsn@xxxxxxxxxxxxx wrote:
[snip]
> > 2) Each sub-project is then consolidated into the "master" project
by
> > COPYING the tasks - no linking, no copy/link, just a raw
consolidation
> > of the tasks. During this process the "master project manager"
(which
> > in our case is more than 1 person), will organize a "full project"
> > outline, and place & consolidate tasks appropriately.
> You do NOT have to use copy/paste to create a master from the
separate
> files. As a matter of fact that is a very inefficient method. Rather,
if
> you do NOT want the original individual files to remain active after
> they are initially uploaded to the master (i.e. statically
consolidated
> master), then go to Insert/Project and in the Insert window that
appears
> uncheck the "Link to project" option at the bottom of the window.
Then
> select all the subprojects and "Insert". Basically, it will create a
> single file of all the subprojects at that point in time. That master

> can then be manipulated (e.g. eliminate duplicate tasks, link
dependent
> tasks, etc.).
>
> If you really want to use static master, (I still think a dynamic
master
> is a better approach), then the Program Manager needs to designate
ONE
> person to be the "curator" of the master file. Otherwise the "too
many
> cooks" rule will apply. Now, there's nothing wrong with a big "come
to
> grips" meeting to get everybody's input when the master is built and
> tweaked to be the working file, but in the end, only one person can
be
> the user of the master file.

Very good point - I often overlook those small, but important
checkbox's "hidden" (only from my rush thru the screen) "down below".

My first preference is still to have a dynamic master. So I guess I
would like to have you elaborate on what that is and how to do it.
Here's my experience and why I went static:

I'm assuming a dynamic master would use linked, inserted sub-projects.
When I tried doing this, we setup dependancies using the
{sub-project_name}\task# convention in the dependancy box.

When people took home their sub-projects, and returned; needless to say
all the dependancies were completely out-to-lunch.

Is there a way around this, or am I using the wrong approach?

> >
> > 3) Dependancies are now linked, and if one manager wants to "keep
> > tabs" on a task or group of tasks that they have little or nothing
to
> > do with - they assign themselves as a "1%" resource. This allows
> > managers to filter the [full] project and see ONLY the things that
they
> > own, or have interest in.
> This is an unnecessary complication and does not reflect what you
> intend. Do NOT keep tabs on unrelated tasks by artificially assigning
a
> resource. Bad idea. A much better and simpler approach is to assign
each
> CAM a spare flag field, (or a coded spare number field could also be
> used), and then set the flag for all those tasks that are of interest
to
> the CAM. A simple filter can be used to show just those tasks.

A VERY obvious solution I overlooked!!! TX

[snip]
> > While I now believe this to be the best solution for our problem -
I
> > must point out, it's the best solution AVAILABLE TODAY. I still
believe
> > that project isn't the right tool in our situation, and I'm sure
many
> > others (short of any significant upgrades). (I'm really complaining
> > about #'s 3 & 4 here - so maybe 1 of you will tell me I'm full of
it -
> > which would make me very happy!)
> Wrong. Project is designed for creating, tracking and managing
schedule
> plans - big or small. No upgrades are needed for what you need, its
> already there and has been since Project was first introduced years
ago.
> What did you have for breakfast? That's the only thing you are full
of
> :-)

OK - no argument from me! :)

> Just because you are having a difficult time getting your arms
> around Project and the best way to use it in you situation, doesn't
mean
> you are off base. Far from it. Rather, you are just another user who
is
> struggling to learn a not-so-user-friendly tool. In my opinion
learning
> to use Project effectively is a long term (i.e. years) proposition.
Oh
> sure, you can take a crash course or be taught by "experts" but
> comprehension and effectiveness takes hands on experience and a lot
of
> it. Most of the MVPs have been using Project for years and at least
for
> this MVP, I'm still learning.

Here, my intention was not to speak with authority, but to expose my
perspective. I was hoping to be proved wrong, and was really looking
for that to happen. I'm the first to admit I'm not a project guru... As
I reread my reply I can see how I missed getting that across...

[snip]

The excluded portions of your reply, I'm in much more agreement than
not.

Again, as always, appreciative for your time and interest!
Ned.

.

Relevant Pages

  • Re: Corrupted Project 2002 master plan
    ... After looking at the master project, there are some links on summary lines. ... lead to corruption. ... With respect to converting the dynamic master with separate subprojects, ... opening the master plan recently, I received one of the typical Microsoft ...
    (microsoft.public.project)
  • Re: Project settings
    ... according with tha start date of the master. ... When creating a static master be aware that the individually inserted ... subprojects lose their identity. ... When creating a dynamic master, the subprojectdo not actually become ...
    (microsoft.public.project)
  • Re: Unmaster a master project
    ... like it to no longer be a master project. ... master with inserted subprojects. ... If the subprojects have external links between them, ... can simply break them and re-establish them once the dynamic master is ...
    (microsoft.public.project)
  • Saving a Dynamic Master Project
    ... When saving a Dynamic Master I receive the following message: ... project has inserted projects that are present as inserted projects in other ... Since each subproject is only linked to a single master, ...
    (microsoft.public.project)
Loading