The document outlines an agile implementation methodology for Open ERP. It discusses implementation challenges when taking an agile approach and the importance of getting early customer feedback. The methodology involves pre-analysis, implementation in short cycles to deliver value quickly, and ongoing maintenance and support. Key phases of the methodology include understanding requirements, delivering screens and logic, integration, and validation before deployment.

1. Open ERP
Agile Implementation Methodology
Agile Implementation Methodology
&A Nom du fichier – à compléter Management Presentation

2. TOC
●
● Agile & Lean Approach
Agile & Lean Approach
● Implementation Challenges
●
Implementation Challenges
● Our methodology
●
Our methodology
● Pre-Analysis
●
Pre-Analysis
● Implementation
●
Implementation
● Maintenance & Support
●
Maintenance & Support
● Contracts
●
Contracts
&A Nom du fichier – à compléter Management Presentation 2

3. Implementation Challenges
Success =
Success =
Flexible Product + Strong Methodology + Smart Supplier
Flexible Product + Strong Methodology + Smart Supplier
•• An Agile approach:
An Agile approach:
•• Your needs evolves every month
Your needs evolves every month
•• => You can't rely on a 9 months old analysis !!
=> You can't rely on a 9 months old analysis
•• Complexity are in the details
Complexity are in the details
•• => Details are usually discovered at the end
=> Details are usually discovered at the end
•• Risk Management:
Risk Management:
•• Customer feedback as earlier as possible, don't wait that we finally deliver the whole
Customer feedback as earlier as possible, don't wait that we finally deliver the whole
project
project
•• Priorities are chaning => Focus on high-value first
Priorities are chaning => Focus on high-value first
•• Change Management
Change Management
•• Help HR to manage the changes
Help HR to manage the changes
•• Train and communicate internally
Train and communicate internally
&A Nom du fichier – à compléter Management Presentation 3

4. Agile Methodology
Traditional Approach Our Approach
 Quote based on customer's own  Adapt the project and the quote to
analysis OpenERP
 Long development cycles, deliver at  Short cycles, deliver every month
the end  Focus on high values firsts, reorder
 Develop to deliver what's promised priorities monthly
on the contract  Try to discover problems earlier
 Usually discover problems at the  Develop the project like an house
end construction
 Divide the project in small part and
implement
&A Nom du fichier – à compléter Management Presentation 4

5. Be Organized & Systematic
Our Methodology
&A Nom du fichier – à compléter Management Presentation 5

6. Methodology Overview
The Implementation Phases
The Implementation Phases
&A Nom du fichier – à compléter Management Presentation 6

7. Methodology – First Meeting
Help the customer to decide...
•• Help the customer to take a decision:
Help the customer to take a decision:
•• Presentation of the company
Presentation of the company
•• Demonstration of OpenERP
Demonstration of OpenERP
•• Explain the methodology
Explain the methodology
•• If you need more information
If you need more information
••We have books,
We have books,
••You can subscribe a training session (pay a little bit to see everything)
You can subscribe a training session (pay a little bit to see everything)
••You can attend free demonstrations at our offices
You can attend free demonstrations at our offices
•• Next Step:
Next Step:
••A quotation for the Pre-analysis
A quotation for the Pre-analysis
••Sample of deliverables
Sample of deliverables
&A Nom du fichier – à compléter Management Presentation 7

8. Methodology
The Pre-Analysis
&A Nom du fichier – à compléter Management Presentation 8

9. Methodology – Pre-Analysis
A fixed price quotation
•• Your goals
Your goals
•• You work with us to evaluate OpenERP
You work with us to evaluate OpenERP
•• You get an dedicated analysis of your need
You get an dedicated analysis of your need
•• We start the project, no GO/NO GO decision
We start the project, no GO/NO GO decision
•• Our deliverables
Our deliverables
•• Summary of the project (risks, needs, ...)
Summary of the project (risks, needs, ...)
•• Detailed scope of the project (.XLS)
Detailed scope of the project (.XLS)
•• A quote for the full project
A quote for the full project
•• The contract (.DOC)
The contract (.DOC)
•• A Planning
A Planning
•• Our Goals
Our Goals
•• Understand your needs before quoting
Understand your needs before quoting
•• Reformulation of your needs according to our solutions
Reformulation of your needs according to our solutions
&A Nom du fichier – à compléter Management Presentation 9

10. Methodology – Pre-Analysis
How...
•• Your project manager attend a generic training to perfectly understand
Your project manager attend a generic training to perfectly understand
OpenERP, his advantages and limits (5 Days)
OpenERP, his advantages and limits (5 Days)
•• Meeting with the management (1 day)
Meeting with the management (1 day)
•• Goals of the project
Goals of the project
•• Company overview
Company overview
•• Analysis with the “project manager” (5 days)
Analysis with the “project manager” (5 days)
•• Use-Cases
Use-Cases
•• Scope Documents
Scope Documents
•• Internal review by OpenERP experts (3 days)
Internal review by OpenERP experts (3 days)
•• Native vs Parametrization vs To Develop
Native vs Parametrization vs To Develop
•• Risks,
Risks,
•• Presentation of the project (1 day)
Presentation of the project (1 day)
•• Detailed Scope
Detailed Scope
•• Implementation Approach, Quote & Planning
Implementation Approach, Quote & Planning
&A Nom du fichier – à compléter Management Presentation 10

