ORACLE UNIFIED METHODOLOGY(OUM)

Oracle is evolving the Oracle Unified Method (OUM) to achieve the vision of supporting the entire
Enterprise IT lifecycle, including support for the successful implementation of every Oracle product. OUM includes three Focus Areas 1) Manage Focus Area : It provides a framework in which all types of projects can be planned, estimated, controlled, and completed in a consistent manner. 2) Envision Focus Area : It deals with development and maintenance of enterprise level IT strategy, architecture, and governance. 3) Implement Focus Area : It provides a framework to develop and implement Oracle-based business solutions with precise development and rapid deployment.

MANAGE FOCUS AREA

The Manage focus area provides guidance and support to the project manager across all kinds of responsibilities.

It consists of 3 phases a)Project Start Up Phase b)Project Execution and Control Phase c)Project Closure Phase Project StartUp Phase : The goal of this phase is to conduct the necessary project start up. The project
manager will define the project with respect to scope, quality, time, and cost. The overall Project Management Plan and the plans for each Manage process will be developed. The Project Start Up phase also includes establishing the project infrastructure and securing project resources.

Project Execution and Control Phase : The Project Control and Execution phase is directly associated
with the project lifecycle phases in the execution method.The purpose of the this phase is to manage the execution of the project.This includes using the policies, standards, and procedures delineated in the Project Start Up phase, and perform the necessary reviews, and measurements to ensure that the project is being executed according to the published plan.It is also the process of comparing actual performance with planned performance, analyzing variances, evaluating possible alternatives, and taking appropriate corrective action as needed.

Project Closure Phase : During the Project Closure phase, the project is "closed" from an administrative
and contractual standpoint. This includes ensuring the project work products are complete and meet the customers expectations, gaining final acceptance and securing all documents for reuse, collection and retention.

The Manage focus Area is organized into thirteen (13) processes:.

Bid Transition Scope Management Financial Management Work Management Risk Management Issue and Problem Management Staff Management Communication Management Quality Management Configuration Management Infrastructure Management

 Procurement Management Organizational Change Management Scope Management : The project scope management is used to limit and control the work included in a
project. It ensure that all the work of the project is included. There are 4 major scope areas: a)Functional Scope (Flow,Modules,Features) b)Technical Scope ( Enhancements , Customizations , Interfaces , Data Conversions) c)DBA Scope d)Testing Scope ( Unit Testing , Integration Testing)

Quality Management : The project quality management will ensure that result of a project meets the needs
for which the project was executed. Processes such as quality planning, assurance, and control are included in this area. Quality Management checks for the Quality of Product , Quality of Delivery Process , Quality of Specification , Quality of Review.

Risk Management : Risk management must be an integral part of any project. Everything does not always
happen as planned. Project risk management contains the processes for identifying, analyzing, and responding to project risk. Risk Management migates the risks and gives the appropriate solutions for the risk that may happen. It also gives solutions for the risks that are already happened.

Configuration Management : The objective of the Configuration Management process is to reduce project
risk by defining appropriate management and control processes for important work products including both documentation and software. A successfully implemented Configuration Management process reduces errors, rework and lost time related to configuration problems such as installing incorrect versions of software, missed patches, obsolete or incorrect documentation.Configuration Management identifies what configuration items will be managed for the project,how they will be identified, how baselines will be established, what management processes will be used to track them, and what metrics will be established for reporting. Configuration Items commonly produced during the course of a project are : a) Functional : Taking the backup of instance,setups and Database Configurations b) Technical : The Configuration Management process provides guidance to the project manager and project team for establishing (or validating the establishment of) a sound Configuration Management for the life of a project.

Organizational Change Management : Organizational change management refers to a project

management process where changes to a project are formally introduced and approved. It is a structured approach in shifting individuals , teams and organizations from a current state to a desired future state.

Communication Management : The purpose of the Communications Management Plan is to define the
communication requirements for the project and how information will be distributed.The Communications Management Plan defines the following: Communication requirements based on roles What information will be communicated How the information will be communicated When will information be distributed Who does the communication Who receives the communication

Commun

Objective of

Frequency

Audience

Owner

Deliverable

ication Type Kickoff Meeting

