How big should a project be before using MS Project Server

W

Wibo

I'm working in a small software company (10-20 people) and my manager
wants me to set up MS Project Server for a project that will take a
year.

I don't have experience with Project Server, but after reading some of
the online documentation I get the feeling this is meant for huge
project's with a lot of resources (hundreds of people).

Can anyone give me some advice ?
How big will the overhead be ?
How much time do you spend on setting up and maintaining the system if
you have to start from scratch ?

any reply or pointers to documentation will be appreciated !

Best regards,
Wibo.
 
J

Jack D.

Wibo said:
I'm working in a small software company (10-20 people) and my manager
wants me to set up MS Project Server for a project that will take a
year.

I don't have experience with Project Server, but after reading some of
the online documentation I get the feeling this is meant for huge
project's with a lot of resources (hundreds of people).

Can anyone give me some advice ?
How big will the overhead be ?
How much time do you spend on setting up and maintaining the system if
you have to start from scratch ?

any reply or pointers to documentation will be appreciated !

Best regards,
Wibo.
Click to expand...

There is a learning curve associated with the software. This is true of
anything, but Project Server utilizes several technologies (SQL Server, Web,
Analysis Services, Sharepoint) so if things don't go right it will require
some skill to get things untangled. If things go right and install perfectly
it is not much of a concern. In a way a smaller group is easier as you do
not need to worry about driving a consistant set of codes and processes
through a large organization. The overhead needs to be balanced against what
you would otherwise do. If your current system is fairly lightweight (and
here I mean in terms of overhead, not in terms of effectiveness) then you
might want to consider not moving to Server. However if you are constantly
working to get updates, produce gantt charts and do analysis then it might
be worth your while. How big the overhead is depends on your skill. You can
reduce it by reading everying about Project Server before you start.

Gary Chefetz has a book out which would be useful in describing what it is
you need to do. Then assess how easy that is for you.



--
Please try to keep replies in this group. I do check e-mail, but only
infrequently. For Macros and other things check http://masamiki.com/project

-Jack Dahlgren, Project MVP
email: J -at- eM Vee Pee S dot COM


+++++++++++++++++++
 
J

JeffG

Hi Wibo-

I also work for a software company. We are a bit larger
(200-300 in our Corp office), we use Project Server 2002
in our Engineering dept to track our software projects. I
would agree with your manager and say it would be worth
your while to invest in MPS. Once the system is up and
running there is little maintance. Only updates to the
project file and changes to resources. We did start from
scratch...we had a consultant come in and help us setup
the server and train a few of us. We have always used
Microsoft Project - but just desktop.

Hope this helps...good luck.

Jeff
 
G

Gary L. Chefetz

Wibo:

Unless you have a specific business driver for this one project that
absolutely requires an application like Project Server to successfully
complete the project, it's difficult for me to see the justification for
implementing it in an organization operating at your scale.

On the other hand, if your manager's goal is to implement the application as
a new way of managing your development process and intends to integrate it
fully into your business, then a mission critical project like the one you
describe certainly helps justify the investment.

With that said, you have two types of overhead to concern yourself with; the
cost of the hardware, software, training and professional services if you
elect to engage them, and the cost to your organization in absorbing the
cultural change.

Your company is at a perfect size to implement and PM strategy that will
carry it through manifold growth cycles, if it can make the commitment.

--

Gary Chefetz [MVP]
http://www.msprojectexperts.com
"We wrote the book on Project Server"

*** Remember to look for line breaks in links posted to the news group, use
cut and paste for these.
 
Top