Podcasts about product vision board

Als Product Owner ist es essenziell, sich kontinuierlich weiterzuentwickeln und die richtigen Werkzeuge für die tägliche Arbeit zu nutzen. In der neuesten Episode der Produktwerker geht es genau darum: Welche Methoden für Product Owner sind wirklich relevant? Eine der wichtigsten Grundlagen ist die Produktvision. Hier hilft das Product Vision Canvas bzw. das Product Vision Board (von Roman Pichler), um ein gemeinsames Verständnis im Team und mit Stakeholdern zu schaffen. Ob mit dem Framework von Roman Pichler oder dem Positioning Statement von Geoffrey Moore – entscheidend ist, dass die Produktvision klar und lebendig bleibt. Eng verknüpft mit der Produktvision ist das Thema Roadmapping. Klassische, feature-getriebene Roadmaps sind längst überholt. Stattdessen setzen erfahrene Product Owner auf Outcome-orientierte Roadmaps, etwa in Form der Now-Next-Later-Roadmap. Dabei geht es nicht darum, starre Zeitpläne einzuhalten, sondern den Fokus auf die gewünschten Wirkungen zu legen. Für eine sinnvolle Planung ist außerdem Story Mapping unverzichtbar. Diese Methode hilft, eine holistische Sicht auf das Produkt zu behalten, Features sinnvoll zu priorisieren und das Team in die richtige Richtung zu steuern. Jeff Patton hat mit dem User Story Mapping eine Praxis entwickelt, die das Verständnis für Wirkungsschnitte und Priorisierung stärkt. Ein weiteres wertvolles Tool im Werkzeugkasten eines Product Owners ist der Opportunity Solution Tree (OST), bekannt aus Teresa Torres' Buch Continuous Discovery Habits. Der OST ermöglicht es, Business-Ziele mit Kundenbedürfnissen zu verknüpfen und den besten Weg zur Lösung abzuleiten. Etwas älter, aber genauso wirksam ist das Impact Mapping von Gojko Adzic – ein strukturierter Ansatz, um zu visualisieren, welche Akteure ihr Verhalten ändern müssen, damit das Produkt erfolgreich wird. In der täglichen Arbeit von Product Ownern spielen Annahmen eine große Rolle. Doch oft sind diese weder hinterfragt noch belegt. Hier kommt das Assumption Mapping ins Spiel. Mit dieser Methode von David J. Bland lassen sich Annahmen systematisch priorisieren und durch gezielte Experimente validieren. Auch das Arbeiten mit User-Feedback gehört zu den essenziellen Methoden für Product Owner. Hier hilft der Interview-Snapshot aus Teresa Torres' Discovery-Ansatz, um strukturierte Erkenntnisse aus Nutzerinterviews zu ziehen. In Kombination mit dem Value Proposition Canvas von Alexander Osterwalder lassen sich die relevanten Pain Points und Gains der Nutzer noch klarer herausarbeiten. Natürlich darf auch das Thema User Stories nicht fehlen. Diese Technik ermöglicht eine nutzerzentrierte Formulierung von Anforderungen. Doch User Stories sind nur so gut wie ihre Akzeptanzkriterien und die Fähigkeit, sie sinnvoll zu schneiden. Deshalb ist es entscheidend, nicht nur das Schreiben, sondern auch das Splitting von User Stories zu beherrschen. Ein weiterer Bereich, der oft unterschätzt wird, ist das Stakeholder-Management. Ohne eine gezielte Strategie kann die Vielzahl an Stakeholdern schnell zur Herausforderung werden. Das Power-Interest-Grid hilft dabei, die richtigen Prioritäten zu setzen und Stakeholder effektiv einzubinden. Daneben sehen wir noch eine elfte Methode, quasi als "Bonus-Thema", das in den letzten Jahren immer wichtiger wird: AI-Prompting. Die Fähigkeit, mit Tools wie ChatGPT oder Perplexity effizient zu arbeiten, kann für Product Owner einen enormen Vorteil bringen – sei es für die Generierung von Ideen, die Analyse von Feedback oder die Strukturierung von Informationen. AI wird zunehmend zum Wingman für Product Owner und sollte daher als fester Bestandteil des Methodensets verstanden werden. Diese zehn Methoden für Product Owner sind nicht nur theoretische Konzepte, sondern praxisbewährte Werkzeuge, die den Alltag eines POs erleichtern und das Produktmanagement auf ein neues Level heben. Welche dieser Methoden setzt du bereits ein? Und welche fehlt deiner Meinung nach in dieser Liste?

