Podcast appearances and mentions of Roman Pichler

Global Agile Summit Preview: Unifying Strategy, Discovery, and Delivery in Product Development With Roman Pichler In this BONUS Global Agile Summit preview episode, we explore a crucial topic that's shaping how we approach product development—sometimes in ways that serve us well and sometimes in ways that hold us back.  There's a growing trend in our industry to explicitly separate strategy, discovery, and delivery into distinct activities or even different teams. On the surface, this seems logical: strategy decides the right thing to do, discovery figures out how to do it, and delivery gets it done. But is this division actually helping us? Or is it creating barriers that make great product development harder? The Origins of Product Discovery "I think it's partly based, at least on Marty Cagan's work, and his insight that many teams are very much focused traditionally on delivering outputs, on writing code. And I think his original intention was to say, 'Let's not worry about creating outputs. Let's also make sure that what we creating makes sense.'" Roman Pichler shares insights on how the concept of product discovery emerged as a reaction to teams being overly focused on outputs rather than outcomes. He explains that conceptually distinguishing between product strategy, discovery, and delivery can be helpful—much like organizing clothes into different sections of a wardrobe. However, in reality, these activities must be connected, informing and guiding each other rather than existing as sequential steps. The Risks of Separating Product Strategy, from Discovery, and from Delivery "If we have a group of people who takes care of strategic decisions, a different group focusing on product discovery, and another group—the tech team—who focuses on product delivery, and those groups don't talk as much as they could and should do, then suddenly we have a sequential process and handoffs." One of the primary challenges with separating strategy, discovery, and delivery is the risk of creating handoffs between different teams. Roman highlights how this sequential approach can slow down value creation, lead to knowledge loss, and increase the likelihood of introducing mistakes. This separation can create barriers that ultimately make product development more difficult and less effective. In this segment, we refer to the podcast interview with Tim Herbig on the concept of Lateral Leadership, and how that is critical for product people. Integrating the Work Streams "What I usually use as a visualization tool is three work streams: a strategy work stream, a discovery work stream, and a delivery work stream. The strategy stream guides the discovery stream. The discovery stream guides the delivery stream, and then the delivery stream informs the discovery stream, and the discovery stream informs the strategy stream." Rather than seeing strategy, discovery, and delivery as separate phases, Roman suggests visualizing them as parallel work streams that continuously inform and guide each other.  This approach recognizes that strategy work doesn't just happen at the beginning—it continues throughout the product lifecycle, adapting as the product evolves. By integrating these work streams and ensuring they're interconnected through feedback loops, teams can create a more cohesive and effective product development process. The Power of Collaboration "The important thing is to make sure that the different areas of work are not disjointed but interlinked. A key element to make that work is to use collaboration and teamwork and ensure that there aren't any handoffs, or avoid handoffs as much as possible." Collaboration and teamwork are essential to successfully integrating strategy, discovery, and delivery. Roman emphasizes the importance of bringing product people—who understand customer needs, business models, and stakeholder relationships—together with tech teams to foster innovation and create value. This collaborative approach helps overcome the challenges that arise from treating these activities as separate, sequential steps. Building an Extended Product Team "Form a big product team, a product team that is empowered to make strategic decisions and consists not only of the person in charge of the product and maybe a UX designer and a software developer, but also key business stakeholders, maybe somebody from marketing, maybe somebody from sales, maybe a support team member." Roman advocates for forming an extended product team that includes not just product managers, designers, and developers, but also key business stakeholders. This larger team can collectively own the product strategy and have holistic ownership of the product—not just focusing on discovery or delivery. By empowering this extended team to make strategic decisions together, organizations can ensure that different perspectives and expertise inform the product development process. Practical Implementation: Bringing it all Together "Have regular meetings. A specific recommendation that I like to make is to have quarterly strategy workshops as a rule of thumb, where the current product strategy is reviewed and adjusted, but also the current product roadmap is reviewed and adapted." Implementing this integrated approach requires practical mechanisms for collaboration. Roman recommends holding quarterly strategy workshops to review and adjust the product strategy and roadmap, ensuring they stay in sync with insights from development work. Additionally, he suggests that members of the extended product team should attend monthly operational meetings, such as sprint reviews, to maintain a complete understanding of what's happening with the product at both strategic and tactical levels. Moving Beyond Sequential Thinking "Unfortunately, our software industry has a tendency to make things structured, linear, and assign ownership of different phases to different people. This usually leads to bigger problems like missing information, problems discovered too late that affect 'strategy', but need to be addressed in 'delivery'." One of the challenges in adopting a more integrated approach is overcoming the industry's tendency toward linear, sequential thinking. Roman and Vasco discuss how this mindset can lead to issues being discovered too late in the process, after strategic decisions have already been made. By embracing a more iterative, interconnected approach, teams can address problems more effectively and adapt their strategy based on insights from discovery and delivery. About Roman Pichler Roman Pichler is a leading product management expert specializing in product strategy, leadership, and agility. With nearly 20 years of experience, he has coached product managers, authored four books, and developed popular frameworks. He shares insights through his blog, podcast, and YouTube channel and speaks at major industry conferences worldwide. You can link with Roman Pichler on LinkedIn and check out the resources on Roman Pichler's website.

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?

If communicating with stakeholders on a regular basis is part of your work and you're looking to improve your stakeholder management skills, this is your podcast. We promise you'll learn practical strategies for effective stakeholder management that you can start using TODAY - or your money back!!!Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as we use the Power-Interest grid to layout an actionable framework for communicating with different stakeholder groups. #ProductManagement #StakeholderCommunication #AgileLeadershipReferences:Stakeholder Management Tips for Product People by Roman Pichler, 2020: https://www.romanpichler.com/blog/stakeholder-management-tips-for-product-people/Getting Stakeholder Engagement Right by Roman Pichler, 2015: https://www.romanpichler.com/blog/stakeholder-engagement-analysis-power-interest-grid/Making Strategy, The Journey of Strategic Management by Colin Eden & Fran Ackermann, 1998Arguing Agile #198 - Better Communication: Mastering Crucial Conversations: https://youtu.be/KgmnrkbNA8I= = = = = = = = = = = =YouTube= = = = = = = = = = = =Subscribe on YouTube:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Applehttps://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotifyhttps://open.spotify.com/show/362QvYORmtZRKAeTAE57v3= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode of Rocketship.FM, host Mike Belsito dives into the common mistakes product managers and leaders make when developing product strategies. Featuring expert insights from Roman Pichler, a renowned product management coach and author, the episode uncovers critical pitfalls to avoid and best practices to embrace in crafting effective product strategies. From the importance of aligning with overall business goals to the necessity of evidence-based decision-making, Roman shares his wealth of experience to guide listeners through the intricacies of product strategy development. This episode is a must-listen for product professionals looking to refine their strategic approach, foster collaboration across teams, and create product strategies that drive success in today's fast-paced digital landscape. This episode is sponsored by: Virtual Edition of INDUSTRY: The Product Conference: Join hundreds of Product Managers and Product Leaders from all around the world for a day-long virtual conference experience -- including keynote sessions, interactive discussions, virtual networking and more. Purchase your pass before September 15th, and you can register for just $99 (saving 50% off of the day of show rate). Wix Studio: Designed for agencies, freelancers and enterprises, Wix Studio lets professional web designers and developers unleash their creativity—faster and better than ever. You can create high-end sites at scale while harnessing the robust infrastructure and business solutions that already come with Wix.  Rocketship.FM is brought to you by Evergreen Podcasts.

Outcome-based product roadmaps offer many benefits over traditional, feature-based ones including a strong focus on the value a product should create. But how can you introduce this new approach when an organisation is used to feature-based plans and stakeholders find it difficult to trust an outcome-based roadmap? To address this challenge, I introduce a four-step process in this article. https://romanpichler.medium.com/how-to-get-started-with-outcome-based-product-roadmaps-68f30098175a How to connect with AgileDad: - [website] https://www.agiledad.com/ - [instagram] https://www.instagram.com/agile_coach/ - [facebook] https://www.facebook.com/RealAgileDad/ - [Linkedin] https://www.linkedin.com/in/leehenson/

The success of any organization, especially in the digital product world, hinges on its ability to strategize effectively. Yet, the concept of strategy remains ambiguous to many. What exactly do we mean by "product strategy," and how can we harness it to achieve our goals?In this episode, Hannah Clark is joined by Roman Pichler to delve deep into the intricacies of product strategy.

Onboarding New Product ManagersIn this episode of Arguing Agile, hosts Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel dive into the challenges and best practices around onboarding new product managers. Topics include:Communicating the company vision, mission and goals Mapping key players, stakeholders and decision-making processesAligning the new PM's goals to organizational objectivesBuilding and owning the product roadmap Understanding customers, segmentation and building empathyThe importance of mentorship and coaching for new PMsWhether you're a product leader looking to optimize your onboarding or a new PM wanting to hit the ground running, this episode provides actionable tips to set up PMs for success from day one!Roman Pichler's Stakeholder Management Article referenced in the podcast:https://www.romanpichler.com/blog/stakeholder-management-tips-for-product-people/= = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Roman Pichler and Tom talk about business strategy, portfolio strategy, product strategy, and how it relates to the roadmap and backlog.

Product strategy is the guiding light that illuminates the path to success for any product. However, articulating and executing this strategy is often easier said than done, says product management expert Roman Pichler. In this episode of Product Momentum, Roman shares valuable insights into the essence of product strategy and how to effectively navigate its … The post 130 / Discovering the Essence of Product Strategy, with Roman Pichler appeared first on ITX Corp..

