how implementing is like an or - doag.org

10/12/2013

1

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.1 Copyright © 2012, Oracle and/or its affiliates. All rights reserved.2

Oracle Unified Method (OUM) Overview

Jan Kettenis

Oracle Global Methods

Oracle Consulting Netherlands

Copyright © 2012, Oracle and/or its affiliates. All rights reserved.3

OR


How Implementing is like an Eating Contest

Jan Kettenis

Oracle Global Methods

Oracle Consulting Netherlands

10/12/2013

2



Of course, everyone wants to succeed*

10/12/2013

3


Steve had a plan for winning

�Prepare

�Assess Risks

�Prioritize

�Approach


Prepare

�Eat

�Fast


Assess Risks

�Space

�Brain Freeze


Prioritize

�Partition

�Determine Order

LiquidsLiquids

SolidsSolids

10/12/2013

4


Approach


So*


Eating contests and IT projects are similar

�Prepare

�Assess Risks

�Partition and Prioritize

�Adopt a winning approach


Program Agenda

� Oracle Global Methods Philosophy

� Vision, Goals, Benefits

� Structure and Principles

� Build it Up – Don’t Tailor it Down

� An Iterative Approach

� OUM Implement Core Workflow

10/12/2013

5


Program Agenda

� Enterprise Application Support

� Partitions

� Iteration Groups

� Applying Partitions and Iteration Groups

� OUM Customer Program

� Summary / For More Information / Q&A


Oracle Unified Method

Oracle Global Methods Philosophy


Oracle Methods Philosophy

� Based on industry standards and field experience

� Iteratively developed through a continuous, evolutionary process

� Highly scalable to support project or program specific requirements

� Tailored through method views, tools, and guidance

Oracle Methods are*



Vision, Goals, and Benefits

10/12/2013

6


Oracle® Unified Method (OUM) Vision

Support the entire Enterprise IT Lifecycle,

including support for the successful

implementation of every Oracle product


Oracle Unified Method (OUM) Goals

� Single body of knowledge

� Standards-based, yet progressive

� Product and technology agnostic

� Support supplemental guidance

� Tight integration between enterprise-level and

project-level processes


OUM Benefits

�Common language

�Renovate implementation processes

�Assimilate acquisitions

�Reduce duplication



Structure and Principles

10/12/2013

7


Manage� Project and Program

Management

� Aligned with Project

Management

Institute (PMI)

Implement� Software Engineering

� Software ImplementationOUMOUMOUMOUMOUMOUMEnvision� Enterprise Business

Analysis

� Enterprise

Architecture

� IT Portfolio

Management

� Governance

� Organizational

Change

Management

Envision Implement

Manage

OUM Focus Areas


OUM

Envision Implement

Manage

Business Process

& Use Case-Driven

Risk-Focused

Iterative &

Incremental

Flexible

& Scalable

Architecture-Centric

OUM’s Core Principles


Flexible & ScalableFrom the OUM Method Overview –

““Do not serve the method, make it serve youDo not serve the method, make it serve you””

“OUM must be scaled to fit your project”“OUM must be scaled to fit your project”

“Build it up. Don’t tailor it down.”“Build it up. Don’t tailor it down.”

“Just Enough Documentation”

“Just Enough Ceremony”


Views

Purpose

• Tailor OUM for various project types

• Isolate core materials

• Point to relevant supplemental guidance

Examples

• Requirements-Driven Apps Implementation

• Solution-Driven Apps Implementation

• Software Upgrade

• Business Intelligence and Analytics

10/12/2013

8


Guidance specifically related to

Products – Tools – Technologies

Project Approach – Architectural Style

Supplemental Guidance

Application Implementation

Application Implementation

Application Integration

Architecture (AIA)

Application Integration

Architecture (AIA)

Oracle Tutor, UPK,

Knowledge Pathways

Oracle Tutor, UPK,

Knowledge PathwaysBusiness Intelligence &

AnalyticsBusiness Intelligence &

AnalyticsEnterprise 2.0 &

Webcenter

Enterprise 2.0 &

Webcenter

Siebel Customer Relationship Management

Siebel Customer Relationship Management

Service Oriented Architecture (SOA)Service Oriented Architecture (SOA)


“The Oracle Unified Method (OUM) is the CIO’s handbook.”

Gary MarshallCIO, Taconic Farms, Inc.



