10/12/ Copyright 2012, Oracle and/or its affiliates. All rights reserved. Oracle Unified Method (OUM) Overview

Size: px

Start display at page:

Megan Stanley
6 years ago
Views:

1 (OUM) Overview Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands 1 2 OR How Implementing is like an Eating Contest Jan Kettenis Oracle Global Methods Oracle Consulting Netherlands 3 4 1

2 6 Of course, everyone wants to succeed 8 2

3 Steve had a plan for winning Prepare Prepare Assess Risks Prioritize Approach Eat Fast 9 10 Assess Risks Prioritize Space Brain Freeze Partition Determine Order Solids Liquids

Approach So 13 14 Eating contests and IT projects are similar Program Agenda Prepare Assess Risks Partition and Prioritize Adopt a winning approach Oracle

4 Approach So Eating contests and IT projects are similar Program Agenda Prepare Assess Risks Partition and Prioritize Adopt a winning approach 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

industry standards and field experience Iteratively developed through a continuous, evolutionary process Vision, Goals, and

5 Program Agenda Enterprise Application Support Partitions Groups Applying Partitions and Groups Oracle Global Methods Philosophy OUM er Program Summary / For More Information / Q&A Oracle Methods Philosophy Oracle Methods are Based on industry standards and field experience Iteratively developed through a continuous, evolutionary process Vision, Goals, and Benefits Highly scalable to support project or program specific requirements Tailored through method views, tools, and guidance

technology agnostic Support supplemental guidance Tight integration between enterprise-level and project-level processes 21

6 Oracle Unified Method (OUM) Vision (OUM) Goals Support the entire Enterprise IT Lifecycle, including support for the successful implementation of every Oracle product 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 Structure and Principles Reduce duplication

OUM Focus Areas Envision Enterprise Business Analysis Enterprise Architecture IT Portfolio Management Governance Organizational Change Management OUM Envision Implement Manage Implement Software

7 OUM Focus Areas Envision Enterprise Business Analysis Enterprise Architecture IT Portfolio Management Governance Organizational Change Management OUM Envision Implement Manage Implement Software Engineering Software Implementation Manage Project and Program Management Aligned with Project Management Institute (PMI) OUM s Core Principles Flexible & Scalable Risk-Focused Business Process & Use Case-Driven OUM Envision Implement Manage Architecture-Centric Iterative & Incremental Flexible & Scalable From the OUM Method Overview Do not serve the method, make it serve you Just Enough Documentation OUM must be scaled to fit your project Just Enough Ceremony Build it up. Don t tailor it down. 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

Supplemental Guidance Guidance specifically related to Oracle Tutor, UPK, Business Intelligence & Knowledge Pathways Products Tools Analytics Technologies Project Approach Architectural Style

8 Supplemental Guidance Guidance specifically related to Oracle Tutor, UPK, Business Intelligence & Knowledge Pathways Products Tools Analytics Technologies Project Approach Architectural Style Application Integration Architecture (AIA) Application Implementation Enterprise 2.0 & Webcenter Siebel er Relationship Management Service Oriented Architecture (SOA) The (OUM) is the CIO s handbook. Gary Marshall CIO, Taconic Farms, Inc OUM is Highly Scalable Build it Up Don t Tailor it Down 1 Build it up. Don t Tailor it Down. 1. Start from a core set of tasks. 1 Balancing 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 OUM is Highly Scalable Build it Up Don t Tailor it Down 1 1. Start from a core set of tasks. 2. Add tasks as you identify scope and risk. 1. Start from a core set of tasks. 2. Add tasks as you identify scope and risk. 3.

9 OUM is Highly Scalable Build it Up Don t Tailor it Down 1 OUM is Highly Scalable Build it Up Don t Tailor it Down 1 1. Start from a core set of tasks. 2. Add tasks as you identify scope and risk. 1. Start from a core set of tasks. 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. 1 Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner 1 Balancing 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. 2. Add tasks as you identify scope and risk. 3. Consider the depth to which you will execute specific tasks. 4. Combine tasks and work products. Define just enough documentation An Iterative Approach 1 Balancing Agility and Discipline: A Guide for the Perplexed by Barry Boehm and Richard Turner

