Nice article. Well summarized. Above the understanding of technical debt, having ongoing visibility and commitment to clear it are the major problems. Especially in the enterprise space, businesses wouldn't like to prioritize technical debt works when compared with new business features, and this approach continues till they wouldn't mov…
Nice article. Well summarized. Above the understanding of technical debt, having ongoing visibility and commitment to clear it are the major problems. Especially in the enterprise space, businesses wouldn't like to prioritize technical debt works when compared with new business features, and this approach continues till they wouldn't move any further with the debt. While writing code that is clean to refactor is important, the shift in the mindset to consider technical debt as an integral part of their journey is also important. By the way, sailor knots is a good metaphor :)
Thank you Sudheer! One way to address technical debt is to reserve a fixed amount of time to maintenance. We use about 20% of the time for it (refactoring + small bugs). This way you don't have to negotiate it every time.
Of course you can't address all technical debt like this — there are tasks that require a higher effort and should be planned separately.
Nice article. Well summarized. Above the understanding of technical debt, having ongoing visibility and commitment to clear it are the major problems. Especially in the enterprise space, businesses wouldn't like to prioritize technical debt works when compared with new business features, and this approach continues till they wouldn't move any further with the debt. While writing code that is clean to refactor is important, the shift in the mindset to consider technical debt as an integral part of their journey is also important. By the way, sailor knots is a good metaphor :)
Thank you Sudheer! One way to address technical debt is to reserve a fixed amount of time to maintenance. We use about 20% of the time for it (refactoring + small bugs). This way you don't have to negotiate it every time.
Of course you can't address all technical debt like this — there are tasks that require a higher effort and should be planned separately.