Oracle Unified Method (OUM) Overview Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands

10/12/2013

How Implementing is like an OR Eating Contest Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands

1 10/12/2013

Of course, everyone wants to succeed

2 10/12/2013

Steve had a plan for winning Prepare

Eat Prepare Fast Assess Risks Prioritize Approach

Assess Risks Prioritize

Partition Space Determine Order Brain Freeze

Solids

Liquids

3 10/12/2013

Approach

Eating contests and IT projects are similar Program Agenda

Oracle Global Methods Philosophy Prepare Vision, Goals, Benefits Assess Risks Structure and Principles Partition and Prioritize Build it Up – Don’t Tailor it Down Adopt a winning approach An Iterative Approach OUM Implement Core Workflow

4 10/12/2013

Program Agenda

Enterprise Application Support Oracle Unified Method Partitions Oracle Global Methods Iteration Groups Philosophy Applying Partitions and Iteration Groups OUM Customer Program Summary / For More Information / Q&A

Oracle Methods Philosophy Oracle Methods are Based on industry standards and field experience Oracle Unified Method Iteratively developed through a continuous, evolutionary Vision, Goals, and Benefits process

Highly scalable to support project or program specific requirements

Tailored through method views, tools, and guidance

5 10/12/2013

Oracle ® Unified Method (OUM) Vision Oracle Unified Method (OUM) Goals

Single body of knowledge Support the entire Enterprise IT Lifecycle, Standardsbased, yet progressive including support for the successful Product and technology agnostic implementation of every Oracle product Support supplemental guidance

Tight integration between enterpriselevel and projectlevel processes

OUM Benefits

Common language Oracle Unified Method Renovate implementation processes Structure and Principles Assimilate acquisitions

Reduce duplication

6 10/12/2013

OUM Focus Areas OUM’s Core Principles Implement Business Process Envision Software Engineering & Use CaseDriven OUM Software Implementation Enterprise Business Analysis OUM Enterprise Flexible Iterative & Architecture Envision Implement & Scalable Envision Implement Incremental IT Portfolio Management Manage Manage Governance Project and Program Management Organizational Manage RiskFocused ArchitectureCentric Change Aligned with Project Management Management Institute (PMI)

Flexible & Scalable Views From the OUM Method Overview – Purpose • Tailor OUM for various project types ““DoDo not serve the method, make it serve you””you • Isolate core materials “Just Enough Documentation” • Point to relevant supplemental guidance “OUM must be scaled to fit your project” “Just Enough Ceremony” Examples • RequirementsDriven Apps Implementation “Build it up. Don’t tailor it down.” • SolutionDriven Apps Implementation • Software Upgrade • Business Intelligence and Analytics

7 10/12/2013

Supplemental Guidance

Guidance specifically related to “The Oracle Unified Method (OUM) is the CIO’s handbook.” Oracle Tutor, UPK, Business Intelligence & Products – Tools – Technologies Enterprise 2.0 & Knowledge Pathways Analytics Webcenter Project Approach – Architectural Style

Application Siebel Customer Gary Marshall Integration Relationship CIO, Taconic Farms, Inc. Architecture (AIA) Management

Application Service Oriented Implementation Architecture (SOA)

OUM is Highly Scalable Build it Up—Don’t Tailor it Down 1

Oracle Unified Method 1. Start from a core set of tasks. Build it up. Don’t Tailor it Down.

1Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner

8 10/12/2013

OUM is Highly Scalable OUM is Highly Scalable Build it Up—Don’t Tailor it Down 1 Build it Up—Don’t Tailor it Down 1

1. Start from a core set of tasks. 1. Start from a core set of tasks. 2. Add tasks as you identify scope and risk. 2. Add tasks as you identify scope and risk. 3. Consider the depth to which you will execute specific tasks.

– Tasks are placeholders for work .

– They are highly scalable.

1Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner 1Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner

OUM is Highly Scalable Build it Up—Don’t Tailor it Down 1

1. Start from a core set of tasks. Oracle Unified Method 2. Add tasks as you identify scope and risk. An Iterative Approach 3. Consider the depth to which you will execute specific tasks. 4. Combine tasks and work products.

