BROADCASTS.com

In this interview Agile Alliance Board Member Declan Whelan makes the case for reframing Technical Debt and having organizations develop practices and programs supporting Technical Health. During the interview we discuss what technical debt it, how our perception of it has evolved and why taking a more positive and proactive stance for it can be so beneficial for organizations that are trying to improve flow and remain competitive in the marketplace.\n\nDeclan also shares details on the Agile Alliance\u2019s OnAgile 2017 virtual conference which is taking place on October 25, 2017.\n\nSHOW NOTES\n\n00:09 Interview Begins\n00:36 Background on Declan\n02:35 What is Technical Debt?\n03:55 How the definition of Technical Debt has evolved\n05:11 Impediments to flow\n06:15 Why it makes sense to think of Technical Debt as Technical Health\n09:42 How does technical debt happen?\n11:15 The environment (or system) may be set up to support increased technical debt\n13:12 Explaining to management why technical wellness is so important\n14:26 Measuring technical health (and debt)\n15:58 Explaining the debt in dollars and showing the value of investing in technical health\n16:22 How much faster could you go?\n17:25 Why Declan enjoys legacy code and why some folks get frustrated with it\n19:00 Finding the right people to work on it\n20:16 Should technical debt go in the Product Backlog?\n20:55 Employing the Boy Scout rule\n24:25 Does Leadership and the PMO understand the importance of dealing with technical debt?\n26:00 How the PMO can have a positive impact on technical wellness\n30:55 OnAgile 2017 - the Online Conference (10/25)\n30:04 What is Psychlomatic Complexity?\n34:16 The things in Agile that Declan is focusing on learning about \n36:00 Contacting Declan\n\nOnAgile 2017 http://bit.ly/2i3G0f6\n\nCONTACTING DECLAN\nLeanintuit http://leanintuit.com\nTwitter https://twitter.com/dwhelan\nLinkedIn https://www.linkedin.com/in/declanwhelan/\nAgile Alliance https://www.agilealliance.org/