Technical debt, or the accumulation of low-quality code, seems to be inevitable when you create software. It is one of the biggest frustrations and demotivators of Development Teams. They are often acutely aware of technical debt, but feel powerless and unable to explain why technical debt should be a priority. Instead, they feel that ‘business keeps adding more features over stabilizing the foundation’.
In this episode we offer four practical tips on how to make technical debt transparent and how to help ‘business’ make a better trade-off between code quality and new features.
This episode is based on this blogpost:
http://bit.ly/2T1jqYD
Donate to support our work
https://bit.ly/supportheliberators
Follow us on Medium:
https://medium.com/the-liberators
Support the show, our research, and community offerings via Patreon:
https://patreon.com/liberators
We're building Columinity to help teams improve continuously based on scientific insights:
https://columinity.com
Check out our webshop for tons of powerful exercises and workshops to run with your team(s):
https://shop.theliberators.com
The music for episodes 91 and onward was written and produced for us by Basanite. The music for episodes 1-90 was acquired through Yummy Sounds. Post-production by Jasper Huiskamp.