The Technical Debt

Technical debt might be one of the things that slows my team down the most day to day. We try to take shortcuts, but watch out for what they’re going to cost us later, in the future.

Imagine you borrow money from the bank today to move faster on your tasks or to acquire something. It’s the same thing in IT. If we decide to take a shortcut and not do something now, it’s a cost we’ll have to pay later, and probably with interest.

What does that actually mean? If your code hasn’t been properly tested, or you haven’t documented it, or you built a feature quickly and told yourself: “Oh, that’s fine, I’ll do it later.” But that “later” will have to be caught up on. And when you have to catch up, it will take time, energy, and figuring out why you did it that way back then.

Be careful, I’m not saying technical debt is a bad thing. Sometimes it can be relevant to test something, to validate a hypothesis, to check that everything works. But you need to be aware of it, estimate it, and know that you’ll have to spend time paying it back in the future.

In short, technical debt is like real money. It’s a loan we take out on time today, but that we’ll have to repay later, in the future, no matter what.

And you, how does your team handle the technical debt?

Sources: https://www.scrum.org/resources/blog/technical-debt-scrum-who-responsible

Leave a Comment

Your email address will not be published. Required fields are marked *

Scroll to Top