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
Maybe your team does have Ready criteria for their backlog. But they look at the backlog item, and they say, “Oh, this is way too big. We have no idea how to start.” That “no idea” often means the work is too large, unclear, or not based on a specific customer with a specific need.
Does your team feel as if they can’t really start when they take an item off the backlog? The team says the item feels too big. Or the team realizes they need someone else from some other team to solve this problem. Worse, the team needs to decompose the item more to make sure they
As far as I can tell, all organizations have the appetite for more work than they have people or time to do that work. It does not matter if the organization is one person or thousands. We all want to accomplish more than we have people. That’s why we need a product vision to drive
I started this series by saying a team can create a useful project charter in less time than you think. So what prevents teams from doing so? Too often, the project is not ready. The team might be ready, but the project is not. In effect, the project starts with scarcity. (I used to think
Do you use schedule or tracking tools to predict the future? None of them can predict the future. Worse, too many of them hide the past, especially the recent past. A schedule or tracking tool can only predict one thing: the first possible date you cannot prove you cannot finish the project/story by. Let me
So far, I’ve addressed how a project charter can help a team start a project fast and well. That’s why the project charter must clarify product vision, the various project risks, and product risks. And, it’s equally important to know what done means. If the team does not know how little they can do to