Right now, my team analyzes the bugs we've fixed within the last month and discuss about them, like what to do to prevent them in the future. We also discuss certain metrics on our products' debts, like test coverage, code complexity, risks, etc.
I'm gathering ideas on how everyone else is doing tech debt analysis and wondering if we could steal some ideas for my own team so that we could make these sessions more effective.
Here are a couple of questions I'd like to inquire:
- What's the general process for identifying/analysing tech debts in your team?
- What tools do you use to facilitate the discussion?