This is the list of the various work items that need to be done: additions, changes, repairs, and sometimes removal of software. The product backlog and the priorities of the backlog items are managed by the product owner, who is tasked with making the best investments in the product.
In addition to deciding which functionality is required first, the product owner also has to strike a balance between the functionality of the application and its technical quality.
An application’s technical quality is often expressed as technical debt.
This is the estimated cost of rework to repair substandard software.
Substandard software is caused by lack of competences and/or lack of time and budget to develop to whatever standard has been set.
Just as with financial debt, technical debt comes at a cost. ‘Interest’ is paid in the form of incidents that cause disruptions to business operations, and required repairs or workarounds.
Technical debt is ‘repaid’ when substandard software is repaired.
Balancing the product backlog
by Mark Smalley
Product-based software development teams are tasked with software design, coding and testing during the whole lifecycle of the software product, not just the initial development. The software product has a product backlog.