11. Methodology – Pre-Analysis
2 Options...
•• Option 1: help in change management & detailed analysis
Option 1: help in change management & detailed analysis
•• Interview of end-users
Interview of end-users
•• When do you need this:
When do you need this:
•• Your project manager does not know perfectly all needs
Your project manager does not know perfectly all needs
•• You need to prepare the employees to the change
You need to prepare the employees to the change
•• Option 2: implement a use case
Option 2: implement a use case
•• Develop/implement a specific use-case in OpenERP
Develop/implement a specific use-case in OpenERP
•• When do you need this:
When do you need this:
•• You are not sure OpenERP perfectly fit your needs
You are not sure OpenERP perfectly fit your needs
•• You need to convince the managers
You need to convince the managers
&A Nom du fichier – à compléter Management Presentation 11

12. Methodology
The Implementation Project
&A Nom du fichier – à compléter Management Presentation 12

13. Methodology – Implementation
Key ideas...
•• Know the big picture:
Know the big picture:
•• We implement ERP like houses: all plans, all foundations, all electricity, then
We implement ERP like houses: all plans, all foundations, all electricity, then
all finitions, etc.
all finitions, etc.
•• Most suppliers split by dept: accounting (plans, code, configure, test), then
Most suppliers split by dept: accounting (plans, code, configure, test), then
stock mgt (plans, code, configure, test...)
stock mgt (plans, code, configure, test...)
•• Steps: (replace by a picture)
Steps: (replace by a picture)
•• Do a detailed analysis
Do a detailed analysis
•• Deliver all screens
Deliver all screens
•• Start data integration (in parallel with others next steps)
Start data integration (in parallel with others next steps)
•• Build the logic (workflows)
Build the logic (workflows)
•• Build Reports
Build Reports
•• Validate everything
Validate everything
&A Nom du fichier – à compléter Management Presentation 13

14. Methodology – Implementation
Step 1 : The Detailed Analysis
•• Deliverable:
Deliverable:
•• A document that describe the solution, not the need
A document that describe the solution, not the need
•• A list of screens
A list of screens
•• A list of workflows
A list of workflows
•• Some use-case and demo data
Some use-case and demo data
•• Goal: The customer can see the final result after this step !!
Goal: The customer can see the final result after this step
•• => Fast Feedback
=> Fast Feedback
•• Tools: Screens & Workflow Designers
Tools: Screens & Workflow Designers
&A Nom du fichier – à compléter Management Presentation 14

15. Methodology – Implementation
Step 2 : The Screens
•• Deliverable:
Deliverable:
•• A working version on OpenERP that has all screens adapted to the customer
A working version on OpenERP that has all screens adapted to the customer
need. Demonstration data are set.
need. Demonstration data are set.
•• After this first development step:
After this first development step:
•• The customer can test the solution and organize workshop with end users →
The customer can test the solution and organize workshop with end users →
Quick feedback
Quick feedback
&A Nom du fichier – à compléter Management Presentation 15

16. Methodology – Implementation
Step 3 : The Logic - Workflow
•• Deliverable:
Deliverable:
•• A working version on OpenERP that integrate all the business logic and
A working version on OpenERP that integrate all the business logic and
computed fields
computed fields
•• After this phase:
After this phase:
•• The whole solution is working and tested by the customer. They are no
The whole solution is working and tested by the customer. They are no
report, nor customer data in the solution.
report, nor customer data in the solution.
&A Nom du fichier – à compléter Management Presentation 16

17. Methodology – Implementation
Step 4 : The Reports
•• Deliverable:
Deliverable:
•• The solution is complete.
The solution is complete.
•• After this phase:
After this phase:
•• Everything works, we still need to validate with customer's own data.
Everything works, we still need to validate with customer's own data.
&A Nom du fichier – à compléter Management Presentation 17

18. Methodology – Implementation
Step 5 : Delivery
•• Deliverable:
Deliverable:
•• All points of the main Scope Documents are signed by the customer.
All points of the main Scope Documents are signed by the customer.
•• After this phase:
After this phase:
•• We can start training end-users and put in production
We can start training end-users and put in production
&A Nom du fichier – à compléter Management Presentation 18

19. Methodology
What's next ?
&A Nom du fichier – à compléter Management Presentation 19

20. Methodology – After-Sales Services
Step 5 : The facts
•• It will not work perfectly, directly !!
It will not work perfectly, directly
•• We continue to assist end-users
We continue to assist end-users
•• We are reactive when troubles are detected in production
We are reactive when troubles are detected in production
•• We need to be supported by management
We need to be supported by management
•• → We do provide a guarantee of needs
→ We do provide a guarantee of needs
•• After 2 months:
After 2 months:
•• Everyone will be happy !!
Everyone will be happy
&A Nom du fichier – à compléter Management Presentation 20

21. Methodology – After-Sales Services
Step 5 : Maintenance & Support
•• … to be continued ...
… to be continued ...
&A Nom du fichier – à compléter Management Presentation 21

22. Next Step ?
&A Nom du fichier – à compléter Management Presentation

23. Next Step
Let's continue...
•• Next Step
Next Step
•• Quote for the Pre-Analysis phase
Quote for the Pre-Analysis phase
•• Option 1: change management
Option 1: change management
•• Option 2: use-case
Option 2: use-case
&A Nom du fichier – à compléter Management Presentation 23