a.s.r.'s public platform carries every incoming insurance application, and it is released into by a scrum team working alongside marketing, IT and business stakeholders. That needs a release process robust enough to match the stakes. We designed one, ran it, and chaired the ceremonies around it.
People whose insurance applications depend on these releases going out cleanly
A platform that carries incoming insurance applications cannot afford a bad release. Every incident is customer facing and every rollback costs the team a day it did not plan for.
Coordinating that across a scrum team and several stakeholder groups needs an agreed process: one shared view of what is going out, when, and who needs to know. Establishing it was the work.
Releases went from regularly going wrong to routine. The team gained a repeatable path to production, and the stakeholders around it gained a reliable picture of what was shipping and when.
We rebuilt and hardened the aanvraagstraat, the main entry point for every incoming insurance application at one of the largest insurers in the Netherlands. It serves hundreds of thousands of users.
A full platform move from Sitecore and Vite to headless Contentstack and Nuxt.js, delivered while the website stayed open to visitors.
We restructured a Vue component layer that had grown past the point of clean change, put automated tests around it, and rolled the result across an entire insurance platform without interrupting live campaigns.
Tell us what you are building and where it hurts. We will tell you straight whether we are the right partner for it.
Book a 15 minute introduction