Articles

25 Latest Articles Current Articles | Archives | Search

Dealing with Technical Debt: Avoiding Technical Bankruptcy - ScrumPulse Webcast #1

- Mark Noneman
in Webcasts

The phrase “technical debt” has become a commonly used phrase in software development. Technical debit is analogous to financial debt; build up too much and you’ll start paying more in “interest” and “principal” than you can invest in future value. This webcast covers what technical debt is, what causes it, and how to deal with it. Both management and engineering techniques in an agile development environment are reviewed.

Share this Article

Comments

Fredrik Vestin
Fredrik Vestin posted on Thursday, June 23, 2016 9:19 AM Permalink to this Comment
Great session! I also think there's another form of technical debt that always occur regardless of how good technical practices the team is using and that is changes in the "infrastructure" of the application, i.e. changes in operating systems, web browsers, development and 3rd party tools.
Examples:
A new release of your development tool is released. Parts of code must be re-written to allow an upgrade of the project. A 3rd party tool vendor stops developing component you use etc. Bottom line, technical debt will accumulate no matter what and need to be paid back continuously.
Mark Noneman
Mark Noneman posted on Thursday, June 23, 2016 2:27 PM Permalink to this Comment
I agree, Fredrik. And to deal with the evolution (and sometimes revolution) in technology, the Product Owner will need to be working with Developers to understand what's needed in architecture, tools, etc. It takes a lot of work to change architectural components so it needs to be planned for. The alternative is technical irrelevance--the ultimate "debt."

Post Comment

Only registered users may post comments.
Feedback
seo