Hit the Ground Running with the Odoo's Implementation Methodology
•Transferir como PPTX, PDF•
0 gostou•29 visualizações
The document discusses how to successfully complete projects by focusing on project success rather than customer satisfaction. It emphasizes setting the project up for success from the beginning by designing implementation cycles, ensuring training and validation are not forgotten, and onboarding users on time and on budget. The overall mindset should be delivering the project on track from start to finish.
Recomendados
Recomendados
Mais conteúdo relacionado
Mais procurados
Mais procurados (20)
Mais de Odoo
Mais de Odoo (20)
Último
Último (20)
Hit the Ground Running with the Odoo's Implementation Methodology
- 2. We learned from our mistakes.
- 4. Don’t be driven by customer satisfaction.
- 5. SATISFACTION TIME Presales Kickoff Implementation Go Live Production
- 7. Onboard users on time & on budget.
- 8. What matters is the mindset.
- 10. Set the project on track from the beginning.
- 14. Never forget training & validation.
- 15. You are ready for the go-live.
- 16. Project Roles
- 19. Thank You
Notas do Editor
- Welcome everyone to this session entitled Hit the ground running with the OIM. My name is Antoine, Business Service Manager at Odoo Belgium and I’ll be your host for the next 30 minutes
- Why another Methodo: Based on experience Adapted to Odoo implementation It works!
- (huge) delays; an important technical debt; a higher complexity. In short, it increases significantly the risk of project failure
- It decreases naturally; It differs from a person to another; Disagreement is healthy; Good temperature check.
- It decreases naturally; It differs from a person to another; Disagreement is healthy; Good temperature check.
- Be patient and competitive, you’re still acquiring your customer 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
- People get the software They get it fast For a fair price => Don’t sell cheap (see my talk tomorrow about how to sell the methodology)
- You are RESPONSIBLE To responsibilize your customer /!\ SPOC => Project consistency 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
- Always start by aligning everyone’s vision & understanding about the project before moving forward: Align on the scope The methodology The role and responsibilities => After that you are ready to begin the implementation
- Always start by aligning everyone’s vision & understanding about the project before moving forward. It is what we call the ROI Analysis Align on the scope The methodology The role and responsibilities Define a planing & budget Sales part => After that you are ready to begin the implementation
- During the implementation you start delivering. Remember: quick wins /!\ → Project moves forward!
- First Kick-off: get the implementation started Cycles based on phasing (Onboard users on time & on budget) Start implementing and deliver the solutions step by step: Analysis refinement => ALWAYS Realization: configuration/dev/data integration
- Valitation: testing / validation If needed go through the process again => Challenging If validation => End user training Critical has it is the last step before the go-live => Change management must happen from day 1 (see change management talk)
- Spend time for the golive Be there, be available, most important: do not delay it
- Staffing: The staffing will depend on the project size & requirements For both customer & integrator 2 examples: QS projects & Large projects
- Quickstart projects which can be described as “simple” projects do not need a lot of people involved Must be: Business advisor + PL + SPOC Can be: Apps expert + dev + sponsor => Output: provide a solution for the end users This can always evolve through time if the project requires it
- We keep the same people Once a project requires it, more people might involved. Must be: Business advisor => work with the steering comity & the delivery team Steering commitee => Project director + SPOC + Sponsor => They do not handle the delivery but ensure that things are moving in the right direction Delivery team: Project leaders & developer + Key users Apps expert: punctual intervention => We deliver for the end users
- OIM: No dev Focus on project success Mindset Project implementation steps Project Roles => Ensure to implement succcessful projects By: Onboard the users on time & on budget