In Part 1, I said that product roadmaps are not like car roadmaps. But even car roadmaps showed places of interest—options—for the driver and passengers. If I stretch that analogy a little, managers need to see where we are predictable for the next bit of time, and the options we see for the future. We […]
In Part 1, I said that customers need a different kind of roadmap than teams do. Teams need the focusing details now and a way to look forward. But, depending on where your product is in the market, your customers might want or need different information. Let’s start there. One thing to remember: you might
As I said in Part 1, teams use backlogs and roadmaps to know what’s now and what’s next. Teams use backlogs for the day-to-day tactical decisions. And when teams can see what’s next, they can keep the strategic decisions in mind. What do teams need to know about the product now to focus their work?
Several of my clients have various roadmap problems. They want a single product roadmap to serve all these purposes: Focus the team’s work for this specific product for the short term. That includes some look-ahead to see the next bit of upcoming work when the team has more capacity. Show customers where the company thinks
Joanie, a new VP Engineering, joined the company a couple of weeks ago. Her boss, the CEO, wants to know how long it will take engineering to finish all the projects. Joanie asked the various leaders these questions for every project in progress: When did you start this project? Are you still working on this
Many organizations ask teams to forecast when the team can deliver a feature. (Or finish a project.) That request often means the teams spend a ton of time forecasting, not delivering. Instead, what if managers told the team when the managers want to make a decision? The team could deliver enough to help the managers
Several of my clients struggle with their deadlines. One of them, Brad, quoted Douglas Adams to me and frowned: “I love deadlines. I love the whooshing noise they make as they go by.” He thought agile approaches would work to “meet” and “enforce” deadlines. I asked him these questions: Do you think people don’t want
Many managers and teams talk about “average” durations for work. On average, how long does it take a team to finish a certain kind of work? However, average doesn’t quite explain why our work takes different durations. Instead of average, consider the word, “typical.” I’ve written about cycle time before. (It’s the time from when
Three Tips to Move from Certainty to Openness Dan, a senior manager, sees the end of the organization’s traditional business lines. He thinks they have a few good years with their current customers and products. However, he’s sure the company needs to find another way to meet their customers’ needs. And probably, acquire more and
Michael Mahlberg taught me something cool last week. We’re writing an article together. Part of the article is about forecasts. I was ranting and raving about how to help people see their confidence levels. He pointed me to this slideshare: Lightweight Kanban Metrics (in German). (Don’t worry about the language.) Go to slides 24, 25,