Troubleshooting Agile

What Happens After Why Last week we explained how asking the simple question “why?” can help you make big improvements in your agile team - and this week we prove it, with two examples from Jeffrey. In one case his company landed a big client, and in the other an angry person actually listened to him! Hear more in this week’s episode! SHOW LINKS: - David Burns, the disarming technique: https://daviddburnsmd.files.wordpress.com/2017/04/the-five-secrets-v-1.pdf - Chris Voss: https://www.youtube.com/watch?v=guZa7mQV1l0 and https://www.youtube.com/watch?v=llctqNJr2IU - Previous podcasts on coherent stories: https://soundcloud.com/troubleshootingagile/why-you-shouldnt-listen-to-your-brain and on the 4 Rs of learning: https://soundcloud.com/troubleshootingagile/learning-through-case-studies-the-4-rs - 7 habits of highly effective people: https://en.wikipedia.org/wiki/The_7_Habits_of_Highly_Effective_People - Squirrel and Jeffrey talk on leadership techniques: https://skillsmatter.com/meetups/11800-leadership-mat

In which we meet Squirrel's client Mr. Why, who wants to know the reasoning behind requests he gets but never actually asks, and we describe how this pattern holds back agile teams and how to break out of it. Surprisingly, lawyers feature prominently in this episode, as both positive and negative examples of effective "why" communication! SHOW LINKS: - Lawyers don't ask "why?": https://aqrlaw.ca/blog/five-questions-you-should-never-ask-on-cross-examination *** 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

Last week we emphasised the importance of practise to help you have better agile conversations and negotiations, and this week we describe two ways to practise - Argyris's two-column case studies and Dr. Burns's relationship journal - and a framework to use with both: record, reflect, revise, and roleplay. Join us in London on 19 March for our talk on "Sprinting In Place: The Cost of Missing Leadership Conversations"! SHOW LINKS: - Argyris's two column case study: https://blog.benjaminm.net/2011/02/16/argyriscasestudylearningmodelii/ https://hbr.org/1986/09/skilled-incompetence - Dr. David Burns's Interpersonal model & relationship journal https://feelinggood.com/2017/10/16/057-interpersonal-model-and-its-all-your-fault-part-4/ https://feelinggood.com/wp-content/uploads/2017/10/rj-revised-v-1c-dvl-v-1.pdf - Our SkillsMatter talk on 19 March: https://skillsmatter.com/meetups/11800-leadership-matters *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on

Today, we explain that when you learn a new skill - whether it's playing the piano, kitesurfing across a lake, or negotiating with others inside and outside your agile team - it's vital to practise to develop your abilities. Don't jump onto the double black diamond run the first time you hit the slopes; instead, find a coach and watch her carefully as she goes down the mountain first. You'll learn to act in unintuitive ways and discover new possibilities you wouldn't have thought of. The same is true of learning to have the difficult conversations you need to improve your agile team - you can listen to us all you want, but you'll need to try (and fail!) to really master the methods. We get started on some methods for effective practise, including the use of a feeling chart, with more to follow in the next episode. Join us in London on 19 March for our talk on "Sprinting In Place: The Cost of Missing Leadership Conversations"! SHOW LINKS: - Jeffrey's blog post on the piano analogy: https://blog.jeffreyfredr

Your brain has two halves - not called left and right, but System 1 and System 2. Today we explain how these two halves of your own brain wind up fooling you and your team into believing things like "New York decided to do this", "customers don't want that feature", and "the business won't let us write tests" - and what you can do to keep your brain from tricking you into believing suspiciously coherent stories. Join us in London on 19 March for our talk on "Sprinting In Place: The Cost of Missing Leadership Conversations"! SHOW LINKS: - Thinking, Fast and Slow by Kahneman: https://www.amazon.co.uk/Thinking-Fast-Slow-Daniel-Kahneman/dp/0141033576 - Our SkillsMatter talk on 19 March: https://skillsmatter.com/meetups/11800-leadership-matters *** 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 her

The agile principles talk about empowerment and autonomy, but do we have to make a complete switch from our current centralised-decision culture to a fully autonomous one? The Satir curve, six thinking hats, and a theory of Tic Tac change (really!) from Jeffrey and Alistair Cockburn, shows us a way to make a series of small changes rather than one big shift. SHOW LINKS: - Theory X and Theory Y: https://en.wikipedia.org/wiki/Theory_X_and_Theory_Y - The Uncanny Valley of A Functional Organization: https://stratechery.com/2013/the-uncanny-valley-of-a-functional-organization/ - Satir curve (J-curve): http://dhemery.com/articles/managing_yourself_through_change/ - Tic Tac presentation (Fredrick/Cockburn): http://blog.jeffreyfredrick.com/wp-content/uploads/2008/07/sdbp06tictactalk.pdf - Six Thinking Hats: https://en.wikipedia.org/wiki/Six_Thinking_Hats *** 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/TShoot

