The document outlines the methodology for an OpenERP project. It describes the key steps and phases in the project including pre-analysis, proof of concept, gap analysis, estimation, planning, analysis, development, testing, deployment, training, and post-deployment support. The goal is to take an agile approach, working in short sprints to quickly deliver value to the customer.

1. OpenERP Project
Methodology
PRESENTER
SAMUEL MARTINS
PROJECT AND SERVICES DIRECTOR
SAM@OPENERP.COM

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

3. Project – phase by phase
GAP-analysis POC GAP-analysis Estimation Planning
The purpose of the Gap Analysis is to
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
GAP-analysis POC GAP-analysis Estimation Planning
HOW?
Step 1: Company Mind Maps – Interviews:

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

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

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

8. Project – phase by phase
GAP-analysis POC GAP-analysis Estimation Planning
HOW?
Step 4: Plan the Project
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
GAP-analysis POC GAP-analysis Estimation Planning
The deliverables of the Gap Analysis are :
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 Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
The Analysis purpose is to
Design the solution
Validate 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 Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
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 Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
How to analyse:
Use the Detailed analysis template to define:
Process description and workflows

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

14. Project – phase by phase
Detailed Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
Access rights
Objects User type 1 User type 2 User Type 3
Rights Rights Rights
Name CRUD C R
Address,… No D U
“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.

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

16. Project – phase by phase
Detailed Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
The deliverables of the Analysis are :
Detailed description of
Processes 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 Functional Technical Development Integration
analysis analysis
Developments s & Unit tests tests
analysis
The deliverables of the Developments are :
Software configuration
Custom modules
Interfaces
Data Import tools
Test plan

18. Project – phase by phase
User
Client testing User training Acceptance
testing
The Client Testing purpose is to
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
User
Client testing User training Acceptance
testing
Bugs shared view

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

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