Release Management Specialist

Release Governance & Change | Power BI Reporting & Automation | Banking

I'm Kev, based in Glasgow, and I've been in IT for over 30 years, which I'm told is a long time. For the last 11 or so I've worked in banking, getting software changes safely into production and then working out how they went. I'm happiest when the data is clean, the reports are ones people trust, and the boring weekly jobs run themselves.

Portrait of Kev Thomas
The route every release takes
  1. INTIntegrationTeams build and join up their changes
  2. SITSystem testDoes it work with everything around it?
  3. NFTNon-functionalSpeed, load and resilience
  4. CABChange boardI present medium and high risk changes
  5. LIVEProductionReadiness confirmed, then deploy and verify

I'm in the room at each stage: chasing evidence, judging risk, and making sure the people who need to say yes have what they need to say it.

A few numbers

Honest about whose they are
187releases I personally coordinated, January 2025 to October 2026mine
~100recurring activities a year now done automatically by two weekly Power Automate flowsmine
1,468production changes across the estate in 2025, up more than 40% on 2024estate I report on
93.87%release success in 2025, up from 92.83% the year beforeestate I report on

"Mine" means I did the work. "Estate I report on" means the whole platform's figures, which the self-service Power BI reporting I helped build and maintain makes visible. I didn't do all of that work myself, and I won't pretend I did.

What I do

Three things, in order of how much time they take

Release and service management

Planning, coordination and production readiness. I take medium and high risk changes to the Change Assurance Board, run live implementations with operations, and check Jira, ServiceNow and testing evidence before anything goes out, so audits find a clean trail.

Reporting people actually use

Self-service Power BI reporting pulling from Jira, ServiceNow and SharePoint, so managers stop emailing for numbers. I spend as much time on data quality as on dashboards: if the count is wrong, nobody trusts the chart.

Automation and a sensible use of AI

Power Automate flows that take repetitive weekly jobs off people's plates, and a Copilot and SharePoint agent proof of concept that answers release-process questions from approved content only. It can't approve, rate risk or make governance calls.

Three stories

What happened, what I did, what changed

The deployment I stopped

Situation
A production deployment to a customer-facing banking application was under way. The backout plan had several options depending on how it failed, and no developer was online to choose between them.
What I did
I halted it, kept the part that had no customer impact, and explained the risk to senior management the next day. The recovery procedure was tested before we rescheduled.
What changed
Developer support during production deployment is now an explicit requirement in my release-readiness communication.

Making two systems talk

Situation
Jira holds releases and ServiceNow holds changes, and nothing connects them. Totals disagreed, archived items inflated counts, and a priority label change quietly hid incidents.
What I did
I set a consistent way to record Jira release references in ServiceNow changes, helped standardise Fix Version statuses, and reconciled report totals back to the source.
What changed
Releases, changes and their outcomes can now be matched and analysed together in Power BI, with far fewer manual information requests.

One page instead of five

Situation
Release information was scattered across tools and teams, and nobody had a single view of delivery, governance, incidents and outcomes.
What I did
I created a fortnightly Release Platform Engineering update that combines Jira, ServiceNow and release data, built on a SharePoint approach that replaced the fragmented summaries.
What changed
It has run since November 2025 and reached its seventeenth edition by August 2026. The approach was nominated for a 2026 Simplification Champion award.

Career, as a changelog

Newest first
  1. currentAug 2018 – present

    Service & Release Specialist · Nationwide Building Society (formerly Virgin Money)

    Release Platform Engineering. Release coordination from planning through SIT and NFT to production, governance and audit-readiness checks, Power BI reporting, Power Automate processes, and mentoring new starters through the team's deployment tooling. Joined the Release Management team in 2018 as a Senior Technology Analyst.

  2. v2017Apr 2017 – Aug 2018

    Senior Technology Analyst · Clydesdale Bank / Virgin Money

    Introduced one estimation and scheduling process across five departments, helping a largely waterfall organisation move towards Scrum. Presented it to senior and Board-level management, coached teams as an Agile ambassador and designed Jira workflows that automated assignment.

  3. v2015Sep 2015 – Apr 2017

    Solution Design Team Lead · Clydesdale Bank

    Led 17 permanent and contract solution designers across several projects at once: resourcing with project managers, appraisals, development plans and recruitment. Pushed projects to involve solution design early.

  4. v2011Jan 2011 – Sep 2015

    Application Support Team Lead · IBM, ScottishPower account

    Led nine engineers, five onshore and four offshore, supporting around 48 applications for a major UK energy network against a 95% availability target. Owned SLA reporting, problem management and customer liaison, with 24x7 standby rotas.

  5. v1.xEarlier

    Development, support and consultancy

    Oracle SQL and PL/SQL development, Unix scripting and root-cause analysis, supporting the ScottishPower contract for about 15 years in total across several suppliers, including IBM.

Skills

What I use, and what I used to

Release and service

  • Release coordination
  • Change Assurance Board
  • Production readiness
  • Audit evidence
  • Risk and dependencies
  • Release closure

Tools

  • Jira
  • ServiceNow
  • Confluence
  • SharePoint
  • GoCD
  • Jenkins
  • OpenShift

Data and automation

  • Power BI
  • Power Query
  • DAX
  • Power Automate
  • Microsoft Copilot
  • Excel and VBA
  • Oracle SQL and PL/SQL
  • Unix scripting

People and ways of working

  • Stakeholder management
  • Agile and Scrum coaching
  • Mentoring and training
  • Team leadership, up to 17 reports
  • Recruitment and resourcing

Dashed chips are skills from earlier in my career. I still understand them, but they're not what I do day to day.

Beyond work

Things I build and shoot for fun

Photography

I run Bearsden Photoworks, with a custom WordPress plugin I built to pull my Instagram feed onto the site.

A flight tracker in the loft

A Raspberry Pi with an ADS-B receiver, logging aircraft overhead in Glasgow, with more camera nodes planned.

Radio, from a distance

I volunteer technical help to KWBG Radio in Boone, Iowa, looking after WordPress and the tooling behind their digital workflows.

Say hello

Glasgow, Scotland

This page sits alongside my CV rather than replacing it. If you'd like the CV, or want to talk about release management, reporting or automation, LinkedIn is the best place to find me.