– Define “just enough” documentation

1Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner

9 10/12/2013

OUM Implement Phase Structure Still Looks Kind of Like a “Waterfally”

Inception

Elaboration

Inception Elaboration Construction Transition Production Construction

Transition

Production

But it’s not intended to be used that way Build Implementation Plan

Inception Based on estimates and experience

Elaboration Project Workplan Implementation Plan Inception Elaboration Construction Transition Production Add OUM Implement phases Project Execution and Control Transition Inception Elaboration Construction Transition Production Production Project Project Startup Closure

10 10/12/2013

Divide Phases into Iterations Iteration length may vary Implementation Plan Based on type of work Iterations determined at outset of project 2 – 3 weeks – Simple configuration (i.e. cloud, solutiondriven) Based on initial estimate – Custom application development 2 to 6 weeks in length 4 – 6 weeks Refined as project progresses – Complex modeling Culminate in a “release” of – Complex or extensive configuration materials or software for inspection – Complex extension or custom development by the business

Build Implementation Plan Divide Phases into 26 week Iterations Project Workplan Implementation Plan Project Execution and Control

Inception Elaboration Construction Transition Production Project Iteration 1 Iteration 1 Iteration 2 Iteration 3 Iteration 1 Iteration 2 Iteration 3 Iteration 4 Iteration 1 Iteration 1 Project Startup Closure

Oracle Unified Method } OUM IMPLEMENT CORE WORKFLOW 2–6 Weeks

11 10/12/2013

Implement Core Workflow Each Box Represents a Few Tasks

Configure Configure

“Setups” “Setups” Business Data Structures Document Map Document Map Objectives Integrate Test Objectives Integrate Test Requirements Requirements Requirements Requirements Application Setups

“Gaps” Business and “Gaps” System Context Conceptual Integrated System Test System Results Analyze & Diagram Prototype Analyze & System Implement Objectives Implement Design Design Components Mapped Components System Components Components MoSCoW List Business Integration Test Requirements Results Data, Behavior, Physical Future Process Functional and UI Analysis Database Model Prototype Design Data, Behavior, Implemented Domain Model Gap and UI Design Components Resolutions Logical Assembled Use Case Database Components Model Design Software Use Case Component Descriptions Design 45 Copyright © 2012, Oracle and/or its affiliates. All rights reserved. 46 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.

Workflow Represents One Iteration Workflow is Repeated in Every Iteration

Inception Inception Elaboration Construction

Iteration 1 Iteration 1 Iteration 1 Iteration 2 Iteration 1 Iteration 2 Iteration 3 LO LA IOC

12 10/12/2013

Construction Shifting Emphasis Reaffirm Objectives Refine Requirements Refine Configuration Elaboration Design Reaffirm Objectives Implement Capture Detailed Requirements Integrate Oracle Unified Method Perform Mapping Inception Test Enterprise Application Configure Confirm Objectives Analyze Support Capture Business Requirements Develop Prototypes Perform Initial Mapping Develop Prototypes

Main Focus

Less Focus

Little Focus

BusinessProcess Driven Two Implementation Views

• Requirementsdriven

• Solutiondriven

13 10/12/2013

Analyze gaps with use cases or user stories Support for agile project management

Use Case Details: Order Skis Predictive Adaptive Actor Does System Does Traditional Agile 1.The customer 2.The system Plandriven Unplanned selects the skis checks the Disciplined Undisciplined that he wishes availability of to order. 3. The 4. The use case customers ends when

Partitioning

Splitting functionality to be implemented in a project Oracle Unified Method into smaller pieces Partitions Look for – – High cohesion within a partition – Low coupling between partitions

14 10/12/2013

Partition Some Partitioning Examples

Inception Elaboration Construction Transition Production Defined part of the total functionality to be implemented May be implemented – – Serially – In parallel – Staggered

Partitioning before Inception Partition before Inception Execute in Parallel Execute Serially Partition2 Partition1 Inception Elaboration Construction Transition Production

Partition 1

Inception Elaboration Construction Transition Production Inception Elaboration Construction Transition Production

