Project Server and Project Online

Project Server and Project Online Implementation 2007/2010/2013/2016

While we have a standard approach to the implementation of PPM and EPM Solutions, PMPi always reviews this approach with clients to ensure we are providing them with the method that meets their specific requirements. Major components of the PMPi approach:

  • Define / review of the client’s requirements.
  • Define / review the client’s business processes and map them to Microsoft Project Server functionality.
  • Define / review the EPM architectural design to ensure hardware and component recommendations support the EPM solution that will be implemented.
  • Perform a complete system installation — Microsoft Project Server, and associated supporting technologies.
  • Configuration of the installed EPM solution components to reflect the client’s specific requirements.
  • Train ALL users — project managers, team members, resource managers, executives — on their EPM solution. This includes both tools, and processes.

During all of the above activities, PMPi actively involves the client’s staff to ensure maximum knowledge transfer. 

Envisioning Workshop/Define Requirements– We conduct brainstorming sessions on site or through Live Meeting with individual and group meetings with selected project managers and IT directors. We will map your current situation and your desired results to drive the configuration of Project Server and to define the best project management process. This will ensure the EPM initiative creates a business-driven solution and make sure there is clear understanding of each section and the stakeholder’s intent. This will provide:

A summary of the business goals

  • General requirements for using the Microsoft EPM solution for Administrators, Project Managers, Team Members and Senior Management
  • Usage scenarios for Microsoft EPM for Administrators, Project Managers, Team Members and Senior Management
  • The general technology requirements for the server(s) and desktops
  • Determination of initiative risks & mitigation strategies, constraints and assumptions

Recommended Project Management Processes
We also develop the following:

Recommended Project Management Process including but not limited to:

  • Definition of a project
  • Recommended Project Management  Process (i.e. Initiating, Planning, Executing/Controlling Closing)
  • Recommend deliverable(s) per step in the Project Management Process (i.e. Customized forms for Scope Document, Risk Plan, Communication Plan, Change Control, etc.  per type of project)
  • Recommended Work flow for project approval and status reviews
  • Recommend content for a PMO site 

Mapping Business Processes to Project Server Functionality – The business process requirements define which processes and standards the organization requires staff to follow so that the organization can accomplish its project management goals. Organizations will vary in their process maturity, ranging from having no standards at all, and through time, to an ability to replicate processes across the organization. It is important to understand where the organization lies along this maturity continuum, as this will determine initiative strategy (a decision to phase in processes), feature implementation, and training requirements.

The EPM team develops a high-level inventory of these processes. This information will include:

  • A description of both the current and desired processes
  • Which of the current processes must be changed based on new Microsoft EPM functionality
  • Which processes are needed to be refined based on new Microsoft EPM functionality

Architect Design and System Installation
 – The architecture design specification describes the hardware and software configuration that must be deployed to support the EPM solution over a designated time period. The goal will be to help determine suitability to the proposed user community and to recommend future best practices to expand the system if needed.

System Implementation
 – the purpose of this phase is to create a Project Server environment.

Develop and Implement Configuration Settings Specification — The purpose of this phase is to determine your organization’s EPM standards. Specific configuration items are:

  • Define and Implement corporate calendar settings — determine the calendar settings that are the basis for resource calendars, used to schedule project work
  • Define and Implement enterprise custom codes to support reporting requirements— determine the company-wide custom codes, both resource and project that need to be created to store information that is not part of the default system
  • Identify and Implement user roles — determine the roles of the system users, as they will appear in Microsoft Office Project Server and Microsoft Project Web App. These are the groups used for security purposes
  • Define and Implement resource settings — determine the resource-related configuration settings. This includes use of generic resources and skill-based resource planning
  • Define and Implement view customization — determine how to best modify the system’s default views and to create custom views to meet the client’s project and resource management information needs

Training & Support

Role-based Training and Coaching: Project Manager, Project Web Access (Team Members and Senior Management), Administrators – our proven effective role-based training programs will be tailored to meet the specific needs based on the configured EPM solution described above. Our training will incorporate the participants’ needs and apply the relevant plans and reports they will use.