Logical planning and implementing company's structure in PS 2007

[metkos]

Hi to readers,

I would like to ask for some help regarding Project Server 2007. Help
could be either some link with good examples from real life, link to
some post or few words which will direct me in proper way.

I have a task to prepare everything regarding Project Server which we
would like to evaluate and use if we become satisfied by. Sharepoint
is not used yet, but will be if we start to use Project Server. I read
both planing and deployment MS guides, Sharepoint farm and Project
server are up and running. But a lot of information now confuses me
and I stacked at logical planning and transferring our corporate
hierarchy and needs to Project Server.

Company structure
--------------------------------------------------
To simplify things, company can be described by this example:
1. Management Board (CEO)
2. |_ Technical division
2a. |_ IT department
2b. |_ Networking department
3. |_ Sales and marketing division
3a. |_ sales department
3b. |_ call center department

Each division has it's executive responsible person, each department
has a "department leader" and workers.

Requirements
--------------------------------------------------
List of functional requirements is too long, these are most relevant:

- CEO will not be just like Project's Executive with read permissions,
he would like to manage one or several high-level projects in which he
will deliver and track global tasks to Division's Executives.

- Division Executives will either manage his task or split, collocate
and track tasks to Department leaders, those leaders will further
break those to his stuff.

- Two Division Executives cannot change anything in a part of project
which is not his/her, each one can put tasks only to Department
leaders in his division. Similar is with different Department leaders.

- There will be conditional tasks between divisions/departments, like
situations where task from Sales depends on finished task from
Tehnical division and vice-versa.

- Each Division Executive and Departments would like to maintain
internal projects in which CEO is not interested and other division
and/or departments should not see.

- Use of Project Professional should be minimized, main work will go
through PWA.

- Administration of Project/Sharepoint will be centralized and made by
IT dept. All users are in Active Directory, of course.

Questions
--------------------------------------------------
For example how to achieve requirements in PS for project that will
contain usual ongoing operations:

1. With one huge project, but with all restrictions explained
above (if it is possible at all and how).

2. With several separate projects: CEO (1), Division executives (1
per division) and per Department leaders (for operations and private
ones). Than each executive/leader will have to manually copy tasks
from his chief project to his own and break them down to workers.

Additional, if I put all except workers in "Project Managers" group,
how to deny some of them to read or write other division/department
projects?

I read about categories, multiple site collections and linked
projects, but still I am confused how to start. And doubts like where
to put a project workspace, subsites or collections, RBS confuses
more. Main concern is how to isolate divisions and departments but
with ability for CEO to see everything, executive to manage only his
division etc. Acceptance of Project server as a solution depends on
this proper beginning.

Sorry if these are dumb and/or repetitive questions in this group, I
searched for a while without wished results.

At last, I do not expect that someone learns Project Server instead of
me, certainly that I will study it thoroughly by time. At this moment
I just need few clarifications and advices how to have a good start.

Big thanks in advance!

Metodi D.

 

[Andrew Lavinsky]

Your best bet is to engage a local partner, or to enroll in a training
provider's Project Server classes. There're a number of options online for
training, and that will give you good guidance to get started.

If those options are not available, I'd go build a VPC, buy one (or more) of
the books on Project Server, and start working through it until you feel like
you are comfortable with the options.

 

[metkos]

I will certainly take a serious learning resources or third party, it
is not questionable. But at this point, first goal is to make some
sort of Project Server demonstration to our management and compare it
with other candidate for project management. Then decision of solution
acceptance will come and all following steps (learning, testing,
learning, staging etc.). Unfortunately, time for demonstration setup
is tight and I can not find a good real-life example.

I do not need "click there and there" instruction, just some clever
direction like "several projects are more suitable (per division/
department), make subsites not collections, use custom categories for
that and that, isolate departments by using X and tune
permissions" (imaginable words). Than I will examine those in details.

IMHO, I have pretty good knowledge, skills and longtime experience in
IT field and with many complex systems, PS is a rare case in which I
have to ask for some help despite the reading a guides.

Nevertheless, honest thank you for replying.

Metodi D.

 

[Gary Chefetz]

Metkos:

It doesn't matter how many years of IT experience you have, this one does
not fall into the do-it-yourself category. It's almost like saying that you
can put together a quick SAP demo without any experience at all. Heed
Andrew's advice and engage a local partner for your demonstration.

 

[metkos]

Huh, ok than.
I fully agree with both of you about proper way to do complex
solutions like SAP, Project/Sharepoint, etc. Usually I did that for
various products/vendors (study, certifications or third party, etc.).
I do not even think out to downgrade all required knowledge and
experience. Mine current bad luck is that this time and for reasons X,
I have to try quick "do-it-yourself" technique and see PS in action,
do not ask why or blame me as it is out of my power.

If there is no chance to "shoot" one of the good logical directions
for start, I respect yours words and move on.

Best regards!

 

[Barbara - Austria]

Hi metkos,

ok, I can now imagine your situation. It seems similar to mine when I
was asked to get Procect Central (2000) up and running without any
support in my earlier company. Fortunately there had been less
functionality by then ;-).

Your questions are quite clear, but to answer them would really extend
the scope of this forum. I completely agree with the others that you
will need some support. Nevertheless, to get your requirements
implemented you will need RBS and Categories extensively. Do you at
least have some budget for books? Then have a look at some book like
Gary's at
https://projectdaddy.com/shopdisplayproducts.asp?id=12&cat=Project+and+Project+Server+Books.
If you see the number of pages you will get an idea why it is not
possible to answer your questions here. There are too many possibilties ....

Reading that it will perhaps give you some direction how to work with
RBS and Categories. And help you to get (a simplified) demo.

Success!
Barbara

Am 24.02.2010 12:56, schrieb metkos:

 

[metkos]

That's why we like ladies, straight to the heart

Thank you, my wished answer was like you said with "you will need RBS
and Categories extensively". Now I know where to continue and with
what features I can do my best to get something. Regarding
possibilites, I assume and understand that there are many, I have
asked just for any to start.

Books or budget are not a problem, just short time and "see if you can
do it before event Y".

Big thank you again Barbara,

Best wishes!

Metodi D.