Troubleshooting Agile

Our first interview ever! We welcome to the studio Chris Clearfield, co-author of Meltdown, a book all about system failure and the reasons for it. Chris explains ideas like tight coupling (not the OO kind!) and system complexity, and we explore how they apply to technical debt and bug prioritisation. We get to hear some of the best stories from the book as well, including the hedge fund that lost £500m in 45 minutes, and we learn about failcake and pre-mortem analysis. GUEST LINKS: - Chris's site: https://www.chrisclearfield.com - Chris's twitter: https://twitter.com/ChrisClearfield - Book site: http://meltdownbook.net - Take the quiz: http://quiz.rethinkrisk.net/quiz/ - Book video preview: https://www.youtube.com/watch?v=0Wi8KA4I34s&feature=youtu.be SHOW LINKS: - Psychohistory: https://en.wikipedia.org/wiki/Psychohistory_(fictional) - Normal Accidents: https://en.wikipedia.org/wiki/Normal_Accidents - John Allspaw: https://www.kitchensoap.com/about-me/ - Just Culture book: https://sidneydekker.com/just-culture/ - Dunbar’s number: https://en.wikipedia.org/wiki/Dunbar%27s_number - Amy Edmondson, Teaming: https://www.amazon.co.uk/Teaming-Organizations-Innovate-Compete-Knowledge/dp/078797093X - Jon Ronson So You've Been Publicly Shamed: https://en.wikipedia.org/wiki/So_You%27ve_Been_Publicly_Shamed - Gary Klein, Pre-Mortem: https://en.wikipedia.org/wiki/Pre-mortem *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Our first interview ever! We welcome to the studio Chris Clearfield, co-author of Meltdown, a book all about system failure and the reasons for it. Chris explains ideas like tight coupling (not the OO kind!) and system complexity, and we explore how they apply to technical debt and bug prioritisation. We get to hear some of the best stories from the book as well, including the hedge fund that lost £500m in 45 minutes, and we learn about failcake and pre-mortem analysis. GUEST LINKS: - Chris's site: https://www.chrisclearfield.com - Chris's twitter: https://twitter.com/ChrisClearfield - Book site: http://meltdownbook.net - Take the quiz: http://quiz.rethinkrisk.net/quiz/ - Book video preview: https://www.youtube.com/watch?v=0Wi8KA4I34s&feature=youtu.be SHOW LINKS: - Psychohistory: https://en.wikipedia.org/wiki/Psychohistory_(fictional) - Normal Accidents: https://en.wikipedia.org/wiki/Normal_Accidents - John Allspaw: https://www.kitchensoap.com/about-me/ - Just Culture book: https://sidneydekker.com/just-culture/ - Dunbar’s number: https://en.wikipedia.org/wiki/Dunbar%27s_number - Amy Edmondson, Teaming: https://www.amazon.co.uk/Teaming-Organizations-Innovate-Compete-Knowledge/dp/078797093X - Jon Ronson So You've Been Publicly Shamed: https://en.wikipedia.org/wiki/So_You%27ve_Been_Publicly_Shamed - Gary Klein, Pre-Mortem: https://en.wikipedia.org/wiki/Pre-mortem *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Our first interview ever! We welcome to the studio Chris Clearfield, co-author of Meltdown, a book all about system failure and the reasons for it. Chris explains ideas like tight coupling (not the OO kind!) and system complexity, and we explore how they apply to technical debt and bug prioritisation. We get to hear some of the best stories from the book as well, including the hedge fund that lost £500m in 45 minutes, and we learn about failcake and pre-mortem analysis. GUEST LINKS: - Chris's site: https://www.chrisclearfield.com - Chris's twitter: https://twitter.com/ChrisClearfield - Book site: http://meltdownbook.net - Take the quiz: http://quiz.rethinkrisk.net/quiz/ - Book video preview: https://www.youtube.com/watch?v=0Wi8KA4I34s&feature=youtu.be SHOW LINKS: - Psychohistory: https://en.wikipedia.org/wiki/Psychohistory_(fictional) - Normal Accidents: https://en.wikipedia.org/wiki/Normal_Accidents - John Allspaw: https://www.kitchensoap.com/about-me/ - Just Culture book: https://sidneydekker.com/just-culture/ - Dunbar’s number: https://en.wikipedia.org/wiki/Dunbar%27s_number - Amy Edmondson, Teaming: https://www.amazon.co.uk/Teaming-Organizations-Innovate-Compete-Knowledge/dp/078797093X - Jon Ronson So You've Been Publicly Shamed: https://en.wikipedia.org/wiki/So_You%27ve_Been_Publicly_Shamed - Gary Klein, Pre-Mortem: https://en.wikipedia.org/wiki/Pre-mortem *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

