2. Developers
  3. Delivery model

Delivery model

We work in an agile mode: As project maintainers, we work in Kanban, a lean method to manage and improve work across human systems. This approach helps to manage work by balancing the demands with available capacity, and improving the handling of bottlenecks. Product releases happen in short cycles (iterations), with semantic versioning to provide a shared indication for library authors and users to communicate with each other, using a three-part number, MAJOR.MINOR.PATCH, incremented as follows:

  • MAJOR, when a change is API-incompatible with previous releases;
  • MINOR, when new functionality is added in a backwards-compatible manner;
  • PATCH, when bug fixes are made in a backward-compatible manner.
Continuous delivery


We constantly review our priorities and adapt to new needs, through a monthly cycle of review and prioritisation of the product backlog by members, delivering in a continuous cycle.

We focus on product quality by following a streamlined development process from plan through to deploy, including multiple systematic testing and quality assurance procedures. We are user driven, with a user centred design approach using a variety of research and design techniques involving users throughout the whole process so to create highly focused and accessible products ensuring a desirable look, feel, and usability – ‘Product Excellence’.


Interested to explore further?

If you would like to get involved and discover more about the .Stat Suite open source project then please visit our Gitlab documentation pages where you’ll find information to help you get started, an overview of the .Stat Suite Open Source Framework and different services, the Community code of conduct, as well as the 3 distinct .Stat Suite delivery mechanisms .Stat Suite from source code, .Stat Suite from containers, .Stat Suite as a Service.

Also in this Section