|
Oct 02, 2008 at 07:08 AM |
|
On any of my projects I like to follow the following 5 project phases. 1) Project Preparation 2) Business Blueprint 3) Realization 4) Final preparation 5) Go Live and Support, it has helped me mitigate and manage risks and dependencies. 1) The project is initiated and the project team consisting of the client and consulting personnel is put in place. The project charter and scope are confirmed and documented. The project work plan is developed. 2) Business requirements are gathered and captured in a process “blueprint” for the organization. End-user training plan is developed and the detailed implementation approach is determined. An evaluation of the Client IT landscape and the projected interfaces are defined. 3) The business and process requirements are configured within the Oracle system. Technical specifications are developed and programmed. Roles are mapped, skill gaps assessed, and training materials developed. Integration testing is executed to confirm configured functionality conforms to business requirements. 4) Testing, end user training, data conversion, production system installation and site preparation are completed. All critical open issues are resolved and the organization is prepared for the “live” environment. 5) The organization transitions from a project-oriented pre-production environment to a live production operation. A change transition assessment is conducted and post-implementation support is provided. |
|
|
Starting point for an upgrade to Oracle 12 Financials |
|
Sep 09, 2008 at 03:48 PM |
|
If you are planning an Oracle upgrade, a good starting point is the Oracle -Business Suite Upgrade Plan on Metalink's knowledge base.There is a lot of information it is important to filter your information and create a plan that is specific to your requirements. No 2 upgrades are the same. |
|
|
Sep 09, 2008 at 11:22 AM |
|
When working on the Chart of Account design for your implementation or upgrade, I use Excel to simplify my job especially for the mapping 
|
|
|
How important is teamwork on a project |
|
Sep 09, 2008 at 08:50 AM |
|
In my experience teamwork has been an important aspect of the success for our projects, I have been lucky not to be involved in any ERP failures. No matter how good you are, the success of any COTS (Commercial off the shelf) application is a team effort. By using simple words like we, us, team the motivation and implication increases two folds. Good ideas come from many areas, details that you may have missed may come from different perpectives or team members. Also implicating and mixing functional and technical individuals in the same meeting may get the ball rolling on out of the box thinking or critical issues that may not have a straight answer. Project success = Teamwork and Managing Change
|
|
|
|
<< Start < Previous 1 2 3 4 5 6 7 8 9 10 Next > End >>
|
