How do you handle bugs and technical debt when many valuable new features are competing for resources?
Focusing solely on shipping new features is a slippery slope that quickly leads to the build-up of technical debt. It is like trade a short-term win—shipping more features—for a long-term liability. Technical debt will inevitably slow down the creature of new Product Increments in the future, probably to a point where the product seems to be at a standstill.
In other words: By accruing technical debt, the very purpose of becoming agile—learning faster as an organization than the competition, thus being able to exploit market opportunities—is at stake.
Hence it is a good practice to allocate around 20 percent of the Developers’ capacity to keeping technical debt at bay at any given time. As an experienced Product Owner I also consider long-term thinking.
**Hit the link to send your queries to us about this question, our experts will reach out to you at the earliest!