Build it up. Don’t Tailor it Down.


OUM is Highly Scalable

1. Start from a core set of tasks.

Build it Up—Don’t Tailor it Down1

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

10/12/2013

9




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.







3. Consider the depth to which you will execute specific tasks.

4. Combine tasks and work products.

– Define “just enough” documentation





An Iterative Approach

10/12/2013

10


OUM Implement Phase Structure

Inception Elaboration Construction Transition Production


Still Looks Kind of Like a “Waterfall-y”

Inception

Elaboration

Construction

Transition

Production


But it’s not intended to be used that way;


Inception

Elaboration

Construction

Transition

Production


Project WorkplanProject Workplan

Build Implementation Plan

� Add OUM Implement phases

Based on estimates and experience

Implementation PlanImplementation Plan

Project

Startup

Project

Startup

Project Execution and ControlProject Execution and Control

Project

Closure

Project

Closure

InceptionInception ElaborationElaboration ConstructionConstruction ProductionProductionTransitionTransition

10/12/2013

11


Divide Phases into Iterations

� Iterations determined at outset of project

�Based on initial estimate

�2 to 6 weeks in length

�Refined as project progresses

�Culminate in a “release” of

materials or software for inspection

by the business

Implementation Plan


Iteration length may vary

� 2 – 3 weeks

– Simple configuration (i.e. cloud, solution-driven)

– Custom application development

� 4 – 6 weeks

– Complex modeling

– Complex or extensive configuration

– Complex extension or custom development

Based on type of work


Project WorkplanProject Workplan

Build Implementation PlanDivide Phases into 2-6 week Iterations

Implementation PlanImplementation Plan

Project

Startup

Project

Startup

Project Execution and ControlProject Execution and Control

Project

Closure

Project

Closure

InceptionInception ElaborationElaboration ConstructionConstruction ProductionProductionTransitionTransition

Iteration 1 Iteration 1 Iteration 2 Iteration 3 Iteration 1 Iteration 3 Iteration 4 Iteration 1Iteration 1Iteration 2

}

2–6 Weeks


OUM IMPLEMENT CORE WORKFLOWOracle Unified Method

10/12/2013

12


ObjectivesDocument

Requirements

Configure

Map

Requirements

Analyze &

Design

Components

Integrate

Implement

Components

Test

“Setups”“Setups”

“Gaps”“Gaps”

Implement Core Workflow


ObjectivesDocument

Requirements

Configure

Map

Requirements

Analyze &

Design

Components

Integrate

Implement

Components

Business and

System

Objectives

Business Data

Structures

Application

Setups

Integrated

System

System Test

Results

System

Integration Test

Results

System Context

Diagram

Future Process

Model

Domain Model

MoSCoW List

Use Case

Model

Use Case

Descriptions

Mapped

Business

Requirements

Gap

Resolutions

Conceptual

Prototype

Functional

Prototype

Data, Behavior,

and UI Analysis

Data, Behavior,

and UI Design

Software

Component

Design

Logical

Database

Design

Physical

Database

Design

Implemented

Components

Assembled

Components

Test

“Setups”“Setups”

“Gaps”“Gaps”

Each Box Represents a Few Tasks


Workflow Represents One Iteration

Inception

Iteration 1

Inception

Iteration 1


Workflow is Repeated in Every Iteration

Inception

Iteration 1

Inception

Iteration 1

Construction

Iteration 2 Iteration 3Iteration 1

Construction

Iteration 2 Iteration 3Iteration 1

IOCIOC

Elaboration

Iteration 1 Iteration 2

Elaboration

Iteration 1 Iteration 2

LOLO LALA

10/12/2013

13


Shifting Emphasis

Inception

� Confirm Objectives

� Capture Business Requirements

� Perform Initial Mapping

� Develop Prototypes

Inception

� Confirm Objectives

� Capture Business Requirements

� Perform Initial Mapping


Elaboration

� Reaffirm Objectives

� Capture Detailed Requirements

� Perform Mapping

� Configure

� Analyze


Elaboration


� Capture Detailed Requirements

� Perform Mapping

� Configure

� Analyze


Construction


� Refine Requirements

� Refine Configuration

� Design

� Implement

� Integrate

� Test

Construction


� Refine Requirements

� Refine Configuration

� Design

� Implement

� Integrate

