Troubleshooting Agile

Guest Paul Julius, CruiseControl founder, discusses agile practices left behind like iterations, predictability, and planning. Transition from predictability to productivity, TDD in consulting, continuous integration, and evolving agile practices are explored.

This week, Jeffrey and Squirrel help a listener with the role of design and architecture in an agile team. The answer involves arcane-sounding but fun concepts like elephant carpaccio, evolutionary design, and YAGNI. SHOW LINKS: - YAGNI: https://en.wikipedia.org/wiki/You_aren%27t_gonna_need_it - Elephant Carpaccio: http://alistair.cockburn.us/elephant+carpaccio - Evolutionary Design: https://martinfowler.com/tags/evolutionary%20design.html - XP Explained: https://www.barnesandnoble.com/w/extreme-programming-explained-kent-beck/1119347147 - GOOS book: http://www.growing-object-oriented-software.com/ - Sprint zero: https://www.frontrowagile.com/blog/posts/125-sprint-zero-for-product-owners - Trim the tail and order by risk: http://alistair.cockburn.us/Design+as+Knowledge+Acquisition - Up-front design in a previous episode: https://soundcloud.com/troubleshootingagile/enhancing-agility-through-technical-excellence-and-good-design *** We'd love to hear any thoughts, ideas or feedback you have regarding 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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This week, Jeffrey and Squirrel look at how to learn new skills in your agile team or elsewhere, and recommend frequent failure as a useful heuristic. SHOW LINKS: - Graham Lee blog post: https://www.sicpers.info/2018/02/to-become-a-beginner-first-become-an-expert/ - No True Scotsman fallacy: https://en.wikipedia.org/wiki/No_true_Scotsman - TDD (Test-Driven Development): https://en.wikipedia.org/wiki/Test-driven_development - Agile principles: http://agilemanifesto.org/principles.html *** We'd love to hear any thoughts, ideas or feedback you have regarding 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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This week, Jeffrey and Squirrel describe some of the methods they used to improve their own skills in implementing and troubleshooting agile methods. They describe techniques from rubber ducking to doppelgängers. Enjoy! SHOW LINKS: - CITCON: http://citconf.com - Breakfast with Squirrel: http://douglassquirrel.com - Communities of Needs and Solutions: https://theitriskmanager.wordpress.com/2015/04/19/communities-of-need-community-of-solutions/ - Dr. David Burns: https://feelinggood.com/ - Paradoxical Double Standard: https://feelinggood.com/tag/paradoxical-double-standard/ - Rubber Duck Debugging: https://en.wikipedia.org/wiki/Rubber_duck_debugging Alberto Savoia, older wiser self: http://www.albertosavoia.com/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: see link on http://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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This week, Jeffrey and Squirrel discuss how to avoid blame - adopting a frame of ownership or problem-solving is a useful concrete action to try to achieve this - and tell a story about replacing one problem with a much bigger one to achieve team improvement. SHOW LINKS: - The 12 Agile Principles: http://agilemanifesto.org/principles.html - Alex Hudson blog post on blame: https://www.alexhudson.com/2018/01/03/troubleshooting-agile-new-podcast-notes-ownership/ - Mark Coleman: https://www.implicit-explicit.com/ - The Power of Habit: https://en.wikipedia.org/wiki/The_Power_of_Habit - https://blog.jeffreyfredrick.com/2016/04/08/coherence-busting-explained/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This podcast discusses how teams handle deadlines, exploring topics such as utilizing prediction models, unintended consequences of setting dates, reassurance in high-trust environments, and navigating scope and stress with burn down charts in Agile teams.

This week, Jeffrey and Squirrel are on the road at CITCON Vienna, interviewing Lydia Tripp about her journey through a wide variety of agile software development teams and her evolving approach to improving delivery and quality. SHOW LINKS: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -CITCON: http://citconf.com/ -Extreme Programming: https://en.wikipedia.org/wiki/Extreme_programming -Lydia: https://www.linkedin.com/in/lydia-tripp-988a79/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This week, Jeffrey and Squirrel are on the road at CITCON Vienna, interviewing participants about how they use agile techniques and principles outside development. SHOW LINKS: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -CITCON: http://citconf.com/ -London Organisational Learning Meetup: https://www.meetup.com/en-AU/London-Action-Science-Meetup/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

In this week's podcast we move on to the final Agile Principle, number 12: "At regular intervals, the team reflects on how to become more effective, then tunes and adjusts its behaviour accordingly." The hard truth is that learning is horrible. It means coming face to face with your own inadequacies, and challenging them. Consequently, mustering up the motivation to learn is too easily and too often avoided. Squirrel and Jeffrey discuss their own experiences with the importance of reflection and some troubleshooting techniques to make learning easier. They also discuss: -How we all need to keep sharpening the saw, because if we're constantly producing we're not learning. -Using Production Vs Production Capacity, from 7 Habits of Highly Influential People, to remind ourselves of this. -How Marginal Gains, just 1%-per-day, compound to make a huge difference over time. -How, unexpectedly, it is often something as simple as poor relationships that are blocking the natural learning a company would like to have. It's much easier to blame the circumstances than have difficult conversations, and this blocks development. Therefore, we have a challenge for our listeners: Look at your current circumstances, at what you think the problems are, reflect, and then ask yourself: what's currently preventing you from taking action on those problems (and that means YOU. You individually. Saying your boss is an idiot is not an answer). There are always opportunities available to you, should you choose to take them. If you agree or disagree with us, let us know, via email, Twitter or in a review below. We'd love to take on some of your cases in upcoming episodes. *** SHOW LINKS: -The 12 Agile Principles: http://agilemanifesto.org/principles.html -James Clear on Marginal Gains: https://jamesclear.com/marginal-gains -The 7 Habits Of Highly Effective People, by Stephen R Covey: https://www.stephencovey.com/7habits/7habits-habit7.php -London Organisational Learning Meetup: https://www.meetup.com/en-AU/London-Action-Science-Meetup/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2

This week we take a short break from the Agile Principles to discuss The Squirrel Test - 12 questions to help founders improve their scale-up company's performance. We also find out if Squirrel, in creating the test, has practiced what he's preached regarding the agile principles. Has he produced working software? Sought early feedback? Kept it simple? Made the most of face-to-face communication? Retained a constant pace? Created a supportive environment for his team? Find out in this week's podcast. We'd like to apologise for the sound quality this week. With Jeffrey on the road we had some mic difficulties that we were unable to fix. We thought about not posting an episode at all, but didn't want to disappoint regular listeners by missing a week. So, again, our apologies for the quality. Next week we will be back to a silky smooth sound. *** LINKS: -The Squirrel Test: http://squirreltest.com -The Joel Test: https://www.joelonsoftware.com/2000/08/09/the-joel-test-12-steps-to-better-code/ *** We'd love to hear any thoughts, ideas or feedback you have regarding the show. Email us: agile@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: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2