Discussion Locked

MS Project Server 2003

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am looking to implement MS Project Server 2003 in the PMO. To do so I have to submit a business case to my executive presenting the benefits such an implementation would have. Therein lies the rub. What benefits are there to be realised and more importantly, how do you quantify them?
Has anyone had recent experience of this and if so, how did you justify the implementation?
Thanks

4 replies

by douglascoulter

Alister

I have previously implmented a MS Project Server implementation for a large NGO (charitable org) here in Ottawa. This organization has branch offices in NFLD N.B. , MB., Sask., and B.C.. These users connect to terminals servers in either Ottawa or Toronto (permanent VPN connection between these 2 cities). All users have access to the Project Server via terminal services.

The immediate benefits is that all users can access project notes, add comments, participate in the planning, development, and execution of current, or future projects.

The CFO, CEO, project co-ordinator can advise, update, make requests or post replies to comments, material in a particular project.

Project server is an excellent tool to allow multiple users, people to participate in all aspects of an organizations project management. This is esspecially beneficial and cost effective if there are branch offices in different area of the country. Reduction in travel, longdistant telephone costs. People can work in their own time zone and still stay in touch. Much easier than sending copious amounts of email to several users on a constant basis to keep everyone updated. This in itself can consume a large amount of a persons valuable time.

Douglas Coulter
douglascoulter@hotmail.com

by mwfrench

When I created a business case for a similar project, I went to Microsoft for some of the literature they use to sell the products. While I don?t advocate you using their documents wholesale, it will give you ideas of how this product will meet identifiable needs in your company.

The most important thing to include in your report is how implementing this product will align with company strategic goals.

As for making a quantifiable report, look at what you are hoping to gain:
- By having a shared database you can alleviate some of the time wasting project meetings to check on the status of the project.
- You can have a link posted on your intranet for the management level staff to get real time project status on all of the projects that they are responsible for, thus allowing them to correct problems sooner thereby saving time and money for the company

Look for free research papers on Gartner and Forrester that talk to quantitative benefits for Project server. Good luck in developing your report.

by andrew.berger

When we implemented Project Server, it was for one MAIN purpose and many lesser.

The main purpose was to TRACK all of the work (which was way too much). Once all projects were identified, we could prioritize and more effectively track them and the resources they were using. We had 17 known projects but could only work effectively on 6 at a time.

The SharePoint side of Project Server was a very nice surprise for collaboration. With or without Project Server, the addition of SharePoint really helped us work together online.

Best of Luck!

This discussion is closed to new replies.