� Test

Main Focus

Less Focus

Little Focus



Enterprise Application Support


Business-Process Driven


• Requirements-driven

• Solution-driven

Two Implementation Views

10/12/2013

14


Analyze gaps with use cases

Use Case Details: Order Skis

Actor Does System Does

1.The customer

selects the skis

that he wishes

to order.

2.The system

checks the

availability of*

3. The

customers*

4. The use case

ends when*

or user stories


AdaptivePredictive

Support for agile project management

AgileUnplanned

Undisciplined

TraditionalPlan-driven

Disciplined



Partitions


Partitioning

�Splitting functionality to be implemented in a project

into smaller pieces

�Look for –

– High cohesion within a partition

– Low coupling between partitions

10/12/2013

15


Partition

�Defined part of the total functionality to be implemented

�May be implemented –

– Serially

– In parallel

– Staggered


Some Partitioning Examples



Partition 1Partition 1

Partition 2Partition 2

Partitioning before InceptionExecute in Parallel




Partition before InceptionExecute Serially

Partitio

n 2

Partitio

n 2

Partitio

n 1

Partitio

n 1

Inception Elaboration Construction Transition Production Inception Elaboration Construction Transition Production

10/12/2013

16


Partitioning after InceptionExecute Serially

Inception Elaboration Construction Transition Production Elaboration Construction Transition Production


Partition after InceptionExecute in Parallel

Inception

Elaboration Construction Transition Production



Partition after InceptionStaggered Execution

Inception




Partition after InceptionExecute in Parallel with Single Transition to Production

Inception

Elaboration Construction

Transition Production


10/12/2013

17


Partition after ElaborationExecute in Parallel

Inception Elaboration

Construction Transition Production



Partition after ElaborationStaggered Execution





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







Iteration Groups

10/12/2013

18


Iteration Group

�Subset of the requirements of

a system (or of a partition)

�Prioritized and

grouped by*

Definition

Customer

Priority

Customer

Priority

RiskRisk

DependencyDependency

ComplexityComplexity

Review Review

Loan forLoan for

ApprovalApproval

Select User Select User

PreferencesPreferences

Make Loan Make Loan

PaymentPayment

Apply for Apply for

MortgageMortgage

Apply for Apply for

A LoanA Loan

Loan Rate Loan Rate

ScannerScanner

Provide Provide

Credit Credit

DetailsDetails


A Set of Functional Requirements (use cases)

Assess Service RequestsAssess Service Requests

Plan Customer VisitsPlan Customer Visits

Re-plan Customer VisitsRe-plan Customer Visits

Invoice Service RequestsInvoice Service Requests

Pay SuppliersPay Suppliers

Order PartsOrder Parts

Notify Parts AvailableNotify Parts Available

Restock Service CarsRestock Service Cars

Register EmployeeRegister Employee

Register CustomerRegister Customer

Log Service Request by

Customer


Customer

Automatic Sign-Off

Service Requests

Automatic Sign-Off

Service Requests

Log Service Requests by

Helpdesk

Log Service Requests by

Helpdesk

Update Service RequestsUpdate Service Requests

Accept Service RequestsAccept Service Requests

Sign-off Service RequestsSign-off Service Requests

Register SupplierRegister Supplier


Grouped by Functional Area

HRHR

LogisticsLogistics

PlanningPlanning








CRMCRM



FinancialsFinancials

Pay SupplierPay Supplier

Invoice Service RequestInvoice Service Request

Service BackofficeService Backoffice


Helpdesk


Helpdesk

Accept Service RequestAccept Service Request

Automatic Sign-Off

Service Request

Automatic Sign-Off

Service Request

Update Service RequestUpdate Service Request

Services WebServices Web


Sign-off Service RequestSign-off Service Request


Apply Prioritization Techniques

Customer

Priority

Customer

Priority

RiskRisk

DependencyDependency

ComplexityComplexity

HRHR

LogisticsLogistics

PlanningPlanning








CRMCRM



FinancialsFinancials



Service BackofficeService Backoffice


Helpdesk


Helpdesk


Automatic Sign-Off

Service Request

Automatic Sign-Off

Service Request


Services WebServices Web



10/12/2013

19

Grouped by Priority into Iteration Groups







Helpdesk


Helpdesk




Iteration Group 1

Increment 1Increment 1