Embark on a captivating journey through the Agile Mentors Podcast in 2023 with Brian Milner. Explore a spectrum of Agile topics, from Scrum Master challenges to leadership insights. Join Brian for insightful summaries, memorable moments, and a walk through the rich tapestry of Agile wisdom on the show. Overview In this episode of the Agile Mentors Podcast, Brian embarks on a retrospective journey through the standout moments of the podcast in 2023. Explore carefully curated episodes, offering solutions to the common challenges and then delving into the world of Agile beyond software development. Listen in as Brian shares insightful summaries featuring memorable moments and a diverse landscape of Agile wisdom shared by his esteemed guests. Categorized into topics like Scrum Masters, Product Owners, Developers, Agile’s use beyond software, general career advice, and leadership and coaching, this retrospective is a treasure trove of practical advice, actionable insights, and real-world experiences. Tune in for an inspiring tour through the rich tapestry of the Agile Mentors Podcast 2023 episodes. Listen Now to Discover: [01:16] - Brian introduces the episode and invites listeners to join him in a retrospective of the year's episodes, highlighting ones that may have been missed or are hidden gems worth revisiting, which he will group by listener preferences and areas of interest. [02:39] - For Scrum Masters: Brian begins discussing the first episodes tailored for Scrum Masters, kicking things off with #47, "Exploring Lean Thinking and Agile Development," featuring guest Bob Payne, who shares insights into lean thinking, a foundational principle in agile development. Brian recommends this episode for Scrum Masters aiming to enhance their understanding of Agile's fundamentals. [03:34] - Episode #52, "The Birth of Agile: How 17 Adventurous Techies Changed the World," features Agile icon Mr. Jim Highsmith, one of the authors of the Agile Manifesto. Jim provides a glimpse into the past and offers insights into the future of Agile. [04:06] - Episode #59, "Revising the Scrum Guide," features Don McGreal, who played a key role in the guide's revision, shedding light on the thinking behind the revisions. [05:31] - In Episode #62, "Effective Sprint Goals," Maarten Dalmijn delves into effective crafting techniques and the finer details of achieving success with Sprint Goals. [06:12] - In Episode #69, "Should Scrum Masters Be Technical with Allison Pollard," Allison and Brian explore the question of whether Scrum Masters should possess technical skills. If you grapple with how technical a Scrum Master should be, this episode provides valuable insights and perspectives. [06:51] - In Episode #39, Mike Cohn, an authority on user stories, shares valuable insights into the art of crafting effective user stories. [07:15] - In Episode #65 with Randy Hale titled "Unlocking Lean Portfolio Management," Brian and Randy explore the concept of moving beyond a single-team focus as a product owner, delving into the realm of lean portfolio management building upon insights shared by Bob in episode #47. [07:50] - For Product Owners: Must listen bonus from last year, Episode #22, with Roman Pichler, who shares his insights on "How to Create Helpful Product Roadmaps," addressing challenges commonly faced by product owners in dealing with the nuanced aspects of their role. The episode covers strategies to avoid pitfalls, especially the dangers of rigidly locking into scope and schedule timelines. [08:54] - For Developers: Episode #33, "Mob Programming with Woody Zuill," introduces developers to the transformative practice of mob programming. Woody Zuill, a pioneer in this way of working, shares insights and a practical and thoughtful approach that makes it worth exploring. [10:00] - In Episode #48, Brian hosts a unique episode featuring the renowned Lisa Crispin and Janet Gregory, experts in Agile testing, in a show called "Holistic Agile Testing." This episode is particularly recommended for developers specializing in testing or involved in testing within a Scrum team. [11:00] - In Episode #54, "Unlocking Agile's Power in the World of Data Science," Brian and Lance Dacy explore the intersection of Agile methodologies and data science. The popularity of this episode prompted a sequel, Episode #63, on the fusion of Agile and data science. [11:58] - In the final developer-focused episode, Carlos Nunez joins Brian to delve into the world of DevOps. Carlos, a speaker at Agile 2023, shares insights on the significance of DevOps in today's Agile landscape, emphasizing DevOps as a means of empowerment rather than gatekeeping. [12:38] - Agile Outside of Software: Episode #32 with Cort Sharp focuses on Scrum in High School Sports—specifically high school swimming. Cort shares his experience applying Scrum principles to create practice schedules and routines for the swim team he coaches, providing valuable insights for those interested in using Agile beyond the software realm. [13:24] - In #38: "Using Agile for Social and Societal Transformation with Kubair Shirazee," Kubair walks listeners through how his nonprofit employs Agile methodologies to empower micro-entrepreneurs in developing countries. The episode highlights success stories, such as a barber's journey from a rented spot to owning a professional store, demonstrating Agile's transformative impact beyond the tech industry. [14:40] - Episode #45 with Scott Dunn explores "Overcoming Agile Challenges in Regulatory Environments." This crucial topic addresses the unique challenges faced in tightly regulated sectors like government, legal, and medical professions, offering a compelling dialogue on navigating regulatory hurdles within an agile framework. [16:00] - Episode #64 features John Grant discussing "How Agile Methodologies Reshape Legal Practices." This episode reveals the transformative impact of Agile in the legal profession and offers a unique perspective on Agile as a philosophy rather than just a practice, illustrating its broader applicability beyond the software realm. [17:00] - Today's episode is brought to you by Mountain Goat Software's Certified Scrum Product Owner (CSPO) course. This is a two-day training course taught by one of our certified Scrum trainers that teaches you how to use the product backlog as a tool for project success and how to respond to changes in business conditions by restructuring the product backlog. For the schedule, visit the Mountain Goat Training Schedule. [17:27] - General Career Advice: #34: "I'm Trained, Now What? with Julie Chickering" addresses the post-training phase for Scrum Masters and Product Owners. Julie shares insights on taking the next steps, implementing knowledge, and finding opportunities to build a resume in Agile roles. [18:29] - In #40: "Is it Time to Go Out on Your Own? Tips and Insights with Chris Li" Brian and Chris Li discuss considerations for those at later stages of their careers contemplating the transition to independent consulting. If you're pondering whether it's time to establish your consultancy, this episode provides valuable insights and considerations to guide your decision-making process. [19:00] - In #42: "The Importance of Self-Mastery with Bob Galen," Bob emphasizes the value of constant learning, even after years of experience, highlighting the importance of staying open to new discoveries and others' experiences. This episode serves as a compelling guide for personal growth and continuous improvement. [20:28] - Episode #46 with Christina Ambers: In this episode, Christina shares insights on "How to Assess Company Culture Before Accepting a Job Offer." As the year closes and people consider new job opportunities, Christina guides listeners through the crucial step of evaluating company culture and the importance of understanding if a company truly embraces Agile values or merely pays lip service to them. [21:14] - Episode #50 celebrated the milestone of the 50th episode. Lance Dacy was on the show to discuss "Choosing Your Path: Exploring the Roles of Scrum Master and Product Owner." The episode offers guidance for individuals at crossroads, helping them decide between Scrum Master and Product Owner roles. It serves as a valuable resource for those navigating career decisions in the Agile landscape. [22:13] - Leadership and Coaching: In the Leadership and Coaching category, Episode #37 features Brad Swanson discussing "Servant Leadership, Not Spineless Leadership." Brad dispels misconceptions and offers valuable insights into the essence of servant leadership, making it a compelling resource for those interested in effective leadership approaches. [23:28] - In Episode 41, Karim Harbott explores "Cultural Transformations in Organizations." The episode delves into the challenges of changing organizational culture, emphasizing the time and effort required beyond implementing specific practices. [24:00] - In "#44: Transformations Take People with Anu Smalley", Anu highlights the often-overlooked aspect of involving people in organizational transformations, shedding light on the human dynamics that can either support or hinder the process. [24:35] - In Episode #53, "Debunking Myths in Agile Coaching with Lucy O'Keefe," we tackle the common myths surrounding Agile coaching and provide insights on unlocking excellence in Agile coaching practices. [25:01] - Episode #66 is a solo episode where Brian shares his insights into navigating team conflicts, laying the foundation for understanding and mastering the essential skill of conflict navigation. [26:00] - In Episode #68, Brian hosts Mike Hall for a discussion of "The Pros and Cons and Real-World Applications of SAFe." Whether you're new to SAFe or deeply involved, Mike's expertise provides valuable perspectives and tips for navigating this framework. [26:42] - In Episode #70, Mike Cohn joins Brian to explore "The Role of a Leader in Agile." Here, Mike shares valuable insights based on his extensive experience, offering sound advice and perspective on the crucial role of leaders in self-organizing teams. [28:10] - Brian encourages listeners, especially newcomers, to explore relevant episodes based on their roles, with the goal being to offer practical advice and solutions on specific issues rather than lengthy discussions. All episodes are available in the show notes for convenient access. [29:33] - Brian expresses gratitude to listeners for the past year, reflecting on the unique nature of podcasting and letting listeners know he cherishes the encouragement and connections made, especially at events like Agile 2023. [31:00] - What do you want to hear in 2024? What are some of the hot-button topics that haven’t been covered on the show or guests you want to hear from? Send Brian an email with your ideas. [32:28] - And don’t forget to share and subscribe to the Agile Mentors Podcast on Apple Podcasts so you never miss an episode. [33:00] - We also have our Agile Mentors Community, where we have discussions about every podcast [33:24] - Wishing you a Happy Holiday Season! We'll see you early again in 2024. References and resources mentioned in the show: #47: Exploring Lean Thinking in Agile Development with Bob Payne #52: The Birth of Agile: How 17 Adventurous Techies Changed the World with Jim Highsmith #59: Revising the Scrum Guide with Don McGreal #62: Effective Sprint Goals with Maarten Dalmijn #69: Should Scrum Masters Be Technical with Allison Pollard #39: The Art of Writing User Stories with Mike Cohn #65: Unlocking Lean Portfolio Management with Randy Hale #22: How to Create Helpful Product Roadmaps with Roman Pichler #33 Mob Programming with Woody Zuill #48: Holistic Agile Testing with Lisa Crispin and Janet Gregory #54 Unlocking Agile's Power in the World of Data Science #63: The Interplay Between Data Science and Agile with Lance Dacy #71: The World of DevOps with Carlos Nunez #32: Scrum in High School Sports with Cort Sharp #38: Using Agile for Social and Societal Transformation with Kubair Shirazee #45: Overcoming the Challenges of Agile in Regulatory Environments with Scott Dunn #64: How Agile Methodologies are Reshaping Legal Practices with John Grant #34: I'm Trained, Now What? with Julie Chickering #40: Is it Time to Go Out on Your Own? Tips and Insights with Chris Li #42: The Importance of Self-Mastery with Bob Galen #46: How to Assess Company Culture Before Accepting a Job Offer with Christina Ambers #50: Choosing Your Path: Exploring the Roles of Scrum Master and Product Owner with Lance Dacy #37: Servant Leadership, Not Spineless Leadership with Brad Swanson #41: Cultural Transformation in Organizations with Karim Harbott #53: Agile Coaching: Debunking Myths and Unlocking Excellence with Lucy O'Keefe #66: Successful Strategies for Navigating Team Conflicts #68: The Pros and Cons and Real World Applications of SAFe with Mike Hall #70: The Role of a Leader in Agile with Mike Cohn #49: Celebrating One Year: A Look Back at 50 Episodes of the Agile Mentor Podcast Certified Scrum Master Training and Scrum Certification Certified Scrum Product Owner Training Advanced Certified ScrumMaster® Advanced Certified Scrum Product Owner® Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast on Apple Podcasts 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? 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.

