Which pair matches the limited software-debt analogy?

• Principal means added change effort; interest means cleanup work
• Principal means cleanup work; interest means added change effort
• Principal means extra testing; interest means the cleanup effort

Changing another hard-coded value automatically reduces the design problem that causes repeated code edits.

Both a hard-coded zone update and a table update need checking. Which effort should count as debt overhead?

• The added effort compared with the table-based process
• The code-edit time before including required checks
• The full hard-coded update time, including shared checking work

A developer dislikes a module's naming style. No added effort or plausible future risk is identified. That preference alone establishes technical debt.

Cleanup takes 168 minutes and then saves 24 minutes on each affected change. Assume constant savings and no other costs. How many whole changes are needed for saved effort to cover cleanup?

Reducing a duplicated configuration requires 60 minutes of restructuring and 35 minutes of regression checks. Both tasks are necessary. What cleanup effort should the plan include?

• 60 minutes: omit the planned regression checks
• 95 minutes: include restructuring and regression checks
• 35 minutes: omit the planned restructuring work
• 25 minutes: subtract testing time from restructuring time

A debt problem has no cleanup date yet. Which statement is justified without further evidence?

• Added effort may recur until the underlying issue is reduced
• Routine edits gradually repay the cleanup effort
• The remaining cleanup effort grows with elapsed time

A preview feature uses a hard-coded display label. The team has assessed and accepted its temporary cost and risk. Which record includes ownership and a cleanup trigger?

• Record the shortcut and assessed risk, but leave cleanup unowned and assume future editors will discover when to act
• Record only the release deadline and omit the shortcut because its temporary risk has already been accepted
• Record the shortcut and risk; assign cleanup to Jo after the preview ends, and link the ticket from the code
• Record the shortcut and risk, assign Jo to it, but explicitly omit any date or event for revisiting the decision

An old importer will retire before any planned imports. No ongoing risk is identified. Cleanup costs more effort than it can save before retirement. What is defensible?

• Consider retirement instead of cleanup and review if plans change
• Schedule cleanup before retirement to recover earlier maintenance costs
• Choose cleanup by comparing the importer's age with replacement components

Cleanup costs 100 minutes. Over the planned work it saves 16 minutes on each of 7 settings updates and 22 minutes on each of 5 imports. Ignore other costs and risks. How many net minutes are saved?