Release Management

Establishing a release cycle is vital because:

• It creates an opportunity to meaningfully discuss nonfunctional testing that the software may need.
• It announces a timetable for when stakeholders can expect to get some functionality. If they know that functionality will be regularly released, they can get on with agreeing what that functionality will be.
• It creates a routine with which all teams can align (including marketing and engineering).
• It gives customers confidence that they can order something and it will be delivered

Year clock

Aim is to make major release every year. In between aim is to make 2-3 smaller releases. Whether it is two or three is up to the Development Streering Group to decide.

1. Major version x.0 will be released in January.
2. Version x.1. around March (bug fixes mainly for x.0),
3. version x.2. in June (smaller new eatures) and
4. version x.3. in September-October (again bug fixes but now for x.2.)

Offer predictability

Intention is that we can offer some kind of roadmap and predictability for the participating companies. This is achieved by having public product backlogs for each version - past, current and future.

Versioned Product backlogs

• Current version roadmap

• older versions...