You've been invited into the Kudos (beta program) private group. Chat with others in the program, or give feedback to Atlassian.
View groupJoin the community to find out what other Atlassian users are discussing, debating and creating.
A release isn't just an application switch. There is much more happening under the hood.
How many times someone told you they just push to production and release is done? Maybe from their side, but there is a much bigger picture we should understand, plan and track when we're delivering a product to our customers.
In product delivery, we can treat stages as quality gates. Changes usually move through different environments where the quality checks are done and it all ends with the production release.
Example stages of the development release process
Well, it's not only about development. Usually, you have many teams aiming towards a single goal - release or in other words - launch. Each of them contributes to the release in a different way.
Let's have a look at an example. To deliver a new web app to the users, the release first goes through design, then it's passed to development and testing. In the meantime, the Marketing team is preparing strategy and content to make sure the Launch date isn't postponed to wait for them.
Example of stages that application release goes through in order to be launched to users.
All teams are busy and need to finish their part on schedule. Even a small delay means blocking the next team to start and pushing the launch date. To be able to identify bottlenecks and prevent slipping of the releases it's good to track not only overall release status but also the statuses of its phases.
Release stages are great, but creating them in a way they fit for every single release and every single client is hard.
But that should be simple enough to solve with release templates. Let's take our web application example again. We identified these types of releases or templates:
Example of different types of application releases
But you can also create types based on the environments (web app, mobile, UI-library) or based on your clients.
Having a stable release process where the length of each stage is planned gives many opportunities for future improvement and success with delivering on time.
If your development team already uses Jira, you can try our app, Swanly - Release Management Timeline.
In Swanly you can create your release templates and track release progress on the timeline or the list. Visit our marketplace listing to start 30 days free trial and learn more.
Releases are the core of every project and it is crucial to understand their stages. On top of that, enhancing the release management will speed up the overall delivery process. It will save time for all teams, involved in the game.
This post was created by Jexo team and is also available on our blog.
Nikki Zavadska _jexo_
Co-founder of Jexo
Jexo
Brighton
14 accepted answers
Atlassian's marketplace partners have had a very productive start to 2021! Since our last roundup, our developer community has added over 160 new cloud apps to the Atlassian Marketplace to help you...
Connect with like-minded Atlassian users at free events near you!
Find an eventConnect with like-minded Atlassian users at free events near you!
Unfortunately there are no Community Events near you at the moment.
Host an eventYou're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events
4 comments