Robust code, real ROI: software quality in the public sector's AI era

Public sector IT leaders face AI-assisted development with a specific handicap: their organizations are highly regulated, decision-making moves slower by design, and the systems in question often can’t afford to break. That makes questions about robust code and software quality harder to answer, not easier.

This webinar looks at what it actually takes to keep software quality under control when AI is writing a growing share of the code: what “robust code” means in practice, how much of the budget should go to new features versus maintaining quality, and which tools actually help make that trade-off visible. It also looks at what this shift means for the product owner, whose job increasingly comes down to defending value over features — a distinction that matters even more in a public sector context built around efficiency, not revenue.

Jakob Konstantin Flink, Chief Consultant at Økonomistyrelsen (Denmark’s Agency for Public Finance and Management), discusses what this looks like from inside a public institution: how to avoid decisions getting made by people who don’t fully understand what’s being discussed, and how to make the ROI of quality software legible across that technical/financial divide.

Join us and learn:

• What “robust code” needs to mean once AI is writing a growing share of it
• How to think about the split between spend on new features and spend on quality
• Which tools actually give you visibility into that trade-off
• How the product owner’s role shifts when AI increases output — and why value over features matters more, not less
• How to bridge the gap between technical teams and non-technical, finance-driven decision-makers
• How to make the ROI of software quality legible in a public sector budget conversation