Eine Frage, die immer wieder aufkommt, ist die nach dem notwendigen technischen Wissen, dass man in der Verantwortung als Product Owner braucht. Dominique und Tim stellen sich in dieser Folge diese Frage und teilen ihre Erfahrungen sowie ihre Einschätzung dazu. Dazu muss man sich zuerst fragen, warum die Frage nach dem technischen Verständnis eigentlich aufkommt. Das kann einerseits an dem zugang zur Verantwortung als Product Owner liegen. Wenn man vorher in verwandten Rollen wie beispielswerise Business Analyst, oder Softwareentwickler gearbeitet hat, bringt man fast schon natürlich ein technisches Verständnis mit. Das könnte zumindest ein Grund sein, warum viele Product Owner bereits ein solches Verständnis haben und dadurch die Erwartungshaltung ihres Umfeldes entsprechend prägen. Ob das technische Verständnis aber immer hilft ist auch fraglich. Immerhin hat das Team in ihrer Domäne Expertenwissen und so manch ein Product Owner kann nicht aus der eigenen Haut und will mitmischen. Am Ende geht es aber in erster Linie darum, dass die Menschen, die zusammen versuchen ein erfolgreiches Produkt zu entwicklen miteinander sprechen können. Sie müssen sich gegenseitig verstehen. Daher ist ein sehr grundsätzliches technisches Verständnis durchaus hilfreich. Es mus snicht umfangreich sein und ein Informatikstudium ist garantiert zu viel des Guten. Wir haben in dieser Folge auf folgende Folgen verwiesen: - Stellenausschreibungen für Product Owner (https://produktwerker.de/product-owner-stellenausschreibungen/) - Vom Entwickler zum Product Owner (https://produktwerker.de/vom-entwickler-zum-produkt-owner/) - Wie No-Code Tools Produktteams helfen (https://produktwerker.de/no-code-tools/) Darüber hinaus haben wir folgende Quellen genutzt: - Six types of a “product” owners von Roman Pichler (https://www.romanpichler.com/blog/six-types-of-product-owners/) - The Product Trio von Teresa Torres (https://www.producttalk.org/2021/05/product-trio/) - Code it! (Coding Courses for Kids) (https://code-it-studio.de/) Diese Folge ist unsere Antwort auf eine Frage aus der Community. Wenn auch ihr eine Frage habt, die wir in einer Folge unbedingt mal beantworten sollten, lasst es uns gerne wissen. Schickt dazu gerne eine Mail an feedback@produktwerker.de. Wir freuen uns auf eure Fragen!

Join Brian as he rediscovers and relives the most captivating topics, memorable guests, and impactful topics from the first year of the “Agile Mentors” podcast. Overview From deep dives into Agile methodologies and practical tips for using your knowledge to benefit others and foster change, the first 50 episodes of the “Agile Mentor” podcast have been filled with fascinating topics and memorable guests. In this episode, Brian Milner embarks on a retrospective journey through the inaugural year of the show. Listen in as he shares the real stars of the podcast, the moments that surprised him, those that took him out of his comfort zone, and the ones that inspired him to push to be better every day! Plus, what’s next for the show. Listen Now to Discover: [00:45] - Brian introduces the retrospective episode to celebrate one year and 50 episodes of the "Agile Mentors" podcast and share what's next. [01:54] - A thank you for YOUR role in the show. [02:17] - The role of marrying the right topic to the right guest. [02:56] - The format that allows listeners to choose the episodes that interest them the most. [04:03] - Pointing you toward the best of the best. Our first several episodes were focused on the Agile Framework and some core topics, including having Mike Cohn on to talk about the different roles and generally accepted practices. [05:13] - Sending out thanks to a few of our guests, including the trainers at Mountain Goat Software, including Lance Dacy. [05:45] - Kert Peterson joined us to share his knowledge, and Scott Dunn shared his insight from the product owner's perspective. [06:05] - On episode 16, Mitch Lacey joined us to discuss The Hidden Secret Ingredient And Julie Chickering brought a great perspective from a project management background and applying that to some of the stuff we've discussed here on the show. [06:39] - The time when one of my mentors joined us on the show to discuss transformation. [07:08] - Learning about coaching and marketing from the best! [07:27] - Roman Pitchler joined us to discuss product roadmaps and planning things from a product owner perspective. And John Miller shared about using Scrum in the education environment. [07:46] - On EP25, Henrik Nieberg came on and talked to us about scaling, and on EP27, Tricia Broderick walked us through leadership without blame. [08:18] - How Scrum can be applied outside of software development and mob programming. [08:42] - The key to working with humans. [09:03] - The episode that surprised Brian a little bit. [09:34] - Three episodes all about change: The first one was about how one organization uses Scrum to help impoverished micro-entrepreneurs succeed (and change their lives). The second featured Chris Li sharing his insight on how to know when it’s time to strike out on your own, and Karim Harbott walked us through the difficulty of transforming an organization's culture. [10:25] - The episode that inspired Brian to try to push in different ways to get better. And how to cultivate an Agile culture in a virtual world. [10:53] - Why transformations take people, how to assess a company’s culture before you accept their job offer, and lean thinking in Agile with Bob Payne. [11:49] - The real stars of the podcast. [12:30] - What’s ahead for the podcast? [13:02] - Stepping off the gas a bit. [13:45] - Virtual dial—targeted tips. [14:32] - The lifeblood of the “Agile Mentors” podcast. [15:06] - Mike Cohn and Brian are both presenting at Agile2023 in Orlando, July 24 through 28th. [15:39] - The most significant benefit of BIG conferences. [16:41] - Thank you for getting us to a year and 50 episodes! Join the Agile Mentors Community to continue the discussion. If you have topics for future episodes, email us by clicking here. And don’t forget to subscribe to the “Agile Mentors” Podcast on Apple Podcasts so you never miss an episode. References and resources mentioned in the show: Agile2023 | Orlando, Florida | Agile Alliance #1: Scrum vs Agile & Keys to Success with Mike Cohn #3: What Makes a Great Product Owner? With Lance Dacy #9: Scrum Artifacts with Kert Peterson #10: Why User Stories are the Best Way to Capture Requirements with Mike Cohn #17: Getting There From Here: Agile Transformations with David Hawks #18 Coaching in an Agile World with Lyssa Adkins #21: Agile Marketing Teams with Stacey Ackerman #22: How to Create Helpful Product Roadmaps with Roman Pichler #23 How Agile Works in Education with John Miller #25: Scaling with Henrik Kniberg #27: Leading Without Blame with Tricia Broderick #29: Influencing Up with Scott Dunn #32: Scrum in High School Sports with Cort Sharp #33 Mob Programming with Woody Zuill #34: I'm Trained, Now What? with Julie Chickering #37: Servant Leadership, Not Spineless Leadership with Brad Swanson #38: Using Agile for Social and Societal Transformation with Kubair Shirazee #40: Is it Time to Go Out on Your Own? Tips and Insights with Chris Li #41: Cultural Transformation in Organizations with Karim Harbott #42: The Importance of Self-Mastery with Bob Galen #43: Cultivating Agile Team Culture in a Virtual World with Richard Cheng #44: Transformations Take People with Anu Smalley #46: How to Assess Company Culture Before Accepting a Job Offer with Christina Ambers #47: Exploring Lean Thinking in Agile Development with Bob Payne Mountain Good Software's Certified Product Owner course Mountain Goat Software Certified Scrum and Agile Training Schedule Join the Agile Mentors Community Subscribe to the Agile Mentors Podcast on Apple Podcasts 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? 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.

In the previous episode (here: https://youtu.be/T1doj980NuE) we explored the things that need to be in-place before a great Product Roadmap can be built. In this episode, we use those concepts to create a Mission, Vision, Strategies, and Goals for our organization and product, the Arguing Agile Podcast!#productmanagement #agile #career 0:00 Topic: Crafting a Mission, Vision, & Strategy1:13 The Existing Mission/Vision2:20 Crafting the Vision4:08 Going One Step Deeper5:56 The Original Mission7:09 Working on the Mission9:26 Roman Pichler's Product Vision Board10:22 Assumption-Based Vision/Mission11:39 Forming a Coherent Mission13:30 Completing Mission16:06 Kernel of a Good Strategy18:19 Sidebar: Strategy in the Real-World20:09 How This All Fits21:22 Strategy #122:23 Saying No23:50 Continuing Strategies and Separating Goals27:19 Identifying Redundant & Missing Strategies29:18 Now, the Roadmap31:08 We Probably Should Have Cut This Section31:29 Wrap-up32:43 Another (Unnecessary) Wrap-Up----------------------Watch us on YouTube: https://youtu.be/RFXd3rqzprASubscribe to the Arguing Agile Podcast: https://www.youtube.com/@arguingagile/featuredOr listen on: Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Google Podcasts:https://podcasts.google.com/feed/aHR0cHM6Ly9mZWVkcy5idXp6c3Byb3V0LmNvbS8xNzgxMzE5LnJzcwSpotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-PodcastStitcher:https://www.stitcher.com/show/agile-podcast-2----------------------AA104 - Creating a Mission, Vision, & Strategy

Join Murray Robinson and Shane Gibson as they discuss the fundamentals of product management with Roman Pichler, author of agile product management with scrum. What is a product manager? What is a product? What's the difference between a product and a project? What's the difference between a product owner and a product manager? How do you know what to build? How do you develop a product strategy? How do you develop a product roadmap and define sprint goals? Focusing on objectives, not lists of features. Focus on one goal at a time. Time box product goals to maximize value for money. Don't be an order taker. And how to do continuous discovery while delivering. Listen to the podcast on your favourite podcast app: | Spotify | Apple Podcasts | Google Podcasts | iHeart Radio | PlayerFM | Amazon Music | Listen Notes | TuneIn | Audible | Podchaser |  Connect with Roman on LinkedIn or at www.romanpichler.com Contact Murray via email or Shane on LinkedIn shagility.   The No Nonsense Agile Podcast is sponsored by: Simply Magical Data

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

The Great Product Owner: The key to an awesome Agile team, the hands-on and insightful Product Owner Tinatin highlights the key traits of a good Product Owner (PO) in this segment. She emphasizes that great PO's are knowledgeable about the product they are working on, as well as its competitors. This knowledge helps the PO to understand what the team needs in order to deliver the best possible product. The PO should be hands-on with the team, and should work closely with them on defining clear acceptance criteria. This helps the team to understand what is expected of them and enables the PO to be more effective in their role. Tinatin also notes that a great PO is easy to work with and has a good synergy with the team. She mentions that the synergy between the PO and the team is a telling factor in the team's success. She stresses that there's not only one way to be a great PO, as different PO's can have different approaches to the role, but when a PO combines knowledge about the product and its competitors with a hands-on approach to working with the team, the result is an awesome PO. The Bad Product Owner: Unleashing the Full Potential of a Product Owner in partnership with the Scrum Master In this segment, Tinatin starts by questioning the essence of the PO role and highlights the importance of commitment and ownership of the product for a team's success. Tinatin emphasizes that a PO should have a clear vision and evolve it based on data and feedback. She stresses the need for a PO to have a foot in both development and business and to be hands-on with the product. As a Scrum Master, Tinatin suggests testing the product and making time to play with it to help the PO understand it better. She also suggests sitting down with the PO to build a roadmap for the product and to ask why they value certain features or deliveries. Lastly, Tinatin highlights the importance of the PO being able to sell the ideas in the backlog to the Scrum team and recommends using tools to help the PO take a more active role with the team. Tinatin also mentions the books by Roman Pichler as resources for Scrum Masters and Product Owners. Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate. About Tinatin Tabidze Tinatin Tabidze is a Scrum Master currently working in Stuttgart, Germany. Originally she started out as a project manager. She has experience with multiple scrum and kanban teams, working with scaled agile frameworks. You can link with Tinatin Tabidze on LinkedIn. 

Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. Tinatin discusses the importance of the scrum values in a team and how well the team is living those values. She highlights the importance of team health checks to identify inefficiencies, which can often result from a lack of collaboration and trust between team members. Tinatin uses the example of the Spotify Squad health check (mentioned several times here on the podcast) that reveals a lack of trust between developers and testers, and offers tips for identifying a lack of trust in a team, such as monitoring levels of comfort among team members, monitoring communication, and observing meetings for signs of discomfort or silence. Featured Book Of The Week: Scrum: The Art of Doing Twice the Work in Half the Time by Sutherland In Scrum: The Art of Doing Twice the Work in Half the Time by Sutherland, the author describes how to optimize work through Agile methodology and Scrum principles. In this episode, Tinatin also refers to Scaling Lean and Agile Development by Craig Larman, and Bas Vodde. Bas Vodde has been a previous guest on the podcast. And she also refers to Strategize: Product Strategy and Product Roadmap Practices for the Digital Age by Roman Pichler.    [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!   About Tinatin Tabidze Tinatin Tabidze is a Scrum Master currently working in Stuttgart, Germany. Originally she started out as a project manager. She has experience with multiple scrum and kanban teams, working with scaled agile frameworks. You can link with Tinatin Tabidze on LinkedIn. 

Julie Chickering sits down with Brian to share the best gift books for the Scrum masters in your life. Overview We all have those books on our bookshelves that we’ve had for years and still refer back to time and time again, or that new title that we’ve just read that blows our mind with the way it makes a new concept more relatable. Julie Chickering is a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), and a traditional Project Management Professional (PMP). Today on the show, Julie joins Brian to discuss the most valuable books they’ve read, the lessons they’ve learned from them, and the best ones for giving to the Scrum Master in your life this holiday season. Listen now to discover: [01:06] - Today, Brian and Julie Chickering will be sharing the most valuable books we’ve read. [02:10] - Julie shares how a book called Two Beats Ahead is helping her learn to let go of her creations. [04:00] - Julie shares an interesting story of how Beyoncé invited musicians in for collaboration and how that opened her mind to learning from her community. [05:07] - Brian shares why Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larson is his #1 book recommendation for Scrum Masters. [06:29] - Julie shares why she’s also a fan of Agile Retrospectives: Making Good Teams Great for the mix-and-mash recipe for creating menu selections. [08:06] - Julie shares why The Culture Code: The Secrets of Highly Successful Groups insight into the three main things that make high-performing teams high-performing is her favorite book to give to the leaders on her list. [10:36] - Brian shares the three things from Daniel Pink’s Drive: The Surprising Truth About What Motivates Us that align with Scrum. [12:34] - Julie shares how she learned to flip the script, start with the hard topics in a conversation, and finish with the positive from Daniel Pink, as included in his book, When: The Scientific Secrets of Perfect Timing. [15:53] - Brian shares why Dan Pink’s books are most enjoyable via audio. [16:15] - Julie shares how a podcast interview with author Scott Sonenshein led her to his book called Stretch: Unlock the Power of Less -and Achieve More Than You Ever Imagined, which helps teams unlock their potential to achieve more. [17:11] - Brian shares Frédéric Laloux's concept of the different colors of organizations as laid out in his book called Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness and how we can better enable change in organizations. [18:57] - Julie shares a book she recommends in Scrum Master class that’s great for sports fans called The Captain Class by Sam Walker, which walks the reader through what makes great sports teams great. [22:15] - Brian shares why sports analogies are great for teaching Scrum. [23:28] - Julie shares how even the Rolling Stones delve deep into figuring out how to improve. [24:30] - Why retrospectives are a great tool for improving the outcome of any mission. [28:25] - Brian shares why we still need to adjust to the current climate, even when the goal remains the same. [30:11] - Brian shares books by recent guests on the show, including Lead Without Blame: Building Resilient Learning Teams by Tricia Broderick, Strategise by Roman Pichler and Coaching Agile Teams: A Companion for Scrum Masters, Agile Coaches, and Project Managers in Transition (Addison-Wesley Signature Series (Cohn)) by Lyssa Adkins. Listen in next time when Scott Dunn will be on the show. References and resources mentioned in the show Two Beats Ahead by Panos A. Panay and R. Michael Hendrix Agile Retrospectives: Making Good Teams Great by Esther Derby, Diana Larsen The Culture Code: The Secrets of Highly Successful Groups by Daniel Coyle DRIVE by Daniel Pink | Animated Core Message Drive: The Surprising Truth About What Motivates Us by Daniel Pink When: The Scientific Secrets of Perfect Timing by Daniel Pink The Power of Regret: How Looking Backward Moves Us Forward by Daniel Pink Stretch: Unlock the Power of Less -and Achieve More Than You Ever Imagined by Scott Sonenshein Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness by Frédéric Laloux The Captain Class by Sam Walker Lead Without Blame: Building Resilient Learning Teams by Tricia Broderick Strategise by Roman Pichler Coaching Agile Teams: A Companion for Scrum Masters, Agile Coaches, and Project Managers in Transition (Addison-Wesley Signature Series (Cohn)) by Lyssa, Adkins Mountain Goat Software Agile Mentors Community Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts 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. Julie Chickering is the brains and brawn behind JC Agile Consulting, believes that Lean and Agile practices are packed with potential — to enable positive culture change, business agility, and breakthrough results. Julie is a past president and board member of the Agile Project Management Network (APLN), a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), as well as a traditional Project Management Professional (PMP).

Julie Chickering sits down with Brian to share the best gift books for the Scrum masters in your life. Overview We all have those books on our bookshelves that we’ve had for years and still refer back to time and time again, or that new title that we’ve just read that blows our mind with the way it makes a new concept more relatable. Julie Chickering is a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), and a traditional Project Management Professional (PMP). Today on the show, Julie joins Brian to discuss the most valuable books they’ve read, the lessons they’ve learned from them, and the best ones for giving to the Scrum Master in your life this holiday season. Listen now to discover: [01:06] - Today, Brian and Julie Chickering will be sharing the most valuable books we’ve read. [02:10] - Julie shares how a book called Two Beats Ahead is helping her learn to let go of her creations. [04:00] - Julie shares an interesting story of how Beyoncé invited musicians in for collaboration and how that opened her mind to learning from her community. [05:07] - Brian shares why Agile Retrospectives: Making Good Teams Great by Esther Derby and Diana Larson is his #1 book recommendation for Scrum Masters. [06:29] - Julie shares why she’s also a fan of Agile Retrospectives: Making Good Teams Great for the mix-and-mash recipe for creating menu selections. [08:06] - Julie shares why The Culture Code: The Secrets of Highly Successful Groups insight into the three main things that make high-performing teams high-performing is her favorite book to give to the leaders on her list. [10:36] - Brian shares the three things from Daniel Pink’s Drive: The Surprising Truth About What Motivates Us that align with Scrum. [12:34] - Julie shares how she learned to flip the script, start with the hard topics in a conversation, and finish with the positive from Daniel Pink, as included in his book, When: The Scientific Secrets of Perfect Timing. [15:53] - Brian shares why Dan Pink’s books are most enjoyable via audio. [16:15] - Julie shares how a podcast interview with author Scott Sonenshein led her to his book called Stretch: Unlock the Power of Less -and Achieve More Than You Ever Imagined, which helps teams unlock their potential to achieve more. [17:11] - Brian shares Frédéric Laloux's concept of the different colors of organizations as laid out in his book called Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness and how we can better enable change in organizations. [18:57] - Julie shares a book she recommends in Scrum Master class that’s great for sports fans called The Captain Class by Sam Walker, which walks the reader through what makes great sports teams great. [22:15] - Brian shares why sports analogies are great for teaching Scrum. [23:28] - Julie shares how even the Rolling Stones delve deep into figuring out how to improve. [24:30] - Why retrospectives are a great tool for improving the outcome of any mission. [28:25] - Brian shares why we still need to adjust to the current climate, even when the goal remains the same. [30:11] - Brian shares books by recent guests on the show, including Lead Without Blame: Building Resilient Learning Teams by Tricia Broderick, Strategise by Roman Pichler and Coaching Agile Teams: A Companion for Scrum Masters, Agile Coaches, and Project Managers in Transition (Addison-Wesley Signature Series (Cohn)) by Lyssa Adkins. Listen in next time when Scott Dunn will be on the show. References and resources mentioned in the show Two Beats Ahead by Panos A. Panay and R. Michael Hendrix Agile Retrospectives: Making Good Teams Great by Esther Derby, Diana Larsen The Culture Code: The Secrets of Highly Successful Groups by Daniel Coyle DRIVE by Daniel Pink | Animated Core Message Drive: The Surprising Truth About What Motivates Us by Daniel Pink When: The Scientific Secrets of Perfect Timing by Daniel Pink The Power of Regret: How Looking Backward Moves Us Forward by Daniel Pink Stretch: Unlock the Power of Less -and Achieve More Than You Ever Imagined by Scott Sonenshein Reinventing Organizations: A Guide to Creating Organizations Inspired by the Next Stage of Human Consciousness by Frédéric Laloux The Captain Class by Sam Walker Lead Without Blame: Building Resilient Learning Teams by Tricia Broderick Strategise by Roman Pichler Coaching Agile Teams: A Companion for Scrum Masters, Agile Coaches, and Project Managers in Transition (Addison-Wesley Signature Series (Cohn)) by Lyssa, Adkins Mountain Goat Software Agile Mentors Community Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts 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. Julie Chickering is the brains and brawn behind JC Agile Consulting, believes that Lean and Agile practices are packed with potential — to enable positive culture change, business agility, and breakthrough results. Julie is a past president and board member of the Agile Project Management Network (APLN), a Certified Scrum Trainer (CST), PMI Agile Certified Practitioner (PMI-ACP), as well as a traditional Project Management Professional (PMP).

Visit his websiteGet the bookSupport the show

In dieser Folge unterhält sich Dominique mit Roman Pichler über das Thema Produktstrategie. Roman hat gerade erst eine neue Auflage seines Buchs Strategize veröffentlicht und die beiden nehmen dies zum Anlass, um über dieses wichtige Thema zu sprechen. Roman sieht dabei die Produktstrategie als einen Plan bzw. den Weg wie man eine Produktvision erreichen möchte. Die beiden sprechen auch über die Probleme beim Entwickeln von Strategien. Oft beobachtet Roman beispielsweise, dass in einer Organisation gar nicht richtig klar ist, was das Produkt ist. Daneben sieht er auch eine fehlende Bevollmächtigung der Produktmanager bzw. Scrum Product Ownern. Aus der Produktstrategie werden dann Teilziele abgeleitet und eine zielorientierte Roadmap entwickelt. Mit Hilfe der zielorientierten Roadmap können Entwicklungsteams angeleitet und Stakeholder miteinander abgestimmt werden. Von Feature Roadmaps rät Roman dabei aber explizit ab, da es ihm weniger um die Auslieferung von Features geht, sondern mehr um das Erreichen von Zielen. Ein besondere Idee hat Roman noch für die Überführung der Strategie ins Product Backlog. Das aktuelle Product Goal wird als alleiniges Kriterium für die Elemente im Product Backlog genommen und nur Elemente, die auf dieses Ziel einzahlen sollten im Backlog aufgenommen werden. Damit wird das Product Backlog recht schlank aber sehr auf das Produktziel fokussiert. Roman war bereit einmal bei uns zu Gast und hat darüber gesprochen, welche Herausforderungen und Praktiken bestehen, um als Product Owner zu führen (https://produktwerker.de/how-to-lead-in-product-management/). Wenn euch das Thema Produktstrategie interessiert, empfehlen wir euch noch folgende Folgen: - The Product Field (https://produktwerker.de/product-field/) - Eine Produktstrategie entwickeln (https://produktwerker.de/produktstrategie-entwickeln/) - Wardley Mapping - Produktstrategie ist wie Schach (https://produktwerker.de/wardley-mapping/)

'Start with the why?' When creating a digital product, we usually focus on a specific problem or opportunity space in order to create a solution to achieve a desired outcome or solve a problem. If only it were so straightforward! In reality, products go through many iterations; more data provides insight, the product strategy evolves, assumptions are tested and hypothesises are proven or disproven. Whether working on the first version or further iterations of a product, it is important to keep focused on the direction of travel in order to keep on the desired path to success. In this episode I am joined by Roman Pichler, Author and renowned Product Expert  and we deep dive into how you can create a captivating vision for your product to start you off on the right footing but also touching on some of the pitfalls to avoid when creating vision.

Get the bookRoman Pichler's websiteRoman Pichler's podcastSupport the show

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.

Brian speaks with Stacey Ackerman about working with Marketing teams using Agile. While the majority of teams using Agile are based in software, one of the fastest growing areas for Scrum teams is in Marketing. There’s a natural fit as Marketers are used to using such practices as A/B testing and getting quick results that feed their next steps. As you can imagine, there are a unique set of challenges that a marketing team presents that other Scrum teams don’t necessarily have to deal with as well. In this episode, Stacey talks us through the process that marketing teams follow when attempting to apply agile principles to their work. Listen now to discover: - 2:28 - what’s different about the way marketing teams approach agile? - 8:51 - what is the Agile Marketing Navigator and how are teams using it? - 15:05 - Stacey goes over the different roles - 17:43 - what are the chief problems marketing teams deal with in adopting this? Listen next time when we’ll be discussing… Product Roadmaps with Roman Pichler! References and resources mentioned in the show Agile Marketing Manifesto Agile Marketing Navigator Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? It would be great if you left 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? Share your thoughts with us as 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. Stacey Ackerman is one of the few agile coaches and trainers that got her start in marketing. After graduating from journalism school, she worked as a content writer, strategist, director, and adjunct marketing professor. She became passionate about agile as a better way to work in 2012 when she experimented with it for an ad agency client. Since then she has been a scrum master, agile coach and has helped with numerous agile transformations with teams across the globe. Stacey speaks at several agile conferences, has more certs to her name than she can remember and loves to practice agile at home with her family. As a lifelong Minnesotan, she recently relocated to North Carolina where she’s busy learning how to cook grits and say “y’all."

Brian speaks with Stacey Ackerman about working with Marketing teams using Agile. While the majority of teams using Agile are based in software, one of the fastest growing areas for Scrum teams is in Marketing. There’s a natural fit as Marketers are used to using such practices as A/B testing and getting quick results that feed their next steps. As you can imagine, there are a unique set of challenges that a marketing team presents that other Scrum teams don’t necessarily have to deal with as well. In this episode, Stacey talks us through the process that marketing teams follow when attempting to apply agile principles to their work. Listen now to discover: - 2:28 - what’s different about the way marketing teams approach agile? - 8:51 - what is the Agile Marketing Navigator and how are teams using it? - 15:05 - Stacey goes over the different roles - 17:43 - what are the chief problems marketing teams deal with in adopting this? Listen next time when we’ll be discussing… Product Roadmaps with Roman Pichler! References and resources mentioned in the show Agile Marketing Manifesto Agile Marketing Navigator Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? It would be great if you left 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? Share your thoughts with us as 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. Stacey Ackerman is one of the few agile coaches and trainers that got her start in marketing. After graduating from journalism school, she worked as a content writer, strategist, director, and adjunct marketing professor. She became passionate about agile as a better way to work in 2012 when she experimented with it for an ad agency client. Since then she has been a scrum master, agile coach and has helped with numerous agile transformations with teams across the globe. Stacey speaks at several agile conferences, has more certs to her name than she can remember and loves to practice agile at home with her family. As a lifelong Minnesotan, she recently relocated to North Carolina where she’s busy learning how to cook grits and say “y’all."

Fragt man drei Product Ownerinnen, was sie als ihre Verantwortlichkeit ansehen, so erhält man vier sehr unterschiedliche Antworten. In vielen Fällen ist eine Ursache für die Vielfalt der Rolleninterpretationen: Manche Product Owner arbeiten in einem Scrum Kontext und andere wiederum als SAFe Product Owner. Es ist also an der Zeit, dass Oliver und Dominique über die Gemeinsamkeiten und Unterschiede sprechen. Denn aus ihrer Perspektive ist dieses Thema eines der großen Missverständnisse in der agilen Produktcommunity. Ein Scrum PO ist etwas komplett anderes als ein SAFe PO. Und nachdem einige Beiträge und Meinungen in den letzten Wochen in die Timeline der beiden gespült wurden, ist es auch ein guter Zeitpunkt die eigene Sichtweise zu formulieren. Dominique und Oliver starten mit einer Reflexion eines Beitrags von Roman Pichler zu "Six Types of Product Owner", der in diesem Podcast schon in der einen oder anderen Episode zitiert wurde. Fokus legen beide aber auf den Scrum Product Owner und den SAFe Product Owner. Wo liegen die Gemeinsamkeiten, welche Unterschiede findet man? Nach einem Blick in den Scrum Guide und in die detaillierteren Erläuterungen in SAFe wird auf die eine oder andere Äusserung von Kollegen referenziert, u.a. Sohrab Salimi oder Heiko Stapf. Natürlich konkretisieren Oliver und Dominique darüber hinaus auch sehr klar ihren eigenen Standpunkt. Sie klären, dass in Produktwerker-Podcast sehr häufig der Scrum Product Owner im Mittelpunkt der Diskussionen steht. Wie immer schließt diese Episode mit konkreten Tipps & Tricks ab.

Join Cynthia, Sabrina and Bel while they discuss topics you should be having with an Agile Coach, but probably aren't. Laugh with us as we put a sassy spin on all things Agile. Today's show is around understanding your customer. Do you know who your customer is? What problems does your product solve? What is the secret sauce? Have you defined the minimum product requirement? The girls get a bit crazed when talking about how Agile focuses on the customer and why many companies miss the mark. Link to Roman Pichler who the girls are very much a fan of him and his work https://www.romanpichler.com/ Co Hosts Belinda Price Cynthia Kahn Sabrina C E Bruce #Agile_World #AgileWorld #Agile #AgileTalkShow #AgileManifiesto #AgileCoach #ScrumMaster Online Agile World News Agile World Institute Agile World Publishing LinkedIn Facebook Instagram Twitter YouTube Podcast Agile World Amazon Music Agile World Audible Agile World Spotify Agile World Apple Podcasts Agile World Google Podcasts Agile World Pocket Casts Agile World Anchor Agile World Breaker Agile World Radio Public Agile World Stitcher Agile World © 2022 Agile World Broadcast Network, Hollywood, California | Content Co-hosts --- Send in a voice message: https://anchor.fm/agile-world/message

Was macht eigentlich ein Product Owner? Wofür braucht es ihn oder sie, und warum ist diese Verantwortlichkeit in vielen Unternehmen falsch besetzt? Wie wachse ich in dieser Rolle und was macht das Zusammenspiel mit dem Entwicklungsteam wirklich wertvoll? Jasmine und Kai beleuchten diese spannende Verantwortlichkeit des Scrum Rahmenwerks in der Tiefe und zeigen Wege auf, wie eine Weiterentwicklung aussehen kann. Shownotes: User Story Mapping mit Jeff Patton: https://www.youtube.com/watch?v=AorAgSrHjKM Raus aus der Feature-Falle von Melissa Perri: https://www.amazon.de/Raus-aus-Feature-Falle-effektives-Produktmanagement/dp/3960091206 Agiles Produktmanagement mit Scrum von Roman Pichler: https://www.amazon.de/Agiles-Produktmanagement-mit-Scrum-Erfolgreich/dp/3864901421 Business Model Generation von Alexander Osterwalder: https://www.amazon.de/Business-Model-Generation-Spielver%C3%A4nderer-Herausforderer/dp/359339474X Werde selbst Agile Coach: https://agilegrowth.de/agile-coach-ausbildung-einleitung/

Eine "Stakeholder Community" zu formen, kann eine Chance für Product Owner sein, aus einer defensiven Rolle des Prügelknaben und aus der Pendel-Diplomatie herauszukommen. Stakeholder sind als Einzelpersonen oder Gruppen definiert, die von den Auswirkungen einer Produktentwicklung positiv/negativ betroffen sind oder die an der Entwicklung als Beteiligte mitwirken. Oft trommeln gerade die "Betroffenen" mit ihren berechtigten oder unberechtigten Interessen und Wünschen immer wahllos auf den/die Product Owner:in ein. Besonders kniffelig ist, dass diese Interessen durchaus sehr unterschiedlich sein können und zum Teil sogar widersprüchlich. Als Product Owner stehst du dann recht hilflos in der Mitte, alle zerren an dir und vielleicht versuchst du es sogar allen recht zu machen. Eigentlich ist das ein zwar sehr ehrenhaftes, aber zugleich auch sehr aussichtsloses Unterfangen. Roman Pichler beschreibt in seinem Buch How To Lead in Product Management die Etablierung einer Stakeholder Community als eine mögliche Lösung des Problems. Um dieses Thema geht es in dieser Episode. Das Buch gibt es übrigens nun seit wenigen Monaten auch in deutscher Fassung unter dem Titel "Leadership im Produktmanagement". Im Gespräch verweisen Tim und Oliver an einigen Stellen auf ihr "POEM", das sog. Product Ownership Evolution Model, welches die beiden 2017 entwickelt haben. Im Gespräch wurde auch auf weitere Folgen Bezug genommen. Daher empfehlen wir euch, auch diese Episoden anzuhören: - Seine Stakeholder kennen und richtig analysieren - Der Umgang mit schwierigen Stakeholdern - Die Relevanz von UX den eigenen Stakeholdern vermitteln - Herausforderungen zwischen Product Owner & Developer - Dein Freund der Scrum Master Weitere Artikel, Videos und Literaturempfehlungen haben wir euch in unserer recht neuen Produktwerker Box (unter https://produktwerker.de/) zusammengestellt. Zu diversen Herausforderungen für Product Owner haben wir dort unsere Content-Empfehlungen zusammengetragen. Eine davon behandelt das Thema: Umgang mit schwierigen Stakeholdern meistern Wie läuft die Zusammenarbeit mit Stakeholdern bei euch ab? Hast du vielleicht selber bereits eine Stakeholder Community geformt? Wir freuen uns, wenn du deine eigenen Erfahrungen mit uns in einem Kommentar teilst, entweder hier oder auf unserer Produktwerker LinkedIn-Seite.

In this episode, I have a chat with Roman Pichler who has been advising, training and coaching Product Managers and leaders for over 15 years.We talk about The challenges faced by a new generation of product leaders The importance of growth and building a team vs. doing operational tasks The challenges of balancing management expectations and the growth of the product team

We sit down with product expert Roman Pichler - key talking points include:Shifting away from the traditional feature-based roadmaps.The power of focusing on the why instead of the how.When to use different types of product roadmaps effectively.The advantages of having a validated product strategy.How leveraging the collective knowledge and creativity of the team adds value.

Hi everyone and welcome to this episode on the Agile Atelier podcast. Today, I'll be chatting with Roman Pichler on the topic of Scaling a Product. Roman Pichler is a product management expert specialised in digital products. He has helped advance product management over the past 10 years by developing new practices that help agile…… Continue reading Episode 38: Scaling a Product with Roman Pichler

Over the last 15 years, Merissa has gone from New York media to Australian finance to German fintechs - with a number of stops in between.  She joins us on the podcast to talk about what she's learned along the way, including: from working in different cultures & industries, influencing executives,knowing if you want to be a people manager, and more!Featured Links: Follow Merissa on LinkedIn and Twitter｜Merissa's article 'Bringing product thinking to any team' | Merissa's article 'How to win at remote product management - Covid 19 edition' | Merissa's article 'Experiment like a boss' | Merissa's New Feature Template form  | Roman Pichler's Decision Making Chart  | Ken Norton's blog post,  'It's time to fight for a dual product management career path' UserLeap Give UserLeap a try for free by visiting UserLeap.com to build better products.

In this episode, I have a pleasure to host Roman Pichler, a leading product management expert specialized in digital products and agile practices. He has more than 15 years experience in teaching product managers and product owners, advising product leaders, and helping companies build successful product management organizations. He is an author of Agile Product Management with Scrum, Strategize, and How to Lead in Product Management and we talk about product management.

Roman Pichler is a Product Management Author, Consultant, and trainer. Check out the full show notes at TheAgileWire.com YouTube: https://youtu.be/JkDcxIEcrG4

In this episode, I have a chat with Roman Pichler who has been advising, training and coaching Product Managers and leaders for over 15 years. We talk about

Abstract:Last year, the Scrum Guide got updated. One of those updates has been the addition of the Product Goal. How do Product Goals relate to the Product Vision or the Sprint Goals. And how can we still distinguish this in our teams with all the different terminology without causing widespread confusion? Product development legend Roman Pichler is here to share his vision on this.What you'll discover in this show:-        Product Goals are goals on the mid-term, six months out from now-        Product Vision and Goals need to be supported by the environment of the team, it's not just the goal of the Product Owner-        Cascading goals makes it easier and more tangible for teams to create value  Speakers:Roman PichlerProduct management expertROMAN PICHLER is a product management expert specialized in digital products. He has played a leading role over the last 10 years in advancing product management and developing new practices that help agile organizations and teams create great products. Roman shares his knowledge through his training courses and consulting services, his three books on product management, his popular blog, podcast, and talks, and his product management tools, including his widely used product vision board.​As the founder and director of Pichler Consulting, Roman looks after the company's offerings. This allows him to continue to practice product management and to experiment with new ideas. Roman is based in Wendover near London in the United Kingdom.​When he's not busy with work, Roman enjoys spending time with his wife and three children, riding his bicycle in the local hills, playing the tenor saxophone, and helping with family events at Amaravati Buddhist monastery.  Contact Roman Pichler: https://www.romanpichler.comhttps://www.linkedin.com/in/romanpichler/ https://twitter.com/romanpichler https://www.youtube.com/romanpichler https://www.instagram.com/roman_pichler/ https://www.facebook.com/pichlerconsulting Sander Dur (host)Scrum Master, Agile Coach, trainer, and podcast host for ‘Mastering Agility”Sander Dur is a business agility enthusiast, with a passion for people. Whether it's healthy product development, agile leadership, measurement, or psychological safety, Sander has the drive to enable organizations to the best of their abilities. He is an avid article writer, working on a book about Scrum Mastery from the Trenches, and is connecting listeners with the most influential people in the industry. https://www.linkedin.com/in/sanderdur/ https://agilitymasters.com/en https://sander-dur.medium.com/ Additional resources: https://www.romanpichler.com/romans-books https://www.romanpichler.com/romans-podcastSupport the show

From Our Homes, UK. In this episode, Geoff and Paul breakdown their chat with another one of their agile heroes, Roman Pichler. In a new type of pubcast for 2021, Geoff and Paul will be chatting with some of their agile heroes over a drink. If you are interested in seeing the full interview with Roman, and getting all the new interviews as they drop, then check out our "Full Pints" membership on patreon.com/theagilepubcast

In this episode,

Roman Pichler discusses the challenges associated with leading in a Product Management role and what you can do to overcome those challenges. The post MBA215: The Challenges with Leading in Product Management appeared first on Mastering Business Analysis.

Hazelcast delivers the in-memory computing platform that empowers Global 2000 enterprises to achieve ultra-fast application performance - at any scale. Built for low-latency data processing, Hazelcast's cloud-native in-memory data store and event stream processing software technologies are trusted by leading companies such as JPMorgan Chase, Charter Communications, Ellie Mae and National Australia Bank to accelerate data-centric applications. On this weeks episode of the Product Launch podcast, Sean and David cover  Why industry subject matter expertise matters and how it differentiate you as a product professional The advantages of building a product for yourself  How to keep your industry subject matter expertise to be better product professional Going from a siloed world of being an individual contributor to more of a leadership role for the organization and various functional groups Why product professionals need to maintain a healthy network of industry professionals Getting to know your customers personally so they will feel comfortable opening up to you so you can help them Resources: Flash Boys, by Michael Lewis - https://www.goodreads.com/book/show/24724602-flash-boys Automate This, by Christopher Steiner - https://www.goodreads.com/book/show/13542772-automate-this Competing Against Luck, by Clayton M. Christensen - https://www.goodreads.com/book/show/28820024-competing-against-luck Playing to Win, by A.G. Lafley - https://www.goodreads.com/book/show/13586928-playing-to-win How to Lead in Product Management, by Roman Pichler - https://www.goodreads.com/book/show/13586928-playing-to-win Hazelcast Websites - hazelcast.org , hazelcast.com Connecting with David: Connect with David on Twitter - https://twitter.com/dbrimley?lang=en

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website. When this story starts, we hear about a Product Owner that had the unfortunate habit of micro-managing the team and assignments. On top of that, the PO was also a yes-man, who wanted to say “yes” to everything the stakeholders came up with. We explore how these behaviors led to the team imploding, and discuss what we can do to help teams and PO’s who start showing the same symptoms. Featured Book of the Week: Agile Product Management with Scrum: Creating Products that Customers Love In Agile Product Management with Scrum by Roman Pichler, found a book that distills the concepts down to practical advice and helps the teams and the Scrum Masters focus on customer needs. He also found that the book allowed him to have great conversations with Product Owners, and coach the PO’s he worked with. In this segment, we also refer to The Leader’s Guide to Radical Management by Stephen Denning.   Are you having trouble helping the team working well with their Product Owner? We’ve put together a course to help you work on the collaboration team-product owner. You can find it at: bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO’s collaborate. About Arjay Hinek Arjay has been an Agilist for over a decade. In the last few years he’s focused on Agile and “product development” for non-software applications. A considers himself a teacher at heart, he uses metaphors and story-telling to help others see their challenges from a different perspective and overcome them.  You can link with Arjay Hinek on LinkedIn and connect with Arjay Hinek on Twitter.  You can follow Arjay’s blog at http://goscrumgo.com/.

In dieser Podcast Folge hatte ich das Vergnügen mit dem Product Owner Papst persönlich zu sprechen: Roman Pichler. Roman ist ein Produktmanagementexperte spezialisiert auf digitale Produkte. Seit mehr als 15 Jahren berät er Firmen rund um das Thema Produkt und hilft ihnen dabei erfolgreiche Produktmanagement Organisationen aufzubauen. Roman ist Autor von drei Büchern zu diesem Thema, das letzte in dieser Reihe heißt "How to Lean in Product Management". Mehr zu Roman findest Du auf seiner Webseite: romanpichler.com   In dieser Episode sprechen wir über folgende Punkte: Was macht ein gutes Produkt aus? Was sind die typischen Fehler im agilen Produktmanagement? Welche Fähigkeiten braucht ein guter Product Owner? Wohin entwickelt sich die agile Produktentwicklung? Viel Spaß beim Reinhören!

Wir steigen in das Thema Stakeholder Management ein und klären zunächst, was hinter dem Begriff "Stakeholder" steckt. Wir erklären im Gespräch, wie ihr als PO alle Eure Stakeholder finden und kategorisieren könnt. Dazu gehört auch eine Einschätzung, wie die verschiedenen Stakeholder untereinander in Beziehung stehen und sich beeinflussen. Da dies zunächst mal aber nur Hypothesen sind, ist es wichtig in Interviews die wahren Bedürfnisse dieser Stakeholder zu verstehen - also zu validieren. Er auf dieser Basis können dann Ableitungen für Handlungsempfehlungen im Umgang mit einzelnen Stakeholdern getroffen werden. Das ganze wird abgerundet von wichtigen Tipps wie eine Gruppe von Stakeholdern gehandelt werden kann. Insgesamt geht es in dieser Folge also vor allem um einen strukturierten Einstieg in ein Stakeholder Management. Die tägliche Interaktion mit einzelnen und v.a. den Umgang mit schwierigen Stakeholdern beleuchten wir hier noch nicht. Während des Gesprächs verweisen wir auf Inhalte folgender Quellen: Stakeholder Management Prozesse des PMI (Project Management Institute) im PMBOK® Guide, 6th Edition (A Guide to the Project Management Body of Knowledge) Als Quelle der Power-Interest-Grid wird allgemein das Buch "Exploring Corporate Strategy" aus dem Jahre 1983 von Gerry Johnson, Kevan Scholes und Richard Whittington angesehen. Roman Pichler hat es mit getauschten Achsen adaptiert und 2015 in seinem Blog-Artikel "Getting Stakeholder Engagement Right" Die Beziehungsmatrix zur Darstellung von Beziehungen von Stakeholdern hat Dominique Winter dargestellt. Für das Buy a Feature Game zur Priorisierung in einer Stakeholder Runde gibt es verschiedene gute Erklärungen im Netz. Zur von Tim genutzten Priorisierung mit der Wäscheleine ist uns keine klare Quelle bekannt. Es ist letztlich eine Abwandlung des Team Estimation Game, das von Daniel Dubbel in einem Blog-Artikel "Alternative Schätzverfahren" (2011) gut beschrieben wird. Im Original wird es Steve Bockman zugeschrieben. Die von Tim z.T. angesprochenen Leitfragen für die vier Steps lauten: 1.) IDENTIFIZIEREN (Vollständige Sammlung aller direkt und indirekt Betroffenen/Beteiligten) - Mit wem interagieren wir? - Wer ist besonders wichtig für unseren Kontext? - Welche Funktionsbereiche sind relevant? 2.) EINORDNEN (Kategorisierung nach Interesse und Einfluss auf unsere Wertschöpfung) - Was würde die Person über unser Vorhaben sagen? - Was passiert, wenn wir nichts tun? - Wie schätzen wir die Beziehungen der Stakeholder untereinander ein? 3.) BEDÜRFNISSE VERSTEHEN (Validierung unserer Hypothesen) - Wie ist Dein Blick auf unser Vorhaben? - Was brauchst Du von uns? 4.) STRATEGIE ABLEITEN (Festlegung, wie wir mit den einzelnen Stakeholdern interagieren, damit unser Vorhaben gelingt) - Wie gehen wir mit den jeweiligen Stakeholdern um? - Wie kommunizieren wir mit ihnen (direkt/indirekt)? Wir freuen uns über Euer Feedback auf produktwerker.de, per Mail an podcast@produktwerker.de oder via Twitter an @produktwerker.

