The challenge
Electric vehicles, autonomous driving, connected cars, new legislation and changing attitudes to fossil fuels have made the automotive world far less predictable. JLR knew it needed to move faster, not just with vehicles but with the systems, factories and digital products around them.
Many agile transformations start with a framework and end with a slide deck. Teams are trained and posters go up, but six months later work is delivered exactly as before. JLR wanted to avoid that, which meant starting with a real product rather than a workshop.
What we did
- 1
Start with a real problem
Dealers could reserve vehicles, but reserved stock that did not sell sat on the forecourt losing value.
- 2
Ship something useful
In 16 weeks we built an iOS app that let dealerships across the country search for and reserve stock from each other.
- 3
Build the framework alongside it
While delivering the app, we shaped JLR's agile delivery framework, including governance, internal standards, how remote teams are managed and how releases go live.
- 4
Define the roles
We set up the product owner role and a digital backlog so priorities were clear and visible.
- 5
Hand over ownership
We established agile guilds inside JLR to own the framework, refine it and drive adoption across the organisation.
The outcome
- Dealers had a live iOS app in 16 weeks, letting them find and reserve stock from one another so reserved vehicles sold before they lost value.
- JLR gained a working agile framework, proven on a live product.
- Internal guilds took ownership, so the framework kept improving after we left.
Why it worked
Learning by delivering
Teams learned agile by shipping a real product, not by sitting through training.
Built for JLR's reality
The framework covered JLR's governance, remote teams and release process, rather than a generic textbook model.
Owners on the inside
Guilds gave the practice a home, so it did not depend on consultants staying.