Product discovery has become increasingly popular in recent years as a way to determine the right solution. In this podcast episode, I explain why you need a product strategy to succeed with product discovery, how the strategy helps you determine the right outcomes and opportunities, and how you can use the Product Vision Board to build an Opportunity Solution Tree.

Roman Pichler is a leading product management expert specialized in product strategy, leadership, and agility. He has advised product leaders and he has taught product managers and product owners for more than 15 years. Roman has pioneered agile product management practices, and he has developed a range of models, methods, and tools to help organizations create successful products. Roman shares his knowledge through his training courses, his four books, his popular blog, podcast, and talks, and his product management tools, including his widely used Product Vision Board. In this episode of the Product Science Podcast, we cover agile and product transformations, what's wrong with the focus on features, and saying no. Read the show notes to learn more: www.h2rproductscience.com/post/the-roman-pichler-hypothesis-establishing-an-effective-agile-product-management-organization-takes-time

Roman Pichler joins Brian to talk about Product Roadmaps. Overview Product roadmaps help teams plan their everyday work and how their products will change over a year. But then, products evolve, and new data is collected and shared. Companies must then decide how to adapt and progress. So, how can we then create a product roadmap? Roman Pichler is an internationally renowned product management expert specializing in product strategy, leadership, and agility. Today on the show, Roman joins Brian to discuss how to create helpful product roadmaps that create value for the end users in a Scrum based context to move forward and simplify product management. Listen now to discover: [00:06] - Brian introduces Roman Pichler, one of his 'agile heroes. [00:35] - Brian shares about the book Strategise, 2nd Edition. [02:54] - Roman answers the question, "What is a Product Roadmap?" [03:58] - Roman explains if product roadmaps are helpful in an agile Scrum based context. [05:31] - Roman discusses using outcome-based goal-oriented roadmaps to determine a company's product value. [07:33] - Roman shares some examples of goals on a product roadmap. [08:12] - Why a goal-oriented based roadmap is all about outcomes. [09:35] - Brian shares insight into Roman's downloadable Go Product Roadmap. [10:07] - Roman shares how the latest version of the Scrum guide fits in with protocols, product goals, and outcome-based roadmaps. [11:54] - Why Roman adds time frame constraints into his product end goals. [14:41] - Roman shares the two things you need to succeed with collaborative product road mapping in an agile space. [16:40] - Roman explains how to incorporate time frame constraints into your roadmap. [19:40] - The difference between an internal and external product roadmap for public consumption. [21:11] - The importance of an impact analysis when determining whether to stick with a specific delivery date or fully meeting a goal. [25:00] - How to get precise estimates for your team. [26:15] - Roman shares his 'sweet spot' for making outcome-based investment decisions. [28:40] - Roman advises setting dates on (internal) roadmaps for contract-based environments. [29:06] - Roman shares Apple's trade-off decision when they launched the original iPhone in 2007. [31:40] - How to use goals to track the most valuable metrics. [34:41] - The importance of understanding the needs of the stakeholders. [35:19] - Roman shares the importance of balancing expectations with empathy for improved collaboration. [39:12] - Brian shares a funny story about the difference in polite communication between Americans and our friends on the other side of the pond. [40:46] - Roman shares why you shouldn't relinquish product road mapping in an agile space too soon. Listen next time when we'll be discussing… Agile and education with John Miller. References and resources mentioned in the show Roman Pichler Strategise Go Product Roadmap Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Roman Pilcher is a leading product management expert specializing in product strategy, leadership, and agility. He has advised product leaders and taught product managers and owners for over 15 years, pioneering agile product management practices. Roman shares his knowledge through his training courses, books, and podcast. You can find his popular Product Vision Board and Go Product Roadmap on his website.