Global Product Management Talk is pleased to bring you the next episode of... The Everyday Innovator with host Chad McAllister, PhD. The podcast is all about helping people involved in innovation and managing products become more successful, grow their careers, and STANDOUT from their peers. About the Episode:  Part of the path to becoming a product master is developing as a leader. Leaders of product management need agility, influence, trust, empathy, and motivating vision. And, those are the topics our guest, Roman Pichler, explores with us in this episode. Roman is a product management expert specializing in digital products. He is the author of several books, including his latest, titled, How to Lead in Product Management. His popular blog is also available as a podcast and both are simply named Roman Pichler.

Learn the qualities of a successful product manager and leader. Part of the path to becoming a product master is developing as a leader. Leaders of product management need agility, influence, trust, empathy, and motivating vision. And, those are the topics our guest, Roman Pichler, explores with us in this episode. Roman is a product […]

Learn the qualities of a successful product manager and leader. Part of the path to becoming a product master is developing as a leader. Leaders of product management need agility, influence, trust, empathy, and motivating vision. And, those are the topics our guest, Roman Pichler, explores with us in this episode. Roman is a product […]

Roman Pichler is a leading product management expert who specializes in digital products and agile practices. He utilizes agile methodologies and consults for some of the world's largest and most respected enterprise companies such as Google, Adidas, Nokia, eBay, Lloyd's of London, and many more. Roman is the author of four books, including How to Lead in Product Management, Strategize: Product Strategy and Product Roadmap Practices for the Digital Age and Agile Product Management with Scrum. In this episode… If you just started your SaaS business or are about to embark on that journey, you would want to get to your minimum viable product on time and on a budget. Agile product management specialist, Roman Pichler, says that the first step to achieve that is to come up with a vision for your product which involves answering the following questions: What's the value proposition of your product? Who are your target customers? What makes your product stand out? What’s your business model and how will you get it monetized? Once you have a visual picture of your answers to those questions, you can consider yourself ready to take the next steps towards your MVP. Join Geordie Wardman on this episode of the Big Break Software Podcast as he discusses with Roman Pichler the best practices for budding SaaS companies that utilizes agile product management. They also talk about how to follow and keep your MVP within your desired time frame and budget, how to work with remote developers, and what the release burndown chart is and how it can make your agile practice even better. Stay tuned.

