Of course, a simple solution is just to have a text file called TODO or similar. It's low maintenance, and particularly appropriate if it's a WORN file (write once, read never).
I would suggest you add an item in your product backlog whenever you deliberately incur technical debt. This way, it is possible to consciously spend time during each iteration.
发布评论
评论（4）
您可以使用任何错误/任务跟踪软件，例如查看此堆栈溢出问题：https ://stackoverflow.com/questions/101774/what-is-your-bug-task-tracking-tool。
当然，一个简单的解决方案就是拥有一个名为 TODO 或类似名称的文本文件。它的维护成本低，如果它是一个磨损文件（只写一次，从不读取），则特别合适。
You could use any bug/task tracking software, eg see this stack overflow question: https://stackoverflow.com/questions/101774/what-is-your-bug-task-tracking-tool.
Of course, a simple solution is just to have a text file called TODO or similar. It's low maintenance, and particularly appropriate if it's a WORN file (write once, read never).
我想说的是代码中的 TODO 注释，但我的经验是开发人员通常会忽略这些。
I'd say TODO comments in the code, but my experience has been that developers generally ignore these.
我建议您在故意产生技术债务时在产品积压中添加一个项目。这样，就可以有意识地在每次迭代期间花费时间。
I would suggest you add an item in your product backlog whenever you deliberately incur technical debt. This way, it is possible to consciously spend time during each iteration.
您可以使用Sonar 插件查找代码库中的潜在问题。
/罗杰
There is a plug-in for Sonar that you can use to find potential problems in your code base.
/Roger