The Openbravo Development Process
This document describes the Openbravo Development Process, which is the methodology used to produce new release of Openbravo ERP.
The objectives of the methodology are:
To achieve these objectives the Openbravo Development Process aims at being lean but formal and takes inspiration from my iterative and agile development processes such as Scrum and the Agile Unified Process.
The above picture is a high level representation of the overall process, which manages the full life cycle of a release and it is composed of four phases:
- Planning: The purpose of the planning phase is to we review the backlog of feature requests and:
- Revise the product road map
- Identify the detailed list of feature candidates for the next release
- Construction: During the construction phase, each candidate feature is independently developed using an iterative approach. At the end, all the features are merged and the new release is packaged.
- Launch: The launch phase covers all the steps that are necessary to deliver a successful release to the Community, including (but not limited to):
- Alpha testing
- Beta testing
- Collateral development
- Maintenance: The maintenance process covers all the activities that are required to update a production release, including fixing bugs and publishing maintenance packs.