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 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.
Suggested Answer:BC🗳️
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. And how it is managed will depend on the team AND context of the situation.
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)
upvoted 1 times
...
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
Mbouzidi
4 months agolenanguyen89
1 year, 5 months agoRajnishSasmal
2 years, 7 months agoRajnishSasmal
2 years, 7 months agonhungnt184
3 years, 7 months agoamog
3 years, 8 months agolenanguyen89
1 year, 5 months agopock
3 years, 11 months agoTripleN
3 years, 10 months ago