JA Sugite - шаблон joomla Оригами

An open source business suite of applications

Odoo OpenERP Implementation Methodology

The following is an overview of our implementation process and the activities we perform or assist you in performing.

1. Business Review

This step begins during our sales process.

  • We speak with you and your users about their requirements and how they currently perform their duties
  • We identify the current processes and document them
  • This provides us with an understanding of your business environment and helps us speak your language

2. Project Planning

Gap Analysis

  • Helps us to cover the functional gap

Project Planning

  • We work with your team to identify the discrete tasks, responsibilities and time lines for your project
  • Establish proper system policies for maintaining and backing-up data
  • Executing tasks as per the Implementation Plan in conjunction with the Project Team
  • Creation of required custom reports

3. Re-engineering, Installation, Team training, Testing, Conference room pilot testing

Customizing, installing and/or upgrading modules and copy it to a test database for use in the pilot testing phase of the project.

Customization using agile Scrum methodology

i. Sprint Planning Meeting (Held at start of every sprint)

At the start of each sprint, the project team will meet for a “Sprint Planning Meeting”. During this meeting the project team determines which items, from the Product Backlog, can be completed for the upcoming Sprint and breaks the items down into tasks in the Sprint Backlog. If new requirements have been discovered or requirements have changed since the Project Estimate Meeting then those items would get updated in this meeting.

ii. End-User Training: The following are some examples of key areas that will be addressed during training:

  • How to enter transactions, and the different ways they can be entered and posted
  • How to maintain the data that is accumulating in your system
  • How to use inquiries and reports to obtain the information you wish to access
  • How to complete period and year-end procedures in each module

iii. Conference Room Pilot Testing

The pilot test is based on the processes that are developed during the business process engineering, and it serves two functions:

  • Test the setup of the system
  • Prove the validity of the re-engineered processes and work instructions
  • Provide additional training for team members by simulating their normal day-to-day activities

iv. Go-Live!

During the go-live period we ensure that all requirements have been covered to ensure a smooth transition onto the new business system. It is at this time that all tasks on the project plan have been complete, all users trained, all processes reengineered, and the final data migration/conversion is performed

4. Post Implementation Review and Continuous Improvement:

A plan for on-going improvement will be discussed and project planning for additional phases of your implementation may be scheduled.


Client Says

" Pragtech did an excellent job of providing research support for populating our applied systems web development wiki."

Daniel Cer

Applied Stacks

I have really enjoyed working with pragmatic. The team stayed organized and followed through with things. We were able to merge the pragmatic team with our own development team in a pretty effective way. I plan on using Pragmatic again on future projects.

David Richards

Fleet Ventures

We are very pleased with the way Pragmatic did the work on the edu2be and learning content management system using Ruby on Rails technology. They put in lot of hard work to deliver the project on time and on budget.

Anjan Acharya