CODEX
Technical Debt Management Best Practices in Software Engineering
Technical debt rate = lines of code that should be reworked / lines of existing source code * 100%
Technical debt exists on each project if it’s more than 1–3 months old. Having technical debt doesn’t necessarily mean that software engineers are not performing well. Technical debt can appear because of business pressure, lack of requirements, lack of interaction between team members etc. However, good software engineers know how to manage the technical debt and do that. Bad software engineers simply hide the tech debt from managers and customers, hoping that the project will be completed before it gets out of hand.
Managing technical debt is not difficult process at all, but it requires from at least lead software engineer to be disciplined and follow best practices described down below.
Technical debt register exists for the project
I believe that every software project has a backlog — a list of user stories that will be implemented in the upcoming sprints. The backlog size can range from a few stories to dozens of stories, depending on whether your product owner and business analysts work well or not. In addition to the user…
