We have several IT teams developing Leon in Agile methodology, incorporating some techniques of Scrum and Kanban as well. Each team specializes in a particular group of functionalities in the application.

Each team works in 2-week sprints and we update Leon in such cycles. During each sprint, developed functions are tested internally and if tests are passed, we schedule to release them to production. If not, it is postponed to the next sprint.

We use a “canary deployment” model, in which we gradually enable new features, starting with a randomly chosen small sample of our customers. On the day of starting the deployment, we update our online manual and release news about new functions/updates via a newsletter on the application page. After a few days, all new features are available to all our customers on the production server (under leon.aero).

If there are any serious issues found, we postpone publishing to the production server for as long as necessary.

After completing a sprint, each team is planning development schedule for the next sprint from our backlog. The backlog is being supplemented by Product Owner based on general development plans, customers suggestions and bug fixes. That is why it usually takes a few sprints to deliver any new functionality or customisation to the production server.

Our current development cycle:

Leon development cycle