How to deal with technical debt - and make your costumers happy paying for it

Technical debt is haunting the entire IT development landscape. It is known as something that is often pointed out as a problem to be solved by developers, but which is rarely allocated sufficient resources to pay off from management.

The reasons are many, but it often maps back to economy: Explaining the business value of addressing technical debt is hard if not impossible to do.

When customers are required to pay on the clock for the hours you spend correcting technical debt, this problem is exacerbated.
The consequence?

Solutions which are hard to maintain and prone to errors. Ultimately this propagates to the customer who potentially becomes dissatisfied which can result in conflicts or termination of contracts.

At Hesehus we confront this problem with the goal of creating happier customers, happier developers, and better solutions.

This talk constitutes part 2 of our presentation on how we deal with technical debt at Hesehus. In this talk, we will dive into more details regarding technical, communicative, and business aspects.

We will also share experiences and adjustments we have made since the last talk, and outline our plan for dealing with technical debt in the future.
Program
17.00: Welcome by Technology Denmark
17.05: Introduction to Hesehus by Martin Rud Ehmsen, CTO of Hesehus
17.20: Joint talk by Anders Clausen, Business Architect and Martin Rud Ehmsen at Hesehus: How to deal with technical debt – and how to make your customers happy paying for it – vol. 2
18:20: Joint discussion and questions with the audience on how to deal with technical debt
18.30: Networking and *hygge*