Odoo General

A Guide to Odoo Implementation

April 19, 2018 · 3 minutes read

Within a short span of time, Odoo became one of the promising and fastest growing Opensource ERP system across the world. Odoo is a unique ERP as their source code is available in public and can be modified and improved by the online developer community. It is a complete suite of application fitting perfectly into the pockets of small, medium and large organizations in the effective implementation of their management activities. Odoo/OpenERP implementation if done in right way saves time and money also a boost to the growth of an organization.

With more than 2 million users and 15,000 +Odoo Apps, Odoo is setting all new trend in the software engineering. Odoo being an all in one suite of business applications, it is positioned high among the business circle. High degree customization in Odoo makes it fit the exact needs of every company. In addition to modifiable database configurations, it also uses a modular system, where it starts with the most basic features and allows companies to add features through modules. They are either available in Odoo app store or can be developed by a skilled Odoo expert.

Let us discuss in detail the different phases encompassing Odoo Implementation.

1. Business Review

Business review happens at the onset of sales process. The idea is to gather overall understanding of the business environment and the further requirements looking forward. Business review is done via speaking to the company and their users.

2. Project Planning

Gap Analysis:- Helps us to cover the functional gap

Project Planning
• Meeting the layout with your team to identify the discrete tasks, responsibilities, and timelines necessitating the project.
• Establishing proper system policies for maintaining and backing-up data
• Executing tasks as per the Implementation Plan in conjunction with the Project Team
• Creation of required custom reports

3. Re-engineering, Installation, Team training, Testing, Conference room pilot testing:

This process involves customizing, installing and upgrading of the modules. The changes are inserted to the test database for pilot testing of the project.

i. Sprint Planning Meeting (Held at start of every sprint)
At the start of each sprint, the project team will meet for a “Sprint Planning Meeting”. During the meeting, project team determines which Product Backlog items can be completed for the upcoming Sprint. If new requirements have been discovered it would get updated in this meeting.

ii. End-User Training: The following are some examples of key areas that will be addressed during training:
• How to enter transactions in different ways
• How to maintain accumulating data in your system
• How to use inquiries and reports to obtain the information you wish to access
• How to complete period and year-end procedures in each module

iii. Conference Room Pilot Testing
The pilot test is based on the processes that are developed during the business process engineering, and it serves two functions:
• Test the setup of the system
• Prove the validity of the re-engineered processes and work instructions
• Provide additional training for team members by simulating their normal day-to-day activities

iv. Go-Live!
During the go-live period, we ensure that all requirements have been covered to ensure a smooth transition into the new business system. It is at this time that all tasks on the project plan have been completed, all users trained, all processes re-engineered, and the final data migration/conversion is performed

4. Post Implementation Review and Continuous Improvement:

A plan for on-going improvement will be discussed and project planning for additional phases of your implementation may be scheduled.


Leave a Reply

Your email address will not be published. Required fields are marked *