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
A senior manager said, “We give our resources everything they could need: technology, tools, even some training. Why are they so slow?” I asked, “How many projects are they working on?” “Each resource has at least two projects so they stay productive and efficient.” These managers have created a resource efficiency culture, not a flow
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?
Before the pandemic, Jenny, the VP of Engineering, insisted that the engineering staff needed to work in the Boston area. She expected that people would mostly work in the office, and they did. However, during the pandemic, Jenny changed her mind. She said that as long as teams had sufficient hours of overlap, she didn’t
We often think that finishing a story from the backlog is “just” tactical. However, the more often we deliver in short feedback loops, the more often we can make strategic decisions. Finishing a story creates a new decision point, for both the product and the corporate strategy. The more often we iterate strategically, the more
Dan, a VP, knows he needs more people to get the work done. Suzanne, one of the directors, starts to hire and realizes she has several problems. First, their salary bands are too low—candidates want more money. In addition, the people want to collaborate more than the existing people seem to. She meets with Dan
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
Acme, a software company, has a technical excellence problem. Its customers report more problems than the product teams do. Two managers, Cindy and David, want to bring specialized training in for product teams. (They want to help their teams learn to use Test-Driven Development, TDD, and Acceptance Test-Driven Development, ATDD. Cindy and David suspect that
The larger your product, the more likely you have components teams. I often see component teams because of the architecture of the product. In this first image, the Integrated System Program, the rest of the product uses the Platform of Common Services as components. Also, the teams find it tempting to think of the common