This talk has been presented at TechLead Conference 2023, check out the latest edition of this Tech Conference.
Video: Measuring Technical Debt Effectively
FAQ
The two types of tech debt are maintenance tech debt and continuous tech debt.
Continuous tech debt is immediately problematic as soon as it is deployed to production, leading to issues like bugs, downtime, and security breaches.
Heuristic metrics include cyclomatic code complexity, code duplication, code smells, maintainability index, tech debt ratio, and heuristically detectable security issues.
Second-tier tech debt metrics are metrics influenced by tech debt, such as effort split between ad hoc support and features, cycle time for feature tickets, bug trends, and software uptime.
Tech debt interest is the additional effort spent on tasks due to tech debt, calculated by comparing the effort required with and without tech debt.
The primary topic is measuring tech debt and interpreting the results.
Tech debt is a tool to temporarily speed up development by cutting corners, at the expense of slowing down later.
Teams can collect tech debt interest by logging time spent on tickets, estimating effort without tech debt, and regularly updating this information in their issue tracker.
Second-tier metrics are important because they show the impact of tech debt elimination efforts and are essential for tracking overall team and software health.
The speaker is Anton, a director of engineering at Westing in Germany and a mentor and coach for engineering leaders.
Check out more articles and videos
We constantly think of articles and videos that might spark Git people interest / skill us up or help building a stellar career
Workshops on related topic
It’s a tale as old as time - collaboration between developers and business stakeholders has long been a challenge, with a lack of clear communication often leaving both sides frustrated. The best developers can deeply understand their business counterparts’ needs, effectively communicate technical strategy without losing the non-technical crowd, and convince the business to make the right decisions. Working at a consultancy, I’ve both failed and succeeded in architecting and “selling” technical visions, learning many lessons along the way.Whether you work at a product company, are a consultant/freelancer, or want to venture beyond just being a developer, the ability to convince and clearly communicate with stakeholders can set you apart in the tech industry. This becomes even more important with the rise of GenAI and the increasingly competitive developer market, as problem-solving and effective communication are key to positioning yourself.In this workshop, I’ll share real-world examples, both good and bad, and guide you through putting the theory into practice through dojos.
Comments