Communication Introduce the project team and the project. Review project objectives and management approach. Review status of the project with the team. Discuss and develop technical design solutions for the project. Report on the status of the project to management. Report the status of the project including activities, progress, costs and issues. Once Project Sponsor Project Team Stakeholders Project Team Project Technical Staff PMO Project Sponsor Project Team Stakeholders PMO Project Manager Agenda Meeting Minutes Agenda Meeting Minutes Agenda Meeting Minutes

Project Team Meetings Technical Design Meetings Monthly Project Status Meetings Project Status Reports

Weekly

Project Manager Technical Lead Project Manager Project Manager

As Needed

Monthly

Monthly

Project Status Report

IMPLEMENT FOCUS AREA :

The Implement focus area provides a framework to develop and implement Oracle-based business solutions with precise development and rapid deployment. The OUM implementation architecture provides a rapid, adaptive, and business-focused, approach to Implementation.These features are embodied within a framework that supports the complete software development and implementation lifecycle.

There are 5 phases in this : a) Inception : Inception Phase is to achieve concurrence among all stakeholders on the lifecycle
objectives for the project. In this phase the BaseLine is set , and all the requirements and the pain points are gathered.

b) Elaboration : Elaboration phase is to move development of the solution from the scoping and highlevel requirements done during the Inception phase to developing the detailed requirements, partitioning the solution, creating and necessary prototypes, and baselining the architecture of the system to provide a stable basis for the design and implementation effort in the Construction phase. In this phase the requirement analysis is done , mapping is done , and the gaps are identified.

c) Construction : The goal of the Construction phase is to take the solution from detailed requirements
models, through configuration of standard packaged software functionality, development and testing of custom components, and integration to a system that is ready for a first release that goes into production, often a limited release and often called a beta release. In short, we complete the development of the application system, ensure that all components fit together, and prepare the system for the Acceptance Test and deployment. In this phase all the documents are prepared.

d) Transition : The goal of the Transition phase is to take the completed solution from installation onto the
production system through the Acceptance Test to launch of the live application, open and ready for business. Ensure that the system is tested systematically and is available for end users. During this phase, the new system is accepted by the client organization, the organization is made ready for the new system, and the system is put into production and, if the new system replaces an old one, a smooth cutover to the new application is provided. In this phase the required training is given, User testing is done.

e) Production : The goal of the Production phase is to operate the newly developed system, assess the
success of the system and support the users. This includes monitoring the system and acting appropriately to ensure continued operation, measuring system performance, operating and maintaining supporting systems, responding to help requests, error reports and feature requests by users, and managing the applicable change control process so that defects and new features may be prioritized and assigned to future releases and put into a plan for future enhancements to the application system, as well as determining, developing and implementing required updates. In this phase the cut over is done.

There are views in the Implement Focus Area a) Requirements Driven Application Implementation b) Solution Driven Application Implementation c) Software Upgrade View d) Technology full cycle e) Business Intelligence of EPM f) BI of custom DataWarehouse g) Enterprise 2.0 h) Core Workflow i) Implement Models. Requirements Gathering : RD.020 ( CURRENT_FINANCIAL_AND_OPERATING_STRUCTURE ) CV.010 ( DATA_CONVERSION_REQUIREMENTS_AND_STRATEGY ) TE.010 ( TESTING_REQUIREMENTS_AND_STRATEGY ) TA.010 ( ARCHITECTURE_REQUIREMENTS_AND_STRATEGY ) Requirements Analysis BP.010 ( BUSINESS_AND_PROCESS_STRATEGY ) BP.040 ( CURRENT_PROCESS_MODEL ) BP.070 ( HIGH_LEVEL_PROCESS_DESIGNS ) MD.010 ( APPLICATION_EXTENSION_STRATEGY ) Analysis BR.030 ( BUSINESS_REQUIREMENTS_MAPPING_FORM ) BP.080 ( BUSINESS_MAPPING_TEST_RESULTS ) BP.090 ( BUSINESS_PROCEDURE_DOCUMENTATION ) RD.080 ( MASTER_REPORT_TRACKING_LIST ) MD.020 ( APPL_EXTENSION_DEFINITION_AND_ESTIMATES ) Design BR.100 ( FUNCTIONAL SETUP ) TE.020 ( UNIT_TEST_SCRIPT )

MD.050 ( APPLICATION_EXTENSIONS_FUNCTIONAL_DESIGN ) CV.050 ( MANUAL_CONVERSION_PROCEDURES ) CV.060 ( CONVERSION_PROGRAM_DESIGNS ) TA.080 ( APPLICATION_SECURITY_ARCHITECTURE )