Configuration Check List for MS EPM

[jglowien]

We've just copied over an existing MS EPM2007 instance to make a new one for our department. Actually the work is being done by a 3rd party hosting service. That leaves our project management group to do the 'business configuration'. Is there a recommended checklist of steps for cleaning up and evolving a config. We've ordered several of Gary Chefetz's books to help us get going:

“Managing Enterprise Projects Using Microsoft Office Project Server 2007”
“Implementing and Administering Microsoft Office Project Server 2007”
“Collaborating on Enterprise Projects using Microsoft Office Project Server 2007”

However, the idea of a proven checklist is appealing.

The Forum's thoughts?

[ssanderlin]

Other than the material in the Implementing and Administering book and the content on TechNet, there's really nothing publicly available for this.

In my experience, a successful configuration requires an in-depth knowledge of the product, its capabilities, and its configuration options. Project Server, especially in the area of security, is not very forgiving when it comes to "configuring as you go". It's usually best to get the "big picture" configuration done first, and then perform adjustments as necessary. However, the longer an environment is in service, the more difficult those adjustments can be. Therefore, it's important to vet a configuration through user acceptance testing with use cases before opening an environment to production.