This series is about helping a team create a less brittle environment—more resilience. Part 1 was about individual work. This part is about shortening feedback loops. Brief description of the problem at a recent client: Person A checked in code that broke an “unrelated” part of the system. I’ll call this checking in code in […]
I’ve been working with clients who have brittle environments. Their brittleness doesn’t show up all the time. When everything is good, they’re able to finish work and deliver. But, someone checks in code that breaks something “over there.” Or, someone gets pulled off to work on production support issues and is no longer available to
I wrote about how I felt about milestones after achieving a significant milestone last week (How Do You Feel When You Achieve a Significant Milestone?) I specifically wrote about my feelings. During a discussion on LinkedIn, a reader suggested I start with the last sentence I wanted to leave my readers with. Then build back
I’m a monthly contributor to the Gurock blog. This month’s article is Feedback & Feedforward for Continuous Improvement: Using Double-Loop Learning Challenges Our Assumptions. Single-loop learning is when you “Plan the work and work the plan.” Double-loop learning is when you challenge assumptions during the project. Agile approaches allow us to do so. This is the
One of the things I like about agile is the fact that it encourages me to learn. I wish I were perfect, able to learn things as soon as I try them. However, I am all too human. It takes me time to learn. I just upgraded one of my text-processing programs, and now about
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. You’ve considered who you need as allies and how to enlist them
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. You’ve considered who you need as allies and how to enlist them
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You’ve started to measure possibilities. You have an idea of who you might talk with as in Becoming an Agile Leader, Part 2: Who to Approach. Now, how do you create allies so you can unwedge
To summarize: your agile transformation is stuck. You’ve thought about your why, as in Becoming an Agile Leader, Part 1: Define Your Why. You have some idea for measurements. Maybe you’ve even started to measure to capture the data. Now, it’s time to talk to people across the organization. The question is this: Who do you talk
What does it mean to be an agile leader? Here’s what I’ve seen work: The leader recognizes a problem the organization needs to solve. There may be many problems, and the leader extricates one to start. The leader explores options with the people involved. Often, the leader asks this question, “What is the smallest change