Download as PDF, PPTX
Uploaded byOdoo
Odoo Implementation Methodology
The document outlines the Odoo Implementation Methodology (OIM) which provides a standardized approach for implementing Odoo projects. It describes key aspects of the methodology including conducting a GAP analysis to validate requirements, aligning stakeholders at a kickoff meeting, implementing in iterative cycles with configuration, data import, development and validation, training end users, and going live in production. It also provides examples of how the methodology would be applied to projects of different sizes, such as a small law firm and a large consulting company. The goal of the OIM is to help projects be delivered on time and on budget by standardizing roles, responsibilities, and processes.
More Related Content
Similar to Odoo Implementation Methodology
Odoo Implementation Methodology
- 1. The Odoo Implementation Methodology CatherineVIESLET • Head of Business Services, Odoo S.A. 2019 EXPERIENCE
- 2. The Book! Get onehere or in the Main Hall!
- 3. Why the OIM? andnot any other existing one...
- 4. Because we learnt fromour mistakes!
- 5. Standard for success. Developmentis your plan Z because this results to... ● (huge) delays; ● an important technical debt; ● a higher complexity. In short, it increases significantly the risk of project failure
- 6. Don’t be drivenby satisfaction. This is not a useful KPI during a project ● It decreases naturally until the Go Live ● Dissatisfaction differs from the CEO to the new comer ● Disagreement is healthy for the project ● Helps in identifying a lack of communication
- 7. Focus on projectsuccess. Be patient and competitive... ● Focus on project velocity & success ○ Huge competitive advantage ○ Postpone the non-mandatory features to a later phase ● Prove yourself before upselling ○ Launch in production first ○ Upsell is 7 times easier than acquizition
- 8. Onboard the USERS Whatreally matters is to on TIME & on BUDGET
- 9.
- 10.
- 11. Odoo Implementation CostEvolution 9K 3.5K Fact 2
- 12. You are RESPONSIBLE ⇢To responsibilize your customer ⇢ Customer: What & Why ⇢ Odoo: How ⇢ Demand to be convinced You’re not there to say Yes Keep things SIMPLE ⇢ Less of everything, move faster (paperwork, people, meetings) ⇢ The most standard possible ⇢ Work on remote Train the Odoo EXPERTS ⇢ Train the SPoC (& Key Users) ⇢ Build trust and confidence in the product ⇢ Keep an eye on change management ⇢ Make sure that the end-users will be trained Bet on the best TALENTS ⇢ A strong mindset is the key ⇢ Product & Business experts ⇢ Retain the top performers Common sense prevails! What matters is mindset.
- 13. Projects actually From thesmallest to the biggest
- 14. Lawyer’s office. ● Staff:5 lawyers ● Legacy system: None ● Scope: 100% Standard - Sales, Invoicing, Project, Timesheet ● Budget: Limited ● Deadline: ASAP
- 15. Consulting company. ● Staff:4000 consultants ● Legacy system: Another integrated software ● Scope: Sales, Invoicing, Project, Timesheet - Development required ● Budget: Unlimited ● Deadline: ASAP
- 16. How to staff? Oneteam, many roles!
- 17. A bunch of Efficientand Smart People Business Advisor ⇢ Advanced Qualification ⇢ Project Follow-up Skills ⇢ Strong mindset ⇢ Product ⇢ Business ⇢ Methodology
- 18. Project Leader Project Manager ⇢Make decisions ⇢ Project on track (plan) ⇢ Coach the SPoC Business Analyst ⇢ How? ⇢ Challenge requirements ⇢ Configure & Import ⇢ Write specifications Skills ⇢ Strong mindset ⇢ Product ⇢ Business ⇢ Methodology Business Advisor (Sales) A bunch of Efficient and Smart People
- 19. Business Advisor (Sales) App Expert ⇢Peer Review ⇢ Punctual intervention on projects Skills ⇢ Strong mindset ⇢ Spec. Product Expertise ⇢ Spec. Business Expertise ⇢ Methodology Project Leader (PM & BA) A bunch of Efficient and Smart People New!
- 20. Business Advisor (Sales) Project Leader (PM) ProjectDirector ⇢ Steering Committee ⇢ Project Monitoring ⇢ Challenge the PL Skills ⇢ Politics ⇢ Strong mindset ⇢ Product ⇢ Business ⇢ Methodology Apps Expert (BA) A bunch of Efficient and Smart People
- 21. Business Advisor (Sales) Project Leader (PM& BA) Project Director (PM) Developer ⇢ Challenge specifications ⇢ Develop Skills ⇢ Strong mindset ⇢ Coding (python, JS, xml, etc.) ⇢ Product ⇢ Methodology Apps Expert (BA) A bunch of Efficient and Smart People
- 22. Business Advisor (Sales) Project Leader (PM& BA) Project Director (PM) Developper SPoC Project Manager ⇢ Project Follow-up ⇢ Project consistency ⇢ Manage the change Business Analyst ⇢ What? & Why? ⇢ Internal Odoo Expert ⇢ Validate the solution ⇢ Train the end users Characteristics ⇢ Available ⇢ Legitimate ⇢ Authority Apps Expert (BA) Odoo Project Stakeholders A bunch of Efficient and Smart People
- 23. Business Advisor (Sales) Project Leader (PM& BA) Project Director (PM) Developper SPoC (PM & BA) Key Users ⇢ Support the SPoC ⇢ Manage the change ⇢ What? & Why? ⇢ End users training Skills ⇢ Spec. Business Expertise ⇢ Available ⇢ Legitimate Apps Expert (BA) Odoo Project Stakeholders A bunch of Efficient and Smart People
- 24. Business Advisor (Sales) Project Leader (PM& BA) Project Director (PM) Developper SPoC (PM & BA) Key Users (BA) Apps Expert (BA) Odoo Project Team A bunch of Efficient and Smart People
- 25. Business Advisor (Sales) Project Leader (PM& BA) Project Director (PM) Developper SPoC (PM & BA) Key Users (BA) Sponsor(s) ⇢ Decision maker(s) ⇢ Project control ⇢ Project support Skills ⇢ Authority Apps Expert (BA) Odoo Project Team A bunch of Efficient and Smart People
- 26. Business Advisor (Sales) Project Leader (PM& BA) Apps Expert (BA) Project Director (PM) Developper SPoC (PM & BA) Key Users (BA) Sponsor(s) End Users Odoo Project Team Customer A bunch of Efficient and Smart People
- 27. How to deliver? Afew steps to ensure the efficiency!
- 28. Phase III ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- Phase II ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- PhaseI ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- Phase III ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- Phase II ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- Methodology Onboarding Analysis & Feasibility Plan Project Qualification ↺Phase I ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- ----------------- Analysis Configuration Development Import Testing Set in production End users training & Final validation ↺ Initiation Validation 15% 80% 5% Go Live!
- 29. GAP Analysis. Convince beforestarting the project ● Purpose ○ Complete project analysis ○ Challenge the requirements ○ Validate the project feasibility ● Output ○ Reviewed project requirements ○ Project planning & Budget Project Initiation Pre-sales
- 30. Interviews Analysis Presentation GAPAnalysis. Hints ● Reassure the customer ● Observe how their currently work ● Replace, don’t replicate ● Don’t give the choice ○ One option ○ Define the Must Have’s ● Peer-review ○ App Expert ○ Developer ● Sort developments ○ Necessary (1st phase) ○ Optimization (2nd deployment) ● Scope highlights ● Planning & Budget ● Risks & Opportunities ● Specific demo to reassure Project Initiation Pre-sales
- 31. Kick-off. Align the visionsfor a project success! ● Purpose ○ Methodology onboarding (approach & mindset) ○ Project GAP Analysis* ○ Project planning & phasing ○ SPoC Responsibilities clarification ○ SPoC learning process The Kick-off is a phase, not a meeting Project Initiation
- 32. Kick-off. Hints ● Check customer’sinvolvement - Availability, Knowledge, Mindset ● Tackle issues directly ○ Too ambitious planning - phasing & deadlines ○ Unclear scope - expected features ○ Wrong SPoC - availability, decision-making, etc. Project Initiation
- 33.
- 34. Implementation cycles. Hints ● Cyclesin phase: Serie of quick wins to constantly moving forward ● Keep challenging your customer - Demand to be convinced ● During training: Let the SPoC drive the mouse ● Meet on-site if required
- 35. Implementation Cycle. Configurations ● Who:Project Leader ● Studio included ● Train the SPoC (& Key Users)
- 36. Implementation Cycle. Data Import ●Who: ○ SPoC (& Key Users) ○ Project Leader (& Developer) ● Master Data vs. History ● Never delay the Go Live because of poor data quality
- 37. Implementation Cycle. Specific Development ●Who: ○ Project Leader (spec & scenarios) ○ SPoC (validate) ○ Developer ● Never too late to challenge ● Testing: ○ Project Leader (Unit & E2E) ○ SPoC (E2E) ○ Developer (automated) ● Developer bug fixes
- 38. Validation & Training. Atthe end of each phase ● Green light given by the SPoC ● User guides are written throughout the phase by the SPoC & Key Users ○ Ensure exhaustive testing ○ Know better processes & Terminology ● End-users’ training
- 39. Go Live. Anticipation isthe key ● Can fail because ○ The solution has not been fully tested ○ The end-users have not been well trained
- 40. Go Live. Hints ● Thebest training means practice ● Cross check testing ● React quickly ● Don’t push back Go Live ● Go on-site on the first day ● Check if they’re really live after a few days
- 41.
- 42. Lawyer’s office. Project Team BusinessAdvisor (Sales) Project Leader (PM & BA) SPoC (PM & BA)
- 43. Project Team Lawyer’s office. ProjectTeam Business Advisor (Sales) Project Leader (PM & BA) SPoC (PM & BA) End Users Apps Expert (BA) Developper Sponsor(s)
- 44. Lawyer’s office. Project plan PhaseI ● Sales ● Invoicing ● Contacts (import) Phase II ● Project ● Timesheet Go Live! Project Qualification Kick-off ↺ Configuration ↺Im port Set in production End users training & Final validation Testing & Validation
- 45. Lawyer’s office. Project plan ●Project duration: a few weeks ● #Specific accepted: 0% ● #Specific 2nd deployment: 0% ● #Specific dropped: 100% ● Team training: 100% standard ● User guides: None ● End users training: SPoC ● Change Management: SPoC
- 46. Consulting company. Project Team BusinessAdvisor (Sales) Project Leader (PM & BA) SPoC (PM & BA) End UsersApps Expert (BA) Developper Sponsor(s)
- 47. Consulting company. Project Team BusinessAdvisor (Sales) Project Leader (PM & BA) SPoC (PM & BA) End UsersApps Expert (BA) Developper Sponsor(s) Key User 1 (BA) Key User 2 (BA) Project Director (PM)
- 48. Project Team Consulting company. ProjectTeam Steering Committee Business Advisor (Sales) Project Leader (PM & BA) SPoC (PM & BA) End UsersApps Expert (BA) Developper Sponsor(s) Key User 1 (BA) Key User 2 (BA) Project Director (PM)
- 49. Consulting company. Project Team BusinessAdvisor (Sales) Project Leader (PM & BA) SPoC (PM & BA) End UsersApps Expert (BA) Developper Sponsor(s) Key User 1 (BA) Key User 2 (BA) Project Director (PM) Delivery
- 50. Consulting company. Project PlanPhase I ● Sales ● Invoicing ● Project ● Timesheet ● Contacts (import) ● Development Phase II ● Development 2nd deployment Go Live! Project Qualification GAP Analysis ↺ Configuration ↺Im port Set in production End users training & Final validation Testing & Validation Second deployment ------------------------- ------------------------- ------------------------- ↺ Developm ent
- 51. Consulting company. Project Plan ●Project duration: a few months ● #Specific accepted in Phase I: 50% ○ Removed in Phase II: 5% ● #Specific 2nd deployment: 20% ○ Actually delivered: 10% ● #Specific dropped: 30% ● Team training: Standard & Specific ● User guides: Key users ● End users training: SPoC & Key users ● Change Management: SPoC
- 52. Onboard the USERS Remember:Only focus on on TIME & on BUDGET
- 53.
- 54. 1 point ● Havea project on time & on budget ● Receive a gift from a satisfied customer ● Deploy min. 4 apps, in 2 weeks per app ● Deliver a project at 80% of initial budget ● Deploy a 25 users company alone 2 points ● Pass Odoo certification with 70%+ ● Go-Live with 70% of the initial budget ● Success in 3 different industries ● Migration from a traditional ERP in 2 months ● Have 3 projects in a row on budget 3 points ● Implement 500 users in production ● Save a customer from bankruptcy ● Have 10 projects on budget ● Did a migration of traditional ERP in 4 weeks Measure your progress.
- 55.
- 56.
- 57.
- 58.