Video: Technical Debt — Including Top 7 Causes, and How to Avoid It


Agile Scrum Guide | Minisode | Technical Debt from Scott Graffius on Vimeo.



This (
https://vimeo.com/238528947) is a “minisode” on technical debt. It’s a 60-second video version of an article on the same topic published earlier in this blog.

The content is an abridged excerpt from the award-winning book, Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions, available in paperback and ebook formats at Amazon. For more on the book, please see agilescrumguide.com.

*****

You're invited to connect with Scott M. Graffius on social. Like his page on
Facebook, follow him on Twitter, and connect with him on LinkedIn.

Scott presents thought leadership on project, program, portfolio, and PMO management related topics of timely importance. He delivers talks at private and public events in the United States and internationally. For information on availability, fees, pro bono work and more, visit
SpeakerHub.

For more information, you can visit Scott's personal
website, review his bio, and read additional stories in the blog. The websites for his business and award-winning book are http://Exceptional-PMO.com and https://AgileScrumGuide.com.






custom - back to main page of blog

7 Causes of Technical Debt and How to Avoid It

stacks-image-01f361e

This is a brief introduction to technical debt—including top causes and how to avoid it.

Technical debt (also known as code debt and design debt) is a term used to describe the eventual consequences of a technical design or development choice made for a short-term benefit but with subsequent consequences. An example is writing suboptimal code to meet a deadline, knowing that the code will have to be rewritten later to make the software maintainable.

Technical debt may have one or more causes, such as:
1. Time pressures
2. Overly complex technical design
3. Poor alignment to standards
4. Lack of skill
5. Suboptimal code
6. Delayed refactoring
7. Insufficient testing

Over time, those factors result in the accumulation of technical inefficiencies that need to be serviced in the future. Unchecked technical debt may make the software more expensive to change than to re-implement.

Technical debt can be avoided or minimized by not taking shortcuts, using simple designs, and refactoring continuously. When there’s technical debt, the team should make the items visible by registering entries in the product release backlog, where the matters will be evaluated and prioritized for resolution.

This content is an abridged excerpt from the award-winning book, Agile Scrum: Your Quick Start Guide with Step-by-Step Instructions, available in paperback and ebook formats at Amazon. For more on the book, please see agilescrumguide.com.


*****

You're invited to connect with Scott M. Graffius on social. Like his page on
Facebook, follow him on Twitter, and connect with him on LinkedIn.

Scott presents thought leadership on project, program, portfolio, and PMO management related topics of timely importance. He delivers talks at private and public events in the United States and internationally. For information on availability, fees, pro bono work and more, visit
SpeakerHub.

For more information, you can visit Scott's personal
website, review his bio, and read additional stories in the blog. The websites for his business and award-winning book are http://Exceptional-PMO.com and https://AgileScrumGuide.com.






custom - back to main page of blog