Please respond to this below. How would this work in a practical setting. Need to see the connection via example or experience. Not a long answer though.

The Product Roadmap is a document that "is a strategic product-planning tool that outlines the vision, direction, priorities, and growth in the long term, say, a year." It is meant to be a precursor to obtaining funding for the project and promote healthy collaboration between the team and stakeholders. In terms of succession, the Product Roadmap comes first to give the team and stakeholders "the strategy, vision and direction" required to begin the project.As for the Product Backlog, it is a document that is comprised of a list of necessary tasks that need to be completed in order to provide the customer with a quality product and for the overall project to be considered successful. It is a follow up document to the Product Roadmap, and gives depth and detail by outlining specifics in each task needed to complete the project.

Seeing that the Roadmap is the overall vision of the project and the Backlog is the supporting details of what's to come in short and long term facets, having one without the other poses a several issues. Without a Backlog, just providing the Roadmap gives the stakeholders and team a vague understanding of how the project will be accomplish. Essentially like drawing a stick figure without giving the details necessary to determine if it's a boy or a girl. On the other end of the spectrum, without the Roadmap, the team and stakeholders have no inclination of how tasks will be divvied up and where the process should be at a specific points. It becomes evident that to produce a successful project, the Product Roadmap and the Backlog, need to work cohesively.