Speaker 2
Do you use the metaphor of technical debt very often in your profession?
Speaker 1
Yeah, we actually have a markdown file that we version in Git, usually called www.tap.md where the development team manage the technical debt. Some issues may make it into the Kanban or the board, where the product manager and the other people, the stakeholders are watching or are participating. We also like to have our own management or care about the technical debt because there are certain things you don't want to negotiate or you don't need to have a meeting for. Say you need two hours to clean up some broken test or you need some more time to finish off one refactoring you were doing. And for that, we don't want to forget. We want to be accountable and make sure that the job is done. But we don't necessarily want to bring those small tasks into the main board.
Speaker 2
Is that because it's difficult to get that prioritized or it just increases the cost of addressing it or a little bit of
Speaker 1
everything? It is to reduce the burden of monitoring the project. I'd say the same way you don't ask for condition or recursive or for loop. You don't bring that into the Kanban board. There are also tests in refactoring tasks that will last for some minutes or a few hours. You don't want the people working around you to be more concerned. But something you are going to do in just today or tomorrow or this week.