10 OUM Implement Phase Structure Production Still Looks Kind of Like a Waterfall-y Production But it s not intended to be used that way Production Production Project Startup Build Implementation Plan Based on estimates and experience Project Workplan Implementation Plan Add OUM Implement phases Project Execution and Control Production Project Closure

Divide Phases into s Implementation Plan s determined at outset of project Based on initial estimate 2 to 6 weeks in length Refined as project progresses Culminate in a

development 4 6 weeks Complex modeling Complex or extensive configuration Complex extension or custom development 41 42 Build Implementation Plan Divide Phases into 2-6 week

11 Divide Phases into s Implementation Plan s 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 length may vary Based on type of work 2 3 weeks Simple configuration (i.e. cloud, solution-driven) application development 4 6 weeks Complex modeling Complex or extensive configuration Complex extension or custom development Build Implementation Plan Divide Phases into 2-6 week s Project Workplan Implementation Plan Project Execution and Control Project Startup Production Project Closure } 2 6 Weeks OUM IMPLEMENT CORE WORKFLOW

12 Implement Core Workflow Each Box Represents a Few Tasks Objectives Document Requirements Map Requirements Setups Integrate Test Objectives Document Requirements Map Requirements Setups Business Data Structures Application Setups Integrate Test 45 Gaps Analyze & Design Components Implement Components 46 Business and Objectives Context Diagram MoSCoW List Future Process Model Domain Model Use Case Model Use Case Descriptions Conceptual Prototype Mapped Business Requirements Functional Prototype Gap Resolutions Gaps Analyze & Design Components Data, Behavior, and UI Analysis Data, Behavior, and UI Design Logical Database Design Software Component Design Implement Components Physical Database Design Implemented Components Assembled Components Integrated Test Results Integration Test Results Workflow Represents One Workflow is Repeated in Every LO LA IOC

Shifting Emphasis Reaffirm Objectives Refine Requirements Confirm Objectives Capture Business Requirements Perform Initial Mapping Reaffirm Objectives Capture Detailed Requirements Perform Mapping

13 Shifting Emphasis Reaffirm Objectives Refine Requirements Confirm Objectives Capture Business Requirements Perform Initial Mapping Reaffirm Objectives Capture Detailed Requirements Perform Mapping Analyze Develop Prototypes Refine Configuration Design Implement Integrate Test Enterprise Application Support Develop Prototypes Main Focus Less Focus Little Focus Business-Process Driven Two Implementation Views Requirements-driven Solution-driven

14 Analyze gaps with use cases or user stories Support for agile project management Use Case Details: Order Skis Actor Does 1.The customer selects the skis that he wishes to order. 3. The customers Does 2.The system checks the availability of 4. The use case ends when Predictive Traditional Plan-driven Disciplined Adaptive Agile Unplanned Undisciplined Partitioning Partitions Splitting functionality to be implemented in a project into smaller pieces Look for High cohesion within a partition Low coupling between partitions

15 Partition Some Partitioning Examples Defined part of the total functionality to be implemented May be implemented Serially In parallel Staggered Production Partitioning before Execute in Parallel Partition before Execute Serially Partition 1 Production Partition 1 Production Production Partition 2 Production Partition

16 Partitioning after Execute Serially Partition after Execute in Parallel Production Production Production Production Partition after Staggered Execution Partition after Execute in Parallel with Single to Production Production Production Production

17 Partition after Execute in Parallel Production Partition after Staggered Execution Production Production Production Projects May Be Divided into Many Partitions Whatever Makes Sense for the Project Situation Production Production Groups Production

