When working on legacy system code with rushed decisions leading to sloppy documentation, this condition is identified during sprint planning as

When working on legacy system code with rushed decisions leading to sloppy documentation, this condition is identified during sprint planning as

• A. Backlog refinement
• B. Technical debt
• C. Definition of ready
• D. Premature optimization

Answer: (B)

Technical debt refers to the extra future work that accumulates when expedient, less-than-ideal decisions are made in coding, especially in legacy systems, and when documentation is rushed or sloppy. The code becomes harder to understand, modify, and extend, so future work—refactoring, adding tests, and improving documentation—is needed to bring the system back to a healthy state. In sprint planning, this debt is surfaced as work items aimed at paying it down, so the team can reduce maintenance effort and avoid slowdowns later. Backlog refinement and definition of ready are about preparing work items to be taken on and ensuring they meet criteria before starting, not the condition causing extra work. Premature optimization refers to optimizing for performance too early, which isn’t the issue here.

Technical debt refers to the extra future work that accumulates when expedient, less-than-ideal decisions are made in coding, especially in legacy systems, and when documentation is rushed or sloppy. The code becomes harder to understand, modify, and extend, so future work—refactoring, adding tests, and improving documentation—is needed to bring the system back to a healthy state. In sprint planning, this debt is surfaced as work items aimed at paying it down, so the team can reduce maintenance effort and avoid slowdowns later.

Backlog refinement and definition of ready are about preparing work items to be taken on and ensuring they meet criteria before starting, not the condition causing extra work. Premature optimization refers to optimizing for performance too early, which isn’t the issue here.