Software dev tools and strategy for UK SME engineering company

I'm a mechanical engineer who has migrated into methods development for a UK engineering firm. I've now been asked to take over tool ownership for the companies internally developed design tools. These are used to do prelim and detail design on the companies products. My responsibilities cover everything from the underlying physics and correlations to bug tracking, feature development, version control, and software Dev internal processes.

We serve an employee user group of 20+, a small number of whom (<5) also contribute to code development under my supervision.

Our current tools are excel, SVN, anaconda, vscode and notepad++. The software is run on desktop engineering pcs or a hpc cluster accessed via thin client. All our tracking and planning happens through excel.

I'm interested in modernising and introducing more agile methods with a view to improving on time delivery, oversight of who is doing what, code review and sign off before merging if new features,and peer assisted code debugging and support.

I would like some input in what is normal for a company of this size and whether DevOps tools such as gitlab/GitHub/Jira etc would be appropriate and cost effective.

Fwiw the company is <5 years old and still largely financed privately but developing commercial opportunities rapidly. We will operate in regulated environments such as aerospace.