18 Group Definition Subset of the requirements of a system (or of a partition) Risk A Set of Functional Requirements (use cases) Assess Service Requests Plan er Visits Pay Suppliers Order Parts Log Service Requests by Helpdesk Log Service Request by er Prioritized and grouped by er Priority Select User Preferences Make Loan Payment Apply for Mortgage Review Loan for Approval Loan Rate Scanner Apply for A Loan Provide Credit Details Dependency Re-plan er Visits Register Employee Register er Notify Parts Available Restock Service Cars Accept Service Requests Update Service Requests Sign-off Service Requests Complexity Register Supplier Invoice Service Requests Automatic Sign-Off Service Requests Grouped by Functional Area Apply Prioritization Techniques Planning Assess Service Requests HR Register Employee Service Backoffice Log Service Request by Helpdesk Planning Assess Service Requests HR Register Risk Employee Service Backoffice Log Service Request by Helpdesk Plan er Visits CRM Accept Service Request Plan er Visits CRM Accept Service Request Re-plan er Visits Logistics Register er Register Supplier Automatic Sign-Off Service Request Update Service Request Re-plan er Visits er Priority Logistics Register er Register Supplier Automatic Sign-Off Service Request Dependency Update Service Request Order Parts Notify Parts Available Restock Service Cars Financials Pay Supplier Invoice Service Request Services Web Pay Supplier Sign-off Service Request Order Parts Notify Parts Available Restock Service Cars Financials Pay Supplier Complexity Invoice Service Request Services Web Pay Supplier Sign-off Service Request

19 Grouped by Priority into Groups Register Employee Register er Register Supplier Log Service Request by Helpdesk Accept Service Request Group 1 Assess Service Requests Plan er Visits Update Service Request Sign-off Service Request Group 2 Invoice Service Request Order Parts Notify Parts Available Re-plan er Visits Pay Supplier Group 3 Restock Service Cars Automatic Sign-Off Service Request Pay Supplier Why iterate and partition? Break down complexity Manage risk Earlier return on investment Demonstrate business value Inhibit scope creep Change Requests for Increment 1 Change Requests for Increment 2 Increment 1 Increment 2 Increment 3 75 One business flow. No custom software High-Level Implementation Plan Using Partitions and Groups High Level Processes

20 Two business flows. Single Partition. Configuration work done in parallel Two business flows. Parallel Partitions. High Level Processes Flow B Flow B High Level Processes Flow B Flow B Two business flows. Two Staggered Partitions. Single Phase Two business flows. Two Serial Partitions. Single Phase High Level Processes High Level Processes Flow B Flow B Flow B Flow B

21 Two (or more) business flows. Serial Partitions. Separate Phases One Business Flow. Minor Extensions Only one Group High Level Processes High Level Processes Flow B High Level Processes Group Group Group 1 Group One Business Flow. Minor Extensions Another Approach High Level Processes Group Group Group 1 Group One Business Flow. Major Extensions High Level Processes Group 1 Group 1 Group 2 Group 1 Group 1 Group 2 Group 3 Group 2 Group 2 Group 3 Group 3 Group

22 Many business flows. Done Serially Many business flows. Two Releases per Flow. Staggered Group 1 Group 2 Group 3 Group 1 Group 1 Group 1 Group 1 Group 2 Group 2 Group 2 Group 2 Group 3 Group 3 Group 3 Group 3 Group 1 Group 2 Group Global Design. Site by Site Deployment. Per Partition Using the Two Step Approach. Per Partition Group 1 Group 1 Group 2 Global Design Group 2 Group 3 Global Design Group 3 Create global design Include only necessary customizations and integration Deploy site by site Include only unique customizations and localizations Site A Deployment Site C Deployment Site B Deployment Site A Deployment Site B Deployment Site C Deployment

23 Everybody wants to go Vanilla But it s hard to attain Start with standard industry business processes wherever possible ize 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 er Program OUM er Program No Cost access to OUM Training, Adoption, and Tailoring Additional Resources 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 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 er to tailor OUM for a single project or for a set of typical projects

24 Steve Knew How to Win Summary Groups Partitions Two Level Plan Prepare using a two level plan Assess and address risks, complexity, dependencies Iterative Implementation Partition and Prioritize Solids Liquids Take small bites For More Information For More Information General Questions tom.spitz@oracle.com ominfo_us@oracle.com search.oracle.com oum-training_us@oracle.com Social Media OUM on LinkedIn ( group) OUM on Twitter (#OUM_info) OUM Blog (blogs.oracle.com/oum)

25 Q&A

An Oracle White Paper February Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions

An Oracle White Paper February 2014 Oracle Unified Method (OUM) Oracle s Full Lifecycle Method for Deploying Oracle-Based Business Solutions Executive Overview... 1 Introduction... 1 Standards Based...