BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Protechtor //NONSGML Events //EN
CALSCALE:GREGORIAN
X-WR-CALNAME:Protechtor: Events
BEGIN:VEVENT
CREATED:20230808T140000Z
UID:3845
DTEND;VALUE=DATE:20230808T130000Z
TRANSP:OPAQUE
SUMMARY:Evolution of a Product Roadmap / Protechtor
DTSTART;VALUE=DATE:20230808T120000Z
DTSTAMP:20230808T140000Z
LOCATION:https://protechtor.io/esemenyek/business/evolution-of-a-product-roadmap
DESCRIPTION:A well-put-together roadmap is an ever-living document that serves as a navigation tool for product companies during product development: it reflects the vision, breaks down the strategy into practical steps, tracks the market, provides ammunition for sales, and builds trust with customers regarding future developments.

A good roadmap often finds its place in the company’s communication toolkit. We can use it as a compass to track the status of the product, in internal and customer communication, but it can also come to the fore when looking for investors.

At the same time, creating a good roadmap is not an easy task: clear strategy, focus, appropriate format, well-circled tasks and of course consensus within the company are required. And what is at least as difficult is not to deviate from everything we have planned on the roadmap during our daily work.

From Balázs Kereskényi’s (the MVP company, IBM Budapest Labs, Ustream) presentation, you can learn:

 	How to get started on creating a roadmap? What formats work? What is good roadmap content?
 	How often should you iterate on the roadmap? Is it worth overturning well-thought-out plans, and if so, how?
 	What level of detail is required for a roadmap in the product lifecycle?
 	When is a roadmap not necessary?
 	How can different stakeholders be aligned with regard to the roadmap?

ORGANIZER:Protechtor
URL;VALUE=URI:https://protechtor.io/esemenyek/business/evolution-of-a-product-roadmap
BEGIN:VALARM
ACTION:DISPLAY
DESCRIPTION:
END:VALARM
END:VEVENT
END:VCALENDAR