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
I recently took a vacation in Israel. I had a blast, and I took a lot of great pictures. Back before we had digital cameras, I had an analog camera. It was a good camera—not high-end, but good enough for my purposes. But when I took pictures, I was almost always disappointed by the results.
I spoke with a new manager, Drew, the other day. His days are full. He’s got tons of meetings. He tries to provide feedback and coaching to his team members, but he has crises up the wazoo. Drew asked for coaching: “I have way too much to do. I need to learn how to manage
We talk a lot in agile about generalizing specialists. Scott Ambler has a terrific essay on what a generalizing specialist is: Has one or more technical specialties… Has at least a general knowledge of software development. Has at least a general knowledge of the business domain in which they work. Actively seeks to gain new
Way back when I was a developer, my professors taught me structured design and design by contract. Those were supposed to be the silver bullets for programming. You see, if you specified things enough, and structured things enough, everything would all work out. I thought I was the only idiot that structure and specification didn’t
Summary: A new approach to projects or a new tool is not a quick fix or a silver bullet. Too often, you have ingrained, systemic problems that require a cultural change. That doesn’t mean a new approach or a new tool won’t help. It can. But you also need to adjust the environment that caused
In a recent estimation workshop, one of the participants asked, “How do we estimate something we’ve never done before?” “Is it a feature or a project?” I asked. “A feature,” she said. “How do you do things now?” Based on her previous comments in the workshop, I suspected she was pretty good at what she
One of my clients was having trouble with estimating work they had never done before, so I wrote an article explaining spikes. That article is up on agileconnection: Need to Learn More about the Work You’re Doing? Spike It! It was a little serendipity; I taught an estimation workshop right after I explained how to