Banking & Finance
Connecting DevOps and change management to govern software quality
A DevOps reorganization programme on the .NET stack: a Helix–Azure DevOps integration already in production, dozens of projects on SonarQube and an ecosystem of reusable internal libraries.
The Client
Software governance in financial services and insurance
An organization in financial services and insurance engaged Reengineering to reorganize DevOps across its .NET software projects. The work covers development and release processes, analysis of a codebase spanning millions of lines, and the connection between development tools and change management. The case is presented anonymously to protect the client's confidentiality.
The Challenge
Connecting change requests, team activities and code
The client's request combines several needs: reorganizing projects in Azure DevOps, integrating code analysis with SonarQube and connecting Helix changes to the corresponding user stories. Alongside these is the need to organize internal libraries as shared, reusable components.
- Connect Normal Changes and Emergency Changes in Helix to user stories in Azure DevOps
- Introduce static analysis with SonarQube across a codebase spanning millions of lines
- Evolve CI/CD processes for .NET software projects
- Organize internal libraries into an ecosystem of artifacts and reusable NuGet packages
The Solution
A cloud bridge between Helix and Azure DevOps, with code quality and reuse built into the process
We built a cloud integration using Azure Functions and the REST APIs of Helix and Azure DevOps. Helix is the IT Service Management platform used to manage change requests: the integration connects Normal Changes and Emergency Changes to the corresponding Azure DevOps user stories. In parallel, we are working on integrating SonarQube into development processes, evolving CI/CD and creating an artifact ecosystem to distribute and reuse internal libraries as NuGet packages.
- Integration infrastructure on Azure Functions, developed on the .NET stack
- Use of both platforms' REST APIs to connect changes and user stories
- Support for the connection of both Normal Changes and Emergency Changes
- SonarQube integration for static analysis of project source code
- Reorganization of CI/CD processes in Azure DevOps
- Organization of artifacts and shared libraries through internal NuGet packages
The Results
A production integration and dozens of projects already on SonarQube
The integration between Helix and Azure DevOps is already in production. Dozens of projects have already been onboarded to SonarQube. Work continues on evolving CI/CD processes and further SonarQube adoption as part of the DevOps reorganization programme.
- In production: integration between Helix changes and Azure DevOps user stories
- Already achieved: dozens of projects onboarded to SonarQube
- Ongoing: evolution of CI/CD processes and further SonarQube adoption
Benefits for the Client
Change traceability and shared foundations for .NET development
An operational connection between Helix change requests and Azure DevOps development activities
SonarQube code analysis already extended to dozens of projects
Evolution of CI/CD processes to structure integration and release activities
An internal NuGet package ecosystem to support library reuse across .NET projects
