And the tools make them look even more certain. My problem with time-based roadmaps is they look so certain. Product leaders need the flexibility to replan. I also assume that this team releases externally, to customers, at least once a month. That's the same as the feature set below in the flow-based roadmap. So Feature Set 1: MVP 1 might be Secure Login Part 1. If I was the product leader, I would write which feature sets and which problems they solve in each of these various minimum boxes. A Time-Based Roadmap to Focus the Team's Work I'm not a fan of time-based roadmaps, but here's how they work to focus the team. Often, we think about the problems and ask the question, “When?” as in, “When can we see some progress?” That's why many people like time-based roadmaps. Where the team thinks it's going next, even in the very short term. #Visualize product roadmap how to#(These problems might be about how to reduce risk, what the users need first, or an experiment the team needs to learn.) This functionality is based on the problems to solve for now.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |