Your SlideShare is downloading. ×
Adventure Works 2006 Sales Proposal
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Adventure Works 2006 Sales Proposal

405
views

Published on


0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
405
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
2
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide
  • Daun
  • Daun Agenda timing: Business situation 7-10 minutes Implementation approach and schedule – 10 minutes Lessons learned – 7-10 minutes Results - 5 minutes Sample views/reports – 15 minutes Q&A – 10-15 minutes
  • Daun
  • Daun
  • Daun
  • Debbie
  • Debbie
  • Debbie
  • Truman
  • Truman
  • Truman
  • Jon
  • Jon We established a “Project Indicator” code (Yes/No) flag field and pre-filter all project views based on this code. This data is maintained by project management staff and used as a dashboard of the portfolio of project health for executives. We also have an automated trigger that runs weekly and populates the Status As of field based on the last time the Health Description was updated. In these screen shots we are suppressing project name information due to client confidentiality Examples of project related views include and are available to all roles Project Health Detail Project Health Summary We also have a few financial related views, which are only available to project managers and management roles. For example: ProForma – All Projects Project Actuals vs. EPK Resource Plan Project Health/Financial Maintenance
  • Jon
  • Jon We also have a few financial related views, which are only available to project managers and management roles. For example: ProForma – All Projects Project Actuals vs. EPK Resource Plan Project Health/Financial Maintenance
  • Jon We have a variety of Capacity Center views, distributed to Resource Management roles. For example: Resource Assignments Assignments by Project
  • Jon
  • Barb
  • Barb
  • Barb
  • Barb
  • Barb
  • Barb
  • Barb Training is available for Resource Management, Project Management and Team Member roles. This allowed for reusable training components, represented as topics or lessons as appropriate for the particular role.
  • All
  • Transcript

    • 1. 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
    • 2. Agenda
      • Business Situation
      • Implementation Approach and Schedule
      • Lessons Learned
      • Results
      • Sample Views/Reports
      User’s Meeting January 23-25, 2007
    • 3. 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
    • 4. 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
    • 5. Project Team Arrangement User’s Meeting January 23-25, 2007 Executive Sponsor Jon Hale Project Sponsor Daun Hugi Project Manager Debbie Bellish Technical Team Linda Lander External Consultants Business Analysts DBA Resourcing Practices Barb Mours Training Scott Berrett Project Management Practices Change Management Truman Hale
    • 6. 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 Complete
    • 7. Implementation Schedule User’s Meeting January 23-25, 2007
    • 8. 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 In Progress – 1Q ‘07 2007 Dates TBD
    • 9. Lessons Learned User’s Meeting January 23-25, 2007
      • 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
    • 10. Lessons Learned User’s Meeting January 23-25, 2007
      • 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
    • 11. Lessons Learned User’s Meeting January 23-25, 2007
      • 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
    • 12. 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
    • 13. Sample Project Health Views User’s Meeting January 23-25, 2007
    • 14. Sample Resource Plan User’s Meeting January 23-25, 2007
    • 15. Sample Project Financial Views User’s Meeting January 23-25, 2007
    • 16. Sample Capacity Center Views User’s Meeting January 23-25, 2007
    • 17. Sample Capacity Center Views 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. Sample Reports User’s Meeting January 23-25, 2007
    • 23. EPM Information Site User’s Meeting January 23-25, 2007
    • 24. EPM/EPK Training Solution User’s Meeting January 23-25, 2007
    • 25. Questions? User’s Meeting January 23-25, 2007