Join 📚 Felicity's Weekly Book Highlights
A batch of the best highlights from what Felicity's read, .
At the end of the day, roadmaps are a communication tool. To figure out which ones are right for your company, think about your audience and what they need to know: Product development teams: These are generally highly detailed, require commitments from engineering by quarter, discovery and delivery status, and are usually a quarter in length. Sales teams: Sales teams need fewer details. They need bigger-picture items that address problems and rough timeline on releases (either quarterly or half year). This is where the narrative/value proposition for each feature to customers is important to include as well. Leadership: These roadmaps focus on the “initiative to strategic intent” layer. They’re used to talking about dependencies and capacity planning, and follow quarterly timelines.
Product Operations
Melissa Perri and Denise Tilles
And as agile methods have become mainstream, organizations around the world are trying to find solutions to making agile scale. This is because, as North indicates, agile is essentially a “team-scale” method of working, and large organizations need a system to coordinate the work of many teams.
Sense and Respond
Jeff Gothelf, Josh Seiden
However, if it's the first time they have worked on this problem, then they will likely need some time to learn the space, start collecting some data to establish a baseline, and get a sense of what the possibilities are. In this case, encourage the team to jump in and not get stuck in paralysis by analysis, and acknowledge with them that they will learn much more as they progress, and that the confidence level will, of course, be low in this first quarter because they are still learning what they don't know.
Empowered
Marty Cagan and Chris Jones
...catch up on these, and many more highlights
Readwise