Related Posts
How does Moses make his coffee?
Anybody know any remote reinsurance roles?
Thoughts on BBH LA?
Additional Posts in Product Management
How does a Microsoft PM differs with Google PM?
New to Fishbowl?
Download the Fishbowl app to
unlock all discussions on Fishbowl.
unlock all discussions on Fishbowl.
I would only care about the tech debt for my product. I am not sure why you care about “company that already has a lot of tech debt”.
I use “age of tech debt” as my metric of success. My KPI is that the Tech Debt Jira tickets are younger than 12 months. Right now I am winning, with the oldest tech debt ticket being 7 months old.
As for how much tech debt is acceptable for a MVP… It depends on a risk assessment. What has the bigger cost or value ? I have accepted a lot of tech debt for a MVP when releasing quickly was the mitigation for a risk. And I have done the opposite (released MVP with little tech debt to mitigate a risk).
Yes, I’m working at a small company and we have 4 products
This is a quite the loaded question. There should always be a trade off decision, and for my teams debt is always a byproduct of doing it faster but you don’t get scale (eg only supports 1000 users) and we make it clear to everyone what we get/what we don’t get and when do we need to revisit. That way it’s easier to burn down your tech debt. So for us it’s usually “when we reach 10k users” or “scale to 5x markets”, etc.
Also, from a scrum perspective, engineers usually like to work on tech debt issues so we generally bake in a sprint of fixing tech debt/bugs or allocating a % of sprints to tech debt every few sprints.
Right on, makes sense. So are the impacts when issues come up cause of tech debt. Thanks!
Hmmm good question. I think if the debt is justified it shouldn't be too much of a problem