ÜBER DIESE EPISODE Produktstrategie, Productdiscovery, Roadmap, Backlog: Der Produktmanager ist meist zu beschäftigt, um sich auch noch um seine Softskills zu kümmern. In dieser Episode diskutieren Roman und Tim über die längst notwendige Aufmerksamkeit für Leadership im Produktmanagement und was das für die Rolle bedeutet. https://www.digitale-leute.de/interview/leadership-produktmanagement ÜBER DEN PODCAST Digitale Leute Insights ist der Podcast für Passionate Product People. Wir interviewen Top-Produktentwickler aus aller Welt und werfen einen tiefen Blick auf die Tools, Taktiken und Methoden digitaler Professionals und Unternehmen. ÜBER DIGITALE LEUTE Wir porträtieren Persönlichkeiten, die digitale Produkte kreieren, gestalten, entwickeln und vermarkten. Mit unseren Interviews geben wir einen Einblick in die Arbeitsweisen, Tools und Taktiken von Deutschlands Digitalunternehmen. Kontaktiert uns für Feedback, Vorschläge oder Anfragen via dlredaktion@digitale-leute.de

In dieser Folge des Produktwerker Podcasts sprechen Oliver und Tim mit Roman Pichler über sein neues Buch "How to Lead in Product Management: Practices to Align Stakeholders, Guide Development Teams, and Create Value Together". Uns interessierte welche Motivation zu dem Buch führte und was Product Owner neben den methodischen Skills noch brauchen, um in ihrer Rolle erfolgreich zu sein. Wir sind gespannt zu hören, welche Herausforderungen Ihr als Product Owner im Kontext Führung seht und welche Empfehlung Ihr anderen geben könnt. Wie immer freuen wir uns über Euer Feedback auf produktwerker.de, per Mail an podcast@produktwerker.de oder via Twitter an @produktwerker.

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.

