Troubleshooting Agile

In this episode Squirrel and Jeffrey discuss the Second Agile Principle: ‘Welcome changing requirements, even late in development. Agile processes harness change for the customer's competitive advantage.’ We hear how the principle is closely related to Lean Startup and Minimal Viable Product, and how, at its core, it is about understanding and learning from one’s environment as quickly and as often as possible. This reminds Squirrel of the OODA loop, the decision cycle developed by military strategist and US Air Force Colonel John Boyd, and he tells us a story about fighter jet dogfights in the Korean War. Jeffrey also tells us a story, about a startup he started way way back in the first dotcom bubble in 1999, which brings to mind another military lesson that ‘no plan survives contact with the enemy.’. Finally, we hear examples of common errors witnessed over the years, such as refusals to fully embrace the Second Agile Principle in favour of misguided efficiency and an often irrational attachment a plan. *** SHOWNOTES: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -The OODA Loop: https://en.wikipedia.org/wiki/OODA_loop -Lean Startup: https://en.wikipedia.org/wiki/Lean_startup *** We’d love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else, for that matter). You can email us, here: [email protected] Or send us a tweet, here: twitter.com/TShootingAgile Or you can find our website, here: http://troubleshootingagile.com/ Also, here is a link to our iTunes: https://itunes.apple.com/gb/podcast/troubleshooting-agile/id1327456890?mt=2 If you felt like liking, Sharing and/or Subscribing, we’d really appreciate it.

In this third episode of Troubleshooting Agile, Squirrel and Jeffrey take a look at the first of the 12 Agile Principles: "Our highest priority is to satisfy the customer through early and continuous delivery of valuable software.” As Jeffrey point out, this principle contains so much that it "could have been an agile manifesto in itself.” Squirrel and Jeffrey both tell stories about previous consulting experiences to highlight where clients have failed to fully deliver on this vital principle in the past, and how businesses can troubleshoot various common problems that arise. Show Notes: - The 12 Agile principles: http://agilemanifesto.org/principles.html - “The Goal: A Process of Ongoing Improvement”, by Eliyahu M. Goldratt: https://www.amazon.co.uk/Goal-Process-Ongoing-Improvement/dp/0566086654/ref=sr_1_1 - CITCON website: http://citconf.com/ We’d love to hear any thoughts you have about this Agile Principle, or about the podcast in general. You can email us, here: [email protected] Or send us a tweet, here: https://twitter.com/TShootingAgile Also, why not Like, Share and Subscribe. We’d really appreciate it.

In episode 2 of Troubleshooting Agile, Squirrel and Jeffrey look at what to do when you've adopted good agile practices but are not seeing good business outcomes; how the most beautiful kanban board on earth doesn't necessarily mean results; and why the 12 agile principles work as a form of feedback and a great guide. Shownotes: - Jeffrey's 2008 blog post – https://blog.jeffreyfredrick.com/2008/11/08/searching-for-an-agile-core/ - The 12 agile principles – http://agilemanifesto.org/principles.html - Chris Matts's blog – https://theitriskmanager.wordpress.com/2015/04/19/communities-of-need-community-of-solutions/ Why not let us know what you think on Twitter @TShootingAgile https://twitter.com/TShootingAgile

In this week's podcast Jeffrey tells us a story about the dangers of blaming human error in the workplace, and we discuss root cause analysis, the blameless postmortem approach and how these are essential components in building productive systems and a great agile team. Normal Accidents – http://bit.ly/2CtawMg http://troubleshootingagile.com/