openerp - project methodology

PRESENTER

SAMUEL MART INS

OpenERP Project Methodology

SAMUEL MART INS

PROJECT AND SERV ICES D IRECTOR

S AM@OP EN ER P . C OM

OpenERP project STEPS

Pre-Sales Demo TrainingPre-analysis

offer

GAP-analysis POC GAP-analysis Estimation Planning

Detailed analysis

Functional analysis

Technical analysis

OpenERP Enterprise

DevelopmentsDevelopments & Unit tests

Integration tests

Client testing User trainingUser

Acceptance testing

DeploymentLive

environment release

Data migration

Go liveWarranty period support

Post Deployment support

L1 support L2 support

OpenERP Enterprise

Project – phase by phase

� The purpose of the Gap Analysis is to

� Evaluate the project scope


Evaluate the project scope

� Determine the customization level which will be required

� Assess the investments required

� Plan the project

� Organise the project governance


HOW?Step 1: Company Mind Maps – Interviews:



HOW?Step 2: Key Users Mind Maps – Interviews:



HOW?Step 3: Define the GAPS and Estimates:


List the GAP’s

Weight the GAP’s :

• Complexity• Analysis• Development


HOW?Step 3: Define the GAPS and Estimates:


Estimation based on:Estimation based on:

• Project Management• Analysis• Development• Testing•Migration• Deployment• Support


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


� The deliverables of the Gap Analysis are :� Gap Analysis reporting (Needs, Scope, Risks, GAP’s)


� Gap Analysis reporting (Needs, Scope, Risks, GAP’s)

� Gap Analysis Matrix

� Project Road map

� Financial estimate

� Agreement on validation process and project


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� The Analysis purpose is to� Design the solution� Validate the solution� Validate the solution� Finalise the development estimationfrom 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


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� BE AGILE

Short Project Cycles:

• Increase Project visibility with client(demo’s, user tests,...)

• Keep control of requirements (quicktechnical and functional validation)

• Increase quality (early testing allowsyou to identify issues early and solvethem)


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� How to analyse:

� Use the Detailed analysis template to define:

� Process description and workflows� Process description and workflows


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� Views and wizards using mockups


Detailed analysis

Functional analysis

Technical analysis


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


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� Change requests

Change Request Flow


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� The deliverables of the Analysis are :� Detailed description of

� Processes and Activities � 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


Detailed analysis

Functional analysis

Technical analysis


Integration tests

� The deliverables of the Developments are :� Software configuration� Software configuration

� Custom modules

� Interfaces

� Data Import tools

� Test plan


� The Client Testing purpose is to

� Train the client End Users


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,...)


� Bugs shared view


Acceptance testing


� The deliverables of the Client Testing (UAT) are :


Acceptance testing

� Training material

� User guides

� Full test report

� Approval for production deployment


� The (post) Deployment purpose is

�Deliver the solution into the production server

DeploymentLive

environment release

Data migration

Go liveWarranty 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,...)

openerp - project methodology

Business