From the course: Agile Product Owner Role: Techniques

Unlock the full course today

Join today to access over 25,200 courses taught by industry experts.

Technical debt

Technical debt

From the course: Agile Product Owner Role: Techniques

Start my 1-month free trial Buy for my team

Technical debt

“

- What happens when teams work fast and furious without an eye towards the product vision and road map, and they take shortcuts, rather than doing it right the first time? Well, they typically create a lot of rework and pain, and in Agile, it's no different. Technical debt is the cost incurred for cutting corners in the short term, and Agile teams can create more than an appropriate amount of it, when only focused on the current sprint. When too much technical debt happens on a solution, over time, the team's pace and velocity slows down. The shortcuts taken earlier can create more work to unravel and refactor, as the team adds more functionality. Some technical debt is good and strategic, and typically this is the case when there are major unknowns, and things like experiments and prototyping, where the team is taking shortcuts to learn and later commit to a technical path. In this case, it's all about the learning and experimenting. Well there are two major contributors to…

Contents