Podcasts about product goal

Stop Doing Scrum All Wrong... Are you finding that Scrum isn't working for you? Do you constantly find that you're never quite able to complete your Sprint Backlog and even when you get close it never really feels like success? You're more of a feature factory than anything else. Well it's almost certainly because of this one thing. What is it? Let's find out! I've been using Scrum with teams and a variety of organisations for the past 20 years, God has it been that long! And when Scrum fatigue sets in it's almost always because the team are not using a Sprint and Product Goal or because they're using them in the wrong way. 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/

Is The Product Owner an Order Maker or Order Taker? In Scrum, the Product Owner includes the perspective of what is valuable (and what is not) regarding the product's ambitions. As the team spends time and money working on the product, the Product Owner ensures this investment returns value to the stakeholders. Close collaboration with the people who have a stake in the product and the developers is essential to decide what is valuable and what isn't. One product has one Product Owner and one Product Backlog with one Product Goal. To keep the speed at which decisions can be made high and adaptation can take place quickly, Product Owners need full mandate over the product. They have the ultimate say over what the ambitions for the product are, what goes on the Product Backlog and what doesn't, and how to spend the budget (or even set it). 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/

In 2020, the Scrum Guide introduced the idea of the Product Goal, but left out anything about Vision. Was this move better or worse for Scrum teams?In this short podcast, Vic Bonacci and Dave Prior, our two resident CSTs, sit down to discuss the difference between product goals and vision and the impact this change is making on Scrum Teams. Contacting Vic Bonacci If you'd like to contact Vic you can reach him at: LeadingAgile: https://www.leadingagile.com/guides/victor-bonacci LinkedIn: https://www.linkedin.com/in/vbonacci/ Email: Victor.Bonacci@leadingagile.com Contacting Dave Prior If you'd like to contact Dave, you can reach him at: LeadingAgile: www.leadingagile.com/guides/dave-prior/ LinkedIn: www.linkedin.com/in/mrsungo Twitter: twitter.com/mrsungo Email: dave.prior@leadingagile.com If you have a question you'd like to submit for an upcoming podcast, please send them to dave.prior@leadingagile.com Interested in CSM or CSPO Training? You can find all the details at www.leadingagile.com/scrum-training/

Is There Ever a Good Time For Multiple Product Owners? According to the scrum guide, there should be one product owner who is in charge of the product vision and decides what to do, to create a better product (Not how to do it!) The Scrum Guide states: “The Product Owner is one person, not a committee.” Yet, in some environments companies build products that are so complex and big that they need multiple teams to get the job done. For these situations the Scrum Guide states: “If Scrum Teams become too large, they should consider reorganizing into multiple cohesive Scrum Teams, each focused on the same product. Therefore, they should share the same Product Goal, Product Backlog, and Product Owner.” Contradictory to these suggestions, I observe that several companies feel the urgency to have multiple product owners for these situations. (They often argue that they “inspected and adapted” and in their case it is a necessary step to make Scrum work.) Let me share my thoughts on that. 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/⁠

In diesem Podcast spricht Jan Fischbach mit André Claaßen über das Produktziel in Scrum aus Sicht von OKR und wie es agilen Teams helfen kann, fokussiert zu bleiben und bessere Ergebnisse zu erzielen.

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/)

The product roadmap is a great product management tool. But it can cause significant issues when it is not used appropriately. In this podcast episode, I discuss ten product roadmapping mistakes you should avoid to fully leverage your roadmap.

The product backlog is a simple yet powerful tool to capture tactical product decisions and direct the work of the development team. To take full advantage of it, it's important to set up the initial backlog in the right way. This episode offers five practical tips to successfully stock the product backlog and lay the foundation for a successful development effort.

Making the right strategic decisions is crucial to achieve product success. If it's not clear, for example, what a product's value proposition is and what its stand-out features are, then it will be difficult to create the desired business value. But I find that many product teams do not use a systematic approach to create and evolve a product strategy. To put it differently, they lack a product strategy model. In this podcast episode, I describe the model that I have developed.

Você sabe de fato o que é o Product Goal dentro dos times Scrum? Em nossas redes sociais e em nossos cursos, os alunos sempre nos questionam sobre o Product Goal e para que de fato ele serve. Pensando nisso, o Rodrigo Pinto, Co-founder da Agile School e Agile.inc nos conta com dicas e exemplos de como aproveitar ao máximo o Product Goal dentro do seu time e como ele pode trazer mais resultados para a empresa. Nosso site: http://agileschool.com.br • Blog: https://agileschool.com.br/category/a… • Ouça nosso Podcast: - Spotify: https://spoti.fi/31GeHfy - iTunes:https://apple.co/31OAxNO • LinkedIn:https://www.linkedin.com/company/agil… • Instagram: https://www.instagram.com/agile.school/ • Facebook: https://www.facebook.com/agileschoolbr/ #productgoalandsprintgoal #metadoproduto #objetivodoproduto

The 2020 version of the Scrum guide introduced the notion of ''product goal' but big visions can sometimes be hard for scrum teams to wrap their heads around which can in turn affect empiricism. What is a product goal and how can we go about having one without affecting empiricism? My LinkedIn: https://www.linkedin.com/in/johncolem... Agility Island Podcast: https://anchor.fm/agilityisland #scrum #agile #kanban #productgoal #agility

When Does a Scrum Team Inspect their Product Goal? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. ⏩ Check out the Full Scrum Framework course with added bonus materials, guides, murals, resources, and LIVE INTERACTION with Ryan, Todd, and Daria: https://community.agileforhumans.com/share/z2K_YMahKAiXn9T9?utm_source=manual 🔥 This Scrum Framework online training course introduces you to the Scrum Framework and gives you fasted path to Scrum Master knowledge and certification. This course will teach you the basics of Scrum and prepare you to take Scrum.org's Professional Scrum Master I (PSM I) assessment. This is the best first step you can take down your path to Scrum mastery! 👉 Professional Scrum Master I (PSM I) assessment: https://www.scrum.org/professional-scrum-master-i-certification Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring practical materials and guides to the course. Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 For more information about Agile for Humans, visit: - Community: https://community.agileforhumans.com  - Facebook: https://www.facebook.com/agileforhumans  - Twitter: https://twitter.com/agileforhumans  - LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc - Website: https://www.agileforhumans.com For more information about Daria and ScrumMastered: - LinkedIn: https://www.linkedin.com/in/dariabagina/ - Facebook: https://www.facebook.com/scrummastered - Twitter: https://twitter.com/bescrummastered - Instagram: https://www.instagram.com/scrummastered/ See omnystudio.com/listener for privacy information.

