New technologies such as artificial intelligence (AI) present a real opportunity for the Government and DVSA to work smarter, to improve services and make roads safer. Head of Vehicle Engineering, Neil Barlow explains how we've used AI to better target fraudulent MOT testers.
How we're designing, building and buying technology that meets user needs, allows us to share across government, and is easy for us to maintain and scale in the future.
To celebrate International Women's Day 2019, Michala Reith shares her experience of what it's like working in tech as a female.
On Friday 18 May 2018, we hosted and took part in our first Amazon Web Services (AWS) GameDay at our office in Nottingham - an event that we'd been eagerly anticipating.
James Munson explains some of the work we've done to make sure we've got solid foundations in place to build on to deliver the DVSA digital, data and technology strategy.
Cloud computing is really important to DVSA - a government agency providing services to millions of users, with staff spread right across Great Britain, and determined to get value for money in everything we do.
Neil Barlow, MOT Service Manager, explains how we've been making MOT data more open - from making it easier to check a vehicle's history online, to creating an API for businesses.
Ken Roberts, a Digital Delivery Lead in DVSA’s software delivery team, shares his first impressions of the team after joining in September 2017, and explains the challenge of building software delivery capability.
Our digital MOT testing service was launched in 2015, providing a critical service to over 23,000 MOT garages across the country. It's remained as a beta service since then, and we've been working hard on improvements to make it ready to be a live service.
The approach we're taking at DVSA to modernising our services and technology so that we can achieve our vision of safer driver, safer vehicles, and safer journeys for all.
We recently reached a big milestone with our official DVSA apps, with one million downloads. Here’s how we did it, and why our users needed native apps.