Oracle Project Management, Application Implementation Methodologies

Depending on years, projects experience Oracle releases its advised project management, implementation methodologies like Project Management Method (PJM), Application Implementation Method (AIM), AIM for Business Flows (ABF). With Oracle Unified Method (OUM, Released in 2006) Oracle combines legacy methodogies for a more complete and standards based one. Here are just a few notes to give an idea, all required information can be found in corresponding guides.

PJM;
"Oracle Project Management Method is Oracle Method’s standard approach to project management for information technology projects. The goal of PJM is to provide a framework in which all types of information technology (IT) projects can be planned, estimated, controlled, and completed in a consistent manner."

AIM;
"Application Implementation Method is a proven approach for implementing Oracle Applications. It provides documentation templates that support the tasks that must be performed to assist the implementation participants in running and managing projects successfully."

ABF;
AIM for Business Flows is a version of AIM which is used for flow based projects. Two things that make a project flow based; focus on business processes provided by the flows and not application modules, solution driven approach and not requirements driven (requirement driven means: Solution is defined during project based on requirements). It also uses CRP Conference Room Pilot method unlike AIM' s User Acceptance Test (UAT).

OUM;
"The Oracle® Unified Method (OUM) is Oracle's full lifecycle method for deploying Oracle-based business solutions. OUM includes the three focus areas: Manage, Envision and Implement. You can tailor OUM to support your specific project situation. With its ready-made templates, guidelines and tailored work breakdown structure, OUM provides the programmatic tools you need to manage the risks associated with your Oracle-based projects. OUM is standards based; it leverages one of the de facto industry standards, the Unified Software Development Process (UP)2"
A note from OUM guide:
"Do not serve the method; make it serve you. The purpose of methods is to identify and manage risks, improve repeatability and quality, and encourage knowledge capture and reuse. If you’re not going to need it, don’t do it."