In this 3rd episode of the PremiumBytes video podcast, hosts Sudhar and Samir discuss how agile and architecture approaches can coexist within insurance organizations despite inherent tensions between them. They start with grounding the terms "architecture" and "agile", noting that adaptability in a changing context is a common foundational motivation for both.

They identify several of the sources of inherent tensions that predictably crop up, such taking the time to deliberately define the architecture being viewed as getting in the way of expeditiously writing code. The hosts provide a reframing that it behooves engineers to be intentional about what characteristics the system they develop exhibits, because they will get some set of characteristics, and odds for all characteristics being desirable are unfavorable.

They also discuss how iterative development is sometimes viewed through the frame of not having done things right the first time. They compare writing software to writing in a natural language such as English, pointing out that natural language writing is very much iterative in that people take the time to prepare an initial draft and successively revise it until they have a high quality version. Having a perfectly written final version the first time is never an expectation in writing in a natural language, so should it not be an expectation when writing in a programming language.

The discussion ends with the hosts offering insurance technology leaders 3 practical tips for resolving some of the tensions: hold delivery teams accountable for making sound architecture, planning for iterative development, and preferring architecture guidelines over hard and fast standards.

For other insightful conversations that shine a light on the unsung world of insurance technology leaders, watch and listen to other episodes.