This article explains the Docebo release cycle which is based on Agile principles coupled with a continuous delivery process of new developments and fixes.
The Agile methodology is essential for SaaS products, such as the Docebo learning platform, because it aligns with the dynamic nature of the software, facilitates quick adaptations, and ensures the delivery of high-quality, continuously improved software solutions.
The Docebo Product team is made up of different teams, each one responsible for one or more areas of the platform. Each team plans and prioritizes the developments that will be included in the major releases according to market needs, known issues and the ideas posted to the Ideas section of Docebo Community.
Development and tests
When future developments are roadmapped, the teams organize their work into sprints.
The coding tasks are divided according to team members’ area of specialization (front-end or back-end) and the code produced is reviewed by a senior developer before it gets tested by the Quality Assurance team both with manual and automated tests.
The Docebo sprint cycle duration is two weeks. It starts on Monday and is completed on the Friday morning of the second week. The Friday afternoon of the second week is used by teams to conduct a Sprint retrospective first and then plan for the following sprint.
The continuous delivery process of Docebo is made up of:
Weekly maintenance releases
All Docebo platforms are updated every week. The updates include both fixes to defects and soft change behavior of existing features. The updates are usually deployed on different days: Mondays are for Docebo internal platforms and small/medium enterprises, the following Wednesdays are for Enterprise customers, and Wednesdays of the following week are for large customers. The deployment process does not require any downtime.
Major changes to existing features or the introduction of new features are managed through a more articulated process composed of three steps:
- Internal roll-out: Updates are released on Docebo's internal platforms ten weeks before they are publicly available. An extended Docebo team is can then navigate the final version of the functionality, provide usability feedback and detect bugs so that the development teams can fix them before features are released on external platforms. This step is also useful to Docebo employees to get to know the new features and provide better support.
- Customer sandboxes: Customer sandboxes are updated two weeks after the internal roll-out is completed (and eight weeks before the general availability) to allow Superadmins and Power Users to learn about what’s new.
- General availability: Eight weeks after the customer sandboxes update, the new features are rolled out on all customers' production platforms.
Find a list of the resources that Docebo makes available to all users to learn more about the content of the releases.
Product updates page on docebo.com
Have a look at the Product updates page on docebo.com (opens in a new tab) to make sure you do not miss out on the newly released features.
Product release area in Docebo Community
The release notes are also available on the Product release area of Docebo Community (opens in a new tab) where you can discuss them with other Docebo users and contact the Docebo staff for further details.
Docebo University releases courses
The Docebo University team prepares a course for every major release to enable you to the new features and functionalities. Have a look at the DoceboU release courses (opens in a new tab).
If you have a sandbox, keep an eye on the Product release area of Docebo Community (opens in a new tab) for the Now live in sandbox posts for a complete overview of the features released. Docebo Help articles are updated when features are released in sandboxes to reflect new features and offer resources in multiple languages.
Known issues page
The Known issues section of Docebo Community offers information on known problems, providing insights into their nature and 'impact on software operation, as well as updates on their resolution status.