Inception Elaboration Construction Transition Production

Partition 2

15 10/12/2013

Partitioning after Inception Partition after Inception Execute Serially Execute in Parallel

Elaboration Construction Transition Production

Inception

Inception Elaboration Construction Transition Production Elaboration Construction Transition Production

Elaboration Construction Transition Production

Partition after Inception Partition after Inception Staggered Execution Execute in Parallel with Single Transition to Production

Elaboration Construction Transition Production Elaboration Construction

Inception Inception Transition Production

Elaboration Construction Transition Production Elaboration Construction

16 10/12/2013

Partition after Elaboration Partition after Elaboration Execute in Parallel Staggered Execution

Construction Transition Production Construction Transition Production

Inception Elaboration Inception Elaboration

Construction Transition Production Construction Transition Production

Projects May Be Divided into Many Partitions Whatever Makes Sense for the Project Situation

Inception Elaboration Construction Transition Production Inception Elaboration Oracle Unified Method Iteration Groups Inception Elaboration Construction Transition Production

Inception Elaboration Construction Transition Production

17 10/12/2013

Iteration Group A Set of Functional Requirements (use cases) Definition Assess Service Requests Log Service Requests by Helpdesk Subset of the requirements of Pay Suppliers Risk Log Service Request by a system (or of a partition) Plan Customer Visits Customer Order Parts

Select User Preferences Loan Rate Scanner Accept Service Requests Replan Customer Visits Make Loan Prioritized and Payment Notify Parts Available Customer Apply for A Loan Dependency Priority Apply for Update Service Requests grouped by Mortgage Register Employee Provide Restock Service Cars Review Credit Loan for Details Approval Register Customer Signoff Service Requests

Complexity Invoice Service Requests Automatic SignOff Register Supplier Service Requests

Grouped by Functional Area Apply Prioritization Techniques

Planning HR Service Backoffice Planning HR Service Backoffice Log Service Request by Log Service Request by Assess Service Requests Register Employee Assess Service Requests RegisterRisk Employee Helpdesk Helpdesk

Plan Customer Visits CRM Accept Service Request Plan Customer Visits CRM Accept Service Request

Register Customer Register Customer Automatic SignOff Automatic SignOff Replan Customer Visits Replan Customer Visits Service Request Service Request Customer Dependency Register Supplier Priority Register Supplier Update Service Request Update Service Request Logistics Logistics

Order Parts Financials Order Parts Financials Services Web Services Web Pay Supplier Pay Supplier Notify Parts Available Pay Supplier Notify Parts Available Pay Supplier Complexity Invoice Service Request Invoice Service Request Restock Service Cars Signoff Service Request Restock Service Cars Signoff Service Request

18 10/12/2013

Grouped by Priority into Iteration Groups Why iterate and partition?

Iteration Group 1 Iteration Group 2 Iteration Group 3

Register Employee Invoice Service Request Restock Service Cars Break down complexity Assess Service Requests Automatic SignOff Register Customer Order Parts Service Request Manage risk Plan Customer Visits Register Supplier Notify Parts Available Pay Supplier Earlier return on investment Update Service Request Log Service Request by Replan Customer Visits Helpdesk Demonstrate business value Signoff Service Request Accept Service Request Pay Supplier Inhibit scope creep

Change Requests for Change Requests for Increment 1 Increment 2

One business flow. No custom software HighLevel Implementation Plan

Oracle Unified Method Using Partitions and Inception Elaboration Construction Transition Iteration Groups High Level Configure Configure System Processes Flow A Flow A Testing

19 10/12/2013

Two business flows. Single Partition. Two business flows. Parallel Partitions. Configuration work done in parallel

Inception Elaboration Construction Transition

Inception Elaboration Construction Transition Configure Configure System Flow A Flow A Testing Configure Configure High Level Flow A Flow A System High Level Processes Testing Processes Configure Configure Elaboration Construction Transition Flow B Flow B Configure Configure System Flow B Flow B Testing

Two business flows. Two Staggered Partitions. Two business flows. Two Serial Partitions. Single Inception Phase Single Inception Phase

