Preparing Practice Exam…
Please wait a moment while the system generates the exam questions, answers, and study session.
Please wait a moment while the system generates the exam questions, answers, and study session.
Question 34 of 141
Free Preview · 141 of 468 · questions 1–141 of 468 are free. Sign up free to sync your progress across devices.
Select one answer.
Written by other learners. Comments can disagree with the marked answer — check the official documentation when in doubt.
Technical debt refers to shortcuts in code, design, or architecture that help deliver functionality faster in the short term but may cause rework or reduced productivity later. It impacts team velocity, quality, and long-term maintainability. By logging technical debt as an impediment, the Agile practitioner can: 1. Make it visible to stakeholders and the team. 2. Facilitate discussions around its impact. 3. Help prioritize refactoring and improvement efforts. 4. Bring it to the attention of the Scrum Master or Product Owner, who can act on it.
This is so obvious: B is the answer. Even if I had to choose another option, that'd be D. Effect of tech debt on the project is either rework or being proactive and refactoring. refactoring is a better option that takes time. this time has to be accounted for in user story estimation. That is it.
The best answer for the scenario is C. Log technical debt as an impediment. Explanation: Technical debt refers to the cost of maintaining and fixing issues that arise from taking shortcuts or not following best practices during software development. It can have a significant impact on project timelines, quality, and overall success. Therefore, it is essential to communicate its effect on the project to stakeholders. Option A, posting and discussing rises in the burn down chart, may not be effective in communicating the impact of technical debt as it only shows progress towards completing tasks and does not provide specific information about technical debt. Option B, adjusting story points to account for technical debt, may lead to inaccurate estimations and does not address the root cause of the problem. Option D, adding refactoring tasks to all stories, may be too time-consuming and may not prioritize addressing technical debt in areas where it has the most significant impact.