Produkt Vision Im Agilen liest man häufig, dass es eine Produkt Vision geben soll. Doch was ist das überhaupt und wie kommen wir dahin? Im aktuellen Scrum Guide wurde die Produkt Vision auch durch das Product Goal ersetzt. Falls Du Dich wunderst, wo dies denn im Guide stünde. Dabei soll die Produkt Vision eine grobe... The post Folge 106 Produkt Vision 1/2 appeared first on Znipcast - für gute Zusammenarbeit | Agilität, Scrum, KanBan, Psychologie, Teamentwicklung und NLP | Podcast der Znip Academy.

Can a Scrum Team Abandon a Product Goal? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley.  ⏩ Check out the Full Scrum Framework course with added bonus materials, guides, murals, resources, and LIVE INTERACTION with Ryan, Todd, and Daria: https://community.agileforhumans.com/share/z2K_YMahKAiXn9T9?utm_source=manual 🔥 This Scrum Framework online training course introduces you to the Scrum Framework and gives you fasted path to Scrum Master knowledge and certification. This course will teach you the basics of Scrum and prepare you to take Scrum.org's Professional Scrum Master I (PSM I) assessment. This is the best first step you can take down your path to Scrum mastery! 👉 Professional Scrum Master I (PSM I) assessment: https://www.scrum.org/professional-scrum-master-i-certification Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring practical materials and guides to the course. Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 For more information about Agile for Humans, visit: - Community: https://community.agileforhumans.com  - Facebook: https://www.facebook.com/agileforhumans  - Twitter: https://twitter.com/agileforhumans  - LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc - Website: https://www.agileforhumans.com For more information about Daria and ScrumMastered: - LinkedIn: https://www.linkedin.com/in/dariabagina/ - Facebook: https://www.facebook.com/scrummastered - Twitter: https://twitter.com/bescrummastered - Instagram: https://www.instagram.com/scrummastered/ See omnystudio.com/listener for privacy information.

What's an Example of a Product Goal and a Sprint Goal? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. ⏩ Check out the Full Scrum Framework course with added bonus materials, guides, murals, resources, and LIVE INTERACTION with Ryan, Todd, and Daria: https://community.agileforhumans.com/share/z2K_YMahKAiXn9T9?utm_source=manual 🔥 This Scrum Framework online training course introduces you to the Scrum Framework and gives you fasted path to Scrum Master knowledge and certification. This course will teach you the basics of Scrum and prepare you to take Scrum.org's Professional Scrum Master I (PSM I) assessment. This is the best first step you can take down your path to Scrum mastery! 👉 Professional Scrum Master I (PSM I) assessment: https://www.scrum.org/professional-scrum-master-i-certification Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring practical materials and guides to the course. Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 For more information about Agile for Humans, visit: - Community: https://community.agileforhumans.com  - Facebook: https://www.facebook.com/agileforhumans  - Twitter: https://twitter.com/agileforhumans  - LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc - Website: https://www.agileforhumans.com For more information about Daria and ScrumMastered: - LinkedIn: https://www.linkedin.com/in/dariabagina/ - Facebook: https://www.facebook.com/scrummastered - Twitter: https://twitter.com/bescrummastered - Instagram: https://www.instagram.com/scrummastered/ See omnystudio.com/listener for privacy information.

What's an Example of a Product Goal and a Sprint Goal? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. ⏩ Check out the Full Scrum Framework course with added bonus materials, guides, murals, resources, and LIVE INTERACTION with Ryan, Todd, and Daria: https://community.agileforhumans.com/share/z2K_YMahKAiXn9T9?utm_source=manual 🔥 This Scrum Framework online training course introduces you to the Scrum Framework and gives you fasted path to Scrum Master knowledge and certification. This course will teach you the basics of Scrum and prepare you to take Scrum.org's Professional Scrum Master I (PSM I) assessment. This is the best first step you can take down your path to Scrum mastery! 👉 Professional Scrum Master I (PSM I) assessment: https://www.scrum.org/professional-scrum-master-i-certification Professional Scrum Trainers Todd Miller and Ryan Ripley built this course to help those interested in Scrum get up and running quickly using the Framework. They've partnered with Daria Bagina from ScrumMastered to bring practical materials and guides to the course. Todd and Ryan also co-authored a book - Fixing Your Scrum: Practical Solutions to Common Scrum Problems. 👉 Buy Fixing Your Scrum at Amazon: https://amzn.to/3BMvkcX ✅Subscribe to our Channel to learn more about Agile, Scrum, and Kanban: https://www.youtube.com/agileforhumans?sub_confirmation=1 For more information about Agile for Humans, visit: - Community: https://community.agileforhumans.com  - Facebook: https://www.facebook.com/agileforhumans  - Twitter: https://twitter.com/agileforhumans  - LinkedIn: https://www.linkedin.com/company/agile-for-humans-llc - Website: https://www.agileforhumans.com For more information about Daria and ScrumMastered: - LinkedIn: https://www.linkedin.com/in/dariabagina/ - Facebook: https://www.facebook.com/scrummastered - Twitter: https://twitter.com/bescrummastered - Instagram: https://www.instagram.com/scrummastered/ See omnystudio.com/listener for privacy information.