This week, Jeffrey and Squirrel discuss the history of “software for humans”, the agile, lean, and devops movements. No links this week as the book deadline looms, but feel free to ask us if you can’t find a reference. Normal service will resume shortly! *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

A listener question about running a Troubleshooting Agile study group inspires advice on keeping your learning from becoming lunchtime entertainment, as well as surprisingly relevant stories about a pottery class, a management seminar, and the Israeli military. SHOW LINKS: - Joel's tweet requesting advice on his study group: https://twitter.com/joelchippindale/status/1143137854278840321 - Our series on the twelve agile principles: https://soundcloud.com/troubleshootingagile/the-importance-of-the-agile-principles - Pottery story from Art & Fear: https://www.amazon.com/exec/obidos/ASIN/0961454733/ via https://stratechery.com/2015/buzzfeed-important-news-organization-world/ - Joel Spolsky on Fire and Motion: https://www.joelonsoftware.com/2002/01/06/fire-and-motion/ - Reg Revans on action and learning: http://actionlearning.academy/benefits.html *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

The engineers know the project is in terrible trouble, but the executives think it's going great. This "greenshifting" anti-pattern occurs at NASA, software companies, and everywhere in between. We tell a few related stories, including a fable, and suggest methods that might work to counteract the greenshifting tendency in your organisation. SHOW LINKS: - "The Mushroom Song" by Steve Savitsky: http://steve.savitzky.net/Songs/mushroom/ - The SNAFU Principle (communication fable) from the Jargon File: http://skeptictank.org/files//cowtext/jargn10.htm - Appendix F on the Challenger disaster, by Richard Feynman: https://science.ksc.nasa.gov/shuttle/missions/51-l/docs/rogers-commission/Appendix-F.txt - Scott Ambler on Greenshifting: https://www.drdobbs.com/dr-dobbs-agile-newsletter/191600661 - Alistair Cockburn on information radiators: http://www.informit.com/articles/article.aspx?p=24486&ranMID=24808 - Brian Marick on lava lamps as build status indicators: https://gist.github.com/marick/3ec112bc38b2af267e15 *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

You can invest a lot of your time in making your software delivery predictable (a la NASA) or in making your team productive (a la early stage startups). Which is best? We introduce the idea of a "tilted slider" to explain this tradeoff, and the "gravity" that pulls you toward predictability even when it may not be the best emphasis. And as usual, we have stories of effective and ineffective action from our own experiences. SHOW LINKS: - Cowboy coding: https://en.wikipedia.org/wiki/Cowboy_coding *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

How are you briefing your team? What measurements are you using to help them learn? Today, we discuss cases where giving the team incentives to make more mistakes produces positive results, and others where urging them to make fewer is catastrophic. SHOW LINKS: - Andon cord: https://en.wikipedia.org/wiki/Andon_(manufacturing) - Toyota Kata: http://www-personal.umich.edu/~mrother/Homepage.html - NTSB immunity for pilots: https://asrs.arc.nasa.gov/overview/immunity.html *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Today we describe a technique for avoiding micromanagement and promoting autonomy - first pioneered by the Prussian military! We describe how briefing and back briefing help Boeing build airplanes and how the method increases efficiency and reduces drama in the agile teams we work with. SHOW LINKS: - Art of Action by Bungay: http://www.stephenbungay.com/Books.ink - Boeing weight economy: in https://www.amazon.co.uk/Serious-Play-Companies-Simulate-Innovate/dp/0875848141 *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2

Today we relate three great stories we heard or told at CITCON in Ghent, all starting with different answers to Jeffrey's question, "Why can't we ship that today?" The answers lead us to different suggestions for helping teams to move faster and get customer feedback. SHOW LINKS: - Value stream mapping: https://en.wikipedia.org/wiki/Value-stream_mapping - CITCON notes: https://citconf.com/wiki/index.php?title=WarStoriesAndSuccesses - Poppendieck and Poppendieck, Lean Software Development: https://www.amazon.co.uk/Lean-Software-Development-Agile-Toolkit/dp/0321150783 *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubleshootingagile.com Tweet us: twitter.com/TShootingAgile Also, if you'd like to leave us a review on iTunes (or just like and subscribe), you'll find us here: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2