Skip to content

Development process

saleiva edited this page Jan 7, 2014 · 15 revisions

Development pace

We target for a new version each two weeks which would include new features or big improvements (X.Y.0). One week after the release, we will release another version which would include fixes and small improvements related to the previously released version (X.Y.Z). This makes a release per week.

Prioritisation

Priorities are set based on these factors: Number of people requesting a feature, possible impact in the KPI's, value added for existing internal processes, difficulty and availability of resources. Priorities are discussed (and changed if it's needed) during an stand-up meeting that occurs weekly. If needed the discussion will be followed by email.

Version tagging

Versions are tagged with 3 numbers (X.Y.Z). First number (X) will only change when mayor changes on the software occur. Second number (Y) indicates versions where we incorporate new features or big improvements. The last number is only being used for versions that only fix bugs and add small improvements related to the actual version.

Clone this wiki locally