A
AndrewO
Hi All,
My company is early in the process of transitioning from PMs using
stand-alone MPPs in stand-alone local copes of Microsoft Project to a
Project Server and Portfolio Server installation. For background
purposes, you should know that about 50% of the PMs hate MSP all
together, 40% use it at a very basic level, and 10% are Project "power
users."
We have about six major organizational units which each manage the
projects in their own area. So a project manager from the widgets
division, wouldn't have much at all to do with a PM from the mousetrap
division. There are a few corporate resources which are shared
throughout the entire company.
There is a lot of discussion going on about how we should implement
Project Server: half the team say that we should have one corporate-
wide installation of MSPS, the other half are lobbying for multiple
instances - so the widget guys can manage their plans in isolation of
the mousetrap guys. The main sticking point is resources - we will
import our 1500 employee Active Directory into MSPS, and the widget
guys don't want their schedules changing due to something a mousetrap
guy did to a project.
The last wrinkle is our PMO, which has oversight of all the projects
in all the divisions... they will use Portfolio Server to manage
things at a corporate level.
First question: Is there any validity to a multiple instance
installation, or are we crippling ourselves from the beginning using
that approach?
Second question: If we use multiple instances, is it possible for a
single portfolio server to "connect" to multiple project server
instances? Again, the PMO must consolidate data from all the silos we
construct.
Thanks for any thoughts - pointers to blogs - whatever you are willing
to provide.
---Andrew
My company is early in the process of transitioning from PMs using
stand-alone MPPs in stand-alone local copes of Microsoft Project to a
Project Server and Portfolio Server installation. For background
purposes, you should know that about 50% of the PMs hate MSP all
together, 40% use it at a very basic level, and 10% are Project "power
users."
We have about six major organizational units which each manage the
projects in their own area. So a project manager from the widgets
division, wouldn't have much at all to do with a PM from the mousetrap
division. There are a few corporate resources which are shared
throughout the entire company.
There is a lot of discussion going on about how we should implement
Project Server: half the team say that we should have one corporate-
wide installation of MSPS, the other half are lobbying for multiple
instances - so the widget guys can manage their plans in isolation of
the mousetrap guys. The main sticking point is resources - we will
import our 1500 employee Active Directory into MSPS, and the widget
guys don't want their schedules changing due to something a mousetrap
guy did to a project.
The last wrinkle is our PMO, which has oversight of all the projects
in all the divisions... they will use Portfolio Server to manage
things at a corporate level.
First question: Is there any validity to a multiple instance
installation, or are we crippling ourselves from the beginning using
that approach?
Second question: If we use multiple instances, is it possible for a
single portfolio server to "connect" to multiple project server
instances? Again, the PMO must consolidate data from all the silos we
construct.
Thanks for any thoughts - pointers to blogs - whatever you are willing
to provide.
---Andrew