软件项目通常需要花费时间处理的另一个任务是偿还技术债务。
Another task that software projects often need time to address is repayment of technical debt.
这一期将讨论如何评估紧急设计，以及如何制定一个令人信服的偿还技术债务方案。
This installment discusses how to estimate for emergent design, and how to make a convincing case for repaying technical debt.
您或许想要仅在那个范围内推迟新的开发，同时在该部分内偿还技术债务(进行代码重构，更新文档等等)。
You might want to put off new development in only that area while you repay any technical debt in that section (refactoring code, updating documentation, and so on).
在决定偿还债务之前，决策者对业务和技术风险都需要有深刻的理解。
The decision to pay down technical debt requires a solid understanding of both the business and technical impacts.
它也是后来最有可能导致大问题的，一旦您意识到您正处于技术债务中，就马上偿还。
And it's the one least likely to cause big problems later, as long as you realize you've incurred debt and can pay it back.
你要清楚地告诉他们，管理人员会重视这些问题，并且已经开始着手偿还这些技术债务了。
Make it clear that the Management appreciates the problem and is prepared to start paying down the debt.
开发人员应该优先考虑这些技术债务，并花费10- 15%的精力来偿还这些技术债务。
The developers should prioritise the debt and spend 10-15% of every sprint paying it down.
开发人员应该优先考虑这些技术债务，并花费10- 15%的精力来偿还这些技术债务。
The developers should prioritise the debt and spend 10-15% of every sprint paying it down.
应用推荐