Inception Elaboration Construction Transition Inception Elaboration Construction Transition Elaboration … High Level Configure Configure System High Level Configure Configure System Configure Configure Processes Flow A Flow A Testing Processes Flow A Flow A Testing Flow B Flow B

Elaboration Construction Transition

Configure Configure System Flow B Flow B Testing

20 10/12/2013

Two (or more) business flows. Serial Partitions. One Business Flow. Minor Custom Extensions Separate Inception Phases Only one Custom Iteration Group

Inception Elaboration Construction Transition Inception Elaboration Construction Transition Inception Elaboration Configure High Level Configure Configure System High Level Configure Configure …… Flow A Processes Flow A Flow A Testing Processes Flow B High Level Flow A Processes Custom Custom Custom IterationIteration Iteration Group 1 Iteration Group Group Group System Testing

One Business Flow. Minor Custom Extensions One Business Flow. Major Custom Extensions Another Approach

Inception Elaboration Construction Transition

Inception Elaboration Construction Transition High Level Configure Configure Processes Flow A Flow A High Level Configure Configure System Processes Flow A Flow A Testing Custom Custom Custom IterationIteration Iteration Group 1 Iteration Group 1 Group 1 Group 1 Custom Custom Custom Elaboration Construction Transition Iteration Iteration Iteration GroupIteration 2 Group Group 2 2 Group 2 Custom Custom Custom Iteration Custom Custom Custom IterationIteration Iteration Group 1 Iteration Group Group Group Iteration Iteration GroupIteration 3 Group Group 3 Group 3 3 System System System System Testing Testing Testing Testing

21 10/12/2013

Many business flows. Many business flows. Done Serially Two Releases per Flow. Staggered

Iteration Group 1

Iteration Group 2

Iteration Group 3

Iteration Group 1 Iteration Group 1 Iteration Group 1 Iteration Group 1 Iteration Group 2 Iteration Group 2 Iteration Group 2 Iteration Group 2 Iteration Group 3 Iteration Group 3 Iteration Group 3 Iteration Group 3

Iteration Group 1

Iteration Group 2

Iteration Group 3

Global Design. Site by Site Deployment. Using the “Two Step” Approach. Per Partition Per Partition

Iteration Group 1

Iteration Group 1 Iteration Group 2 Global “Design” Global “Design” Iteration Group 2 Iteration Group 3 Iteration Group 3

Site A Deployment Site A Deployment Create global design – Include only necessary

customizations and integration Site B Deployment Site B Deployment Deploy site by site – Include only unique customizations and localizations Site C Deployment Site C Deployment

22 10/12/2013

Everybody wants to go “Vanilla” But it’s hard to attain

Start with standard industry business processes wherever possible Oracle Unified Method Customize only for competitive differentiation Customer Program – Not “that’s the way we’ve always done it.” Create Governance process with criteria for customizations – At the global level – At the site level Ensure adherence to the governance process – Pay attention to ensure that escalations are not inhibiting the speed

OUM Customer Program Training, Adoption, and Tailoring No Cost access to OUM Additional Resources

Available as a benefit of consulting engagement of two weeks or longer OUM Implement Core Workflow Licensed for internal use, in perpetuity OUM Tailoring Guide – White Paper including in Method Pack Includes three year, renewable access to updates Online Level 1, 2, and 4 Training available – free of charge Instructorled Level 3 Gathering Requirements (2 day) Adoption services available to work with Customer to tailor OUM for a single project or for a set of “typical” projects

23 10/12/2013

Steve Knew How to Win

Prepare using a two level plan Partitions Iteration Oracle Unified Method Groups

Summary Two Level Assess and address risks, Plan complexity, dependencies

Solids Partition and Prioritize Iterative Implementation Liquids

Take small bites

For More Information

General Questions search.oracle.com Oracle Unified Method – [email protected] Oracle Unified Method For More Information – [email protected] – oum[email protected] Social Media – OUM on LinkedIn (Oracle Unified Method group) – OUM on Twitter (#OUM_info) – OUM Blog (blogs.oracle.com/oum)

24 10/12/2013

Q&A