A lot of people still feel a great sense of unease prior to releases of new applications. We ourselves remember the days when sites were down for a whole weekend and we had to work at a feverish pace to ensure everything would be up and running properly by the Monday. Everyone would have butterflies in their stomachs. But nowadays things are completely different. The time from user story to going live has dropped from several months to 48 hours in the most extreme cases.
Then, big launches were the order of the day, and these also involved big risks. Today almost no big launches take place, for a number of reasons. Firstly, you can no longer wait months to launch when there is so much pressure from competitors. Nor can you take big risks in a cutthroat business climate.
1. The time aspect
There has been a radical change in the timeframe from user story to going live. What once took several months can now be counted in days. For businesses, the advantage of more frequent smaller releases is that the development team can get feedback from customers sooner as to what works and what does not.
2. Increased revenue
Frequent launches also result in closer business relationships and more opportunities for new business. If customers return more frequently to your site because they know that new experiences await them, this enhances the site’s time-to-value.
Automating the release process with different tests right up to going live also allows more secure roll-out. Larger amounts of changes can be handled, at the same time as retaining the high quality of the IT services.
4. Greater flexibility
Within e-commerce, being able to respond to the smallest change in the market and to trends as they emerge is a matter of life and death. Tracking and analysing large quantities of data during the release process provides a quicker insight into changes in customer behaviour and needs.
5. Increased productivity
Automations that are based on standards and best practices result in increased productivity, as different steps and environments from development to release can be streamlined.
6. Eliminate duplicate work
With a strict release process and automation, unnecessary duplicate work and the risks associated with manual interventions disappear. Instead, interconnected tests are carried out step by step, based on correct information.
7. Better cooperation
One of the most important gains with the release process is the potential for improved cooperation. Information sharing and regular communication bridge the differences in experience and methodologies of the development teams.
Why is RedBridge so successful in its release process?
“It holds no surprises. Our process minimises the risks associated with launches. The overall control allows you to take decisions based on reliable information data. If we see an error, we go back to the previous release, make the necessary corrections and continue from there. Many people get stressed out if a release doesn’t work as it should. They start looking to correct the error in the production environment and circumvent all agreed rules. This is risky,” says Stefan Andersson of RedBridge.
“We help the developers by showing them how you can roll out small changes in a structured way on a continual basis without incurring any risk, instead of doing it just a few times over but at high risk. We also offer good support to smaller organisations that do not have the necessary