TinQwise Product release cycle

Our product development and release cycle

Eva Tjitske Jansen avatar
Written by Eva Tjitske Jansen
Updated over a week ago

We work in 2-week sprints with agile methodologies.

We write our sprints in the following manner: here's the example S21.13

  • S = Sprint

  • 21 = the year 2021

  • 13 = the week 13

S21.13 means we included tickets (chunks of work) in the Sprint backlog to be worked on during week 13 and week 14. Usually we then push the changes during releases on Wednesdays of the following week, in this example it would mean week 15.

If it’s an urgent issue or a bug fix, we usually push a hotfix before, in this case during week 13 or week 14.

We send out release notes every second Wednesday internally and soon through Intercom.

Here's a summary of all activities part of our release cycle:

Did this answer your question?