Click the diagram to open the interactive DA Browser, where you can learn more about the decision points and options of this goal.
Why This is Important
This goal is important because it enables us to:
- Pay down technical debt. Technical debt refers to the implied cost of future refactoring or rework to improve the quality of an asset to make it easy to maintain and extend. We want to pay down technical debt, in other words fix the quality problems within our assets, to enable us to evolve them safely and quickly. High-quality assets are easier and cheaper to work with than low-quality assets.
- Avoid new technical debt. At a minimum we shouldn’t make our organization’s technical debt problem any worse than it already is. By being quality focused, by quickly addressing any quality problems that we do inject into our work (often via refactoring), we can avoid adding new technical debt.
- Work in a more enterprise-aware manner. Quality problems affect everyone—they affect our team’s ability to evolve our solution to meet the changing needs of our stakeholders, they affect the user experience of our solution, and they reduce the value of our solution to our organization.
Important Questions to Consider
- How will we address technical debt within our system(s)?
- How will we produce high-quality documentation?
- How will we take advantage of existing infrastructure and other assets?
- Technical debt is slowly choking the life out of your organization, reducing your ability to respond to opportunities in the marketplace and increasing your cost of operations.
- The easiest technical debt to pay down is the debt that you don’t incur in the first place.
- Consider paying down technical debt gradually over time, making it part of what you normally do as a matter of course.