Releases

A software release is the sum of the stages of development and maturity for a piece of computer software. Releases continuously increase the feature set of your application without prolonging the wait

Why we work with Releases

1. The whole agile process is coordinated around Release, means we build, test and reviewied in every Release.

2. The process involves several activities that include requirements analysis, code development, creating the build, deployment, and software testing.

3. A release cycle is a collection of tasks and requirements to be implemented in a specified time.

4. Releases are the key for every successful project, the complexity of requirements and eventual complications can be avoided.

Types

We differentiate between 3 types of releases to further enhance the flexibility of implementing features while still maintaining the stability and continuity of the production application.

Feature Release

Contains stories and tasks which enhance the application with new features and functionalities. All of those require (as a rule of thumb) more then 4 hours to be implemented and are connected to a wider set of functionality. Those releases are generally longer in duration > 2 weeks as the complexity of tasks require the time to be implemented and tested. Tasks and delivery is planned in advance together with the client to control feature rollout timelines.

Refinements

Refinements discovered during acceptance phase will enhance the feature release with additional tasks that are collected separately in a release marked as "Refinements".

Support Release

The agile counter part to our feature releases, short duration < 5 working days, issues and corrections which urgently need to be delivered to the client. This improves the stability and continuity of the current production application.

HotFix Release

Used in case of a critical issue on any production application, containing one task solving the problem.

Phases

To monitor and track the current progress and state of a releases we defined following 8 states.

• PLANNING - Collect requirements and define the timeline

• APPROVED - Approved by the client, awaiting implementation

• DEVELOPMENT - Currently in development

• RELEASED - Development completed (Internal QA passed)

• TESTING - Currently deployed for acceptance testing from client.

• ACCEPTED - Ready for deployment (Acceptance testing passed)

• REJECTED - Release didn't pass acceptance

• CANCELLED - Cancelled (Req. new planning)

Numbering

Every release (so called version) has predefinition numbering system so everyone can track progress.