Throughout their careers, whatever question either Lily or Randy has had, Roman Pichler’s probably had some great advice on the topic! A longtime consultant, author and teacher, we grabbed him for a chat focusing on some of the lessons contained in his fourth book, How to Lead in Product Management. Quote of the Episode A [...] Read more » The post Conversations, Conflict and Leadership – Roman Pichler on The Product Experience appeared first on Mind the Product.

In this podcast I'm talking to Roman Pichler. Roman is incredibly well known in the Product Space for his unique approach to Product.  He has a new book called: How to Lead in Product Management: Practices to Align Stakeholders, Guide Development Teams, and Create Value Together The focus is on Product Leadership and that's exactly what this podcast is about.  Keep listening to learn:  How to deal with really difficult situations.  Should Product People learn more about how to negotiate?  How to deal with leadership when you don't have direct authority Whats the best way to work with Scrum Masters And Roman is going to help us learn more about other leadership skills we need as Product Leaders His book is available at Amazon here:   You can find Roman on Linkedin here: His website is at:  Really hope you enjoy it!

This is our 1st episode of 0100 Conferences Podcast in collaboration with 3TS Capital Partners, one of the leading European technology-focused private equity and venture capital firms. Elbruz Yilmaz, Investment Director at 3TS was talking with Andrew Schafer, CTO of Entelo, about the distributed technology teams. How to build them, manage them and grow them over time. Elbruz is responsible for investment sourcing, analysis, business development, transactions and portfolio management in CEE and Turkey. Entelo is the world’s first all-in-one, an automated, source-to-hire recruitment platform that’s changing the way companies hire. Andrew is the CTO of Entelo, where he leads the product, design, and engineering teams to build one of the leading recruiting automation and digital interviewing platforms on the market. Andrew likes the blog of Roman Pichler, who provides fantastic explanations about various issues on this subject. In terms of books, he really likes “Creativity; Inc.” from Edwin Catmull, President at Pixar. Roman Pinchler's Blog: https://www.romanpichler.com/ Creativity, Inc.: http://www.creativityincbook.com/

Read the full Show Notes and search through the world’s largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website.  Martin shares a story of an engagement which goal was to help a department adopt Agile. We review his first steps in that change, what he observed when the engagement started. We then discuss some of the tools he helped implement in that organization and how that was done.  In this episode, we refer to the Goal Roadmap by Roman Pichler, and one of the most critical skills for Scrum Masters working with change: to be able to distinguish what can be changed, influenced, and what cannot be changed. Are you trying to change too much?  About Martin Lambert Martin's an agile coach, trainer and scrum master. He’s a Northener making a living in the south of England, and finds great energy and sense of purpose from the agile movement during the second act of his career. Loves the hills and being out on a road bike. And to all the European listeners, he says: "sorry for you know what". You can link with Martin Lambert on LinkedIn.

Will Larson on Greater Than Code, Marcus Blankenship on Software Engineering Radio, Sonal Chokshi on Software Engineering Daily, Roman Pichler on Being Human, and Dave Thomas and Andy Hunt on Hanselminutes. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. And, if you haven’t done it already, don’t forget to hit the subscribe button. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting September 2, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. WILL LARSON ON GREATER THAN CODE The Greater Than Code podcast featured Will Larson with hosts Jessica Kerr, Arty Starr, and Rein Henrichs. Will talked about systems thinking, specifically referencing Donella Meadows’ Thinking in Systems: A Primer. As a sixteen-year-old, he was exposed to systems thinking by his economics professor father. They talked about how to bring about change in complex systems and Rein brought up Virginia Satir’s change model.  They talked about various forms of dysfunction, with an example being tasks that are marked as completed by developers without first doing the work of validation. Will’s own example is that executives never miss their goals; they just redefine the goals so that they hit them. There is a certain level of seniority where you can never be held accountable because you are the accountability function. Getting back into the topic of how to change complex systems, Will referenced the book, The First 90 Days as a great explanation of the need to go slow and observe before you try to change things. He says that the “great man theory” has been out of style for decades in the study of history, but is still in style in tech as the most causal way to understand how change works and also the most comforting. Rein talked about how the heroic individual myth is the other side of the coin to the scapegoat. Just as you pile all the blame onto the scapegoat, you pile all the credit onto the hero. He says that cultures that engage in hero myth-building are also likely to engage in scapegoating. Will says he himself has not seen much scapegoating at the companies he works at, likely because those cultures were unwilling to hold folks accountable for their work, but he has seen the hero myth at every company he has worked. Will then spoke about the 10x engineer myth. Will says he meets people who have been in tech for six or seven years who have the idea that they are almost done with their career. It may be due to the “senior engineer after two years” phenomenon where the career path is not well-defined and a lot of companies don’t know how to take advantage of the skills of people with 15 to 20 years of experience. A second reason is that the industry is an overwhelming and draining environment and people choose to opt out of it. As a result, we have very few engineers who have been around long enough to witness the long-term consequences of their brilliant ideas. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/142-modeling-constraints-in-human-systems-with-will-larson/id1163023878?i=1000446345964 Website link: https://www.greaterthancode.com/modeling-constraints-in-human-systems MARCUS BLANKENSHIP ON SOFTWARE ENGINEERING RADIO The Software Engineering Radio podcast featured Marcus Blankenship with host Travis Kimmel. They talked about motivation, specifically motivation of engineering teams. Marcus says that motivation is the desire to get things done and every engineer coming out of school is motivated from day one. If you get one of these people hired onto your team and, two years later, they are demotivated, suffering from PTSD, scared to offer ideas, and figuring they are just a cog in a machine, your problem is your company or your team, not the engineer you hired. Marcus says he is doing secret research on motivation as he is now interviewing candidates for a job and asking them why they are looking to leave their current job. Nobody says, “Pay.” Often the answer is a lack of alignment with their boss or their company, resulting in the engineer losing the desire to contribute because of a relationship problem. These engineers are not stick-in-the-muds that are angry they don’t get to use COBOL anymore. Something happened where instead of having their ideas valued and heard and being part of the discussion, they somehow got disconnected from their boss. In the seventies, Marcus says, researchers discovered a strong correlation between positive employer-employee relationships and the amount of job satisfaction, quality of work, turnover intentions, and amount of promotions. We are thirty-five years into a few thousand scientific studies that continue to prove that the relationship one has with one’s supervisor matters more than any other factor when it comes to job performance and job satisfaction. Marcus says that a supervisor’s one true job is to create a trusting relationship with the people that report to you. Travis shared his own experience in having one-on-ones with his supervisors that felt to him like they were trying to artificial manufacturing a relationship because there was no indication of what the goal of the meeting was.  Marcus says that good one-on-ones are bi-directional. One-on-ones in which the boss just gets status updates from the subordinate and gives new marching orders are often dissatisfying for both parties. Another flawed kind of one-on-one is where it is all about the employee. Such one-on-ones are not effective and neither party likes these either. Marcus suggests that we apply to our one-on-ones the same Agile thinking that we apply to our work. Every month, at one of your one-on-ones, do a retro on the one-on-one. Talk about why you are doing them, what value you’re getting from them, and how to make them better. They talked about psychological safety. Marcus says a lot of managers don’t realize that they are not in a good position to measure psychological safety based on their own gut. He says tools like Claire Lew’s knowyourteam.com, officevibe.com, and other anonymous survey tools can help. When we become a manager or team lead that has you supervising or leading, we forget that we are in a position of power. Travis added that leaders need to be careful about what they say casually so that it doesn’t get taken as a mandate. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/episode-374-marcus-blankenship-on-motivating-programmers/id120906714?i=1000445260176 Website link: https://www.se-radio.net/2019/07/episode-374-marcus-blankenship-on-motivating-programmers/ SONAL CHOKSHI ON SOFTWARE ENGINEERING DAILY The Software Engineering Daily podcast featured a16z podcast host Sonal Chokshi with host Jeff Meyerson. Jeff started out by asking why a VC firm decided to start a podcast. Sonal says that a16z has always had a culture of writing, blogging, and sharing ideas. This led them to develop an editorial operation from which the podcast naturally followed. Jeff asked what lessons from blogging apply to podcasting. Sonal sees podcasting as the next evolution of blogging because of its similar intimacy and a similar feeling of authenticity. The difference, she says, is that podcasting is a community and a movement.  Sonal talked about her favorite a16z episodes, including an episode on emojis. She loved it because everybody understands how to use emojis but there is a lot of deep tech and governance involved in making emojis possible. That episode, she said, encapsulates the whole a16z podcast: the intersection of technology, people, politics, context, culture, and humanity.  Jeff brought up a16z’s connection to Mike Ovitz’s Creative Artists Agency. Having read Ovitz’s book and noticed how it portrays Ovitz as a workaholic, Jeff asked Sonal how she finds balance while drinking from the addicting technological firehose. Sonal says there is a lack of nuance in the debates about screen time and work/life balance. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/a16z-podcasting-with-sonal-chokshi/id1019576853?i=1000446547922 Website link: https://softwareengineeringdaily.com/2019/08/09/a16z-podcasting-with-sonal-chokshi/ ROMAN PICHLER ON BEING HUMAN The Being Human podcast featured Roman Pichler with host Richard Atherton. Richard asked Roman what a product manager is. Roman says a product manager is someone who takes an idea and helps bring it to life, launch it, make it successful, and keep it successful. Richard asked about the distinction between a product manager and Scrum’s notion of product owner. Roman sees the product owner as a product management role, but methodologies like SAFe have redefined the product owner to be a tactical role, misunderstanding the intention behind the role and the practicalities such as answering questions from the dev team, refining backlog items, and answering support and sales questions. He says there is too much focus on the details and this risks losing sight of the big picture. To do a good job for users and for the business, Roman says it is helpful to have people looking after digital assets with the right qualifications, skills, organizational support, authority, and autonomy. He says the term “mini-CEO” appeals to some product people because it indicates that product people need a certain level of authority, but a CEO would have marketing and sales functions under their control and product people do not. Richard asked what talents Roman had to develop to be a great product person. Roman started out as a programmer and began to help business groups come up with new products. What helped him most was to boost his own understanding of how business works and the second most important element was letting go of being interested in how digital products work and focusing instead on who benefits from them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/72-to-manage-products-is-to-care-with-roman-pichler/id1369745673?i=1000446514943 Website link: http://media.cdn.shoutengine.com/podcasts/4081235a-554f-4a8f-90c2-77dc3b58051f/audio/9b2501e7-e618-46f6-8f41-abd69c871211.mp3 DAVE THOMAS AND ANDY HUNT ON HANSELMINUTES The Hanselminutes podcast featured Dave Thomas and Andy Hunt with host Scott Hanselman. Scott started by asking whether Dave and Andy knew at the time they wrote the Pragmatic Programmer 20 years ago that they were writing what would become a seminal work. Dave said that both of them were stunned by its success. The book was intended as a way to clarify their own thoughts based on their experiences as consultants in which their clients all had the same kinds of problems: inconsistent builds, the shipping of untested code, and impossible-to-change designs. Scott asked about the importance of the name of the book. Andy said that there was a strain of thought at the time the book was written that was dogmatic and they deliberately pushed against such approaches. Dave pointed out that this was harder on their readers because it forced them to figure out for themselves what works for them. They got into a discussion of what kind of educational background one needs to be a successful programmer. Dave revealed that he is currently teaching classes at SMU to, he says, corrupt the youth by teaching them things like functional programming, and because traditional computer science education is poorly serving the industry and the student. People are coming out of university with tens or hundreds of thousands of dollars of debt and, in terms of their value in the industry, they are not much different from people who are coming out of eight-week bootcamps. He teaches third or fourth year undergraduates and graduate students and he has found that none have been shown any form of testing. He would much rather hire someone who had the right attitude, was smart, and who could talk to people and he could show such a person how to code while on the job. Andy added that he gets the feeling that most computer science programs are there to teach you to become a professor of computer science rather than a problem-solver. What Andy says people need to learn, and what university education is not providing, are problem-solving skills. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/pragmatic-programmer-celebrates-20-years-dave-thomas/id117488860?i=1000446461596 Website link: https://hanselminutes.simplecast.com/episodes/the-pragmatic-programmer-celebrates-20-years-with-dave-thomas-and-andy-hunt-VBmLw9lP LINKS Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this week's episode, I talk with Roman Pichler, a leading expert in Product Management. With Roman, I explore:- His preference for the term 'Product People' over getting hung up on role descriptions- Why caring for others is at the heart of product management- The importance of adapting leadership style for different contexts- The lessons he learnt failing with an e-learning product- Why mindfulness and meditation are at the core of his approachEnjoy!https://www.romanpichler.com/Roman's book 'Strategize': http://tiny.cc/bcvw9y

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this week's episode, I talk with Roman Pichler, a leading expert in Product Management. With Roman, I explore:- His preference for the term 'Product People' over getting hung up on role descriptions- Why caring for others is at the heart of product management- The importance of adapting leadership style for different contexts- The lessons he learnt failing with an e-learning product- Why mindfulness and meditation are at the core of his approachEnjoy!https://www.romanpichler.com/Roman's book 'Strategize': http://tiny.cc/bcvw9y

