I said earlier in this series that no one cares about how “agile” your team is. Or the kind of “agile” your team professess to be. Managers do care about agility: the ability to respond quickly to a changing or changed environment. And that depends on where your team has delays. That’s why value stream […]
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. In Part 2, I discussed cooperative teams that have working agreements on when to do code review or make other decisions as a team. While those teams exhibit somewhat more agility, cooperative teams are still not collaborative. So
In Part 1, I wrote about what the value stream map looked like for expert-focused “cross-functional” teams. While those teams are cross-functional, they are not collaborative. However, these expertise-focused “teams” are not the only type of non-collaborative agile teams. There are also cooperative teams. Cooperative teams still tend to work sequentially, focused on each person’s
We talk about cross-functional agile “teams” as if they are the norm. That’s what I show in this image: some responsible person creates a ranked backlog that the cross-functional, collaborative team works on. That team delivers increments of value on a regular basis. At some point, the team will demo their work and retrospect on
Let’s assume that your team does have a definition of Ready. And that they (possibly with a product leader) have shaped the work. But the team still says they don’t know how to start—they don’t have the right people to think through the problem and finish it. If you have component teams, the team is
If your company is similar to my clients, they want agility. That agility will allow their organizations to learn and deliver faster. That has all kinds of wonderful effects, such as capitalizing software earlier. But, too few teams have enough access to real product leadership, where a single product leader can make all the various
This is Johanna Rothman’s January 2026 Pragmatic Manager newsletter. The unsubscribe link is at the bottom of this email. Many managers think they empower their teams to solve problems autonomously. Unfortunately, that autonomy only lasts when managers feel relaxed enough to “allow” that autonomy. When managers feel too much pressure, that autonomy vanishes. Under pressure,
So far, this series has focused on smaller efforts, such as one or two products or one or two teams. But what if you have a larger effort, where several teams need to collaborate to deliver the business value? That’s a program. (I wrote Agile and Lean Program Management: Scaling Collaboration Across the Organization to
This is Johanna Rothman’s December 2025 Pragmatic Manager newsletter. The Unsubscribe link is at the bottom of this email. In the first part of inviting culture change, I wrote about Stephanie, a senior leader who wants more organizational agility. She’s used the flow metrics to invite that culture change. So far, she’s succeeded with the
I started this series bemoaning the fact that we have too few product managers. That leads to no product leaders for a team. Worse, some teams have either strategic product thinkers or tactical thinkers—but not both. Instead, we can consider several possible product value teams to prevent insufficient product leadership. I already discussed the Vertical