Roman Pichler joins Brian to talk about Product Roadmaps. Overview Product roadmaps help teams plan their everyday work and how their products will change over a year. But then, products evolve, and new data is collected and shared. Companies must then decide how to adapt and progress. So, how can we then create a product roadmap? Roman Pichler is an internationally renowned product management expert specializing in product strategy, leadership, and agility. Today on the show, Roman joins Brian to discuss how to create helpful product roadmaps that create value for the end users in a Scrum based context to move forward and simplify product management. Listen now to discover: [00:06] - Brian introduces Roman Pichler, one of his 'agile heroes. [00:35] - Brian shares about the book Strategise, 2nd Edition. [02:54] - Roman answers the question, "What is a Product Roadmap?" [03:58] - Roman explains if product roadmaps are helpful in an agile Scrum based context. [05:31] - Roman discusses using outcome-based goal-oriented roadmaps to determine a company's product value. [07:33] - Roman shares some examples of goals on a product roadmap. [08:12] - Why a goal-oriented based roadmap is all about outcomes. [09:35] - Brian shares insight into Roman's downloadable Go Product Roadmap. [10:07] - Roman shares how the latest version of the Scrum guide fits in with protocols, product goals, and outcome-based roadmaps. [11:54] - Why Roman adds time frame constraints into his product end goals. [14:41] - Roman shares the two things you need to succeed with collaborative product road mapping in an agile space. [16:40] - Roman explains how to incorporate time frame constraints into your roadmap. [19:40] - The difference between an internal and external product roadmap for public consumption. [21:11] - The importance of an impact analysis when determining whether to stick with a specific delivery date or fully meeting a goal. [25:00] - How to get precise estimates for your team. [26:15] - Roman shares his 'sweet spot' for making outcome-based investment decisions. [28:40] - Roman advises setting dates on (internal) roadmaps for contract-based environments. [29:06] - Roman shares Apple's trade-off decision when they launched the original iPhone in 2007. [31:40] - How to use goals to track the most valuable metrics. [34:41] - The importance of understanding the needs of the stakeholders. [35:19] - Roman shares the importance of balancing expectations with empathy for improved collaboration. [39:12] - Brian shares a funny story about the difference in polite communication between Americans and our friends on the other side of the pond. [40:46] - Roman shares why you shouldn't relinquish product road mapping in an agile space too soon. Listen next time when we'll be discussing… Agile and education with John Miller. References and resources mentioned in the show Roman Pichler Strategise Go Product Roadmap Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. Got an agile subject you'd like us to discuss or a question that needs an answer? Please share your thoughts with us at podcast@mountaingoatsoftware.com This episode's presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He's passionate about making a difference in people's day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Roman Pilcher is a leading product management expert specializing in product strategy, leadership, and agility. He has advised product leaders and taught product managers and owners for over 15 years, pioneering agile product management practices. Roman shares his knowledge through his training courses, books, and podcast. You can find his popular Product Vision Board and Go Product Roadmap on his website.

The product vision can be a powerful tool to align stakeholders and development teams. When used effectively, it acts as the product's true north, and it inspires and guides people. This episode helps you create such a vision. It describes six essential qualities that a compelling product vision has to have.

Our ultimate goal as product people is to achieve sustained product success: to ensure that our products do a great job for their users and customers and that they generate value for our businesses on a continued basis. While achieving product success cannot be reduced to a simple formula, there are four factors that have a profound impact on it, as I discuss in this podcast episode.

Agilibrium - le balado pour les agilistes qui souhaitent bonifier leurs pratiques.S01E02 - Fiche de produitDans cet épisode Nous sautons dans l'action pour commencer à créer notre vision de produit, vision qui sera le pilier de notre stratégie de valorisation. Nous travaillerons ensemble à identifier les bénéficiaires de notre produit, à comprendre leurs enjeux et à nous situer en tant qu'équipe de produit par rapport à ces informations. 00:40 - La fiche de produit à 4 colonnes: QUI, QUOI, POURQUOI et COMMENT01:47 - Qui sont les bénéficiaires de notre produit et trois modèles de distribution de produit08:06 - Quels bénéfices souhaitent retirer nos utilisateurs de notre produit 13:40 - Quoi lire cette semaine - Simon Sinek, Start With Why14:47 - Pourquoi les personas identifiés recherchent-ils les avantages ou les bénéfices à utiliser notre produit16:52 - Précisions sur le mode Push17:58 - Utilisation de données pour remplir notre fiche de produits18:58 - Les raisons qui font de notre produit une meilleure alternative aux yeux des personas identifiés20:42 - Comment notre produit peut répondre aux besoins identifiés24:49 - ConclusionNotesRoman Pichler's Product Vision Board https://www.romanpichler.com/tools/product-vision-board/ À proposJe suis Denis St-Michel, passionné d'agilité depuis 2006. Je possède les certifications PAL, PSM II et PSPO II de scrum.org. Je rends les équipes hautement performantes et j'accrois la valeur des produits numériques.Musique originale "Folle", une création personnelle que vous pouvez retrouver sur mon album "Underscore", disponible sur Spotify et Apple Music. Spotify https://open.spotify.com/album/4sfnhseocnThIDf9hOFDUn?si=rVBt3wb7TmSj79bubv8W7ARejoignez-moi Sur LinkedIn - https://linkedin.com/in/dstmichel Par courriel - stmichel.denis@gmail.com  

