• Save
HP PPM Summit Customer Case - Mining
Upcoming SlideShare
Loading in...5
×
 

Like this? Share it with your network

Share

HP PPM Summit Customer Case - Mining

on

  • 1,154 views

Case study on the deployment and adoption of HP Project and Portfolio Management in a mining client.

Case study on the deployment and adoption of HP Project and Portfolio Management in a mining client.

Statistics

Views

Total Views
1,154
Views on SlideShare
1,154
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment

HP PPM Summit Customer Case - Mining Presentation Transcript

  • 1. Mining Successful AdoptionSteve Jenner – EOH Europe© Copyright 2011 Hewlett-Packard Development Company, L.P. The informationcontained herein is subject to change without notice. Confidentiality label goeshere
  • 2. Agenda• Introduction• Implementation• Roadmap• Challenges• Solution• Lessons Learned2 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 3. EOH at a glance• HP Partner in Europe and South Africa• 3200 employees• JSE listed• Partner with a number of leading technology brands• Consulting – Technology – Outsourcing3 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 4. IntroductionThe so-what test for case studies?• Mining industry (mining, processing and exploration)• Large multinational that has grown by acquisition• Focus on capital projects, not IT• Six Locations • South Africa (HQ, Mine and Smelt) • Australia (Supply and Finance, Mine and Smelt)4 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 5. Business DriversWhy do this?• Global recession and focus on cost saving• History of poor project delivery throughout the group• Project execution: Key targeted improvement area identified for FY09 by Group• No ownership and accountability in projects• Burning need for centralisation and single version of the truth5 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 6. ObjectivesWhat needed to be done• Visibility of full Capital and Business Improvement portfolio (Scattered sources)• Standardisation of methodologies and alignment of all business processes• Single source of all project information (Inbox, shared drives, Documentum)• Alignment across group to facilitate group wide reporting standardisation• Fast response times across all assets (replacing MSP & Excel)6 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 7. ChallengesA few points to overcome• Previous Failures • 2 previous attempts at establishing a single technology for project management • Negative user perception of this type of technology• Response times • Comparison to desktop/laptop hosted MSP and Excel • Dependency on group 1WAN project & remote locations• Culture • South African vs. Australian culture • General Manager has much of the power7 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 8. HistoryFirst the past• Business requirements assessment, RFP process and selection: April – June 2008• PPM Project formally kicked-off 23-24 July 2008 with a requirements confirmation workshop• Initial implementation timeframe based on big-bang assumptions: August 2008 to February 2009• Scope change due to Change Readiness Assessment: November 2008: Extended to June 2009• Go-live on 1 July 2009 on V7.5: Spent year in Stabilisation & Business Adoption8 Phase © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 9. RoadmapNow and Next• Recent • Since 1 July 2010: Optimisation phase • Upgrade to V9.1 planned for March – June 2011• Current • Organisational operational model changes • Support creation of the Projects function• Future • Procurement process integration • OneSAP programme9 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 10. Early Post Implementation Behaviour Usage Proficiency Maturity Month 2 Month 4 Month 6 Month 8 Month 10 Month 1210 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 11. Compliance – Before and After © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice.11 Confidentiality label goes here
  • 12. Success FactorsProject hand over• Ownership of PPM must pass from the project team to the business• A PPM Governance team must be established to own the system and processes• PPM is a cross functional system and must be owned across business functions• The PPM Governance team must ensure that PPM is kept crisp, fresh and alive• Middle management buy-in is key to overcoming project team resistance12 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 13. Success FactorsPost Implementation Assimilation• Assimilation of PPM into the business is imperative to ensure return on investment• Mandating alone will not ensure usage and adoption• Must be driven by leadership• The majority of PPM implementations fail if assimilation activities and behaviour are not followed through13 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 14. Lessons LearnedIf we knew then…• Maturity Assessment is key to understanding project challenges and planning• Manage customer expectations for the Journey (3-5 years)• Manage customer expectations on speed of implementation impact• PPM is not designed to work in a federated/distributed architecture• Simplicity in design is key• Get users to see the benefit in using the application – then add constraints14 © Copyright 2011 Hewlett-Packard Development Company, L.P. The information contained herein is subject to change without notice. Confidentiality label goes here
  • 15. Q&A© Copyright 2011 Hewlett-Packard Development Company, L.P. The informationcontained herein is subject to change without notice. Confidentiality label goeshere
  • 16. Thank you© Copyright 2011 Hewlett-Packard Development Company, L.P. The informationcontained herein is subject to change without notice. Confidentiality label goeshere