Troubleshooting Agile

Squirrel describes two shirts he makes for clients, the How Shirt and the What Shirt, that provide a brief and memorable description of the roles of a technical leader and a product leader respectively, reducing chaos and confusion in agile teams. You may not need job descriptions if four words on a shirt suffice, and as a bonus, the shirts can help your team define what they are doing and how the...

We welcome agile thinker and experienced CTO Chris Parsons, whose blog Delivery Doubled makes the case that cookie-cutter agile approaches don't work. We discuss why out-of-the-box agile training doesn't work, whether we'll have figured out the "right" way to agile a few hundreds of years hence, and how one client discovered that everything Chris was teaching wouldn't work for them and what he and...

Squirrel describes a client of his that is "thrashing"—trying to do so many different things that they aren't getting anything finished. We reflect on why this happens, including the idea that being busy feels good while increasing focus can mean disrupting comfortable routines. We suggest asking "why can't we finish this today?" as a forcing mechanism for discovering bottlenecks and alternative a...

We're joined by Steve Berez, partner at Bain and co-author of Doing Agile Right: Transformation Without Chaos. Steve tells us some stories from his 30-year consulting career, illustrating missteps he's seen in digital transformations like "You Folks Do Agile" and "Agile as a Quick Fix". He advocates the metric of "team fun" as the best way to determine whether you're doing agile right. SHOW LINKS:...

A reader points out that our example conversations often show people masking emotions, but we don't say as much about what to do when someone is being rude or when you yourself feel your emotions are out of control. We suggest ways to increase your sense of safety with an escape plan, but also demonstrate methods for staying in the conversation and learning from it even if it's challenging to do s...

We respond to an article on user stories that has some good points (user stories are prompts for conversations) and, in our view, misses the mark on others (claiming that tasks are better than user stories for technical work). This leads us to propose "human stories" which may not involve traditional users but do involve humans who are affected by the software we're building in some way (partners,...

Clarke Ching has been studying bottlenecks and constraints for thirty years, and has lots of stories and insights for us. He explains why bottlenecks are important, why your developers should always be your bottleneck, and how to explain the theory of constraints using a herd of buffalo. SHOW LINKS: Our Sloan Management Review article: https://sloanreview.mit.edu/article/solving-the-problem-of-sil...

Jeffrey and Squirrel had very different experiences at recent tech conferences including DOES London/Virtual. We describe what worked and what didn't for us, and how listeners can apply the lessons to their own remote attendance at conferences and meetings. SHOW LINKS: Audiobook Companion at IT Revolution site: https://itrevolution.com/agile-conversations Podcasts on remote working and affordances...

Coming to the final chapter of Agile Conversations, we look at how leaders can not only provide accountability for others, but be accountable themselves, including stories from the early days of agile and from today's clients. SHOW LINKS: - XP Explained book: https://www.goodreads.com/book/show/67833.Extreme_Programming_Explained - Rapid Development book: https://www.goodreads.com/book/show/93892....

Moving on to Chapter 6 of Agile Conversations, it's time to talk about commitment. Not engagement, which we argue is insufficient to produce effective results, only enthusiasm that is far too often misdirected out of confusion about what important words mean and how to measure progress. We offer specific tools for effective commitments and hear a story about a company that created a pile of bones...

Although we talk about joint design a lot, we haven't managed to do an episode on it. As we get to chapter 4 in our tour through Agile Conversations, it's time to rectify that! We focus on a common error that we didn't cover in depth in the book: how trying to "convince" someone through advocacy fails. Using the Four Rs, we roleplay an ineffective advocacy-heavy conversation about tech team execut...

We're up to chapter 4 of Agile Conversations: "Fear: The Default Feeling". We look at why defaulting to fear was a successful adaptation for our ancestors and why it serves us poorly now, for example leading to the phenomenon of "greenshifting" that can lead to catastrophic misunderstandings. We explain why starting sentences with the phrase "I'm afraid that..." can help you expose and reduce fear...

We reflect on chapter 3 of Agile Conversations, all about building trust as the first step to a successful agile team. We respond to a reader who had an interesting understanding of the "Test-Driven Development for People" technique and relate the Trust Conversation to vulnerability, exploratory testing, and the painful process of learning. SHOW LINKS: - Previous episodes on trust: - https://sound...

