Alternatives for Agile and Lean Roadmapping: Part 3, Flow-Based Roadmapping

In Part 1, I wrote about thinking in feature sets so everyone could see smaller chunks of work. (If you can see them, you might be able to plan for smaller and deliver smaller.) In Part 2, I suggested smaller rolling waves than an entire quarter (two months, or preferably one month) so people could …

Alternatives for Agile and Lean Roadmapping: Part 2, Rolling Wave Planning Inside One Quarter

In Part 1, I wrote about thinking in feature sets and how to quickly create a feature set of—with any luck—smaller features. That’s because features don’t arrive at the same rate and they change in value, during a quarter. Because features change in value and because some feature sets need to deliver value on a more regular …

Alternatives for Agile and Lean Roadmapping: Part 1, Think in Feature Sets

Many teams and organizations try to create one-quarter roadmaps. Here are the problems I see: Teams spend a ton of time estimating what they might do and then they select what will fit into a quarter. They feel or are asked to commit to all that work. The product managers and project portfolio managers depend on …

Team Size Matters, Reprise

Several years ago, I wrote a post for a different blog called “Why Team Size Matters.” That post is long gone. I explained that the number of communication paths in the team does not increase linearly as the team size increases;  team communication paths square when the team increases linearly. Here is the calculation where N is …

What’s Minimum: Thinking About Minimum Viable Experiments

When I talk about Minimum Viable Products or Minimum Viable Experiments, people often tell me that their minimum is several weeks (or months) long. They can’t possibly release anything without doing a ton of work. I ask them questions, to see if they are talking about a Minimum Indispensable Feature Set or a Minimum Adoptable …