Swiss Re Halves Release Management Team’s Support Time

by Philipp Junghans // Last updated on July 12, 2024  

Release Management Apwide Golive Swiss Re Study Case
Philipp

After replacing Excel spreadsheets, Philipp Junghans, Release Manager at Swiss Re, noticed a 50% reduction in calls and e-mails for his team.

This case study was first published on June 20, 2020

Last September, I accepted a new mission at Swiss Re:
Taking over the Release Management for a program of 12 (very) inter-connected applications.

Our teams were already embracing Agile methodologies:

  • Each application had its own Scrum team
  • 2-week sprints, monthly cross-application release cycles
  • High-level prioritization for the whole program on a quarterly basis
  • All dev teams using Atlassian suite (Jira, Bamboo, Confluence)

Challenge

However, we were facing some difficulties as well:

  • Quite a lot of manual testing, with QA teams spread around the world
  • A limited number of end-to-end Test Environments, creating bottlenecks
  • Many calls and emails about the same kind of questions:
Swiss Re Release Management Questions

People often complained about planning changes, because the information was not well communicated, and also because they did not understand the complexity that our Release Team was dealing with!

After some discussions with our main stakeholders, it appeared that the root cause was a lack of transparency around our Release Planning. Not surprisingly: it was stored in an Excel spreadsheet:

Excel Timeline For Release Management

Our initial Timeline updated in an Excel Spreadsheet - Full size on click!

This manual process was not only error-prone but also frustrating, for instance when one of our coworkers went for a 3-week holiday and left locked the file we had to update urgently...

Excel File Locked For Editing

Moreover, it became clear that every stakeholder was interested in different pieces of information present on our Timeline. Dev teams were mostly interested in the deployments to non-production environments, QA teams in the testing phases, business in the Go-live dates, etc.

How do we get a single source of truth and provide each stakeholder with the information they need, in real time?

Basic Solution: Confluence Team Calendars

After a round of discussions, we agreed to replace our Excel spreadsheets with Confluence Team Calendars. Each Environment category (DEV, TST, SIT, PROD) got a dedicated Calendar.

Confluence Team Calendars For Release Management

Confluence Team Calendars used for Release Management - Full size on click!

It was a revolution - we finally got our single source of truth, accessible live and for everyone! We could show/hide Calendars with the tick-boxes from the right panel and it was even possible to display the Timeline in our Outlook Calendars.

But there were still some requirements not entirely fulfilled:

  • How could we know if the reality was in line with the plan?
  • How could people be notified when new events were scheduled on specific Environments?
  • How could we support the Environment booking process?
  • How could we compare the planning with the reality and understand how to improve for future releases (PIR: Post-Implementation Reviews)?

It became clear that we had to look for a proper Environment Management tool if we wanted to go further in improving our Change and Release Management processes.

Best Solution for Release Management: Golive for Jira

Our first reflex was to look at the Atlassian Marketplace.
That's where we found Golive, the Release & Environment Management Hub for Jira.

In a few hours, we managed to install, configure the tool, and import our Confluence Team Calendars using the Calendar iCal import feature.

Release Timelines

Release Management Timelines With Jira

Release Timeline with Jira and Golive - Full size on click!

Golive Timelines are similar to Team Calendars, with additional advanced features, for instance:

  • Create swimlanes per Environment or per Calendar
    → Easily measure the impacts when planning activities and releases
  • Issue Calendars to display Jira issues (with dates)
    → Very useful for our infra activities that were already using Jira issues
  • Milestones
    → A better way to show our Deployments and Go/NoGo Meetings

When we save a Timeline, it remembers all the settings: lists of selected Calendars, which ones are shown/hidden, timeframe, etc. That way, we can easily share Timelines showing different views for different stakeholders.

Moreover, Golive Timelines can be embedded into Jira Dashboard and Confluence pages - useful for sharing an always-up-to-date plan with the rest of SwissRe.

Release Management With Jira Dashboards

Change & Release Management Dashboard - Full size on click!

Apwide Ebook Banner
Mastering Communication With Release Dashboards

Notifications

Before, people often complained about receiving too many emails from our Release Team.

Now with Golive, we could move from a PUSH to a PULL mechanism, where our team members and stakeholders could subscribe to granular notifications (and unsubscribe in a single click!).

For instance, just subscribe to "status change" and "deployments" notifications for the UAT and SIT Environments. That way, you will avoid all non-relevant communications (linked to other activities or other Environments).

Granular Notifications To Follow-Up On Environment Changes

Different types of notification for each Environment

Bamboo Integration

We moved to the next level when we decided to automate the updates of the versions deployed on the Golive Environments.

It was super easy to make this integration - we followed the Bamboo integration video tutorial and only had to write a few lines to create a new task in our deployment script, updating Golive automatically each time a new deployment was executed.

Deployed versions are now updated in real-time in all our Jira and Confluence dashboards:

Swissre Environment Gadget

Environment Gadget for Jira and Confluence - Full size on click!

And we can easily compare the plan (milestones) to the reality (yellow boxes):

Compare Deployment Logs With Release Plans At Swissre

Timeline showing Deployments vs Release Plans - Full size on click!

Results

We wanted people in our organization to better understand the complexity we were dealing with.

With Golive, we were able to "decompile" that complexity and thanks to the new Timelines and Dashboards, our stakeholders can identify the reasons of planning changes and the impacts of delaying the activities under their responsibility.

In summary, Golive helped us to:

  • Get a single source of truth for all activities impacting our Environments (instead of spreadsheets, calendars, emails)
  • Define different views of that information, perfectly fitting the needs of each of our stakeholders
  • Connect the plan and the reality: show the Deployments on the Timeline, with an automatic synchronization with Bamboo

We decreased the number of questions to the Release Management Team by at least 50%

The feedback I got from our management and stakeholders was very positive:

  • "Release Management is less a concern than it used to be"
  • "People are able to better understand the complexity we are dealing with"
  • "Planning and reality are available to anyone, there is much less blame game"
  • "We decreased the number of questions/emails to the Release Team by at least 50%"

And we will not stop there!

Our next step is to configure Golive for managing our Environment Booking Requests and aggregating the scope of our Releases. A good topic for a future case study!

Thanks for reading and contact me for any question!

Philipp Junghans


Apwide Golive Logo

Transform your Test Environment Management with Apwide Golive:

  • Never hunt for environment info again,
    it's all in Jira where your team already is!
  • Say goodbye to environment booking conflicts,
    and hello to seamless test campaigns and demos
  • Keep your inbox organized,
    by choosing the environment notifications you need via email, MS Teams or Slack
  • Streamline your environment planning,
    with easy drag-and-drop on an intuitive timeline

Leading companies have already Golive as part of their DevOps toolchain:

Southwest Airlines Company
Mercedes-Benz Company
Manulife Financial Corporation Is A Canadian Multinational Insurance Company And Financial Services Provider.
Sky Television Company
Macy's Operates With 508 Stores In The United States.

Free trial / Free forever up to 10 Jira Cloud users!

About the author

Philipp Junghans

Philipp Junghans is an experienced IT specialist in finance and release management, currently leading Tax IT at Swiss Re, with notable tenures at Credit Suisse and Deutsche Bank.

More Insightful Articles

How the largest food company provisions Jenkins instances in less than 10 minutes

To get a new Jenkins instance used to be manual and the lead time was over a month. It now takes 10 minutes for a team to request and start using a new Jenkins!

How the largest food company provisions Jenkins instances in less than 10 minutes