Welcome back to our blog series, “Tackling Technical Debt.” In Part 1, we discussed the different categories of technical debt you may encounter in various projects. We then covered a couple of scenarios that show taking on technical debt can be a strategic decision that helps the business in Part 2. In this third post, we will help you create a plan for tackling existing technical debt.
Over time, software development projects can accrue technical debt through intentional and unintentional choices. When teams intentionally choose technical debt, they make a plan to address it later when they have more time, more resources, or more funding. Unfortunately, these tasks are not always well tracked or get delayed for more urgent requests. The growing list of technical debt tasks becomes more daunting to resolve. How do development teams and business leader prioritize which technical debt to fix first? The answer lies in a modification of the time management matrix first popularized by President Eisenhower.
What is the Eisenhower Matrix?
It’s a system for prioritizing tasks into four quadrants based on their urgency and importance: