Opinions wanted (1)

[James Dixon]

Hi there -

I though I'd cross-post this from project2000 since it's going out of
action, and I'm after as many different opinions on the subject!

One of our managers has come up with two suggestions for using Project,
which I'd like to pose. The second is in another posting to keep threads
separate...

======================================
1. Resource-based vs WBS-based outline.

We have both graphical and technical staff working on the project. A
simplified schedule would be as follows (prop spaced font required. Sorry.
Could have done pictures, but figured it antisocial...)

Milestone 1 V----------------V
Art Staff V----------V
Fred V-------V
Task 1 xxx
Task 2 xxx
Task 3 xxx
Joe V----------V
Task 4 xxxx
Task 5 xx
Task 6 xxxxxx
Tech Staff V----------------V
Jane V----V
Task 7 xx
Task 8 xx
Task 9 xx
Ed V----------------V
Task 10 xxxxxxx
Task 11 xxxx
Task 12 xxxxxxx

Task 1, 4, 9 and 11 could all be part of the same package, a page of a
website, say. So traditionally, the outline would have been:

Website Project
Page 1
Task 1 (design)
Task 4 (script)
Task 9 (artwork)
Task 11 (testing)
Page 2
Task 2
...

The primary advantage is that it allows us to set the deadline on all
summary tasks, so as soon as a resource goes critical, the missed deadline
indicator will appear against their *name* summary task.
It's also easy to look at other staff for that milestone to see who is in a
best position to reassign work to.

The main disadvantage as I see it is that we totally lose any concept of a
WBS. How bad do you guys think this would be?

Thoughts from the professional crowd?

Thanks,
James Dixon.

 

[Dave W]

You are unnecessarily complicating something that is relatively simple. I
don't think I would divide the tasks up by individual. I think it is better
to organize the project so that it flows logically. You can list the tasks
by any individual at any time using the Using Resource filter.

Project
Deliverable1
Activity1
Task1
Task2
Milestone
Activity2
Task1
Task2
Milestone
Deliverable2
..
..
..

 

[Jan De Messemaeker]

???
IMHO in the second method you do not LOSE the concept of WBS, you GAIN it.
The first method is maybe OBS but definitely not WBS.
I prefer the second method, since Project gives me the result from your
first one.
HTH

--
Jan De Messemaeker
Microsoft Project Most Valuable Professional
Project Management Consultancy
Prom+ade BVBA
32-495-300 620

 

[James Dixon]

Agreed. Sorry, wasn't very clear - the second method is what I would have
traditionally done before the new (first) method was proposed at our
company.

I guess the questions has come to how I use Project to show me this
information using a "proper" WBS structure.
i.e:

1. Quickly see a gantt for eah resource (I guess that's just using a filter
for that resource)
2. Quickly seeing *who's* late on a particular milestone
3. Quickly seeing who's got spare slack on a particular milestone for
reassignment

I need clear answers to these to persuade our other managers this is the way
to go. I'll happily play around trying to get examples o convince them!

Cheers,
James.