Configuration Vs Customization Vs Development
Configuration Vs Customization Vs Development
odoo.com/fr_FR/slides/slide/technical-theory-1213
45 min
preparation
45 min
with your onboarder
As a project manager you are responsible to ensure that your project will be a success.
Making a project successful means that all along the way you were able to take the right
decision at the right moment and to explain why it was the best way to do things. This is true
for functional, project management and technical aspects. By knowing that those topics exist,
it will help you to consider more options in order to select the best one.
Among others, the technical decisions we make during the project implementation may have
more or less impacts on the way the project is managed or on the technical side the
database itself (velocity, stability, maintainability, ...). In order to avoid creating complicated
situations, it is important to acquire good reflexes when dealing with this kind of questions.
Evaluating the pro's and con's of a decision on the short or long term will help ensuring the
longest retention possible of all the projects you will be working on.
For instance:
Doing too much development might be a good short term solution for the project to
meet the customer requirements but might also delay the implementation or prevent to
have a smooth migration as the database complexity increases. This is why it is always
important to challenge the customer before developing. A development should be done
only when it is a real added-value for the project.
1/3
Using the right platform will allow us to provide the most accurate service. For simple
projects with no development, the SaaS is the best one while for complex and heavily
customized project, Odoo.sh or on-site installation are a must have.
The purpose of this task is to guide the consultant to understand those technical concepts,
their impacts and the way they have to deal with.
Before the session (individually): Read carefully the documentation below. These are
external links that will introduce you to some very important contextual information:
During the session with your Odoo Onboarder: listen to their presentation of the differences
between Odoo SaaS and Odoo.sh and the link between these platforms.
After the session: Come back to this task (or the video if the Onboarding session was
recorded) when you want to review the topic. Don't hesitate to contact your Odoo functional
expert (at Odoo or in your company) to be sure that you have taken the right decision. It will
always take less time to double-check than having to fix a bad decision.
Not mandatory for this course topic, but if you want to dive deeper in Odoo.sh, you can
always have a look at the Odoo.sh presentation made just after its release:
This task is about understanding the differences between the different Odoo environment
(Saas, .sh, on site) and its consequences on the possibility to configure, customize or
develop on the customer database.
Output
Understand what we mean by configuration, customization & development and you are
able to show and explain the differences;
2/3
You understand the impacts of going too fast into developments (impact on the direct
and indirect costs);
You can explain what Github is and its link with Odoo.sh;
You know in the broad lines what Odoo Studio can or cannot do;
You know how to switch from Odoo Studio to Odoo.sh/local environment if needed.
3/3