In the past, teams could tell project stakeholders that software debt existed, but it was difficult to describe where and how much. Teams would increase their estimates for features that used to seem simple because it meant making changes to areas of the code they knew were infested with software debt. In the worst situations, teams would recommend a full rewrite of an application because the software debt was too difficult to work around anymore.
Advisor
How Much Software Debt Do We Have?
Posted June 8, 2011 | Technology |
About The Author
Brent Barton is a founding partner at Sterling Barton, LLC, a software product and consulting services company. Brent has used Agile practices for a decade as a Chief Technology Officer, PMO manager, project manager, development manager, software developer, ScrumMaster, Product Owner, coach, consultant, and trainer. He applies agility, pragmatism, persistence, organizational constructs, and process disciplines to help organizations outperform… Read More
Chris Sterling is Director of Engineering at Rally Software Development. Mr. Sterling works with clients as an Agile coach, certified Scrum trainer, and technology consultant. He has an extensive technology, process, and consulting background, allowing him to work with a diverse set of clients and teams. Mr. Sterling brings his real-world experience and deep passion for software development into his engagements, enabling others to grasp… Read More
Chris Sterling is Director of Engineering at Rally Software Development. Mr. Sterling works with clients as an Agile coach, certified Scrum trainer, and technology consultant. He has an extensive technology, process, and consulting background, allowing him to work with a diverse set of clients and teams. Mr. Sterling brings his real-world experience and deep passion for software development into his engagements, enabling others to grasp… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.