> Sign Up For Our Newsletter: http://www.firsthuman.com/being-human-newsletter/In this week's episode, I talk with Roman Pichler, a leading expert in Product Management. With Roman, I explore:- His preference for the term 'Product People' over getting hung up on role descriptions- Why caring for others is at the heart of product management- The importance of adapting leadership style for different contexts- The lessons he learnt failing with an e-learning product- Why mindfulness and meditation are at the core of his approachEnjoy!https://www.romanpichler.com/Roman's book 'Strategize': http://tiny.cc/bcvw9y

Hello, my name is Gerry Scullion and welcome to Bringing Design Closer, which is part of the This is HCD Network.  I’m a service design practitioner and trainer based in Dublin City, Ireland.  Bringing design into organisations is hardly every straightforward, it always comes with its own unique set of problems.  In Bringing Design Closer, the podcast, we discuss with thought leaders around the world, what has worked for them in enabling design revolutions to occur.  Whilst at the Leading the Product Conference in Stockholm recently, I caught up with Roman Pichler, widely considered to be an expert in agile methodologies and product management. Have a comment about this episode that you'd like to share? Now you can leave us a voicemail Have something to share about this episode? Leave us a voicemail now Roman Pichlers website Product Canvas Roman on LinkedIn Roman on Twitter  Connect with This is HCD Follow This is HCD us on Twitter Follow This is HCD on Instagram Sign up for our newsletter (we have lots of design giveaways!) Join the This is HCD Slack Channel Follow us on Medium Other podcasts on This is HCD Network Power of Ten with Andy Polaine EthnoPod with Dr John Curran Bringing Design Closer with Gerry Scullion ProdPod with Adrienne Tan This is HCD is brought to you by Humana Design and The Academy.ie Support the show.

Hello, my name is Gerry Scullion and welcome to Bringing Design Closer, which is part of the This is HCD Network.  I’m a service design practitioner and trainer based in Dublin City, Ireland.  Bringing design into organisations is hardly every straightforward, it always comes with its own unique set of problems.  In Bringing Design Closer, the podcast, we discuss with thought leaders around the world, what has worked for them in enabling design revolutions to occur.  Whilst at the Leading the Product Conference in Stockholm recently, I caught up with Roman Pichler, widely considered to be an expert in agile methodologies and product management. Have a comment about this episode that you'd like to share? Now you can leave us a voicemail Have something to share about this episode? Leave us a voicemail now Roman Pichlers website Product Canvas Roman on LinkedIn Roman on Twitter  Connect with This is HCD Follow This is HCD us on Twitter Follow This is HCD on Instagram Sign up for our newsletter (we have lots of design giveaways!) Join the This is HCD Slack Channel Follow us on Medium Other podcasts on This is HCD Network Power of Ten with Andy Polaine EthnoPod with Dr John Curran Bringing Design Closer with Gerry Scullion ProdPod with Adrienne Tan This is HCD is brought to you by Humana Design and The Academy.ie Support the show.

Si quieres ver el vídeo con slides: https://youtu.be/dhEk91QucEM When working on digital products, we spend most of our time carrying out tactical tasks, such as writing and prioritising users stories, making design and architecture decision, implementing and testing software, gathering and analysing user feedback and data, and updating the product backlog. While attention to detail is necessary to develop a great product, we are in danger of no longer seeing the wood for the trees if we focus too much on the tactics. In the worst case, we develop a product with amazing features and cutting-edge technology that nobody really wants and needs. My talk will help you avoid this trap. It will show you how you can take advantage of a product strategy that clearly communicates the value your product should create, aligns people, and guides the tactical work.

Roman Pichler explains, during his talk, how to formulate and to develop an effective product strategy by taking into account your innovation strategy and your product’s lifecycle stage. Join #productized18 to learn more about the latest trends.

  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.

Episode 8: Stefan Roock und Henning Wolf / it-agile und die Geschichte von Agil in Deutschland   Episode 8 ist für mich eine ganz besondere und sehr persönliche Folge. Und das hat mit den Gästen zu tun. Ich habe die Folge mit Stefan Roock und Henning Wolf in den wunderbaren Büros Ihrer weithin bekannten Firma it-agile am Hamburger Hafen aufgenommen. it-agile ist für mich die Firma für agile Kultur, Methoden, Techniken und Transitionen. Mit den beiden und ihrer Firma verbindet mich unglaublich viel: wir sind Kollegen, Partner und Freunde. Wir arbeiten zusammen, wir geben hie und da gemeinsam Trainings. Stefan und Henning haben aber als meine ehemaligen Coaches in der Transition von mobile.de einen unglaublichen Einfluß auf mich, meine Arbeit und meine Leben gehabt, der bis heute wirkt. Stefan hat mich - ein kleines Beispiel - zu meinen ersten Vorträgen überredet. Diese Folge ist vor allem ein entspanntes Gespräch über die Zeit von 1995 bis heute und über das was im agilen Umfeld so passiert ist. Es hat sich natürlich angeboten, mit den beiden die so lange in diesem Geschäft sind, einen Rundumschlag und Überblick über das anzugehen was in der gesamten Szene und Bewegung in all den Jahren passiert ist. Um das ganze ein wenig zu strukturieren gehen wir anhand von Büchern und Ereignissen zumindest grob chronologisch vor. Ein paar Muster habe ich erkannt und werde sie am Ende noch einmal zusammenfassen. In dem Gespräch streifen wir alle möglichen Themen angefangen von keinem Prozess, über Extreme Programming (oder was daraus gemacht haben), Scrum, Kanban, DevOPs, Kultur und Leadership, Transitionen und Skalierung. Es kommen die Möglichsten und Unmöglichsten Anekdoten zu Erfahrungen, erfolgen und Misserfolgen auf. Ich will jetzt gar nicht zu viel vorwegnehmen! Viel Spaß mit dieser Folge und dem gesammelten wissen von Stefan Roock und Henning Wolf. Kapitel 00:02:38 - Jahre 1995 bis 2000 00:29:52 - Jahre 2001 bis 2005 00:47:38 - 2005 Ops und Produkte spielen eine Rolle, Disziplinen spalten sich ab? 00:52:04 - 2008 Transition bei mobile.de beginnt, wir drei lernen uns kennen, lustige Anfänge 01:08:28 2009 Kanban, David Anderson, Don Reinertsen 01:21:58 2009+: Fokus auf Produkt: Luke Hohmann, Roman Pichler, Lean Startup 01:31:53 2011 Continuous Delivery, DevOps 01:36:48 2011 bis heute Skalierung; SAFe, Less und Anderes 01:49:34 Ausblick: Wie geht es weiter mit agil? Kapitelnotizen 00:02:38 Jahre 1995 bis 2000 Erstes Scrumpaper Das Wort agil gibt es noch nicht Viele machen noch Rational Unified Process oder andere schwere Prozesse, nur ein paar arbeiten anders. Alls war „wir coden". 1999 „Extreme Programming explained" erscheint 00:29:52 Jahre 2001 bis 2005 2001 XP Buch Roock und Wolf Schwaber Beedle „Software Development with Scrum" Schwaber „Agile Project Management with Scrum" Erste XP Konferenz, Sardinien, Italien - Gepäck geht verloren, man sitzt nass in den Konferenzräumen auf Sardinien Erste XP Days Deutschland 00:47:38 Jahre 2005 bis 2007 Ops/Produkte spielen eine Rolle, Disziplinen spalten sich ab?   „Man kann doch nicht erwarten, dass die Leute in 2-3 Wochen etwas erreichen wofür 12, 15 Jahre gebraucht haben" 00:52:04 - 2008 Transition mobile.de beginnt, wir drei lernen uns kennen, lustige Anfänge Eine Menge unreifes Scrum. „… wir haben uns in Projekten belohnt mit Storypoint, z. Bsp für Bugfixing. Mein Gott, hatten wir Velocity." „Rezepte": Es war klar, dass man das macht, es gibt interne, die Feuer fangen mit denen man arbeiten kann. Es war klar, wer die anderen sind, mit denen man reden muss. Der Kunde hat nicht die Idee, dass die Coaches da sind und die Probleme lösen. Muster: „Transitionen sind dann erfolgreich, wenn sich interne Mitarbeiter in das Thema Einfräsen. Schwierig wird es immer, wenn sich solche Mitarbeiter nicht finden. Die Energie, die dazu notwendige ist, kann nicht dauerhaft von aussen zugeführt werden." Change Modelle hatten wir noch nicht. „Wir sind da einfach reingestolpert. Ich habe mit allen möglichen Leuten geredet um mich abzustimmen. Ich habe ich ständig mit dem CTO häufig abgestimmt und fokussiert. Wäre das Warum nicht klar gewesen, hätte das wahrscheinlich nicht geklappt und ich wäre frustriert gewesen und mir wäre nicht klar gewesen warum das nicht klappt."   01:08:28 2009 Kanban, David Anderson, Don Reinertsen Auf welchen Umwegen it-agile Kanban entdeckt und für sich entwickelt. Ein Stahlwerk spielt eine Rolle und ein großes Versehen. Dissonanzen zwischen Scrum und Kanban. „So wie Scrum ein verweichlichtes XP zu sein schien, schien Kanban ein verweichlichtes Scrum zu sein." Erste Kanbanschulung mit David Anderson in Deutschland. Diskussionen mit der Scrum-Community: Ist der Schutz noch da, Kanban vs. Scrum Tree Hugging Kanban als Möglichkeit mit Operations umzugehen. Arne Roock wird Mr. Kanban Germany und schreibt unglaublich viel, organisiert die erste LKCE Konferenz.   01:21:58 2009+: Fokus auf Produkt: Luke Hohmann, Roman Pichler, Lean Startup Lean Startup March bei it-agile intern. Feststellung: „Wir sind einem Missverständnis aufgesessen, dem viele aufgesessen sind, die damals das Eric Ries Buch gelesen haben. Wir haben das Gefühl gehabt, wir müssten unheimlich viel quantitativ validieren." „Wir haben Adwords Kampagnen geschaltet und dann hat da keiner uraufgedrückt. Und dann weisst Du nicht was los ist. Gibt’s das Bedürfnis nicht? Ist Deine Lösung doof? Oder hast Du nur falsche Keywords benutzt? Wie lange muss man denn warten? Ist es schlimm wenn nach 24 Stunden noch keiner raufgedrückt hat? Sollen wir noch warten? … Was wir am Ende den gemerkt haben war, dass quantitative Auswertung viel zu früh ist und wir auf qualitative Auswertung umsteigen müssten." 01:31:53 2011 Continuous Delivery, DevOPs 01:36:48 2011 bis heute Skalierung; SAFe, Less und Anderes Grund: Die Umgebungen in denen agil angewendet wird werden komplexer, große Teams und Teams von Teams arbeiten zusammen. „Das größte Mistverständnis ist: Viele skalieren an der falschen Stelle. Wie kann ich 150 Leute binnen 2 Monaten agil kriegen? Aber das wann dann bekommen ist wahrscheinlich doch etwas mechanisch. … eine Tücke an diesem Skalieren ist, dass die Leute es ist so schnell wollen." „In dem was wir gemacht haben sind ja auch eine Menge Techniken eingesetzt worden, die heute in SAFe drin sind. Aber sie sind eben nur da eingesetzt werden wo sie notwendig waren und nur so lange wie sie notwendig waren." „Und das ist auch eine Geschichte davon, dass Du dienen Softwareentwicklungsprozess selber besitzen musst." „Im Komplexen kommt man nicht drumrum dass man selber denken muss. Es gibt zwar Hilfestellungen, aber die eigentliche Arbeit muss man selber machen." „Die einzelnen Entwicklungsschritte in den Firmen sind nicht nachzuvollziehen, wenn man die Geschichte der vorangehenden Schritte nicht kennt." Skalieren Firmen an den richtigen Stellen? Sollten Banken eventuell alles auf den Kopf stellen und bei den Cobol-Systemen anfangen zu agilisieren? 01:49:34 Ausblick: Wie geht es weiter mit agil? Alle Großkonzerne werden einsteigen. Management und Leadership wird eine größere Rolle bekommen und auch die Theorie darüber wie Transitionen funktionieren. Scrum geht dahin zurück wo es herkommt: Zur Hardware-Entwicklung. Es gibt eine zweite Welle der Agilisierung für die Bestandteile der Unternehmen, die nicht software-Entwicklung ist. Die kleinen Startups in Berlin als Feigenblatt werden nicht für immer für die großen Konzerne funktionieren. Wahrscheinlich muss man doch an die verkrusteten Strukturen ran. Wrap Up: Ein paar Muster Ein paar Dinge, die bei mir hängen geblieben sind und die vielleicht auch nur erzählt werden können um klar zu machen, wie zufällig vieles im Moment wirkt und wie klar es im Nachhinein dann doch sein kann. Und auch wie stark das mit den Erwartungen an einen eventuell industrialisierteren Beratungsprozess kontrastiert, wie es sie heute vielleicht oft gibt.: In vieles snd wir einfach hineingestolpert und haben vieles einfach probiert. An vielem sind wir im ersten Anlauf gescheitert und haben es erst im Laufe der Zeit herausgefunden Im Nachhinein war alles klar und einfach. „Transitionen" klappen besser wenn der Grund klar ist commitment zur Transition klar ist und nicht in Frage gestellt werden kann auch wenn das „Wie“ noch nicht klar sein kann sich interne Mitarbeiter finden, die für das Theme wirklich brennen und die Freiheiten haben das Notwendige zu machen. Dazu gehört es auch, immer wieder Unbequemes anzusprechen und zu diskutieren. sonst ist Verbessern nicht möglich. Nichts klappt schnell, Eile im Umbau ist kontraproduktiv Man muss den (Software-Entwicklungs-)Prozess selber besitzen. man muss selber nachdenken und die Arbeit machen. Man wendet nur die wenigen Mittel an, die man gerade braucht und nur so lange man sie braucht. Ein paar Links aus der Episode it-agile, die Firma - Stefan Roock auf twitter, Bücher von Stefan bei amazon Henning Wolf auf twitter, Autorenseite bei amazon „XP explained" von Kent Beck Ken Schwaber bei Wikipedia „Kanban" von David Anderson, deutsche Ausgabe - „The Lean Startup" von Eric Ries - „Continuous Delivery" von Jez Humble - Blog von Arne Roock, Stefan’s Bruder und deutscher Kanban Pionier - LKCE Konferenz

