Most Powerful Open Source ERP

ERP5 Guideline Project Management Best Practice

Table of Contents


The following guidelines contain conventions for managing projects in ERP5 from basic setup of repositories to structuring of a project and its implementation.

They guidelines have been created based on successful and failed projects from the past years and are an attempt to formalize the lessons learnt in order for future project to be successful. The guidelines are for managers and developers alike and aim to provide a basic set of conventions around which to structure and organise a project.

ERP Implementations Fail Often

If you are familiar with ERP implementations at Nexedi and beyond you will know that a considerable number of projects fail during different stages. Reasons can be multiple from definition of the overall project scope to formailization of requirements or their subsequent implementation. A project team can put in their best effort and the project may still fail due to reasons outside of the project teams sphere of influence.


There is no golden rule to make a project a success and a lot of effort and preparation should go into the sales phase to ensure a project is realistic enough to be managed successfully.

Still, the red line guiding through all conventions is communication: within the team, between team and project management, towards the client or with management - communication ensures that everyone involved knows what needs to be done when and avoids wasting time, resources and energy on topics potentially not relevant for the project outcome.

The following guidelines are split into recommendations, rules and crimes and every project manager at Nexedi should know them inside out to help in day-to-day management of projects.