Why Businesses should not ignore Technical Debt - A Case Study

Cases like the Toyota’s Unintended Acceleration case of 2007 highlight the impact of bad engineering practices on the quality of the product. This eventually impacts the business and the organization’s reputation as well. There have been several such instances in recent history, yet business stakeholders get tempted to compromise on the sound engineering practices for having quick gains. This approach, most of the times, is due to lack of understanding of these practices and under-estimating their negative impact in the long run. The aim of this paper is to highlight this impact and present a strong case for paying enough focus on concept like technical debt to reduce and control it in software development context.

1 favorite thumb_down thumb_up 0 comments visibility_off  Remove from Watchlist visibility  Add to Watchlist

Outline/structure of the Session

  1. Present the Case Study
  2. Root Causes for failure
  3. Why Businesses should track and monitor it - Business Impact!
  4. How Engineering teams should make Technical Debt visible?
  5. How to factor Technical Debt in Estimation?

Learning Outcome

  1. Business Impact of high Technical Debt
  2. How to make Technical Debt visible?

Target Audience

Business Executives, Product Owners, Business Analysts, Product Leadership

schedule Submitted 2 years ago

Comments Subscribe to Comments

comment Comment on this Submission