Theory X organisations don't trust their people - or do they? To be agile we have to move our organisations to a Theory Y model with empowerment and autonomy - or do we? Organisational change has to be painful - or does it? And what does all this have to do with creepy robots? SHOW LINKS: - Theory X and Theory Y: https://en.wikipedia.org/wiki/Theory_X_and_Theory_Y - J Jonah Jameson: https://www.youtube.com/watch?v=mhDBWiTfNCU - The Uncanny Valley: https://en.wikipedia.org/wiki/Uncanny_valley - The Uncanny Valley of A Functional Organization: https://stratechery.com/2013/the-uncanny-valley-of-a-functional-organization/ *** 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

Due to illness and travel, Jeffrey and Squirrel present one of their greatest hits of the past! *** Squirrel and Jeffrey look at a recent article by Luke Tomas on the "employee engagement industry" (we didn't even know it *was* an industry!) Jeffrey rapidly links this to Brian Marick's idea of Ease and Joy at work and we all agree that engagement, happiness, and joy are all useful, but lagging, indicators of team success - so you can't improve them directly with bigger bonuses or tougher objectives. Instead alignment, focus, and autonomy work to create these results by creating the conditions for happiness and good performance. SHOW LINKS: - Luke Tomas, The Employee Engagement Myth: medium.com/@lukethomas14/the-e…t-myth-3885526782d7 - Brian Marick, Ease and Joy at Work: exampler.com/ease-and-joy/ - Previous episode on technical excellence: Troubleshootingagile – Fowlers-state-of-agile-part-two - Reinventing Organisations (Teal and other colours): www.reinventingorganizations.com/ - Theory X and Theory

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 fe

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 of its six key recommendations for figuring out whether you're agile team isn't really agile - which leads us to discuss what end-users really are and why financial traders are so insane. 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 *** 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

Once you've been vocally critical and identified areas to improve in your agile team, what next? "We should" too often turns into "We won't", so good intentions aren't enough. Jeffrey tells the story of teaching TDD and the tools he learnt and developed to foster internal commitment to change - paradoxically, this involves questioning whether the change is actually worth doing! SHOW LINKS: - SPIN selling book: https://www.amazon.co.uk/SPIN-Selling-Neil-Rackham/dp/0566076896 - Previous episode on earning trust through vocal self-criticism: https://soundcloud.com/troubleshootingagile/earning-trust-at-amazon - Previous series on unilateral control: https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-i *** 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://i

Inspired by a listener comment, we look at one of Amazon's leadership principles, which describes how leaders are expected to earn trust in that organisation. It seems to us that the principle lays the foundation for effective psychological safety for the avoidance of error, but there are some traps to watch out for on the way to that end. SHOW LINKS: - Amazon leadership principles: https://www.amazon.jobs/en/principles - Ladder of inference annotated diagram: http://troubleshootingagile.com/docs/TheLadderOfInference.pdf *** 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

In our one-year anniversary episode, we start with a story about "flickering" tests and generalise to look at the idea of normalisation of deviance. We suggest that psychological safety lets you hear from those who see the deviance but aren't speaking up, with examples from oil rigs, and tie to pair programming as a way to create a safe environment for reiterating agreed non-deviant behaviour. SHOW LINKS: - Diane Vaughan and links to normalisation of deviance: https://en.wikipedia.org/wiki/Diane_Vaughan - Bystander effect and smoke experiment; https://en.wikipedia.org/wiki/Bystander_effect#Social_psychology_research - Psychological safety: https://www.businessinsider.com/amy-edmondson-on-psychological-safety-2015-11?r=UK&IR=T - Oil rig creating psychological safety: https://www.npr.org/sections/health-shots/2016/06/17/482203447/invisibilia-how-learning-to-be-vulnerable-can-make-life-safer and https://hbr.org/2008/07/unmasking-manly-men *** We'd love to hear any thoughts, ideas, or feedback you have about

We've been talking about building trust in agile teams by aligning your stories; an important ingredient for this is being predictable, so others can believe you actually have a story they can align with. We tell an extended story about a developer with a severely misaligned story and how Squirrel's route to trust with him included crawling around on the floor reconfiguring cables. SHOW LINKS: - Argyris, Espoused Theory vs Theory in Use: http://infed.org/mobi/chris-argyris-theories-of-action-double-loop-learning-and-organizational-learning/#_Theories_of_action - Previous podcast on acting unilaterally: https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-iv - Annotated Ladder of Inference diagram: http://troubleshootingagile.com/docs/TheLadderOfInference.pdf - Schwarz, Eight Behaviours for Smarter Teams: https://www.csu.edu.au/__data/assets/pdf_file/0008/917018/Eight-Behaviors-for-Smarter-Teams-2.pdf *** We'd love to hear any thoughts, ideas, or feedback you have about the

We answer a listener question about standups for feature teams, but we think the problem is actually a larger one of disengagement. A common symptom is people sitting down for their standup (oxymoron alert!) We recommend some ways to overcome disengagement using Coherence Busting and the Ladder of Inference, tools we've been discussing on recent podcasts. SHOW LINKS: - Feature teams: http://featureteams.org - Ladder of Inference episodes: https://soundcloud.com/troubleshootingagile/test-driven-development-for-people and https://soundcloud.com/troubleshootingagile/introspection-with-the-ladder-of-inference - Coherence busting: https://blog.jeffreyfredrick.com/2016/04/08/coherence-busting-explained/ and https://soundcloud.com/troubleshootingagile/removing-the-blame-frame *** 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 subs

Last time we talked about sharing reasoning and building trust in your agile team using TDD for People, one way to use the Ladder of Inference. Today we look at how the Ladder can help you discover your own reasoning as well, to discover ways to promote mutual learning with your own behaviour. SHOW LINKS: - Top Business Podcasts for CEOs, from Fiona Anderson: https://www.rocktime.co.uk/insights/listen-and-learn-the-art-of-podcasting-for-ceos/ - The Ladder of Inference (annotated by Jeffrey): http://troubleshootingagile.com/docs/TheLadderOfInference.pdf - The London Organisational Meetup: https://www.meetup.com/London-Action-Science-Meetup/ - Thinking Fast and Slow, Kahneman: https://en.wikipedia.org/wiki/Thinking,_Fast_and_Slow *** 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://it

As promised, we start describing our favourite trust-building technique: the Ladder of Inference. Our take this week is on using the Ladder to understand someone else's reasoning and align your stories, creating trust as a foundation for further improvement in your agile team. Surprisingly, the experience of using the Ladder in this way is similar to Test-Driven Development: careful, understandable, small steps with confidence, and meaningful signals from both success and failure. SHOW LINKS: - Peter Senge, The Fifth Discipline: https://www.amazon.co.uk/dp/B003ELY7OW/ref=dp-kindle-redirect?_encoding=UTF8&btkr=1 - The Ladder of Inference (annotated by Jeffrey): http://troubleshootingagile.com/docs/TheLadderOfInference.pdf - Cognitive biases book and more: https://youarenotsosmart.com/ - Schwarz on unilateral control (again!): http://www.schwarzassociates.com/managing-performance/how-unilateral-control-undermines-team-results-and-relationships-2/ - TDD for people video: https://www.douglassquirrel.com/how-i-

We start previewing the ideas in our forthcoming book on using conversations to improve your agile results. First up: why you need trust before you do anything else (including hold a standup, write unit tests, or move your desks together). Next week, a step-by-step technique to build trust. SHOW LINKS: - The first thing to build is trust, Brad Appleton: http://bradapp.blogspot.com/2005/02/first-thing-to-build-is-trust.html - Psychological safety: https://www.jstor.org/stable/2666999?origin=JSTOR-pdf&seq=1#page_scan_tab_contents - The story I'm telling myself: https://blog.jeffreyfredrick.com/2015/08/31/the-story-im-making-up/ - Naive realism: https://en.wikipedia.org/wiki/Na%C3%AFve_realism_%28psychology%29 and previous TA episode: https://soundcloud.com/troubleshootingagile/how-to-fail-by-acting-unilaterally-part-i *** 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

We cap our five-part series on undermining your agile team with the pinnacle of ineffective behaviour: the belief that you are not contributing to the problem. Inaccurate estimates, useless meetings, directionless standups - so long as you're sure all these are entirely someone else's fault, you'll be sure never to fix them, and thus leave your team high and dry. Master this technique and never worry about having an effective team again! Bonus at the end on what's next for the podcast... SHOW LINKS: - Roger Schwarz on unilateral control: http://www.schwarzassociates.com/managing-performance/how-unilateral-control-undermines-team-results-and-relationships-2/ - Belief bias: https://en.wikipedia.org/wiki/Belief_bias - Emotional reasoning: https://en.wikipedia.org/wiki/Emotional_reasoning *** 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

Why listen to team members and peers when your feelings and behaviours are obviously justified? We continue our how-to series on undermining your agile team with two stories about people who, believing they are clearly correct about how to improve their agile teams, move to shut down communication and manipulate the environment to ensure their approaches are adopted - with, predictably, zero internal commitment from the rest of the team. SHOW LINKS: - Roger Schwarz on unilateral control: http://www.schwarzassociates.com/managing-performance/how-unilateral-control-undermines-team-results-and-relationships-2/ - Jeffrey's "Frustrated? It's Probably Your Fault" session: https://blog.jeffreyfredrick.com/2015/07/18/video-frustrated-it-is-probably-your-fault/ - Model I characteristics: http://infed.org/mobi/chris-argyris-theories-of-action-double-loop-learning-and-organizational-learning/#_Model_I_and *** We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us: see link on troubl