Which of the following statements are true about Technical Debt? Select two answers.

Which of the following statements are true about Technical Debt? Select two answers.
A . Only the Developers need to be concerned with Technical debt.
B. A team that continuously incurs technical debt will increase the velocity in the short term. Changes and development will seem easy and fast.
C. The amount of technical debt is described as quality standards in the Definition of Done.
D. Technical debt can be handled after delivery with refactoring sprints.
E. Technical debt is a threat to the long-term viability and maintainability of a product.

View Answer

Answer: B,E

Explanation:

The Scrum Guide does not mention technical debt. Technical debt refers to any flaws in the code and occurs a. If not addressed, it will get worse and harm the ability of the team to deliver. It implies the cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer. The pressure to meet deadlines, implement business requirements, and complete sprint tasks can all lead to a large amount of technical debt that leads to low code quality, which ultimately leads to lower productivity for existing and new Developers. Common causes of technical debt include not only team pressures, but lack of a test suite, delayed refactoring, business pressures, last-minute specification changes, and poor leadership. A team can artificially inflate a high velocity by taking shortcuts, implementing fast with code hacks, and keeping technical debt in the system. This can give a false assumption about the current state of the product. Initially, it can look good and like is showing value fast, but the reality and maintenance for the long term will be more difficult. Ideally, the code must be refactored continuously to avoid technical debt, but that is not always possible when building complex products. There are no special sprints just to fix the technical debt, all Sprint must provide value.