When people discuss quality in software development, they typically refer to quality assurance testing. While testing is a significant factor in software quality, it isn’t the only thing to consider. For project or quality managers, there are a few other areas to consider for your organization. Three significant considerations are code reviews, continuous feedback loops, and knowledge sharing.

In software development, technical debt can come in many forms. For instance, a new product was created using a prototype that was never architected after the proof of concept was created. Another example is bugs that had workarounds, but a fix has not been implemented yet. Another issue is that a series of software upgrades need to be implemented, but the team is understaffed. These are only a few examples of technical debt, but all of them create a problem that can haunt a project in the form of risk. How does a project manager dig their way out of technical debt?