SPaMCAST 112 - Israel Gat, Technical Debt

Welcome to the Software Process and Measurement Cast 112! The Software Process and Measurement Cast this week features an in interview with Israel Gat, Practice Director for the Cutter Agile Practice.  We explored the concept of technical debit, how it is measured and the impact of technical debt on the organization. Israel Gat is recognized as the architect of the agile transformation at BMC Software. Under his leadership, BMC software development increased Scrum users from zero to 1,000, resulting in nearly three times faster time to market and 20-50% improvement in team productivity. Dr. Gat’s executive career spans top technology companies, including IBM, Microsoft, Digital, and EMC. He has led the development of products such as BMC Performance Manager and Microsoft Operations Manager, enabling the two companies to move toward next-generation system management technology. Dr. Gat is also well versed in growing smaller companies and has held advisory and venture capital positions for companies in new, high-growth markets. Dr. Gat currently splits his time between consulting and writing. He focuses on technical debt, large-scale implementations of lean software methods and agile business service management (“devops”). His recent e-book, The Concise Executive Guide to Agile, explains how the three can be tied together to form an effective software governance framework. Dr. Gat holds a PhD in computer science and an MBA. In addition to publishing with Cutter and the IEEE, he posts frequently at The Agile Executive and tweets as agile_exec. Emial:  isrgat@gmail.comAgile Executive: http://theagileexecutive.comCutter Consortium:  http://www.cutter.com/index.html Contact information for the Software Process and Measurement CastEmail:  spamcastinfo@gmail.comVoicemail:  +1-206-888-6111Website: www.spamcast.netTwitter: www.twitter.com/tcagleyFacebook:  http://bit.ly/16fBWV Next!SPaMCAST 113 inlcude an entry from the Metrics Minute on the concept of assignment scope (some think of this as maintenance productivty . . . not quite). I will also have some confernece news.