Es gibt viel zu tun und die Ideen werden nicht weniger. Schnell stellt sich dann das Gefühl ein, dass das eigene Team einfach zu klein ist und man das gar nicht alles schaffen kann. Es sind halt einfach zu wenige Entwickler im Team. Dominique und Oliver sprechen in dieser Folge darüber, wann der Eindruck zu weniger Entwickler entsteht und welche Lösungsstrategien wir als Product Owner haben. Dazu müssen wir aber zuerst klären: Ist die geringe Teamgröße das Problem oder vielmehr das Symptom für ein anderes Problem. Ausgehend von dieser Frage entstand eine spannende Diskussion über mögliche Gründe, warum wir als Product Owner den Eindruck haben können, dass wir zu wenige Entwickler im Team haben. Das kann zum Beispiel damit zusammenhängen, welche Erwartungshaltungen an Output und/oder Outcome wir (Stakeholder, aber auch wir selbst) stellen. Auch ein sehr volles Product Backlog kann diesen Eindruck direkt erhöhen; der Zufluss ist größer als die Umsetzung. Vielleicht entsteht der Eindruck zu weniger Entwickler aber auch, weil nicht alle notwendigen Fertigkeiten im Team vorhanden sind (z. B. weil die Sprintziele nicht erreicht werden). Nichtsdestotrotz sprechen die beiden über konkrete Lösungsstrategien. Dazu gehören zum Beispiel ein stärkerer Fokus auf Priorisierung, das Outsourcen von Aufgaben oder das stringente Verfolgen der Produktvision und des Product Goals. Durch die Unterstützung durch Scrum Master und Team können verschiedene Lösungen aufgedeckt und umgesetzt werden, die wir vielleicht alleine gar nicht auf dem Schirm gehabt hätten. Wenn ihr mehr zu einzelnen Themen erfahren wollt, haben wir hier noch ein paar passende Folgen für euch: - Sprintziele: https://produktwerker.de/sprint-ziel-als-product-owner/ - Priorisieren von Anforderungen: https://produktwerker.de/priorisieren-von-anforderungen/ - Produktvision: https://produktwerker.de/wie-die-produktvision-hilft-product-ownern-eine-richtung-zu-geben/ - Product Goal: https://produktwerker.de/das-product-goal-und-seine-bedeutung-fuer-product-owner/

On this episode, Brian Orlando and Om Patel discuss the product that is the Agile Podcast! We discuss what we've learned this year, what future ideas do we have up our sleeves for shows and guests, and what changes to the product are we thinking about...0:00 Topic Intro0:35 Clip-show VS Podcasting3:30 Product Discussion: 5-Minute Monologue5:15 Clips from the Agile Podcast6:42 Takeaway - Splitting Channels9:43 Clips and Production "Tricks"13:06 Product Goal of the Podcast15:26 Future Guest, Curtis Round 217:33 Future Guests, by Role22:33 Future Topic: Non-Agile Companies24:11 Future Topic: Spotify Model29:49 Future Topic: Trainers without Experience31:47 Future Topic: Spotify, Again36:54 Other Future Topics39:20 Tangent on Asking for a Pay Raise40:27 Process of Doing the Podcast43:04 Remote Guests44:08 Future Topic: Product Blind-spots45:33 Wrap-Up= = = = = = = = = = = = Also available on YouTube:https://youtu.be/iJNyoTcr4z8Please Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1= = = = = = = = = = = = 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= = = = = = = = = = = = AP42 - Agile Podcast Year-End Retrospective

