The document outlines the methodology for an OpenERP project, including phases for gap analysis, analysis, development, client testing, deployment, and post-deployment support. The purpose of each phase is described, such as evaluating requirements during gap analysis, designing and validating solutions during analysis, and implementing the solution and testing during development. Key deliverables are also listed for each phase, such as gap analysis reports, detailed process descriptions, and test plans.

1. P R E S E N T E R
S A M U E L M A R T I N S
OpenERP Project
Methodology
S A M U E L M A R T I N S
P R O J E C T A N D S E R V I C E S D I R E C T O R
S A M @ O P E N E R P . C O M

2. OpenERP project STEPS
Pre-Sales Demo Training
Pre-analysis
offer
GAP-analysis POC GAP-analysis Estimation Planning
Detailed
analysis
Functional
analysis
Technical
analysis
OpenERPEnterprise
Developments Developments
& Unit tests
Integration
tests
Client testing User training
User
Acceptance
testing
Deployment
Live
environment
release
Data
migration
Go live
Warranty
period
support
Post
Deployment
support
L1 support L2 support
OpenERPEnterprise

3. Project – phase by phase
The purpose of the Gap Analysis is to
Evaluate the project scope
GAP-analysis POC GAP-analysis Estimation Planning
Evaluate the project scope
Determine the customization level which will be required
Assess the investments required
Plan the project
Organise the project governance

4. Project – phase by phase
HOW?
Step 1: Company Mind Maps – Interviews:
GAP-analysis POC GAP-analysis Estimation Planning

5. Project – phase by phase
HOW?
Step 2: Key Users Mind Maps – Interviews:
GAP-analysis POC GAP-analysis Estimation Planning

6. Project – phase by phase
HOW?
Step 3: Define the GAPS and Estimates:
GAP-analysis POC GAP-analysis Estimation Planning
List the GAP’s
Weight the GAP’s :
• Complexity
• Analysis
• Development

7. Project – phase by phase
HOW?
Step 3: Define the GAPS and Estimates:
GAP-analysis POC GAP-analysis Estimation Planning
Estimation based on:Estimation based on:
• Project Management
• Analysis
• Development
• Testing
• Migration
• Deployment
• Support

8. Project – phase by phase
HOW?
Step 4: Plan the Project
GAP-analysis POC GAP-analysis Estimation Planning
Plan the project trying to phase development in small sprints:
• short analysis/development time => Quick in customer’s hand
=> Be AGILE

9. Project – phase by phase
The deliverables of the Gap Analysis are :
Gap Analysis reporting (Needs, Scope, Risks, GAP’s)
GAP-analysis POC GAP-analysis Estimation Planning
Gap Analysis reporting (Needs, Scope, Risks, GAP’s)
Gap Analysis Matrix
Project Road map
Financial estimate
Agreement on validation process and project

10. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
The Analysis purpose is to
Design the solution
Validate the solutionValidate the solution
Finalise the development estimation
from both a functional and technical point of view
The Development purpose is to
Implement the solution,
Test the solution
Validate the solution with Key Users

11. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
BE AGILE
Short Project Cycles:
• Increase Project visibility with client
(demo’s, user tests,...)
• Keep control of requirements (quick
technical and functional validation)
• Increase quality (early testing allows
you to identify issues early and solve
them)

12. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
How to analyse:
Use the Detailed analysis template to define:
Process description and workflowsProcess description and workflows

13. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
Views and wizards using mockups

14. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
Access rights
Objects User type 1 User type 2 User Type 3
Rights Rights Rights
“Rights” = access rights.
“C” = create : user can create a new value for the object,
”R” = read : user can read/access the object,
“U” = update : user can modify an existing object,
“D” = delete : user can delete an existing object,
“No”: user has no access to the object.
Rights Rights Rights
Name CRUD C R
Address,… No D U

15. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
Change requests
Change Request Flow

16. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
The deliverables of the Analysis are :
Detailed description of
Processes and ActivitiesProcesses and Activities
Views, Workflows and Wizards
Access rights
Reports and Data Model
Detailed interface description
Infrastructure setup
High level Test Plan
Review workload estimates and planning

17. Project – phase by phase
Detailed
analysis
Functional
analysis
Technical
analysis
Developments
Development
s & Unit tests
Integration
tests
The deliverables of the Developments are :
Software configurationSoftware configuration
Custom modules
Interfaces
Data Import tools
Test plan

18. Project – phase by phase
The Client Testing purpose is to
Train the client End Users
Client testing User training
User
Acceptance
testing
Train the client End Users
Handover the application to the client
Allow the client to perform end to end testing including:
Application
Interfaces
Access rights
Outputs
Reports
Put in Place the support tools (Bugs shared view,
governance,...)

19. Project – phase by phase
Bugs shared view
Client testing User training
User
Acceptance
testing

20. Project – phase by phase
The deliverables of the Client Testing (UAT) are :
Client testing User training
User
Acceptance
testing
Training material
User guides
Full test report
Approval for production deployment

21. Project – phase by phase
The (post) Deployment purpose is
Deliver the solution into the production server
Deployment
Live
environment
release
Data
migration
Go live
Warranty
period
support
Post
Deployment
support
L1 support L2 support
Deliver the solution into the production server
Migrate the data if any
Launch the production activities
Support users (Question / bug fixing,...)