Transcript Adventure Works 2006 Sales Proposal

FIS Enterprise Solutions
EPK/EPM Implementation
Debbie Bellish, Jon Hale, Truman Hale,
Daun Hugi, Barb Mours
Fidelity National Information Services (FIS)
User’s Meeting January 23-25, 2007
1
Agenda
•
•
•
•
•
Business Situation
Implementation Approach and Schedule
Lessons Learned
Results
Sample Views/Reports
User’s Meeting January 23-25, 2007
2
Business Situation
• Large geographically dispersed resource pool of 750
serving 100+ financial services customer account teams
 Resource staffing requirements/capabilities critical
 Access database utilized for resource staffing
• PMBOK-based project management methodology
 Formalized in 1999 and continuously improved
 Emphasis on scope, time (schedule) and budget management
with software development influences
 Defined project management roles and organization
 Manually intensive report production
 Lotus Notes database for document (including .mpp files),
risk, issue, action item management
• Minimal user Project Server experience
 Other divisions had implemented Project Server
User’s Meeting January 23-25, 2007
3
Business Situation
Project Objectives:
 Integrated project and resource information
 Enhanced capacity and resource planning capabilities
 Presented in automated, user configurable dashboard
views
User’s Meeting January 23-25, 2007
4
Project Team Arrangement
Executive Sponsor
Jon Hale
Project Sponsor
Daun Hugi
Project Manager
Debbie Bellish
Resourcing Practices
Barb Mours
Technical Team
Linda Lander
Training
Scott Berrett
Project Management
Practices
Change Management
Truman Hale
External Consultants
Business Analysts
DBA
User’s Meeting January 23-25, 2007
5
Implementation Approach
• Phased Approach
 Phase 1 - Implement MS Project 2003 Server, MS Project
Professional 2003 and MS Project Web Access (PWA), EPK
Portfolio, EPK Resources, and Enterprise Resource Planning
• Retire Access database
User’s Meeting January 23-25, 2007
6
Implementation Schedule
Initiating & Planning
/ Requirements
7/1
8/1
9/1
6/1/05
9/30/05
Design
10/3/05
11/1
11/16/05
EPK Custom Development/Technical Testing
12/1
11/14/05
1/1
2/1
3/1
4/1
4/14/06
3/10
EPK Group Configuration Review
Report
Development
5/16/06
6/2/06
Process and Training Development
1/1
12/18/05
2/1
3/1
4/1
5/1
6/1
6/30/06
User Acceptance
Testing
4/24/05
6/30/06
Implementation
8/1
User’s Meeting January 23-25, 2007
7/6/06
8/28/06
7
Approach and Schedule
• Phased Approach
 Phase 2 - Implement MS Share Point Team Services
(document management and team information), Rational
(risks, issues, action items, defects) and automated status
reporting
• Retire Lotus Notes tool
 Phase 3 – Implement EPK Time and interfaces to Oracle
Financials
• Retire PlanView
User’s Meeting January 23-25, 2007
8
Lessons Learned
Successes
 Smooth implementation facilitated by:
• Established resource and project management practices
• Heavy user involvement in requirements, testing and support
• Virtual training and job aids, plus live meeting Q&A sessions,
provided on demand training solution for users
• Opportunities/staffing guidelines identified tool best practices
 Change champions facilitated tool adoption
 Inclusion of requirements into EPK core product
 EPK Group configuration review
User’s Meeting January 23-25, 2007
9
Lessons Learned
Challenges
 Virtual team: needed face-to-face interactions at critical
junctures
 Internal project that required significant project
management discipline
 Recreating Access database functionality vs. defining
“real” requirements
 User representatives needed direct line of communication
with EPK Group regarding requirements
 Delayed testing of EPK and lack of understanding of core
functionality led to theorizing about the tool
User’s Meeting January 23-25, 2007
10
Lessons Learned
Challenges
 Integration with corporate HR systems, e.g., PeopleSoft
 Major configuration error (most codes on Project Server vs.
EPK) corrected late in the development cycle
 Lack of resource Requirements visibility in Capacity Center
requires reliance on reports vs. standard EPK functionality
User’s Meeting January 23-25, 2007
11
Results
• Other FIS divisions have adopted (or plan to adopt)
EPK after reviewing the solution
• Increased productivity
 Collocated, refreshed project status and resource
information readily available
• Portfolio visibility for executives and senior
management
User’s Meeting January 23-25, 2007
12
Sample Project Health Views
User’s Meeting January 23-25, 2007
13
Sample Resource Plan
User’s Meeting January 23-25, 2007
14
Sample Project Financial Views
User’s Meeting January 23-25, 2007
15
Sample Capacity Center Views
User’s Meeting January 23-25, 2007
16
Sample Capacity Center Views
User’s Meeting January 23-25, 2007
17
Sample Reports
User’s Meeting January 23-25, 2007
18
Sample Reports
User’s Meeting January 23-25, 2007
19
Sample Reports
User’s Meeting January 23-25, 2007
20
Sample Reports
User’s Meeting January 23-25, 2007
21
Sample Reports
User’s Meeting January 23-25, 2007
22
EPM Information Site
User’s Meeting January 23-25, 2007
23
EPM/EPK Training Solution
User’s Meeting January 23-25, 2007
24
Questions?
User’s Meeting January 23-25, 2007
25