Das Priorisieren von Anforderungen gehört für die Verantwortung als Product Owner zu den wichtigsten Aufgaben. Die Anzahl der Möglichkeiten unser Produkt weiter zu entwickeln ist schier unendlich und da unsere Umsetzungskapazitäten beschränkt sind, müssen wir die im Moment wertvolleren Anforderungen von den weniger wertvollen unterscheiden. In dieser Folge sprechen Dominique und Oliver nicht nur über Techniken wie der Priorisierung nach Eisenhower, der MoSCoW-Technik, Bewertung von Merkmalen nach Kano oder der gewichteten Priorisierung. Sie reflektieren auch, in wie weit Priorisieren überhaupt im Rahmen der Product Backlog Pflege statt finden sollte. Ergibt sich die Wichtigkeit nicht schon aus Product Roadmap, Product Goal und Product Vision? Wir haben das Kano-Modell in dieser Folge etwas kürzer gehalten, da wir es in einer anderen Folge schon ausführlicher besprochen haben (https://produktwerker.de/kano-modell/). Dominique sprach in der Folge außerdem auch von einer gewichteten Priorisierung. Mehr Informationen dazu findet ihr unter https://www.processimpact.com/articles/prioritizing.pdf. Wenn euch die Folge gefallen hat würden wir uns über Feedback in eurem Podcatcher oder auf unserer Website freuen.

Who Creates the Product Goal on a Scrum Team? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. What do you think? Let us know in the comments! Take a Professional  Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti! https://www.eventbrite.com/e/professional-scrum-with-kanban-psk-online-certification-class-psk-i-tickets-167900832911 Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -  https://amzn.to/3fMpH5a Join Ryan and Todd in a Professional Scrum Master course:  https://www.scrum.org/agile-humans And make sure you subscribe to the channel! DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week! FTC DISCLAIMER: This video is not sponsored by anyone. Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems. #scrum #agile #scrummaster See omnystudio.com/listener for privacy information.

Can the Product Goal Change in Scrum? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. What do you think? Let us know in the comments! Take a Professional  Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti! https://www.eventbrite.com/e/professional-scrum-with-kanban-psk-online-certification-class-psk-i-tickets-167900832911 Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems -  https://amzn.to/3fMpH5a Join Ryan and Todd in a Professional Scrum Master course:  https://www.scrum.org/agile-humans And make sure you subscribe to the channel! DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week! FTC DISCLAIMER: This video is not sponsored by anyone. Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems. #scrum #agile #scrummaster See omnystudio.com/listener for privacy information.

Durch das Refinement wird das Product Backlog zu einem gut gepflegten Product Backlog und ist dadurch ein wichtiges Werkzeug für Product Owner. Tim und Dominique unterhalten sich in dieser Folge über das Refinement des Product Backlogs und welche Bedeutung es für uns als Product Owner hat. Zu Beginn klären wir erst einmal, was Refinement eigentlich ist und wie es in Scrum passt. Das Refinement wird zwar oft als Termin gesehen, ist aber eigentlich ein Prozess. Deshalb sprechen wir über den allgemeinen Ablauf des Refinements, wer alles mitwirkt und was wir als Product Owner vorbereiten sollten. Wir sind nämlich davon überzeugt, dass wir neben Vision und Product Goal auch eine aktuelle Roadmap dabei haben sollten. Dank dem Refinement haben wir dann nicht nur ein gepflegtes Product Backlog; wir erhalten auch neuen Input für die Priorisierung von Product Backlog Items und erlangen ein Verständnis über Umfang, Kosten, Risiken und anderer Aspekte der ganzen Backlog Items. Wir können daher dank des Refinements bessere Entscheidungen treffen. Und wie in jeder Folge wollen wir mit ein paar Tipps abschließen. Habt ihr beispielsweise mal daran gedacht das Refinement eines bestimmten Themas als Product Backlog Item einzuplanen, damit im nächsten Sprint an diesem Thema gearbeitet wird? In der Folge erwähnen wir übrigens kurz das Product Backlog Refinement Canvas, eine gut geeignete Vorlage, um sich eine strukturierte Übersicht zu machen. Ihr findet es unter https://www.kaizenko.com/the-product-backlog-refinement-canvas/ Wenn ihr noch mehr über das Product Backlog hören wollt, dann empfehlen wir euch die folgenden Folgen: - Das Product Backlog (https://produktwerker.de/product-backlog/) - Ist dein Product Backlog voll bzw. zu groß? (https://produktwerker.de/product-backlog-voll/) - Product Backlog Einträge sind nicht nur User Stories! (https://produktwerker.de/product-backlog-eintraege/) Wenn euch dieser Podcast gefällt, freuen wir uns auch über eine positive Bewertung in eurer Podcast App oder als Feedback per Mail an podcast@produktwerker.de oder via Instagram oder Twitter (@produktwerker).

Can the Product Goal Change in Scrum? Let's explore the options this situation presents. All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. What do you think? Let us know in the comments! Take a Professional Scrum with Kanban Course with Todd, Ryan, and Daniel Vacanti!https://www.eventbrite.com/e/professional-scrum-with-kanban-psk-online-certification-class-psk-i-tickets-167900832911 Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems - https://amzn.to/3fMpH5a Join Ryan and Todd in a Professional Scrum Master course: https://www.scrum.org/agile-humans And make sure you subscribe to the channel! DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week! FTC DISCLAIMER: This video is not sponsored by anyone. Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems. #scrum #agile #scrummasterSee omnystudio.com/listener for privacy information.

The product backlog is a simple yet powerful tool to capture and revise detailed product decisions and direct the work of the development team. Unfortunately, effectively using the backlog can be challenging. This episode discusses seven common product backlog mistakes to help you recognise and fix them.

Dave Prior and Lance Kind discuss a new item from the Scrum Guide: Product Goal. Listen in while Dave teaches Lance what the product goal is, ideates on how to implement, and debates as to the value product goal provides. As a bonus, Dave and Lance: discuss how “real options” relate to product backlogs, that there will be a struggle about where to put backlog items that don't fit the product goal, and how computers have become like the Tardis.

Scrum Values Successful use of Scrum depends on people becoming more proficient in living five values: Commitment, Focus, Openness, Respect, and Courage The Scrum Team commits to achieving its goals and to supporting each other. Their primary focus is on the work of the Sprint to make the best possible progress toward these goals. The Scrum Team and its stakeholders are open about the work and the challenges. Scrum Team members respect each other to be capable, independent people, and are respected as such by the people with whom they work. The Scrum Team members have the courage to do the right thing, to work on tough problems. These values give direction to the Scrum Team with regard to their work, actions, and behavior. The decisions that are made, the steps taken, and the way Scrum is used should reinforce these values, not diminish or undermine them. The Scrum Team members learn and explore the values as they work with the Scrum events and artifacts. When these values are embodied by the Scrum Team and the people they work with, the empirical Scrum pillars of transparency, inspection, and adaptation come to life building trust. Scrum Team Developers Developers are the people in the Scrum Team that are committed to creating any aspect of a usable Increment each Sprint. The specific skills needed by the Developers are often broad and will vary with the domain of work. However, the Developers are always accountable for: ● Creating a plan for the Sprint, the Sprint Backlog ● Instilling quality by adhering to a Definition of Done ● Adapting their plan each day toward the Sprint Goal ● Holding each other accountable as professionals Product Owner The Product Owner is also accountable for effective Product Backlog management, which includes: ● Developing and explicitly communicating the Product Goal ● Creating and clearly communicating Product Backlog items ● Ordering Product Backlog items ● Ensuring that the Product Backlog is transparent, visible and understood The Scrum Master serves the Scrum Team in several ways, including: ● Coaching the team members in self-management and cross-functionality ● Helping the Scrum Team focus on creating high-value Increments that meet the Definition of Done ● Causing the removal of impediments to the Scrum Team's progress ● Ensuring that all Scrum events take place and are positive, productive, and kept within the timebox The Scrum Master serves the Product Owner in several ways, including: ● Helping find techniques for effective Product Goal definition and Product Backlog management ● Helping the Scrum Team understand the need for clear and concise Product Backlog items ● Helping establish empirical product planning for a complex environment ● Facilitating stakeholder collaboration as requested or needed The Scrum Master serves the organization in several ways, including: ● Leading, training, and coaching the organization in its Scrum adoption ● Planning and advising Scrum implementations within the organization ● Helping employees and stakeholders understand and enact an empirical approach for complex work ● Removing barriers between stakeholders and Scrum Teams Aleph Technologies specializes in providing hands-on classroom-based and onsite IT certification training courses taught by expert instructors with practical industry experience. Classes span focuses on Business Analysis, Health Insurance & Systems Domain, IT Project Management, and IT Services with emphasis on Certified #SCRUM Master, #ScaledAgile #Certifications in Dallas and leadership roles in #Agile development. Since 2000, over 3000 course participants from more than 100 organizations across the globe have enhanced their skills through intensive, applicable exercises and education. https://www.aleph-technologies.com/ https://www.aleph-technologies.com/events https://www.aleph-technologies.com/courses https://www.aleph-technologies.com/trainers We guide you through your #Agile Transformation. --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

Scrum Events The Sprint is a container for all other events. Each event in Scrum is a formal opportunity to inspect and adapt Scrum artifacts. These events are specifically designed to enable the transparency required. Optimally, all events are held at the same time and place to reduce complexity. The Sprint Sprints are the heartbeat of Scrum, where ideas are turned into value. They are fixed length events of one month or less to create consistency. All the work necessary to achieve the Product Goal, including Sprint Planning, Daily Scrums, Sprint Review, and Sprint Retrospective, happen within Sprints. During the Sprint: ● No changes are made that would endanger the Sprint Goal ● Quality does not decrease ● The Product Backlog is refined as needed ● Scope may be clarified and renegotiated with the Product Owner as more is learned Sprints enable predictability by ensuring inspection and adaptation of progress toward a Product Goal at least every calendar month. A Sprint could be cancelled if the Sprint Goal becomes obsolete. Only the Product Owner has the authority to cancel the Sprint. Sprint Planning Sprint Planning initiates the Sprint by laying out the work to be performed for the Sprint. This resulting plan is created by the collaborative work of the entire Scrum Team. The Scrum Team may also invite other people to attend Sprint Planning to provide advice. Sprint Planning addresses the following topics: Topic One: Why is this Sprint valuable? The Product Owner proposes how the product could increase its value and utility in the current Sprint. Topic Two: What can be Done this Sprint? Through discussion with the Product Owner, the Developers select items from the Product Backlog to include in the current Sprint. Selecting how much can be completed within a Sprint may be challenging. Topic Three: How will the chosen work get done? For each selected Product Backlog item, the Developers plan the work necessary to create an Increment that meets the Definition of Done. The Sprint Goal, the Product Backlog items selected for the Sprint, plus the plan for delivering them are together referred to as the Sprint Backlog. Sprint Planning is timeboxed to a maximum of eight hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. Daily Scrum The purpose of the Daily Scrum is to inspect progress toward the Sprint Goal and adapt the Sprint Backlog as necessary, adjusting the upcoming planned work. Sprint Review The purpose of the Sprint Review is to inspect the outcome of the Sprint and determine future adaptations. The Scrum Team presents the results of their work to key stakeholders and progress toward the Product Goal is discussed. The Sprint Review is the second to last event of the Sprint and is timeboxed to a maximum of four hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. Sprint Retrospective The purpose of the Sprint Retrospective is to plan ways to increase quality and effectiveness. The Sprint Retrospective concludes the Sprint. It is timeboxed to a maximum of three hours for a one-month Sprint. For shorter Sprints, the event is usually shorter. Aleph Technologies specializes in providing hands-on classroom-based and onsite IT certification training courses taught by expert instructors with practical industry experience. Classes span focuses on Business Analysis, Health Insurance & Systems Domain, IT Project Management, and IT Services with emphasis on Certified #SCRUM Master, #ScaledAgile #Certifications in Dallas and leadership roles in #Agile development. Since 2000, over 3000 course participants from more than 100 organizations across the globe have enhanced their skills through intensive, applicable exercises and education. https://www.aleph-technologies.com/ https://www.aleph-technologies.com/ev... https://www.aleph-technologies.com/co... https://www.aleph-technologies.com/tr... We guide you through your #Agile Transformation. Reap the benefits of --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

Scrum Artifacts Scrum's artifacts represent work or value. They are designed to maximize transparency of key information. Thus, everyone inspecting them has the same basis for adaptation. Each artifact contains a commitment to ensure it provides information that enhances transparency and focus against which progress can be measured: ● For the Product Backlog it is the Product Goal ● For the Sprint Backlog it is the Sprint Goal ● For the Increment it is the Definition of Done These commitments exist to reinforce empiricism and the Scrum values for the Scrum Team and their stakeholders. Product Backlog The Product Backlog is an emergent, ordered list of what is needed to improve the product. It is the single source of work undertaken by the Scrum Team. The Developers who will be doing the work are responsible for the sizing. The Product Owner may influence the Developers by helping them understand and select trade-offs. Commitment: Product Goal The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal. The Sprint Backlog is a plan by and for the Developers. It is a highly visible, real-time picture of the work that the Developers plan to accomplish during the Sprint in order to achieve the Sprint Goal. Consequently, the Sprint Backlog is updated throughout the Sprint as more is learned. It should have enough detail that they can inspect their progress in the Daily Scrum. Commitment: Sprint Goal The Sprint Goal is the single objective for the Sprint. The Sprint Goal is created during the Sprint Planning event and then added to the Sprint Backlog. Increment An Increment is a concrete stepping stone toward the Product Goal. Each Increment is additive to all prior Increments and thoroughly verified, ensuring that all Increments work together. In order to provide value, the Increment must be usable. Multiple Increments may be created within a Sprint. The sum of the Increments is presented at the Sprint Review thus supporting empiricism. However, an Increment may be delivered to stakeholders prior to the end of the Sprint. The Sprint Review should never be considered a gate to releasing value. Work cannot be considered part of an Increment unless it meets the Definition of Done. Commitment: Definition of Done The Definition of Done is a formal description of the state of the Increment when it meets the quality measures required for the product. The moment a Product Backlog item meets the Definition of Done, an Increment is born. If the Definition of Done for an increment is part of the standards of the organization, all Scrum Teams must follow it as a minimum. If it is not an organizational standard, the Scrum Team must create a Definition of Done appropriate for the product. The Developers are required to conform to the Definition of Done. If there are multiple Scrum Teams working together on a product, they must mutually define and comply with the same Definition of Done. Aleph Technologies specializes in providing hands-on classroom-based and onsite IT certification training courses taught by expert instructors with practical industry experience. Classes span focuses on Business Analysis, Health Insurance & Systems Domain, IT Project Management, and IT Services with emphasis on Certified #SCRUM Master, #ScaledAgile #Certifications in Dallas and leadership roles in #Agile development. Since 2000, over 3000 course participants from more than 100 organizations across the globe have enhanced their skills through intensive, applicable exercises and education. https://www.aleph-technologies.com/ https://www.aleph-technologies.com/ev... https://www.aleph-technologies.com/co... https://www.aleph-technologies.com/tr... We guide you through your #Agile Transformation. Reap the benefits of Aleph Technologies' expertise applying #Agile methods --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

Com a mais nova atualização do Scrum Guide, algumas mudanças e novos elementos foram adicionados à ele, e uma delas foi o Product Goal. Fizemos uma live sobre comentando sobre toda essa atualização, e claro que o Product Goal também foi abordado, que é o que trazemos neste episódio. Tem dúvidas sobre esse assunto? Alguma sugestão de conteúdo que quer ver por aqui? Deixe aqui nos comentários! • Nosso site: http://agileschool.com.br • Blog: https://agileschool.com.br/category/a… • Ouça nosso Podcast: - Spotify: https://spoti.fi/31GeHfy - iTunes:https://apple.co/31OAxNO • LinkedIn:https://www.linkedin.com/company/agil… • Instagram: https://www.instagram.com/agile.school/ • Facebook: https://www.facebook.com/agileschoolbr/ ​ Qualquer outra dúvida, só mandar e-mail no faleconosco@agileschool.com.br #productgoal #productgoalscrum #mudancascrumguide

Today's question explores when a Product Goal is created on a Scrum Team. Should a Scrum Team do this during Sprint Planning? Does the Product Owner do this on their own? All of this and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. When does your Scrum Team create their Product Goals? Let us know in the comments! This is one of those Scrum Master interview questions about Scrum that can throw you off. Do you understand the need for a Product Goal? These Scrum Master day in the life questions can be tricky. Perhaps some Scrum Master training could help? Want to learn more about Scrum? Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems - https://amzn.to/3fMpH5a Join Ryan and Todd in a Professional Scrum Master course: https://www.scrum.org/agile-humans And make sure you subscribe to the channel! DISCLAIMER: Links included in this description might be affiliate links. If you purchase a product or service with the links that I provide, I may receive a small commission. There is no additional charge for you! Thank you for supporting the channel so we can continue to provide you with free content each week! FTC DISCLAIMER: This video is not sponsored by anyone. Sharing Scrum knowledge to help you grow as a Scrum Practitioner and to solve complex problems. #scrum #agile #professional scrumSee omnystudio.com/listener for privacy information.

In November of 2020, Ken Schwaber and Jeff Sutherland released an update to the Scrum Guide. One of the changes they introduced was the Product Goal. This is a change which, to me, seemed like a brilliant way to keep the Product Backlog focused on achieving a measurable outcome, but at the same time, it seemed at odds with how I had come to think about and work with a Product Backlog. For the past few months, I’ve been speaking with Agile and Scrum thought leaders in podcast interviews, trying to get my head around the concept. All of the conversations have helped me deepen my understanding of this topic, but the ones I have had with Don McGreal reshaped how I understand the way that the Product Goal impacts my entire understanding of a Product Backlog and how to work with it. Don McGreal is the VP of Learning Solutions at Improving, the co-Author of The Professional Product Owner book, the co-founder of TastyCupcakes.org, and a Scrum.org Professional Scrum Trainer. He’s also a really nice guy and he was kind enough to spend some time talking with me about the Product Goal. In this interview, Don shares how 4DX has impacts his approach to Product Ownership, working with the Product Backlog, and how it fits with the Product Goal serving as a measurable step towards achieving the Product Vision. As Don and I continue the discussion we explore some of the choices that Product Goal is going to force you to make about how you work with a Product Backlog. For example: If the Scrum Team is focused on one Product Goal at a time, and all the work in the Product Backlog should serve the Product Goal, what do we do with technical debt? If you are trying to get your head around Product Goal, this interview is going to pose some important questions that require you to reconsider how your team (and your organization) works with a Product Backlog, what jobs you are hiring it to do, and how to be disciplined, but not dogmatic in your practice of Scrum. Links - The Scrum Guide (November 2020) https://scrumguides.org - 4 DX: https://www.franklincovey.com/the-4-disciplines/ - The Professional Product Owner: https://amzn.to/3eVXkkV - TastyCupcakes: https://www.tastycupcakes.org - Upcoming classes at Improving: https://improving.com/training - Improving's Virtual Events: https://improving.com/virtual-events - Ralph Jocham's Product Goal Canvas: https://effectiveagile.com/download/productgoalcanvas/ Contacting Don - Improving.com: https://improving.com - LinkedIn: https://www.linkedin.com/in/donmcgreal/ - Email: donmcgreal@gmail.com - Twitter: https://twitter.com/donmcgreal

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

TLDR - My podcast interview with Scrum.org CEO Dave West on the Product Goal - what is it, how do I work with it. In November 2020 Jeff Sutherland and Ken Schwaber introduced a new version of the Scrum Guide. There are a number of changes they introduced to Scrum in the update, including the topic of Product Goal. Here is what the Scrum Guide says about Product Goal: “The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define “what” will fulfill the Product Goal. A product is a vehicle to deliver value. It has a clear boundary, known stakeholders, well-defined users, or customers. A product could be a service, a physical product, or something more abstract. The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next.” Initially, I found this mildly at odds with respect to how I tend to think of the Product Backlog - as a set of options... all the things we could do. And the more I tried to understand it, the more I felt it slipping through my fingers. I've raised my concerns about the Product Goal in a few other interviews recently, but I got to a point where I knew I needed help getting my head around it. So I reached out and I am deeply indebted to the folks from Scrum.org who were kind enough to share their time and wisdom with me. This interview with Scrum.org CEO, Dave West, is one in a series of podcasts I am going to post on the topic. Dave not only helped me get a better understanding of the concept, but he challenged me with something towards the end of the interview that helped me shake off my dogmatic blues and re-embrace the idea of Scrum being a framework that is meant to be adapted. Links from the podcast - The Scrum Guide: https://scrumguides.org - What is Scrum at Scrum.org https://www.scrum.org/resources/what-is-scrum - Ralph Jocham's Product Goal Canvas https://bit.ly/3eRu519 - The Professional Product Owner: Leveraging Scrum as a Competitive Advantage by Don McGreal and Ralph Jocham https://amzn.to/33c2n9Z Previous Interviews that involve Product Goal: - The Product Goal w/ Ryan Ripley: https://soundcloud.com/drunkenpmradio/the-product-goal-w-ryan-ripley - Scrum Guide 2020: Scrum Artifacts w Chris Li: https://soundcloud.com/drunkenpmradio/scrum-guide-2020-scrum-artifacts-w-chris-li If you'd like to contact Dave West you can find him here: - Email: Dave.West@Scrum.org - LinkedIn: https://www.linkedin.com/in/davidjustinwest/ - Scrum.org: https://www.scrum.org/scrumorg-staff - Twitter: https://twitter.com/DavidJWest

Das Sprint Planning ist für Product Owner ein wichtiges Event in Scrum. Dennoch passieren oft zahlreiche Fehler im Hinblick auf Selbstorganisation und Product Ownership des ganzen Teams. Zudem fühlt das Planning sich für viele Product Owner auch häufig eher merkwürdig an. Oliver und Dominique berichten von ihren eigenen Erfahrungen und welche Fehler ihnen selbst im Sprint Planning schon unterlaufen sind. Im Gespräch beleuchten die beiden das Event aus Sicht des Product Owners. Dabei geht es sowohl um die Zweck, den das Planning für den Product Owner erfüllen soll, welche Vorbereitungen man treffen sollte und letztlich wie ich ein gutes Sprint Planning als Product Owner gestalte. Die Ergebnisse aus dem Sprint Planning haben einen großen Einfluss auf den Erfolg eines Sprints. Daher ist es so wichtig, die drei grundsätzlichen Fragestellungen gut zu bearbeiten: Warum, Was und Wie? Warum? Als Product Owner solltest Du einen Vorschlag machen, warum es Sinn macht, in den nächsten Sprint zu investieren und damit dem Team auch die Relevanz erklären können. Den Kontext für das kommende Sprintziel geben dabei Produktvision, Roadmap und Product Goal. Was? In diesem Schritt erfolgt die Auswahl der Product Backlog Elemente und ihre Übernahme in das Sprint Backlog durch bzw. gemeinsam mit den Developern. Dabei sollte der Fokus darauf liegen, was zur Erfüllung des Sprintziels notwendig ist und nicht ob die Auslastung aller Teammitglieder sichergestellt ist. Schließlich wollen wir primär den Wert des Produkts maximieren und nicht die Auslastung optimieren. Wie? Während die Developer in diesem Schritt planen, wie sie während der Iteration vorgehen wollen, um das Sprint Goal zu erreichen, nimmt der Product Owner eine passive Rolle ein und steht mindestens für weitere Rückfragen und Entscheidungen zur Verfügung. Stolperfalle: hier geht es ums Planen, wie das Team das "Wie" angeht - noch nicht um die (technische) Konzeption und Lösungsfindung an sich! Als Ergebnis vom Sprint Planning haben wir ein vollständiges Sprint Backlog. Dies umfasst das Sprintziel, die ausgewählten Items und den gemeinsam erstellten Plan für Umsetzung.

This week on the Agile Coaches’ Corner Dan and Sam are switching things up with a new episode format. In this episode, they’re looking back on Sam’s three-part Trainer Talk series on the key changes that were made in the new Scrum Guide that was released in November 2020.   This episode compiles all three of Sam’s Trainer Talks that focus on the three key changes that were made to the Scrum Guide around the product goal, the sprint goal, and self-organizing teams. Sam shares his thoughts on why these changes are important to recognize; what these changes mean for organizations, Scrum Teams, and Product Owners; and the specific benefits that come with these changes.   Tune in to learn all about the three key changes that organizations using Scrum need to pay close attention to!   Key Takeaways How has the Product Goal Changed with the New Scrum Guide? Why is it important and what are the benefits? What the Scrum Guide has to say about the Product Goal: “The Product Goal describes a future state of the product which can serve as a target for the Scrum Team to plan against. The Product Goal is in the Product Backlog. The rest of the Product Backlog emerges to define ‘what’ will fulfill the Product Goal” The Scrum Guide is now making the Product Goal an explicit part of Scrum (which is crucial in creating a unified vision for the team to work toward) This change highlights the difference between a Product Goal and a Product Vision which is important because a product vision is lacking the characteristics of SMART goals (“specific, measurable, achievable, relevant, and time-bound” goals) With the Product Goal in the Product Backlog, the rest of the Product Backlog emerges to define WHAT will fulfill the Product Goal (this has specific benefits such as creating transparency, understanding what the value is that is expected to be created so that the team can validate if their efforts are creating the desired outcome, and in helping the team understand what should be in the Product Backlog vs. what should be out of it) With a Product Goal being in the Product Backlog and the rest of the Product Backlog emerging around that, it is possible to validate PBIs against the Product Goal The Scrum Guide also says that “The Product Goal is the long-term objective for the Scrum Team. They must fulfill (or abandon) one objective before taking on the next” (which is hugely beneficial as it will help teams focus) With a Product Goal and the expectation that the Product Backlog, by and large, contains items that emerge as a result of that Product Goal, it is possible to make much more meaningful Sprint Goals The Product Goal helps the Product Owner move beyond being a mere order taker and, instead, create a stance where they are initiating requirements How has the Sprint Goal Changed with the New Scrum Guide? Why is it important and what are the benefits? The new Scrum Guide underscores the commitment and purpose of a Sprint Goal Jeff and Ken introduce a new topic for Sprint Planning in this update, which is: “Why is this Sprint valuable?” (In other words, “What do we hope to get out of it?”) — Asking this question helps craft the Sprint Goal Establishing a Sprint Goal allows the team to create a well-rounded SMART (“specific, measurable, achievable, relevant, and time-bound”) goal If you don’t have a Sprint Goal, the Sprint Backlog becomes just a list of Product Backlog Items to fill up a team’s capacity with no coherence to it With a Sprint Goal, the team is able to create a coherent Sprint backlog that will help them meet their goals and objectives Though there might be things in your Sprint Backlog that are not strongly correlated to the Sprint Goal, doing what is necessary to achieve the Sprint Goal needs to be the priority (If you find that some of these other items keep getting pushed aside, maybe they should be the focus of a Sprint Goal themselves) Once a Sprint Goal is established and it has helped the team select a coherent group of Product Backlog Items for their Sprint Backlog, the Sprint Goal then helps address the topic of: “How are we going to do it?” Good Sprint planning includes creating a plan for working together and breaking things down into the tasks that the team needs to achieve Without a Sprint Plan, there is a lack of transparency and the Scrum Team cannot see at their Daily Scrums whether or not they are making good progress towards the Sprint Goal The Sprint Goal creates transparency and the ability for a Scrum Team to deliver reliably and predictably each and every Sprint (additionally, it helps establish a sustainable pace, which creates better morale and a more fulfilling work environment) How has Self-Organizing Changed to Self-Managing in the New Scrum Guide? Why is it important and what are the benefits? Even though the change may seem merely semantic, it has a massive impact on how organizations will see Scrum in a new light and will be a shock to those organizations that have not allowed their teams to be self-organizing or self-managing at all When organizations use Scrum but do not allow their teams to be self-managing this leads to a lack of engagement and a lack of ownership; it destroys morale and causes turnover In Daniel H. Pink’s book, Drive, he discovered the three factors that truly motivate knowledge workers are autonomy, mastery, and purpose (and self-managing teams leverage all three of these things [and Scrum done well has all three built-in!]) Scrum gives team autonomy by allowing them to decide what to work on and in setting their own Sprint Goal “Scrum encourages mastery. The Scrum team is accountable as a whole for delivery, so there’s no idea that ‘This is my area and I don’t have to do anything else.’ We all expand our knowledge together and work together.” — Sam Falco Self-managing teams create less overhead for managers as they don’t have to spend time directing people and telling them what to do “Self-managing is serendipity in development” (when you hand someone a problem, get out of their way, and they will solve it in ways that you never could have imagined [and maybe even better than if you had solved it yourself!]) In complex product development, something new is always going to come up and there is an enormous amount of uncertainty — Scrum allows self-managing teams to adapt to this uncertainty as it arises and every Sprint offers an opportunity to change direction You can work towards self-managing teams by empowering your Product Owners to make decisions and shepherd their products; feeding your teams with objectives, not tasks; setting the boundaries within which your teams can make their own decisions and steer their own course; encouraging the Scrum team as a whole to be accountable toward each other and toward achieving positive outcomes   Mentioned in this Episode: The Scrum Guide Agile Coaches’ Corner: Trainer Talk: “How Has the Product Goal Changed with the New Scrum Guide?” Agile Coaches’ Corner: Trainer Talk: “How Has the Sprint Goal Changed with the New Scrum Guide?” Agile Coaches’ Corner: Trainer Talk: “How Has Self-Organizing Changed to Self-Managing in the New Scrum Guide?” Agile Coaches’ Corner Ep. 106: “What’s New with Scrum?” Drive: The Surprising Truth About What Motivates Us, by Daniel H. Pink   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

Seit dem großen 2020er Update des Scrum Guide hat das Product Goal Einzug gehalten. Wir gehen auf die Fragen von Hörer Sven zum Product Goal ein und besprechen, ob Product Goal und Produktvision eigentlich synonym sind, was mit Dingen passiert, die nicht ins Ziel passen, wie man ein gutes Product Goal findet, was man damit dann anstellt und vor allem: Wie mache ich das eigentlich in Jira!?!

Pour voir la version vidéo : https://sl.run/ObHr7u ----- Comment faire le pont entre la vision produit, souvent vague et flou, et le quotidien des sprints, lui très concret ? Avec le Product Goal ! Scrum l'a introduit dans sa version 2020. Comment bien l'utiliser ? Comment le définir ? Venez découvrir l'ultime épisode de l'équipe Panda et de la série la gestion de produit en pratique ! #ProductGoal #ProductVision #SprintGoal

Join V. Lee Henson, President & Founder of AgileDad as we discuss the five types of product value:1) Commercial Value: “The key questions to ask here is: ‘(With the Product Goal in mind) How does this item increase our revenue or profit?'”2) Efficiency Value: "The key question to ask is ‘(With the Product Goal in mind) how does this item save us money or time?'”3) Market Value: "The key question to ask is ‘(With the Product Goal in mind) how does this item allow us to attract more users or customers?'”4) Customer Value: "The key question to ask here is ‘(With the Product Goal in mind) how does this item increase the likelihood that a customer continues to use our product?'”5) Future Value: "The key question to ask here is “(With the Product Goal in mind) how does this item save us money or time in the future?”6) BONUS Value..  No Value - You should avoid these at all cost. 

Ben Hodson with JobNimbus joins us to discuss how to maximize your CRM for your roofing company. JobNimbus users are seeing a 43% average revenue growth! New Sales Dashboard Subject Line Templates Coming Soon... Product Goal and Roadmap Integrations CRM Customizations