"Context over content" is a good metaphor to keep in mind when considering a technical debt assessment, reduction, and prevention engagement. Specific patterns in your code and the intricacies of your programming environment are paramount factors in determining how general insights will be turned into actions. In other words, it is unlikely that a technical debt engagement in your company will evolve along similar lines to those taking place in your competitor's "shop" down the street.
Advisor
About The Author
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
Dr. Israel Gat is an expert in Agile and Lean methods, devops, software governance, technical debt and technical due diligence. He served as Cutter Fellow and the Director of the Agile Product Management & Software Engineering Excellence practice from 2008 until 2015, and now splits his time between consulting and writing. Dr. Gat has received many accolades from clients, such as “His approach is the only one I’ve found that actually works… Read More
Don’t have a login?
Make one! It’s free and gives you access to all Cutter research.