As a software developer myself, I found it very surprising that you could obtain a time estimate for technical debt. In my experience, time estimates are notoriously inaccurate for any non-trivial software development (why we use story points instead). Can you elaborate more on how you derived a time estimate?
Good question though. Basically to estimate time spent on technical debt we use methods and techniques defined by Carlos Fernández-Sánchez, Carlos Vidal and others in their technical debt management work and of course use some tools such as duetask https://marketplace.atlassian.com/apps/1224361/duetask-for-jira
As a software developer myself, I found it very surprising that you could obtain a time estimate for technical debt. In my experience, time estimates are notoriously inaccurate for any non-trivial software development (why we use story points instead). Can you elaborate more on how you derived a time estimate?
Good question though. Basically to estimate time spent on technical debt we use methods and techniques defined by Carlos Fernández-Sánchez, Carlos Vidal and others in their technical debt management work and of course use some tools such as duetask https://marketplace.atlassian.com/apps/1224361/duetask-for-jira