2 min read

Visualizing technical debt using quality views

Visualizing technical debt using quality views

Previously, I wrote about how to build a business case for reducing technical debt including the importance of making the impact of technical debt visible to the business.

In this article, I describe another way to make technical debt visible: quality views. They are a useful tool that enables developers to show the business how technical debt will impact the implementation of a work item, such as a feature. Let’s look at quality views in more detail.

This post is for paying subscribers only