I think for me, the problem is often relating to prioritising the fixes. As engineers, how do we go about communicating to our stakeholders and product owners the value of resolving tech debt?
I found a really valuable post by Riot Games (The company behind League of Legends), titled "The taxonomy of tech debt". It details how you may measure the impact, fix cost, and how likely tech debt is to spread, it's a great read and is available here: technology.riotgames.com/news/taxo...
I've created spreadsheets before to help discuss our tech debt related stories (These are stories raised by anyone in the team ahead of these discussions). This helps get them prioritised against new features and other work.
For further actions, you may consider blocking this person and/or reporting abuse
We're a place where coders share, stay up-to-date and grow their careers.
Hi,
I think for me, the problem is often relating to prioritising the fixes. As engineers, how do we go about communicating to our stakeholders and product owners the value of resolving tech debt?
I found a really valuable post by Riot Games (The company behind League of Legends), titled "The taxonomy of tech debt". It details how you may measure the impact, fix cost, and how likely tech debt is to spread, it's a great read and is available here: technology.riotgames.com/news/taxo...
I've created spreadsheets before to help discuss our tech debt related stories (These are stories raised by anyone in the team ahead of these discussions). This helps get them prioritised against new features and other work.