The product vision board is a simple yet powerful tool to capture the product vision and the product strategy. Despite its simplicity, effectively using it can be challenging. I have seen many boards over the years that suffered from a number of shortcomings including a poorly defined target group, an unconvincing value proposition, and business goals that weren’t measurable. This article helps you recognise and rectify common product vision board mistakes, thereby maximising the chances of creating an inspiring vision and a winning product strategy.

Aujourd'hui, découvrons le parcours d'Estelle Landry, Product Owner chez Pix. Allier les contraintes business, utilisateur et technique au sein d'une même vision, la vision produit, c'est son métier. Diplômée de l'école d'ingénieur, Polytech Montpellier en 2013, elle est d'abord passée par les cases développeuse, puis assistante maîtrise d'ouvrage, cheffe de projet informatique. Son projet professionnel a bien évolué troquant alors son IDE pour un Product Vision Board. Estelle a de l'énergie à revendre, et s'engage activement en promouvant la prise de parole des femmes dans le milieu en qualité d'organisatrice de nombreux événements tech (Sunnytech, Flupa, Meetups…). Découvrez son parcours inspirant, riche en enseignements ! Découvrez notre formation fullstack JS RebootJS sur http://flint.sh/fr/academy ! 

Die Produktvision beschreibt eine Zukunft, die durch das eigene Produkt erreicht werden soll. Für Product Owner ist sie ein hilfreiches Instrument und wichtige Entscheidungen können von ihr abgeleitet werden. Wo und wie eine Produktvision hilft, aber auch welche Methoden zur Erarbeitung möglich sind, darüber haben Oliver, Dominique und Tim miteinander diskutiert. Wir freuen uns über Euer Feedback auf produktwerker.de, per Mail an podcast@produktwerker.de oder via Twitter an @produktwerker.

  I don’t really dare to introduce Roman. He is such a big name in Agile Product Management. Since his beginnings in Scrum, he was totally focused: Scrum it will be, Product it will be - and everything that belongs to it. No more, no less. Clarity. In the field of Agile Product Management, he is really known for his great Scrum Product Owner courses, but also his books. His latest book is called Strategize and is all about product strategy. Unlike with many other books on strategy, what Roman accomplishes with his book, is to get the topic out of the vague. He gives clear cut advice in an otherwise often blurry topic. Knowing Roman for many years, it actually took me until this interview to actually decode one of his main qualities: Calm and certainty. Roman, in the best sense, gives you the clarity and certainty you expect from a teacher. While many teachers may bring you to the brink of doubt, Roman in a very calm, distinct and respectful way tells you what he found out to be the core of any topic he writes about. He really helps you to accept this things and go on with them. While I sometimes struggle and have to tell the world about all the different aspects of a topic, Roman already did all the thinking and came to a conclusion. And that helps. He does not leave out the rest of the truth, he just helps you to focus on the core and makes it easy to take the next step in your journey. I guess, it also has to do with his experience: he seen them all and has been in many contexts. He is running his brand as a business since 2006 and was amongst the first Certified Scrum Trainers in Europe. He really was amongst the pioneers and saw the potential when nothing was yet clear. He also writes a prominent blog on his website. These days, his focus is on leadership and product portfolio topics. It is also the topic of his newest blog posts on his blog. The Interview During the podcast we go through the following topics: What is a product strategy? Ways to work on product strategy in the context of new products Working on existing, mature products How to work with Roadmaps What was the writing process for Srrategize? What’s next from Roman? Citations Here some citations from the conversation: "The main challenge initially really is to get to a launch": On why focus and a minimal good enough product is needed in the beginning. "What good enough means, what minimal means, depends very much on the innovation we’re dealing with." "There is a correlation between the amount of time we spend on something and the level of attachment that results": On why it is psychologically so hard to change plans, even though we know it is necessary. "Two aspects are important: Do we have the right skills? And: are people empowered to do the product strategy work?" Often times, senior management is doing the product strategy work, which limits the strength and growth of the company. Management should do the business strategy and let the product department do the product strategy.“ Links  The home of Roman’s company  Roman's blog Roman’s LinkedIn Profile Lots of tools and resources that Roman invented and provides for free, e.g. the Product Vision Board template, a template for goal oriented GO Roadmaps, his Product Management Framework (a structured approach to ordering the disciplines and capabilities involved in product work) and much much more! Strategize - Roman’s latest book, self published in 2016. Buy it! Read it!  Agile Product Management with Scrum - Roman’s 2nd book, published with Addison Wesley in its Mike Cohn Signature Series, a German version is also available - Scrum: Agiles Projektmanagement erfolgreich einsetzen, published with d.punkt Oh, if you like the music in the background, it is my first try at doing the music myself.