Continuing our tour of our new book Agile Conversations, we come to our chapter on the foundational method for conversational analysis, the Four Rs. We briefly explain the value of conversational analysis, and share our observation that even highly motivated people who know how much it can help their agile teams find it hard to actually pull out a piece of paper and do an analysis. The reasons for...

The first chapter of Agile Conversations is all about people-centred development, and we tell the story of our own journey from over-determined software factory to today's feature factories, with similar Taylorist theories of management in both. In today's episode, we go into more depth on the causes of this tragic journey, touching on old and new topics like Theories X and Y, the Cynefin framewor...

Once again we speak with a fellow author - Mik Kersten. His book Project to Product explains, among many other things, why you shouldn't assign developers to more than one value stream—and what a value stream is, anyway! SHOW LINKS: - Mik Kersten: https://projecttoproduct.org - Project to Product: https://projecttoproduct.org/about-the-book/ - IT Revolution discount on 11 May 2020: https://twitter...

Our book Agile Conversations is nearly out (publication date is 12 May 2020)! We reflect on how we struggled with agile adoption and accountability in our teams and how we learnt to study and improve our conversations to get dramatically better results and internal commitment, eventually leading to us writing Agile Conversations to help spread the word about these techniques. Transcript: https://w...

We reach into the archives for an interview with Matthew Skelton and Manuel Pais, authors of the definitive guide to optimizing software team structures: Team Topologies. SHOW LINKS: - Team Topologies book: https://teamtopologies.com/ - Webinar: https://itrevolution.com/webinar-sign-up/ - One-day discount info on the IT Revolution Twitter feed: https://twitter.com/ITRevBooks/status/125285490221434...

We welcome a guest today - Mark Davis, the Cultural Negotiator. He uses a "cultural intelligence framework" to suggest how one might approach difficult negotiations with customers and team members, in a way that is sensitive to their values and capabilities. SHOW LINKS: - Mark Davis: https://www.linkedin.com/in/theculturalnegotiator/ and https://culturalq.com - Cultural intelligence: https://en.wi...

What we're doing these days is not "remote working"—we have people ill, kids at home, and no option to work from a cafe. But even more than this, most of us haven't put in place alignment and accountability mechanisms, and we're operating on shared understanding from March that is going to expire very soon if it hasn't already. We discuss these and other challenges and briefly point to solutions t...

Switching to remote working means big shifts in the communication patterns of our teams, and the tools we use to do that make some things harder and others easier—they have different "affordances". We explore these differences and suggest strategies for better effective collaboration. SHOW LINKS: - Classic book on affordances: https://en.wikipedia.org/wiki/The_Design_of_Everyday_Things - Concept B...

Active Listening is very useful for normal conversations and meetings, but even more valuable when everyone's remote. We describe the technique, give listeners a chance to practise it, and give refinements like the Active Listening Relay for group discussions. SHOW LINKS: - Xavier Amador and LEAP: http://dramador.com/ and https://www.youtube.com/watch?v=bnbOizw_zS0 - Chris Voss, Never Split the Di...

With a pandemic raging around the world, how can you and your agile team make sense of the world around you and adjust accordingly? The Cynefin framework gives you a way to categorise known and unknown information and figure out how to approach and change your work appropriately. We describe the framework (including how to pronounce Cynefin!) and explain how you might use it to help your agile tea...

When a client tells Squirrel "of course there are no releases on Fridays", it's a red rag to a bull. After Squirrel rants for a bit, he calms down and we argue strongly for releasing often, even when it hurts—in fact particularly when it's difficult!—to "bring the pain forward" (Jez Humble). SHOW LINKS: - Jez Humble on doing painful things more often: https://continuousdelivery.com/ - Dr. David Bu...

Following up from last week, we propose some ways to become emotionally aware, which we argue again is a key skill for success in an agile team. We suggest enriching your feeling vocabulary, self-distancing through disciplined recording of your conversations, and using check-in methods to spread the practise across your team. SHOW LINKS: - Center for Nonviolent Communication Feelings Inventory: ht...