New features on top. A rewrite running underneath.
Their member app launched three months after we took over the code, and it has stayed live through every release since.
A launch date, and an app that had to be ready
Tiger Wheel & Tyre's member app is how customers join their membership, manage their vehicles and claim their benefits. When their previous partner let them down, they called us in with a launch already committed and members using the app every day.
Too live to stop, and too important to get wrong.
There was a launch commitment to keep, and members were using the app every day.
The textbook answer was a rebuild.
The impact we made
The app was too live to stop, so we didn't stop it.
A rebuild would have meant close to a year with nothing to show, so we ran two tracks in the same sprint.
New features went on top, against the business's own priorities. Underneath, every service a feature touched was rewritten to our standards as it went. The rewrite was paid for out of the same capacity as the features, so the roadmap never waited for the clean-up, and the clean-up never waited for a quiet month.
Every feature left the code safer to change.
Here is how the work ran, and why.
A small change is now an ordinary ticket.
More than 1,300 tickets later, a request from the business goes into the backlog and goes live. Here is what members can do now.
And the whole app has a new look, delivered on the same running product.
They came back with two more products.
Alongside the member app, the business asked us for two more products: an app for their branch teams, and a platform for their corporate customers.
The corporate platform was built clean from our own templates. On our own internal code-quality rating it scores 95%.
New features on top, the rewrite underneath, and you stay live the whole time.
Yours is live too. You don't have to switch it off to fix it.
Tell us about a project like this.