1 / 6

Initial Setup and Testing of EPM 2010 at Intel IT: Key Insights and Challenges

This document outlines the initial setup and configuration of the EPM 2010 environment at Intel IT, led by Scott Stanko, PMP and PMI-SP. Built on MOSS 2010, the basic site was provisioned by server administrators, with a focus on BI and portfolio management, though these features were not utilized initially. Key challenges include workflow creation requiring coding, limitations on project editing without fixed tasks, and the need for Visual Studio 2008 for customizations. Next steps involve pilot testing with a diverse user base to ensure effective deployment.

lowell
Download Presentation

Initial Setup and Testing of EPM 2010 at Intel IT: Key Insights and 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. EPM 2010 at Intel IT Scott Stanko, PMP, PMI-SP, MCITP

  2. Initial Set up • Built on MOSS 2010 SAN • Basic site provisioned by server administrators • BI and Portfolio management built in but not using at this time • Started with test sites on test servers • Recreated each new site • Supposed to be able to export site config but never tried

  3. Site setup • Enterprise fields, views, filters work the same • Created in the same way • No coding changes needs to macros • Custom Project types/detail pages needed to create new projects from web • Minor changes to permissions • Mainly around Project delegates

  4. Gotchas • Work flows sound great but cannot be created without coding • Need Visual studio 2008 or greater • SharePoint designer will not work on PWA • Can edit projects on the web as long as they don’t have any fixed work tasks • Code that calls PSIs will probably need to be recompiled

  5. Gotchascon’t • Custom tool bars are handled differently • Need IE 7 or greater for PWA • Backwards compatibility with 2007 not used as there will be some performance degradation

  6. Next steps • Pilot testing with 40-50 users/projects • Small/large • Geographically diverse • Broad range of experience

More Related