In what two ways is velocity and technical debt related? (Choose two)

A. They are not related because technical debt is non-functional and velocity is calculated based on end user functionality.
B. As the Development Team is working on new Product Backlog items, they may unexpectedly run into technical debt that will result in the team’s velocity dropping.
C. A Development Team can artificially increase velocity by allowing technical debt to be incurred.
D. Adding estimates to technical debt will allow the Development Team to maintain constant velocity therefore ensuring predictability.

Answer: B,C

Technical debt is a natural occurrence when developing complex products. It is a concept in software development that reflects the implied cost of additional rework caused by choosing an easy solution now instead of using a better approach that would take longer. In the short term this results in a short fix, long term this usually results in an unstable product and extra work that has to be done to rectify the problem