Does your team have tech debt?
If you say we don’t have, it looks strange to me 😅
If you say we have a lot, it’s good news that your team is moving forward quickly and your product is growing. On the other hand, your team will have more work next time and needs to reduce it as much as possible if it doesn’t want to face a nightmare in the future.
I won’t mention the definition of tech debt in this post(you can search for it, or I’ll write it in another post). I like the “Boy Scout Rule,” so I continuously monitor tech debts and set a quota of around 10–20% of the team’s capacity to solve tech debts.
I encourage team members to proactively discover tech debts, note them, think about solutions, and write them down in a document to share with the team.
To help team members quickly write tech debt documents and determine which significant items should be cared for, and the whole team can follow and discuss, I created a template based on RFC(request for comment process).
There are two versions, full and short templates, and you can choose one that fits your style.
Full version: https://lnkd.in/g7Uvsmdx
Short version: https://lnkd.in/gaqkbuP8
You can read my article about RFC here: https://lnkd.in/gfS3c6VV
Hope you like it, cheer!
