How to Detect Agile BS - Part 2

The US Defense Department (yes, the huge bureaucratic government body) recently released a brief and readable guide to troubleshooting your agile team. We have a look at three more of its key recommendations for figuring out whether you're agile team is really agile - which leads us to discuss when software developers should wield soldering irons and how continuous integration is better with a rubber chicken. SHOW LINKS: - Detecting Agile BS: https://media.defense.gov/2018/Oct/09/2002049591/-1/-1/0/DIB_DETECTING_AGILE_BS_2018.10.05.PDF - The Defense Innovation Board: https://innovation.defense.gov - Continuous Integration on a Dollar a Day (aka the Rubber Chicken): https://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html - IMVU continuous deployment: http://timothyfitz.com/2009/02/10/continuous-deployment-at-imvu-doing-the-impossible-fifty-times-a-day/ - CITCON (Continuous Integration and Testing Conference): https://citconf.com/ *** 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