In unserer ersten Folge sprechen wir über das Phänomen "Flying Dutchman Scrum": wenn ein Team ständig vor sich her entwickelt, nie aber ein konkretes Ziel zu erreichen scheint. Oder aber, wenn auf dem Weg zum Ziel alle paar Sprints der Fokus wechselt und man das große Ziel aus den Augen verliert - vielleicht aber auch gar keines hat. In diesem Kontext stellen wir das ProdPad Product Vision Template vor, schauen kurz auf das Product Vision Board von Roman Pichler, erklären den Unterschied zwischen Produktvision und Mission Statement und reden kurz über den Business Model Canvas und den Value Proposition Canvas. In den Picks: Dominik stellt den lesenswerten Artikel "So, how do you make Agile successful" von Chen Ping vor, Sebastian erklärt, wie ihr mit haveibeenpwnd.com herausfindet, ob eure Zugangsdaten in irgendeinem Datenleak auftauchen. Alle Shownotes und Links zur Sendung finden sich auf http://meinscrumistkaputt.de/folge-1-flying-dutchman-scrum/

A estratégia de produto descreve como o objetivo de longo prazo será atingindo, inclui a proposta de valor do projeto, mercado, as funcionalidades-chave e as metas de negócio. O Roadmap do produto mostra como a estratégia do produto será colocada em prática através de RELEASES específicas com datas, metas e funcionalidades. Visão: A razão para criar o produto. (ex: ajudar as pessoas viverem com mais saúde) Estratégia: Como a visão vai ser realizada (ex: monitorar consumo de calorias). Roadmap: Como a estratégia vai ser implementada. Backlog: Detalhes para desenvolvimento do produto de acordo com o Roadmap. A estratégia do seu produto vai mudar ao longo do tempo, a media que o mercado muda, e seu produto amadurece, por isso deve ser constantemente revisada. A estratégia do produto deve estar alinhada a estratégia da organização. Baixe o seu Product Vision Board em http://www.romanpichler.com/tools/vis... Aprenda mais lendo o livro "Strategize: Product Strategy and Product Roadmap Practices for the Digital Age (English Edition)” http://amzn.to/2aug9f7 Receba as novidades em seu e-mail: ✩ http://blog.andrefaria.com/vip Assine o podcast: ✩ Youtube http://andrefaria.com/youtube ✩ iTunes http://andrefaria.com/itunes ✩ Android http://andrefaria.com/android ✩ SoundCloud http://andrefaria.com/soundcloud Encontre-me nas redes sociais: ✩ Blog http://blog.andrefaria.com ✩ LinkedIn http://andrefaria.com/linkedin ✩ Twitter http://twitter.com/andrefaria ✩ Facebook http://andrefaria.com/facebook ✩ Instagram http://instagram.com/andrefaria ✩ Slideshare http://slideshare.com/andrefaria ✩ Snapchat http://andrefaria.com/snapchat ✩ About.me http://about.me/andrefaria