1 min
Technical Debt is a recurring topic in Engineering. It is a challenge that has a lot of misconceptions and misunderstandings leading to many heated discussions.
On our blog, we previously shared an article on Technical Debt https://projectsimple.ai/from-agile-to-burden-the-impact-of-agile-on-your-growing-tech-debt/. This time, we dive deeper.
In this post, we share a great and insightful conversation our founder, Alex Polyakov shared with Brian Orlando and Hemant (Om) Patel, on an Arguing Agile Podcast.
In this Podcast, Brian, Om, and Alex cover lots of topics:
- 0:32 What is Technical Debt
- 2:51 "A Mess" Is NOT Technical Debt
- 6:25 Pitching Debt Reduction
- 10:25 Types of Technical Debt
- 11:56 Intentional Decision-Making
- 16:12 Agile Path to Value
- 18:12 Separate Tech Debt Backlogs
- 21:07 Refactoring
- 22:33 Incented on Speed
- 24:45 Who Pays for Debt
- 26:45 Causes of Debt
- 30:52 Just-in-Time Design
- 34:11 Agile Doesn't Work Here
- 36:45 Refactoring, A Deeper Dive
- 41:36 Discussing and Aligning on Value
- 43:48 Balancing Debt with User Needs
Check it out!
