You’re about half right, except what you’re referring to is a release plan, not a roadmap. Or at least a very poorly constructed roadmap, and what is but a misconception of what most people think a roadmap is like.

A roadmap, first off, is not a collection of features that are to be released. A roadmap is a communication tool that outlines what problems you are trying to solve and the steps you are going to take to get there. At no point should your roadmap outline delivery dates or time estimates either.

I do agree with you — ditch *this* type of roadmap. It serves absolutely no purpose whatsoever! Go instead for a theme-based roadmaps that focuses around the problems you are trying to solve and provide a high level view and understanding for everyone. This will help communicate your vision and direction to your team, while maintaining transparency with your customers and stakeholders. I wrote about it here: https://medium.com/@dreasaez/how-to-build-a-product-roadmap-everyone-understands-522b36270e5#.76qtzucng