I continue to work with people who have trouble with their agile approach. They tell me their relative estimation isn’t working for them. They continue to roll over items, from sprint to sprint. They’ve rolled over some items for six months or longer. The people feel demoralized. And the Scrum Masters or agile project managers […]
Several of my clients are trying to do the impossible right now—plan their portfolio for an entire year. Or plan their product backlogs for eighteen months or longer. When I ask them how well that’s worked for them in the past, they often say, “Our planning works great. Our execution? Not so well.” That’s my
Susan, a senior leader, wants faster throughput. She can see people working hard. Yet, all the projects seem to take much longer than anyone expects. They’re doing a lot of the right things. No team is multitasking—the teams work on one project at a time. And the teams manage their inside-the-team WIP (Work in Progress).
Ted Williams said, “If you don’t think too good, don’t think too much.” I’ve got a bad head cold, so I’m not thinking too “good” at all. Here are three not-so-intuitive tips I use all the time, and that you might have missed: Move from “How much” to “How little” thinking. Finish something clean, every
Susan, a senior leader of a 300-person department, wanted to reduce the risks of late deliveries, and respond to customers faster. Susan suspected the managers and teams were too wedded to their plans and not experimenting enough. That meant she needed an agile approach. But while she had been a part of several supposedly agile
I’ve been thinking about flow… In his first week, Tom, a new manager, realizes the four teams he leads and serves are frantically trying to finish their work. Each team feels too much pressure to have one-on-ones with him, in this, his first week. He first checked the project portfolio. Here’s what he discovered: His
Most projects encounter problems at some point, regardless of the size of the team and the people’s capabilities. For example, in a six-person team, TeamA, Tom resigned to follow his wife to her new job. Dick became quite ill and went out on short-term disability for the next three months. And Harry needed significant time
Stan, a prospective client, had trouble making time for our discovery call. (That’s the call where the client and I discuss the boundaries of a consulting engagement.) After he canceled three scheduled calls, I suspected we would not work together. But then he asked me for an evening conversation, after his day’s “craziness.” (His words,
Sid, a senior leader, wants the benefits of an agile transformation. While he doesn’t care about agility per se, he wants the organization to be more effective. His goals: Open new markets for their products. Gain new customers in those markets. Retain more current customers. He suspects that if the teams release faster, the organization can achieve those
Barney, a senior manager, said, “I need everyone to return to the office. I’m okay with what they’re doing, although I miss the buzz of people doing the work. But I don’t know how to build the human connection with them when they’re not here.” I nodded. “You’re always telling me to have empathy with