The concept of Technical Debt is always different when you ask a developer or a sponsor. Why is it that complicated to understand for the sponsors? why do developers struggle to explain it? I’m sharing my failed and successful attempts with Technical Debt in three different countries.
The concept of Technical Debt is always different when you ask a developer or a sponsor. Why is it that complicated to understand for the sponsors? why do developers struggle to explain it? I’m sharing my failed and successful attempts dealing with technical debt in three different countries and different contexts. Each time I was on a different role and my perspective was different, but in every case, I needed to deal with technical debt. Agenda of the talk: – what’s technical debt? Quick review of the definition of technical debt and how we can generate more without knowing it.
– Prelude What does the developer mean with technical debt? What does the sponsor understand with technical debt? How can we understand each other talking about technical debt?
– Chapters 1 to 7 Sharing working situations of generation of technical debt and ways to deal (or not) with it. There would be a mixed of failed and successful shared experiences.
– Epilogue Some tips to work better as a team dealing with technical debt
No special requirements for this talk other than the usual for any talk. I have more than 15 years experience working on IT, from Software development to project management and ending up as an Agile Delivery Consultant. I’m passionate about improving teams in order to achieve the best possible results for the company, and I believe than sharing failure and success stories trying things can definitely help others to improve. Not to copy my success stories, but to try every idea they have to improve.
I’ve performed this talk at Voxxed Days Thessaloniki, Greece. Nov 2017, JAX DevOps London, UK. 9-12 Apr 2018 and DevOps D-Day 2018, Marseille, France