In what two ways is velocity and technical debt related? (Choose two.)
In what two ways is velocity and technical debt related? (Choose two.)
Technical debt and velocity are interrelated in two significant ways. Firstly, as the Development Team works on new tasks, they might encounter technical debt unexpectedly, which can cause a drop in their velocity due to the need to address these issues. Secondly, a team might artificially increase their velocity by incurring technical debt, taking shortcuts to speed up delivery, which increases the visible rate of progress at the cost of future work to correct or improve underlying issues.
why C is correct?
This is my experience. The team can do a fake high velocity by trying to do the hard code and not covered the non-functional requirement or full of abnormal/exceptional cases of the feature. PO and SM did not know about that until some additional requirements are added and make the dropping velocity in some sprint later. (Maybe there are too late to fix it at that time)
Yes, they can hard-code and temporary increase the performance Answer is B and C
Can you pls explain more? i still think D is more appropriate than C
B and C.
I have doubt that C is correct or not.
D is more appropriate.
B & D are correct