In this episode that I speak with Rich Mironov, Roman PIchler, Steven Haines, Chad McAllister and Cindy Alvarez about the biggest mistakes product managers make. What will you learn – Biggest Mistakes!! You will learn about the biggest mistakes Product Managers make from these 5 successful product management experts. Orchestrate executive management Executive level roadmap clarity Disconnection between […]The post DYT 076 : Biggest Mistakes Product Managers Make appeared first on .

Roman Pichler on like PM roles, leadership styles, mindfulness, decision-making, and stakeholder management etc.

Richard and Dave Show Notes Podcast Topic - You’ve taken CSM Training and passed the Exam. Now what? In this podcast Certified Scrum Trainers Richard Cheng and Dave Prior share their thoughts on most important things that Certified Scrum Master students can do to be successful Scrum Masters once they have completed the training and passed the CSM Assessment Exam. The podcast includes an exploration of why each of the recommendations is critical to making Scrum work and both Richard and Dave share examples from their experiences in the field working with teams who did, and did not have these practices in play. Links Mentioned in the Podcast Geoffrey Moore Vision Statement https://www.joelonsoftware.com/2002/05/09/product-vision/ Crossing the Chasm by Geoffrey Moore http://amzn.to/2h3ruRS Roman Pichler’s website (where you can find the tools we mentioned) http://www.romanpichler.com Roman Pichler’s books https://www.amazon.com/Roman-Pichler/e/B00359XCV2/ref=sr_ntt_srch_lnk_1?qid=1482305119&sr=8-1 Contact Info Richard Cheng Works for Excella Consulting https://www.excella.com Twitter: https://twitter.com/RichardKCheng Email: richard.cheng@excella.com Dave Prior Works for LeadingAgile http://www.leadingagile.com Twitter https://twitter.com/mrsungo Email: mrsungo@gmail.com Blog: http://drunkenpm.blogspot.com The music featured in the podcast was downloaded from The Free Music Archive http://freemusicarchive.org Intro Song Cash Rules by Ari de Niro. For more info: http://www.needledrop.co/wp/artists/ari-de-niro/ or http://freemusicarchive.org/music/Ari_de_Niro/ Outro Song Cherry Skies - The New Mystical Troubadours. Find them here: http://freemusicarchive.org/music/The_New_Mystikal_Troubadours/

In this Topical Zoom episode of The Design Your Thinking Podcast, I speak with Roman Pichler who is a product management expert specialised in digital products, about Product Strategy and Roadmaps. Who is Roman Pichler? Roman Pichler is a product management expert specialised in digital products. He has 15 years experience in teaching product managers […]The post DYT 021 : What Product Managers Need to Know about Product Strategy and Roadmaps with Roman Pichler appeared first on .

    One of the best resources for Product Owners is Roman Pichler’s blogs and books. His latest book “Strategize” is a great source of information about Product Strategy and Roadmaps. Roman joins on this episode to discuss some of those areas of his book as well as the ideas around how best to use that information. It’s part of the job for PO’s to be constantly learning, and Roman is a great teacher.   Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host Roman Pichler - romanpichler.com & @romanpichler Strategize - Strategize Product Strategy Roadmap Practices Gregor Meyenberg - benefits-of-transparent-costs Amy Morin - 5 things to remember the next time you're tempted to say yes to something you don't want to do Luis Goncalves - NPS - Help PO structure Backlog  

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/

Breakthrough Radio is a global business radio show that delivers high impact & pioneering knowledge for leaders in business. Entrepreneurs, startups, sales/marketing/IT professionals join us every Monday. Fractional CMO, Digital Marketing Strategist, and Leadership Keynote Speaker Michele Price brings you weekly access to the top minds to Master the Inner and Outer Game of business. ? Roman Pichler, author and product management expert, Strategize -Product Strategy and Product Roadmap Practices for the Digital Age. Follow us & ask your questions via twitter using #BBSradio.  You are invited to visit radio show blog at www.TheBreakthroughRadio.com

Roman Pichler, one of the leading voices in Agile Product Ownership has released a new book, "Strategize: Product Strategy and Product Roadmap Practices for the Digital Age", that presents a number of tools and techniques Product Owners and Product Managers can use to gain a deeper understanding the product(s) they are developing in order to stock and maintain a better product backlog. Show Notes: Why the wrote Strategize 00:26 Adding Product Strategy to Agile Planning 2:46 Vision to Strategy to Roadmap 5:37 How to use the Go Product Roadmap to feed Release Planning 6:00 Who you need to create the Roadmap? 8:40 How Strategize should help Product Owners and Product Managers 10:30 Is the focus on Product Ownership increasing and maturing? 11:50 Explaining the difference between and Product Owner and a Product Manager? 15:20 The key elements of Product Strategy 19:20 Aligning products across the portfolio 21:24 Product Owner at the Portfolio level 23:00 How often should you update your Vision Board and Roadmap? 24:05 How important is it that Team Members know the Product Vision? 25:50 If there was one misunderstanding about Product Ownership that you could fix, what would it be? 27:54 How to get in touch with Roman 30:00 If you'd like to get in touch with Roman, you can reach him at http://www.romanpichler.com If you'd like to pick up a copy of Strategize, you can find it here: https://www.amazon.com/Strategize-Product-Strategy-Roadmap-Practices/dp/0993499201/ref=sr_1_1?ie=UTF8&qid=1466442777&sr=8-1&keywords=strategize

Fractional CMO, Digital Marketing Strategist, and Leadership Keynote Speaker Michele Price brings you weekly access to the top minds to Master the Inner and Outer Game of business.  Breakthrough Radio is a global business radio show that delivers high impact & pioneering knowledge for leaders in business. Entrepreneurs, startups, sales/marketing/IT professionals join us every Monday. Roman Pichler, author and product management expert, Strategize -Product Strategy and Product Roadmap Practices for the Digital Age. Michele Price, your fractional CMO delivers the Breakthrough Tips segment on "Mastering the Art of Execution". Yared Akalou, co-founder Opening.Co delivers the Breakthrough Byte segment on #FutureofWorkforce. Follow us & ask your questions via twitter using #BBSradio.  You are invited to visit radio show blog at www.TheBreakthroughRadio.com

Roman Pichler talks about strategy and roadmapping practices.

  Working with the delivery team and customers is not all a Product Owner has to do.  There are other people who are interested, invested, or yes even paying for the product you are trying to build.  Their buy-in and questions are key to getting and sustaining any agile product efforts.  Managing the stakeholders needs and expectations is an important piece to get right. In this episode, there are some tricks, priorities, and ideas to explore with stakeholders to keep them happy and you sane.         Feedback: twitter - @deliveritcast email - deliveritcast@gmail.com   Links: Co-host Post - http://deliveritcast.com/looking-for-a-new-co-host Jeremy Jarrell - Evil User Stories Derek Sivers - https://sivers.org/hellyeah Elizabeth Hendricksen - http://testobsessed.com/2015/05/i-prefer-this-over-that/ Roman Pichler - https://www.linkedin.com/pulse/stakeholder-analysis-power-interest-grid-roman-pichler Agile Modeling - http://agilemodeling.com/essays/activeStakeholderParticipation.htm

Jochen (Joe) Krebs speaks with Roman Pichler about agile product management, the role of the product owner and his book “Agile Product Management with Scrum”.

Jochen (Joe) Krebs speaks with Roman Pichler, Author of "Agile Product Management with Scrum" and expert in product and UX design. They discuss the role of a product owner in small and large organizations and the challenges that come with it. They also reflect on Roman's tools for product visioning and product strategy.

In dieser Episode spreche ich mit Roman Pichler, Autor des einzigen deutschsprachigen Buchs zum Thema "Agiles Produktmanagement". Es geht um Hintergründe von Product Ownern, wo sie herkommen, wie sie zu Product Ownern werden, und wie sie sich weiterbilden können. Dabei kommt natürlich auch viel zur Sprache, was ein Product Owner können muss.

In this episode, we discuss with Roman Pichler how Scrum impacts product management and how agile product management differs from traditional approaches. The topics covered include product owners on large projects and product owner teams, facilitating customer feedback through early and frequent releases, envisioning the product, and creating products with the minimum functionality. Enjoy!

In this episode, we discuss with Roman Pichler how Scrum impacts product management and how agile product management differs from traditional approaches. The topics covered include product owners on large projects and product owner teams, facilitating customer feedback through early and frequent releases, envisioning the product, and creating products with the minimum functionality. Enjoy!

In this episode, we discuss with Roman Pichler how Scrum impacts product management and how agile product management differs from traditional approaches. The topics covered include product owners on large projects and product owner teams, facilitating customer feedback through early and frequent releases, envisioning the product, and creating products with the minimum functionality. Enjoy!

This episode features Scrum, a very popular Agile software development framework. We interview Roman Pichler, a Certified ScrumMaster Trainer and independent consultant. Roman explains the principles behind Scrum, its roles and its key practices. He also answers FAQs. This episode continues our track on software development processes discussing an additional Agile method. Roman is currently writing a book on Scrum in German that provides more in-depth information of the topics discussed in the podcast. The book will be available in autumn 2007 published by d.punkt (Heidelberg, Germany).

This episode features Scrum, a very popular Agile software development framework. We interview Roman Pichler, a Certified ScrumMaster Trainer and independent consultant. Roman explains the principles behind Scrum, its roles and its key practices. He also answers FAQs. This episode continues our track on software development processes discussing an additional Agile method. Roman is currently writing a book on Scrum in German that provides more in-depth information of the topics discussed in the podcast. The book will be available in autumn 2007 published by d.punkt (Heidelberg, Germany).

This episode features Scrum, a very popular Agile software development framework. We interview Roman Pichler, a Certified ScrumMaster Trainer and independent consultant. Roman explains the principles behind Scrum, its roles and its key practices. He also answers FAQs. This episode continues our track on software development processes discussing an additional Agile method. Roman is currently writing a book on Scrum in German that provides more in-depth information of the topics discussed in the podcast. The book will be available in autumn 2007 published by d.punkt (Heidelberg, Germany).