Troubleshooting Agile

We start our conversation with Ryan Singer, Head of Strategy at Basecamp, by asking him to help us understand how their Shape Up process works and how they developed it. He explains how the fear of not shipping drove their movement to frequent delivery of carefully designed (or "shaped") features, why their teams avoid single-page apps to ensure designers can make the maximum contribution, and why...

Squirrel adds to last week's story, describing how being transparent and curious helped him uncover a conflict that helped lead to insight and better alternatives. SHOW LINKS: - The HiPPO effect: https://www.forbes.com/sites/bernardmarr/2017/10/26/data-driven-decision-making-beware-of-the-hippo-effect/ - The Uncanny Valley of a Functional Organization: https://stratechery.com/2013/the-uncanny-vall...

Squirrel tells a story in which digging for emotional signals helps a technical team find alternatives to an arbitrary-looking initiative. Jeffrey explains how nonviolent communication provides a framework for seeking emotional understanding first. SHOW LINKS: - Nonviolent communication: https://www.cnvc.org - Feelings inventory: https://www.cnvc.org/training/resource/feelings-inventory - Kano mod...

We saw last week how inflexible implementation killed checklists at hospitals - and the same disease affects agile development, we've found. Do you think there's a single "recipe" for agile, like our friends at Basecamp who claim they're not agile because they don't use post-its, backlogs, or standups? If so, we think you're missing some important opportunities for building internal commitment and...

Troubleshooting Checklists Checklists are a great way to capture learning in any organisation, but sometimes they don't work - why not? A recent study of hospitals with varying levels of success in adopting checklists helps us reflect on similar adoption challenges for agile methods. SHOW LINKS: - Checklist article from Nature: https://www.nature.com/news/hospital-checklists-are-meant-to-save-live...

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...

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...

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...

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...

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....

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 seri...

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: htt...

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 actio...

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 - NT...

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:...

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/ind...

After the Mutual Learning and Unilateral Control models, this week we examine one more model for working with your team, perhaps the easiest: giving up! This one feels the best, since everyone is involved and gets to express his or her feelings. But unsurprisingly, giving up control means you give up valuable information that could help you make a better decision. SHOW LINKS: - Giving Up Control a...

After our series on mutual learning values, we look at those of an alternative, the Unilateral Control Model, which match our default behaviour but don't normally lead to the type of learning your team is probably looking for. We look at why convincing others usually doesn't work and welcome Al Pacino for a brief cameo. SHOW LINKS: - Unilateral Control article by Roger Schwarz: http://www.schwarza...

Third in our series on using the Mutual Learning Model to improve your agile team. We look at accountability as a frightening prospect and as a route to ease at work (thanks Kent Beck). Then we consider how you might benefit from compassion - not only for your team and stakeholders, but also for leaders and for yourself. SHOW LINKS: - 8 Behaviours for Smarter Teams: https://www.csu.edu.au/__data/a...

Agile teams do better, we find, when they are transparent ("here's what I did last sprint") and curious ("what business problem are you trying to solve?"). Most people we meet claim they are both transparent and curious in their conversations and processes - but usually their actual behaviour when there's something at stake is very different. We introduce a 2x2 matrix that can help you measure whe...

First of a series on using the Mutual Learning Model to get better results in your agile team. Today, why informed choice can help us avoid mistakes as minor as missing a requirement or as major as launching a rocket with a fatal flaw. SHOW LINKS: - The Five Dysfunctions of a Team: https://en.wikipedia.org/wiki/The_Five_Dysfunctions_of_a_Team - 8 Behaviours for Smarter Teams: https://www.csu.edu.a...

When your team talks about "what the business wants", do they know who they mean? Do they have evidence for the wishes of this amorphous group? It's impossible to negotiate with an undefined entity, but we offer some not-too-surprising ideas for making progress and discovering the real needs of "the business". SHOW LINKS: - XP Explained: https://www.amazon.co.uk/Extreme-Programming-Explained-Embra...

Triggers and Tells We explain how to use observations of your own and others' behaviour to understand how to improve your conversations and get better agile results! SHOW LINKS: - Previous episode on learning from observations: https://soundcloud.com/troubleshootingagile/learning-through-case-studies-the-4-rs - Previous episode on "why" as a trigger: https://soundcloud.com/troubleshootingagile/why...

In response to Michael Bolton's comment on last week's episode, we discuss genuine questions, reminding yourself to be curious, and converting your internal "why" to a more constructive question. SHOW LINKS: - Tweets from Michael Bolton and Brian Deyo: https://twitter.com/michaelbolton/status/1111083757971345413 and https://twitter.com/briandeyo/status/1111252749658869760 - Chris Voss, Never Split...

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://dav...