Legacy insurance systems have accumulated decades of complexity in their codebases and business logic. This complexity is spread across batch jobs and shaped by regulation, rather than architecture. Directly applying modern Agile modeling to such a landscape often throws developers off track and into frustration.
That is where Agile can work, but only when recentered around the realities of the domain. A domain-first perspective is captured by the fact that success in these environments cannot be achieved by providing screens and endpoints but by replicating the essence of how the business operates.