Is project 2k3 server overkill for a medium sized company?

[Steven Seim]

Hello.

I'm looking to learn if Project Pro is sufficient for my needs, or should I
go with Project Pro -and- Project server.

I have a need to share project artifacts across global teams, to push to
SharePoint, and have teams contribute through standard (ITIL) change
management practice.

Do I need only one copy of server for the entire company? Would one copy of
project pro per business unit do what I need?

I could use some advise. It is my understanding that even in many large
corporations, Project Server is considered overkill.

Aside from this post, I can be reached at:

(e-mail address removed)

I am located in the Redmond Washington area. A quick phone call or meeting
is an option, if appropriate.

Many thanks to you.

Steven

 

[Rod Gill]

One copy of Project Server is fine. Larger organisations may have several
copies where they have independent divisions, each with their own project
office.

You need one copy of Project Professional for each project manager to
schedule their projects with and one CAL for each person who is going to use
Project Web Access which is the web interface displayed using IE5.5+

Project Server returns the best value when you are operating at a high 3
level of project management maturity or higher. Saying Project is overkill
in a large organization is possibly to say we don't do resource management,
manage issues and risks or share much project data: this is maturity level 2
or less behavior!

 

[Steven Seim]

Thank you Rod.

I'm getting the impression that with Project server and Project Pro,
projects can be generated such that they create a web presence in SharePoint,
that at the same time grants access to parties outside the company that
generated the project to begin with.

If I have this right, this would be useful to project managers that are not
very technical.

Am I on track here? If so, this would be overhead savings to a point.

Thanks

Steven
(e-mail address removed)

 

[Rod Gill]

Yes the project can be published to Project Web Access (based on SharePoint
Services) but you do have to be careful and follow recommended architecture
to make the whole system secure over the Internet.

 

[Steven Seim]

Understood Rod, and thanks.

Issues associated with publishing can likely be covered through training.
As a second step, it might be wise to push the project to MIS/OPs folks
first, and let them guarantee security and rights before posting.

Now for installation and configuration: on a scale of 1 to 10, where 10 is
expert, our companies MIS/OPs group would rate a 4.5. Given the scalability
and complexity of the Project server, SharePoint and SQL combo, my guess is
that we should hook up with a consultant type post purchase.

Many thanks to you

Steven

 

[jlarscheid]

If you use the Project Publisher for Microsoft Office Project utility it can
Publish and Update Microsoft Project tasks, project and resource information
to and from SharePoint. You also can publish multiple Microsoft Project
plans to a single SharePoint site so you can create lightweight EPM solutions
around the SharePoint platform.

They have a free 30 trial at http://www.projectpublisher.com