Implementing Odoo the OBS way - Part 2
Organization, roles and responsibilities for a successful Odoo implementation
10 June, 2020 by
Implementing Odoo the OBS way - Part 2
OBS Solutions GmbH, Tobias Hammeke

After we introduced our Blog Series "Implementing Odoo the OBS way" in part one, the second part of our will be about the different roles and areas of responsibility a project team should consist of to ensure a successful Odoo implementation.

Conventional enterprise resource planning (ERP) providers  define and use a long list of roles — from project managers, junior business analysts and senior business analysts to product specialists, testers and trainers —  when analyzing their client’s business and proposing an implementation solution. But, too many cooks spoil the broth!

The right implementation always involves a compromise between certain business requirements and existing product features. By considering the needs of too many stakeholders in the process, decision making quickly becomes inefficient — and expensive.

The solution? An Odoo implementation the OBS way.

Defining Odoo Project Roles 

Odoo as a product is much easier to use than traditional ERPs. A single consultant can easily understand both the business requirements and the features within Odoo — something competitors can't do.

Although it is important to reduce complexity in your organization, it’s still essential to have certain key roles defined in any Odoo implementation project. 

For a successful Odoo implementation for your business, the following roles are critical:  

  •        OBS Project Lead (PL)

  •        Client Single Point of Contact (SPoC)

  •        OBS Project Director (PD)

  •        Client Project Owner (PO)

The OBS Project Lead (PL) and the Client Single Point of Contact (SPoC) are responsible for the operative implementation of the project, whereas the OBS Project Director (PD) and the Client Project Owner (PO) consider the overall business perspective and set the right frame conditions to ensure the necessary resources for a successful implementation. 

                                      OBS Project Lead  (PL)

                                      OBS PL is responsible for the operative implementation of Odoo and is the key point of contact for the client. The OBS PL is responsible for:

                                      • Understanding all business requirements
                                      • Challenging Odoo and the client’s requests
                                      • Proposing business solutions in Odoo
                                      • Coordinating with functional specialists and developers
                                      • Conducting the system configuration and data migration

                                      OBS Project Director (PD)

                                      OBS PD is responsible for the overall client relationship and overlooks the entire project, as well as:

                                      • Conducting "proof of concept" or analysis
                                      • Setting frame conditions and project plans
                                      • Challenging the project on both sides
                                      • Tracking the efficiency and commercial agreement

                                      Client Single Point of Contact (SPoC)

                                      Client SPoC is the client-side equivalent of the OBS PL and is responsible for the operative implementation on the client side, including:

                                      • Gathering and assessing the project requirements
                                      • Making operative decisions
                                      • Being an ambassador for Odoo
                                      • Planning the end-user training
                                      Ensuring first-level support

                                      Client Project Owner (PO)

                                      The Client PO is the sponsor of the project and ensures the necessary resources are available for implementation, including:

                                      • Determining the project scope, priorities and extensions
                                      • Maintaining overall budget responsibility
                                      • Defining resources for the project and ensuring their availability
                                      • Tracking the success of the project

                                      Depending on the project scope, it could be necessary to consolidate roles or define further supporting roles in the project. For example, in very small projects, the roles of the PL and PD on the OBS side and SpoC and PO on the client side can be consolidated. 

                                      However, for larger projects, additional roles may be necessary in order to ensure an optimal Odoo implementation. Let’s take a look at some of the additional OBS and client roles that may be recommended, depending on the scope of your project.

                                      Additional OBS Roles 

                                      Sub Project Leads (SPL) 
                                      are necessary on large projects to support the project lead (PL). These are specialists in the required function and are responsible for a specific work package. 

                                      Functional Specialists (FS) are specialized in one key app like accounting, CRM, inventory, manufacturing or project management.

                                      Technical Consultants (TC) make sure technical requirements are fulfilled and, in case customization is necessary, that it is done considering the highest standards of development.

                                      Additional Client Roles

                                      Work Package Responsible (WPR) leads
                                       are normally leading departments that are affected by the Odoo implementation. It is essential to include these functions in the project from the very beginning. Together with the SPoC they are deciding on the software requirements and the solution that is finally implemented.

                                      Key Users (KU) are necessary on larger projects in addition to the WPR to conduct functional testing and support with the end-user trainings.

                                      Other Stakeholders (OS) might be necessary to support the project, such as external tax advisors, business consultants or technical specialists. These individuals are usually not part of the project team, but are requested based on individual implementation needs.

                                      Project Organization (exemplary)

                                      According to Odoo methodology, the rule should be to "establish the project organization as simple as possible, but define the roles as exact as necessary" — depending on the project scope and maturity of the client organization. The larger the project and the more mature the client organization, the more precise the roles, responsibilities, rules and formal project organizations have to be defined. 

                                      For smaller projects, complex project organization isn’t necessary.

                                      Each Odoo implementation project will be overseen by a steering committee as well, which is a decision board that aligns commercial and operative targets and makes sure the overall project objectives are met. Both the steering committee as well as the overall project organization should be set up to be as lean as possible.

                                      Odoo • Text and Image

                                      Implement Odoo with OBS!

                                      If you’re ready to use a leading ERP system with expert implementation, contact us to schedule your free Odoo Demo appointment now!

                                      Odoo 14 - Release Note