Jared Richardson is a Principle Consultant and a member of the core team at RoleModel Software, where he works alongside Ken Auer and the other software craftsmen who use Agile techniques to build excellent custom software for their clients. Jared sold his first software program in 1991 and has been immersed in software ever since. He has made a career out of helping teams find and fix their process blind spots. Jared has authored and coauthored a number of books, including the best selling Ship It!: A Practical Guide to Successful Software Projects, and Career 2.0: Take Control of Your Life. He is a frequent speaker at software conferences and a thought leader in the Agile space. Jared lives with his wife and children in North Carolina where he recently, quite by accident, became a backyard chicken farmer.
Find Jared on the web at Agile Artisans.
Technical debt has long been recognized in technical circles for years, but convincing your manager to budget time to repay "technical debt" has always been problematic. Let's couch the term technical debt concept in language more familiar to our managers: credit card debt. Like credit card debt, technical debt accumulates slowly over time, and usually takes just as long to pay off. The interest slowly builds up until you're no longer able to pay off the principle: your entire development cycle is devoted to just "paying the interest". We'll examine common types of technical debt and strategies to effectively communicating the problems, and their solutions, to your managers. Credit Card Debt: A New Paradigm for Recognizing and Repaying Technical Debt.