206490 implementation best practice

Oracle Primavera
Implementation Best
Practices
David Goodrich
PGBU Project Manager

Oracle Primavera Implementation Best
Practices
 OUM
 Burning Platforms
 The Contract
 User Adoption
 Risks & Issues

OUM
 It’s a methodology with an expansive library of tools for assisting
project managers with implementing Oracle products and technologies
 Based on industry standards such as:
– PMBOK
– Unified Process
– Business Process Modeling
 Comprehensive toolkit that supports PPM solutions, Application
implementations, Software upgrades, or Tools and Techniques
 OUM creates standardization for how you organize and manage your
projects
Oracle’s Unified Method

OUM
 Volumes of processes, plan templates, use cases and forms.
 All are applicable to Requirements Driven implementations, Solution
Driven implementations, Software Upgrades, Technology Full Cycle
projects, BI or EPM implementations, etc.
How does it benefit me?

OUM

Burning Platforms
 It’s imperative that you understand why your
client is implementing a new solution
 More often then not, the pain of remaining the same is greater then
making a change
 Typically procurement or “non-Business” people purchase the
Primavera software
 Change causes stress
Why has your client decided to do this work?

Burning Platforms
Organization Change Leadership
Define the
Change
Assess the
Climate
Identify Change
Approach
Generate
Sponsorship
Develop Target
Readiness
Create
Cultural Fit
Build Agent
Capacity
Develop
Reinforcement
Strategy
Build
Communication
Plan
Prioritize
Action
Envision
ImplementManage

Contracts
Transpose Contract SOW into Project Plan
 The contract is the official statement of work
 Use the scope and deliverables of the SOW
 Develop a project charter
 Review the role of the PM and team members
 Simple projects – P6 schedule and resource histogram
 More complicated projects – Use OUM content
 We’re not professional athletes

Contracts
Transpose Contract SOW into Project Plan

User Adoption
 Our experience shows that a narrow set of functionality used by a wide
set of people promotes adoption much quicker
 Learn to roll over before you crawl and then crawl before you walk
Wide but shallow

Risks and Issues
 Identify risks early and monitor them often
 Communication is critical to every project’s success
 Management would rather know about a risky project early than be
blindsided with bad news without any news
 Standard risks can be as simple as resource availability, sponsorship
for change, mandatory completion dates.

Build a Risk Register in P6

 Use standard methodologies to ensure repeatable success
 Understand the key reasons for why you are making changes
 Understand the contract terms inside and out
 Recognize user adoption issues and be prepared to address OCL
 Identify risks and issues early
 Communicate, communicate, communicate
Wrap up

Questions ?

206490 implementation best practice

More Related Content

What's hot (19)

Similar to 206490 implementation best practice (20)

More from p6academy (20)

Recently uploaded (20)

206490 implementation best practice