It seems that the toughest questions have the fewest words.
From a simple, technical point of view:
1. If you are simply rolling out a piece of software to let people create
and maintain plans then you need Project Standard. This will do
everything they need to do to maintain those plans.
2. If you are rolling out software to let a few people create and
maintain plans and you want others to either/both (i) view the plans and
(ii) update the plans with the actual hours they worked then you want to
look at Server plus Project Pro (for the people who will be creating and
maintain the plans) and CAL (Client Access Licenses) for the people who
will be viewing the project plans and/or entering time against those
plans. You will also need a Win2003 Server and SQL Server and a few other
related pieces of software to hook it all up.
If you start to go down the second path, be warned: you do not install
Project Server, you implement it. (To others reading this: yeah, yeah, I
know -- technically you are just doing a bunch of installs on the
server(s) and desktop(s) and, yes, it is possible to do the installs and
walk away.)
In reality, you will only get the full benefits of Server if you organize
your project management and your corporate data requirements to harness
the power of Server. The collaborative aspects and the corporate-wide
view and management of projects that Server supports need considerable
pre-installation thought.
I am about to purchase a large number desktops installations (~100) and
am
looking from some input from the folks out there on the benefits
(technically and financially) between the two products.
Does it make sense to implement the server and have all users connect
back
to this to update project plans. Do you have any experience in this.
Thanks
--