Rejoice product owners – the days of dual entry for your roadmaps are gone! No longer will you need to remember to update the roadmap when the ‘real’ plan changes. No longer will you be called out in meetings when your roadmap is out of date. No longer will stakeholders silently wonder if what they are seeing is current and you erode confidence. We’ve heard about the pains you’ve shared with us and have responded.
In the Summer 2016 Release, Roadmaps in VersionOne Lifecycle are now consolidated and driven by the very portfolio items that you naturally use for your planning. You have two views that you can use to visualize the plans – board view that shows the planned end dates for items and a timeline view that shows the duration of planned work.
Board views are great for stakeholders and customers: they focus on what is planned for delivery. The timeframes are, of course, configurable to address both the level of the roadmap being displayed and the realistic planning horizon. For a young product in a dynamic market, for example, you may want to use a six-month roadmap with general goals rather than specific features. For a mature product in a stable industry, on the other hand, might be better suited to a two-year roadmap with more specific features listed.
Timelines are perfect for internal development teams to see the big picture of what is planned to be worked on when. This helps to point out when the plan looks a little too optimistic, or where gaps in the schedule can allow items to be started earlier.
Notice the graph at the bottom of the timeline view. It shows the capacity needs based on the plans, so it’s a good idea to check versus your organization’s higher level velocity. See any spikes or dips in there? That’s a problem. A nice smooth line consistent with what’s been delivered in the past gives you a level of comfort that your plans seem reasonable.
With VersionOne Roadmaps, you can see either view and it all comes from the same underlying portfolio item data. You can configure your roadmaps to show the right level of detail (e.g. Epics, Capabilities, or Features), and the right timeframe for your organization. You can organize your roadmap into appropriate groups (Strategic Themes are perfect for grouping), and even use color coding (Legend provided at no extra charge) to help communicate the plans.
Increasing flexibility and communication were two big goals for the enhanced Roadmaps. Give them a try and you’ll see just how easy it is to use Roadmaps. If you have more suggestions, please keep them coming via IdeaSpace.VersionOne.com.