SugarCRM Development

sugarCRM Development

The Enable SugarCRM Development team are based in the UK at our Head Office just outside of London, that have been developing and customising SugarCRM solutions since 2004.

We use the Agile Software development method, which is where requirements and solutions evolve through collaboration between self-organising and cross functional teams.

It promotes adaptive planning, evolutionary development and delivery, a time boxed iterative approach, and encourages rapid and flexible response to change. It is a conceptual framework that promotes foreseen interactions throughout the development cycle.

Contact our SugarCRM Development Team for more information and quotes.

Development Procedures

We commit all of our changes to a development branch of the application and the code is both reviewed and tested prior to deployment to the master branch.

A rollback of code is always possible due to the way the code is deployed, but we back up our development environments on a 4 hourly schedule.

The customisation/integration procedures normally follow these guidelines but can vary:

  • Analyse the business process
  • Determine customisation requirements and specifications
  • Approve and freeze customisation specifications
  • Develop the customisation
  • Review the customisation
  • Test the system
  • Get a pilot group to use the product
  • Finish the customisation
  • Process audit

Quality Management

All code deployed within the SugarCRM application has been unit tested and reviewed before deployment. Any development carried out by our developers is subject to the same unit testing, using both Jenkins servers and auto unit testing methods.

All code developed by us is via a development change server which both provides both forward and undo capability.

Data Capture

Data Capture is via the SOAP and REST API which is fully documented on SugarCRM web site

Our development department use both scripts for data mapping and CloverETL Designer to ensure quality of data imports these can be saved and run either manually or automated.