CDA Technical Debt & Refactoring Strategies 3

Question 1

In DA, which governance mechanism helps teams balance new feature work against technical debt repayment each iteration?

Accepted Answer

Capacity allocation (e.g., 20% of capacity to debt)

Answer

Reserving a fixed percentage of team capacity each iteration for debt items ensures ongoing debt reduction alongside feature delivery.

Question 2

A DA practitioner encounters 'reckless technical debt.' What distinguishes this from deliberate debt?

Accepted Answer

It is incurred without awareness or a remediation plan

Answer

Reckless debt is taken on without understanding the consequences or planning to address it, making it the most harmful type.

Question 3

Which refactoring technique is most appropriate when a DA team finds that a single class has grown to handle too many responsibilities?

Accepted Answer

Extract Class

Answer

Extract Class splits an overloaded class into two focused classes, each with a single responsibility.

Question 4

According to DA, what role does the architecture owner play in managing technical debt?

Accepted Answer

They guide technical direction and ensure architectural debt is visible and addressed

Answer

The architecture owner in DA is responsible for ensuring the technical vision is sound and that architectural debt is tracked and reduced.

Question 5

A DA team wants to visualize their technical debt alongside feature work. Which tool best supports this?

Accepted Answer

A shared backlog with debt items tagged and visible to stakeholders

Answer

Making debt items visible in the main backlog enables stakeholders to make informed trade-off decisions about priority.

(CDA) Certified Disciplined Agilist Practice Test