1 / 5

Best Practices for EPM Deployments: Cultural and Process Challenges

This guide outlines essential best practices for deploying Enterprise Project Management (EPM) systems, emphasizing that successful deployment is more about culture and process than technology. Key recommendations include fostering communication, taking manageable steps, securing Project Manager and Executive buy-in, and the importance of a Proof of Concept and User Acceptance Testing (UAT). It stresses the need for well-thought-out configurations, user-friendly design, proper training, and the value of pilot projects, as well as practical management of technological resources and dependencies.

kyle
Télécharger la présentation

Best Practices for EPM Deployments: Cultural and Process Challenges

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. MPUG – October 2008 Ian Radcliff

  2. Standard Best Practice for EPM Deployments • Don’t be a “techie” - EPM deployments are a cultural and process challenge, not a technical one • Don’t keep the deployment a secret - communicate widely, deeply, often, across different media • Don’t be ambitious – take easy steps, each with clear wins, towards an agreed long term vision • Don’t go it alone - Project Manager buy-in and Executive drive is vital • Don’t be idealistic – work around, work with, work for, negotiate, ... • Don’t forget a Proof of Concept and full UAT – the middle steps can seem “hidden” to many stakeholders

  3. Standard Best Practice for EPM Deployments • Don’t over configure – focus on what is needed not what is possible, but capture task level data early in the deployment • Don’t rely on user text input – use drop –down lists, use must-fill, use defaults, use formulae, avoid naming conventions • Don’t forget training – method, functionality and then process • Don’t undervalue the pilot project(s) – choose with care, a valuable and visible project, adaptable team • Don’t be mean with kit – memory , disk space, testing platforms, minimums are just that, SharePoint will grow! • Don’t believe everything you read (apart from Christophe’s blog) - not everywhere is like Microsoft....

  4. Recent “Challenges” • WSS templates – work hard for Day1 , changing may not be easy later on • Keep workflows simple – manage expectations, parallel tasks are a “challenge” • Manage the “server” –close plans “properly” , look for pending check-ins, teach users to clean the cache • Dependencies – use “soft” and not “hard” links • Reporting database – be aware of what it can and cannot support • Tasks and timesheets – try Codeplex approach, task status maybe enough • Implement the ability to absorb Cumulative Updates (every two months)

More Related