Iteration Group 2

Change Requests for

Increment 1

Change Requests for

Increment 1

Increment 2Increment 2


Automatic Sign-Off

Service Request

Automatic Sign-Off

Service Request


Iteration Group 3

Change Requests for

Increment 2

Change Requests for

Increment 2

Increment 3Increment 3Copyright © 2012, Oracle and/or its affiliates. All rights reserved.75

Why iterate and partition?

�Break down complexity

�Manage risk

�Earlier return on investment

�Demonstrate business value

� Inhibit scope creep



Using Partitions and Iteration Groups


One business flow. No custom softwareHigh-Level Implementation Plan

Inception

High Level High Level

ProcessesProcesses


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition

10/12/2013

20


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

Inception Elaboration Construction


ProcessesProcesses

Configure Configure

Flow AFlow A System System

TestingTesting

Configure Configure

Flow AFlow A

Configure Configure

Flow BFlow B

Configure Configure

Flow BFlow B

Transition


Two business flows. Parallel Partitions.

Inception


ProcessesProcessesElaboration Construction

Configure Configure

Flow BFlow B

System System

TestingTesting

Configure Configure

Flow BFlow B

Transition


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition


Two business flows. Two Staggered Partitions.Single Inception Phase

Inception


ProcessesProcesses


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition


Configure Configure

Flow BFlow B

System System

TestingTesting

Configure Configure

Flow BFlow B

Transition


Two business flows. Two Serial Partitions.Single Inception Phase

Inception


ProcessesProcesses


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition Elaboration …

Configure Configure

Flow BFlow B

Configure Configure

Flow BFlow B

10/12/2013

21


Two (or more) business flows. Serial Partitions.Separate Inception Phases

Inception


ProcessesProcesses


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition Elaboration

Configure Configure

Flow BFlow B……

Inception


ProcessesProcesses


One Business Flow. Minor Custom ExtensionsOnly one Custom Iteration Group

Inception Elaboration Construction


ProcessesProcesses

Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition

Custom Custom Iteration Iteration GroupGroup






Iteration Group 1Iteration Group 1


One Business Flow. Minor Custom ExtensionsAnother Approach

Elaboration Construction Transition

Inception


ProcessesProcesses


Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Transition

System System

TestingTesting









One Business Flow. Major Custom Extensions

TransitionConstructionInception Elaboration


ProcessesProcesses

Configure Configure

Flow AFlow A

System System

TestingTesting

Configure Configure

Flow AFlow A

Custom Custom Iteration Iteration Group 1Group 1


















System System

TestingTesting

System System

TestingTesting




10/12/2013

22


Many business flows.Done Serially











Many business flows.Two Releases per Flow. Staggered











Global Design. Site by Site Deployment.

� Create global design

– Include only necessary

customizations and integration

� Deploy site by site

– Include only unique customizations and

localizations

Per Partition

Global “Design”

Site A Deployment

Site B Deployment

Site C Deployment





Using the “Two Step” Approach.Per Partition




Global “Design”

Site A Deployment

Site B Deployment

Site C Deployment

10/12/2013

23


Everybody wants to go “Vanilla”

� Start with standard industry business processes wherever possible

� Customize only for competitive differentiation

– 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

But it’s hard to attain



Customer Program


OUM Customer Program

� Available as a benefit of consulting engagement of two weeks or longer

� Licensed for internal use, in perpetuity

� Includes three year, renewable access to updates

No Cost access to OUM


Training, Adoption, and Tailoring

� OUM Implement Core Workflow

� OUM Tailoring Guide – White Paper including in Method Pack

� Online Level 1, 2, and 4 Training available – free of charge

� Instructor-led 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

Additional Resources

10/12/2013

24



Summary

Iterative Implementation

Two Level Plan

Iteration Groups

Partitions


Steve Knew How to Win

� Prepare using a two level plan

� Assess and address risks,

complexity, dependencies

� Partition and Prioritize

� Take small bites

LiquidsLiquids

SolidsSolids



For More Information


For More Information

�General Questions

– [email protected]



�Social Media

– OUM on LinkedIn (Oracle Unified Method group)

– OUM on Twitter (#OUM_info)

– OUM Blog (blogs.oracle.com/oum)

search.oracle.com


10/12/2013

25


Q&A


how implementing is like an or - doag.org

Documents