Communicating Technical Debt
Most developers have worked in environments where they are unable to pay down technical debt, not due to the technical difficulty of the task, but because of organizational priorities, fears, urgent deadlines, and a lack of clear understanding of the full impact of technical debt on their software.
In this chapter, we’ll explore some of these factors that can prevent you and your team from resolving technical debt and introduce some ways of helping the organization understand and value the refactoring process.
We’re going to cover the following main topics:
- Overcoming barriers to refactoring
- Communicating technical debt
- Prioritizing technical debt
- Getting organizational buy-in