Podcasts about scrum events

In this episode of Ask a PST, we focus in on Product Ownership, Sam Falco answers questions about stakeholder engagement, PO participation in Scrum Events, measuring value, the shift from a Scrum Master to a Product Owner and more!

Agilität ist tot! Agiles Arbeiten macht alles nur noch komplizierter! Ohne agiles Arbeiten war ich produktiver! Agiles Arbeiten ist nur Mehraufwand! Die ganzen Scrum Events sind alle Zeitverschwendung. All diese Dinge hört man immer wieder und zur Zeit gefühlt auch immer öfter. In dieser Folge nehme ich mich dieser Probleme an. Viel Spaß beim Reinhören

In dieser Episode sprechen wir mit Jan Fischbach über das spannende Thema des agilen Arbeitens. Wir beginnen mit einer klaren Frage: Was ist Agilität eigentlich genau? Dabei prüfen wir, ob Frameworks wie Scrum unverzichtbar für agile Prozesse sind.Ein wichtiger Punkt dieser Diskussion ist die Rolle des Agile Coaches und Scrum Masters. Wir beleuchten, was diese Rollen wirklich ausmacht und werfen einen kritischen Blick darauf. Außerdem erkunden wir, dass die Wurzeln der Agilität viel älter sind, als oft angenommen.Besonders interessant wird es, wenn wir über die Strukturen und Kultur sprechen, die notwendig sind, um agil zu arbeiten. Hier erläutern wir, wie Unternehmen ihre Hierarchien und Arbeitsweisen anpassen müssen, um echte Selbstorganisation und Agilität zu ermöglichen. Wir diskutieren auch, welche Führungsaufgaben in agilen Rollen stecken und wie diese die Zusammenarbeit im Team und die Prozesse beeinflussen.Diese Folge ist perfekt für alle, die einen realistischen Blick auf agile Arbeitsmethoden werfen und verstehen wollen, was es wirklich braucht, um Agilität in einem Unternehmen zum Leben zu erwecken. Schaltet ein für eine klare und ehrliche Diskussion über Agilität im Arbeitsalltag!Jan Fischbach ist Geschäftsführer in der Organisationsberatung Common Sense Team und langjähriger Coach und Mitorganisator bei Scrum Events. Seit über 10 Jahren ist er als Experte in agilen Arbeitsweisen unterwegs und berät Unternehmen zu SCRUM und anderen agilen Frameworks.Infos über Jan Fischbach:https://www.linkedin.com/in/janfischbach/https://www.commonsenseteam.dehttps://www.scrum-events.deDas ist der Podcast von agyleOS - der People & Culture Plattform für Skill-basierte Organisationen. Erfahrt mehr darüber, wie ihr mit agyleOS eine euer Unternehmen entwickeln und visualisieren könnt auf unserer Website. Für die neuesten Updates zu agyleOS folgt uns auch auf LinkedIn.Feedback zum Podcast per Mail oder auf LinkedIn:Erdal: ea@agyleos.com oder LinkedInNino: nc@agyleos.com oder LinkedInPodcast LinkedIn Profil.Musik & Postproduktion:Joscha Grunewald

Felix Rink ist wie versprochen zum zweiten Mal Gast im Produktwerker Podcast. Er spricht mit Oliver über Flow Metriken und in wie weit diese für Produktmenschen hilfreich sein können. Nachdem die beiden vor einigen Wochen über Sinn und Unsinn von Vorhersagbarkeit in der Produktentwicklungen philosophiert haben, wird es in dieser Episode also wesentlich konkreter. Zu Beginn der Folge klären Oliver und Felix, was Flow überhaupt ist und welche Voraussetzungen erfüllt sein müssen, damit man Flow messen kann. Der Kanban Trainer bricht die Flow Metriken im Anschluss auf die vier wichtigsten Basis Metriken herunter. Besonders wertvoll für den eigenen Kontext sind Felix Ideen und Anregungen, in welchen Scrum Events und bei welchen Praktiken und Artefakten diese Flow Metrics die Verantwortlichkeit eines Product Owner unterstützen können. Im Detail geht es um das Sprint Planning und das Sprint Review, sowie die Arbeit mit dem Product Backlog. Wie gewohnt schließt die Podcastepisode mit Tipps und Tricks für deine tägliche Arbeit als PO ab. Felix empfiehlt in der Episode, Actionable Agile für Flow Metriken oder die Monte Calo Simulation einzusetzen. Actionable Agile - https://www.actionableagile.com Es gibt wie erwähnt auch Excel Alternativen. Felix empfiehlt zwei Templates: https://github.com/SkeltonThatcher/bizmetrics-book#example-spreadsheets https://www.focusedobjective.com/pages/free-spreadsheets-and-tools

Es gibt Situationen, in denen eine Organisation sich entscheidet, zwei Product Owner einem Scrum Team zuzuordnen. Also zwei Menschen sollen sich diese Verantwortlichkeit teilen: gemeinsam das Product Backlog managen, gemeinsam mit dem Scrum Team die Scrum Events durchführen usw. - auch wenn der Scrum Guide das definitiv anders beschreibt: Ein Team sollte genau eine Product Ownerin ("The Product Owner is one person, not a committee.") und ein Product Backlog haben. Aber in der gelebten Realität sieht man das schon mal anders. Wie kommt es dazu und geht das denn überhaupt? Tim und Dominique nennen in dieser Podcast-Folge die Gründe, wegen derer sich Organisationen für mehr als eine Product Ownerin entscheiden. Anschließen diskutieren sie die Risiken und Schwächen einer solchen Situation - insbesondere vor dem Hintergrund ihrer eigenen Erfahrungen mit solchen Konstellationen. Tim berichtet z.B. von einem Versuch, vier PO für ein Team zu installieren. Der Versuch scheiterte allerdings ziemlich schnell. Natürlich zeigen die beiden auch Lösungsansätze auf, um die Situation zu überwinden und diese "organisatorische Schuld" abzubauen. Wie kann es gelingen, das ganze auf nur einen Product Owner zu reduzieren? Abschließend besprechen die beiden aber auch, was geschehen müsste oder gegeben sein muss, um (zur Not) auch mit mehr als einem PO zu arbeiten. Diese Podcast-Episoden passen zum Thema bzw. wurden erwähnt: - Organisatorische Schulden beeinflussen deinen Erfolg als Product Owner - Product Owner in Teilzeit - Wie die Produktvision hilft, Product Ownern eine Richtung zu geben - Warum scheint die Product Owner Rolle so schwer zu sein? (Gast: Markus Andrezak) Hast du das auch schon mal erlebt: zwei PO in einem Scrum Team? Was war der Grund, dass ihr euch so aufgestellt habt? Und welche Erfahrung habt ihr dabei gemacht? Vielleicht hast du noch gute Tipps, wie eine solche Konstellation gelingen kann. Wir freuen uns, wenn du deine Erfahrungen aus der Praxis mit uns in einem Kommentar des Blog-Artikels teilst oder auf unserer Produktwerker LinkedIn-Seite. **Folgt uns Produktwerker auf** - LinkedIn -> https://bit.ly/3gWanpT - Twitter -> https://bit.ly/3NitkPy - Youtube -> https://bit.ly/3DIIvhF - Infoletter (u.a. mit Hinweisen auf Konferenzen, Empfehlungen, Terminen für unsere kostenfreien Events usw.) -> https://bit.ly/3Why63K

@your Agile Coach Thank you all for watching To sign up for my upcoming coaching program- click here .https://www.scrummasteryplaybook.com/courses/copy-of-scrum-mastery-playbook-course-1 interested in joining the inner circle agile community? a community for aspiring scrum masters and new scrum masters to collaborate and practice on a daily basis? then click here to join https://www.paypal.com/webapps/billing/plans/subscribe?plan_id=P-5TD8616732895651VMRLUY4Q for monthly membership or click here and join the yearly membership and get instant access to a full library of Agile resources https://www.scrummasteryplaybook.com/courses/inner-circle-agile-community if you have any questions, kindly drop in the comment section or send an email to onlineagilecoach@gmail.com if you want to connect on other platforms, we are on LinkedIn and Instagram IG: @youragilecoach LinkedIn- Yinka Okunlade

In this recording of Ask a Professional Scrum Trainer, PST Jay Rahman answers questions about Product Ownership, Scrum Master challenges, Scrum Events, facilitation and more!

60 Second Sprints on The 5 Scrum Events... Ready? GO! The first event is the Sprint. The Sprint is a time-boxed period where the team works to deliver a potentially releasable product increment. A Sprint usually lasts between one and four weeks. During the Sprint, the team plans, designs, develops, and tests the product increment. The Sprint is a crucial event because it provides a fixed time frame for the team to work within and allows them to focus on delivering a specific set of features. The second event is Sprint Planning. Sprint Planning is a time-boxed meeting where the team plans the work they will do during the upcoming Sprint. During this meeting, the team decides what items from the Product Backlog they will work on and how they will achieve their Sprint Goal. The Sprint Goal is a statement that describes what the team will accomplish during the Sprint. Sprint Planning helps the team understand what they need to do and how they will do it. The third event is the Daily Scrum. The Daily Scrum is a daily meeting where the team comes together to plan their work for the day. During this meeting, each team member answers three questions: What did I do yesterday? What will I do today? Are there any impediments in my way? The Daily Scrum is a quick meeting that helps the team stay focused and aligned on their work. The fourth event is the Sprint Review. The Sprint Review is a time-boxed meeting where the team demonstrates the product increment they have built during the Sprint. The team presents the product increment to stakeholders and receives feedback. The feedback is used to help the team improve the product increment and plan for the next Sprint. The Sprint Review is a crucial event because it provides an opportunity for the team to receive feedback and make changes to the product. The fifth and final event is the Sprint Retrospective. The Sprint Retrospective is a time-boxed meeting where the team reflects on the Sprint and identifies what went well and what could be improved. During this meeting, the team discusses their processes and identifies areas where they can make changes to improve their performance. The Sprint Retrospective is an important event because it helps the team continuously improve their processes and work together more effectively.

Responsibilities vs Accountabilities - A Better Understanding of Agile Roles Product Owner: Accountabilities Product Vision: Craft a Product Vision that points the team in a meaningful direction. Product Strategy: Define a strategy enabling the team to decide what to do and what not to do. Goals: Set meaningful goals that enable teams to focus and intensively collaborate towards a unique direction. Value Maximization: Prioritize meaningful problems that maximize the outcomes for users and businesses. Communication: Ensure stakeholders are well-informed about results, decisions, progress, etc. In summary, they should never say, “I was unaware of that.” Responsibilities Stakeholder Management: Engage with stakeholders to partner up and create value for products. This includes organizing meetings, workshops, communication, etc. Backlog Management: Curate, sort, and clean up the Product Backlog to ensure it has the most relevant items to create value. Roadmap: Craft product roadmaps to provide perspective and set expectations on where the product is heading. Monitor results: Constantly evaluate KPIs to understand how the product creates value for end-users. Product Discovery: Ensure continuous learning to enable innovation and solve problems users care about. ScrumMaster: Accountabilities Scrum Understanding: Ensure business stakeholders understand how to play the Scrum game. Atmosphere: Develop a collaborative atmosphere with a balance between learning and delivering. Framework: Ensure that all Scrum events occur and that all artifacts are created as defined in the Scrum Guide. Teams' Effectiveness: Enable the team to grow and become as effective as possible. Enable Self-management: Unleashes the team's potential by helping them become self-managing teams. Responsibilities Ensure the Sprint Retrospective takes place: The Scrum Master may facilitate the Sprint Retrospective, but the responsibility is ensuring that it happens. Another team member can run the show. Ensure Retrospectives End Up with Actions: After each Sprint, Scrum teams discuss how to get better as a team. Scrum Masters ensure the result of the session has clear agreed actions. Coach stakeholders: Invest whatever is necessary to coach key business people to enable teams to thrive with Scrum. Scrum Events: Ensure the team respects the Scrum Events frequency and timeboxes them. Development Team: Accountabilities Quality: Ensure the code meets the agreed quality standards. Scalability: Creates solutions that scale to the required business needs. Efficiency: Guarantee solutions are efficient from the users' perspective. Maintainability: Develop an application that can be maintainable by other professionals. Responsibilities Solution: Implement solutions that solve the agreed problems. Test: Perform required tests to meet the quality expectations. Delivery: Define a delivery process and execute it accordingly. Estimate: Only those who work on the solution can estimate it.

Should the Scrum Events Be Entertaining? Let's go ahead and explore the options this situation presents. This and more are discussed in today's episode of Your Daily Scrum with Todd Miller and Ryan Ripley. ⏩ Join Ryan and Todd for a Scrum.org's course: https://buytickets.at/agileforhumansllc

#5amMesterScrum Show 900 (Oh My!) Live - Coaching Up -Managers attending Scrum Events especially Daily - Today's topics: (1) Coaching managers and setting up the team for success with managers attending scrum events Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum 5am Mester Scrum Show 900 went live on Youtube, LinkedIn and Facebook Tuesday 11/8/2022 from Philadelphia, PA  Happy Scrumming, video version: https://youtu.be/fNK-kx0yJEA Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum)  

#5amMesterScrum Show 899 Live - Team Events Should be 1st Priority - Today's topics: (1) So many times I see Scrum Masters and Team members miss Scrum Events for other meetings, customers or bosses.  Wrong Mindset. Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum 5am Mester Scrum Show 899 went live on Youtube, LinkedIn and Facebook Monday 11/7/2022 from Philadelphia, PA  Happy Scrumming, video version: https://youtu.be/bUbxlAtsW7g Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum) 

Have you ever been asked to invite someone outside of the Scrum Team to one or more of the Scrum Team's Events?On this episode, Product Manager Brian Orlando and Enterprise Agile Coach Om Patel go event by event to talk about when it is right to invite stakeholders to your Scrum Events, and when it is "not right!"0:00 Topic Intro0:20 Daily Scrum, by the Book2:48 Daily Scrum, the Real World6:49 Uninvited Guests9:58 Disciplined & Undisciplined Stakeholders14:35 Sprint Retrospective16:56 Outsiders in the Retro18:51 Sprint Review23:03 External vs Internal Stakeholders26:48 Sprint Planning, by the Book28:05 Sprint Planning, the Real World31:47 Backlog Refinement34:42 Optional Scrum Team Attendees at Refinement37:22 Wrap-up= = = = = = = = = = = =Watch it on YoutubePlease 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= = = = = = = = = = = = AA84 - Stakeholders in the Scrum Events

Great Scrum Teams are self-managing, cross-functional and have the ability and skills necessary to drive to successful outcomes. However, team interactions don't always go as expected and can cause conflict or roadblocks. Effective facilitation can help the Scrum Team move forward toward their desired outcomes. Within the Scrum events and beyond there are a lot of opportunities where good facilitation can help teams work better together.In this episode of Ask a Professional Scrum Trainer moderated by Patricia Kong, PSTs Simon Flossmann and David Spinks answer your burning questions about Scrum and the challenges you or your teams may be facing when using Scrum, particularly within the Scrum events and other scenarios when it may be difficult to reach a decision on things, that could be resolved with good facilitation techniques and skills.

This episode is for all Scrum Masters who want to be excellent at facilitating Scrum events and meetings in general . Don't forget to send a message (Info@unpuzzledinc.com) if you want me to discuss your topic in any of my episodes Enjoy and please leave a review thank you

#5amMesterScrum Show 862 Live - Use Existing Events and Don't Create Another Meeting - Today's topics: (1) So many people default to let's create a meeting to discuss a problem.  Scrum Masters should only use the Scrum Events. Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum 5am Mester Scrum Show 862 went live on Youtube, LinkedIn and Facebook Wednesday 9/14/2022 from Philadelphia, PA  Happy Scrumming, Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum)

Learn effective ways of running a backlog refinement meeting/event in this latest episode. The tips are easy to adopt and you will see great progress in your meeting afterwards Enjoy. if you are interested in me discussing any topic, do send an email to info@unpuzzledinc.com or youragilecoach@gmail.com Happy listening and a big thank you to everyone who sends me a message of gratitude. Love you all --- Support this podcast: https://anchor.fm/adeyinka-okunlade/support

In dieser Episode ist Dennis Willkomm unserer Gast und spricht mit Oliver über das Produkt Buch. Genauer gesagt handelt es sich bei dieser Folge um einen Erfahrungsbericht zum Buch schreiben. Und da es bei dem betrachteten Werk um Dennis erste Veröffentlichung geht und er quasi als Product Owner (und auch als Developer) für sein Buch agiert hat, diskutieren die beiden spannende Learnings, die unserer Meinung nach auch auf dein Produkt übertragen werden können. Dennis erklärt anhand der im Produktmanagement weit verbreiteten Praktiken - Product Vision, Product Roadmap, Product Backlog - wie "agil" oder "nicht agil" er an die Herausforderung herangegangen ist. Natürlich spielen auch die Scrum Events wie Sprint Review und Sprint Retrospektive eine gewichtige Rolle in dem Gespräch. Zu Abschluss erklärt Dennis, was er aus der Erfahrung Product Owner für ein Buch zu sein gelernt hat und was er beim Schreiben seines zweiten Buches anders machen möchte. Dennis Buch "Roadmap durch die VUCA-Welt: Für Führungskräfte, Scrum Master und Agile Coaches" ist im Oktober 2021 bei UVK erschienen. Aus unserer Sicht ist das Buch ein wirklich beeindruckendes Nachschlagewerk, welches u.a. die Themenschwerpunkte "Von der Industrialisierung zur Digitalisierung", "Der Mensch im Mittelpunkt", "Das Team als treibende Kraft", "Führung in Veränderung" und "Denken, fühlen und handeln für die Welt von morgen" intelligent erläutert. Dennis war bereits bei uns zu Gast in einer der ersten Podcastfolgen. Tim und Dennis unterhielten sich angeregt zu einem von seiner Lieblingsthemen: das agile Mindset. Hier der Link zur Episode: Das Product Owner Mindset.

On this episode, Brian Orlando and Om Patel are joined by our favorite Special Mystery Guest to ponder an important question that does not get asked enough - does a Scrum Master really need to attend every single Scrum event (and every non-scrum event) that involves their team? 0:00 Intro & Topic Intro0:32 What Else Are You Doing?3:58 Scrum Events without the Scrum Master6:12 Scrum Master and Refinements11:07 Three Teams is Two Too Many13:33 Can You Skip Sprint Review?16:35 Fact Checking Time18:08 Essential Scrum Master Event19:59 Tangent on Taking Advantage of Commitments26:06 Scaling without Scaling30:21 Not Doing Three Question Stand-Ups35:38 PO Protecting Psychological Safety36:20 Brian as a Scrum Master38:06 Different Ways into Product Manager/Owner43:10 Communicating and Importance of the SM46:44 Hold Leadership Accountable with Kanban49:25 Positive Influence through Visualization53:57 Wrap-Up54:15 Blooper Reel= = = = = = = = = = = =Watch it on YouTube:https://youtu.be/WU0t-ZHmBsMPlease 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= = = = = = = = = = = = AP55 - Can a Scrum Master Skip Meetings?!?

Does a Scrum Master Facilitate All of the Scrum Events? 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.

In this episode I will share with you on how I as a Scrum Master would handle a situation when the Product Owner can not attend the Scrum events? Check it out if you as a Scrum Master are currently experiencing this situation right now.

Managing the Scrum Events During the Holidays. 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.

Does the Order of Scrum Events Really Matter? 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.

Why Are the Scrum Events Sometimes Called Ceremonies? 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.

We get this question pretty often, especially when speaking at conferences: I'm a tester or quality assurance (QA) specialist at a company that just adopted Scrum, am I now out of a job? The quick answer is: Of course not, but there are likely some changes coming your way. Quality isn't optional in Scrum. Software testing is a much-needed skill on a Scrum Team. Ryan and Todd take the question head-on in today's video. This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand how a Scrum Team makes sure that they deliver high-quality products? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

#5amMesterScrum Show 654 Live - Courage in Scrum Events +1 (plus one being Backlog Refinement - Today's topic: (1) The Scrum Values are Commitment, Focus, Openness, Respect, and Courage and in this episode we talk about COURAGE inside each Scrum Event plus Refinement and how the team roles need courage. Please like and subscribe and share 5amMesterScrum.  Please send me your topics.   You are are doing Great Please Keep on Sharing. 5am Mester Scrum #5amMesterScrum #scrum #agile #business #scrummaster #agilecoach #coaching #philadelphia #philly #value #event #courage #review #customer #dailyscrum #dsu #retrospective #refinement #dor   5am Mester Scrum Show 654 went live on Youtube  Wednesday 6/30/2021 from Philadelphia, PA  Happy Scrumming, Social Media: - search 5amMesterScrum or #5amMesterScrum  and you should find us and if not please let us know LinkedIn, Youtube, Facebook, Instagram, Twitter, TikTok     Podcasts: (search 5amMesterScrum)

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

The foundation of #Scrum lies in "empirical process control theory," or empiricism. Empiricism asserts that knowledge comes from experience and making decisions based on what is known. #Scrum employs an iterative, incremental approach to optimize predictability and control risk. Three pillars uphold every implementation of empirical process control: #Transparency, #Inspection, and #Adaptation. #Transparency: Significant aspects of the process must be visible to those responsible for the outcome. #Transparency requires those aspects to be defined by a common standard so observers share a common understanding of what is being seen. That is to say: A common language referring to the parts of the process must be shared by all participants, and, Those performing the work and those inspecting the resulting increment must also share a common definition of "#Done." #Inspection: #Scrum users must frequently inspect #Scrum artifacts and progress towards a #Sprint Goal to detect undesirable variances. Their inspection should not be so frequent that inspection gets in the way of work. Inspections are most beneficial when diligently performed by skilled inspectors at the point of work. #Adaptation: If an inspector determines that one or more aspects of a process deviate outside acceptable limits and that the resulting product will be unacceptable, the process or the material being processed must be adjusted. An adjustment must be made as soon as possible to minimize further deviation. The #Scrum framework includes four formal events for #Inspection and #Adaptation, as described in the #Scrum Events sections of the #Scrum Guide™ #Sprint Planning Daily #Scrum #Sprint Review #Sprint Retrospective In the next video, we'll be talking about "The Values of #Scrum" #scrumorg #agile #scrummaster #scrum #productowner #scrumalliance #productmanagement #psm #agilecoach #scaledagileframework #devops #scrumtraining #productmanager #itbusinessanalyst #businessanalyst #agileproblems #itbusinessowner #developmentteam #scrumteam #agileprocess #scrummasters #scrumdotorg #agil #certificacaoscrum #retrospectivas #teambuilding #agiledevelopment --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

The #Scrum #Master is responsible for promoting and supporting #Scrum as defined in the #Scrum Guide. #Scrum Masters do this by helping understand #Scrum theory, practices, rules, and values. The #Scrum #Master is a servant-leader for the #Scrum Team. The #Scrum #Master helps those outside the #Scrum Team understand which of their interactions with the #Scrum Team are helpful and which aren't. The #Scrum #Master helps everyone change these interactions to maximize the value created by the #Scrum Team. #Scrum #Master Service to the #Product #Owner The #Scrum #Master serves the #Product #Owner in several ways, including: Ensuring the goals, scope, and product domain are understood by everyone on the #Scrum Team as well as possible; Finding techniques for effective Product Backlog; Helping the #Scrum Team understand the need for clear and concise Product Backlog items; Understanding product planning in an empirical environment; Ensuring the #Product #Owner knows how to arrange the Product Backlog to maximize value; Understanding and practicing #agility; and, Facilitating #Scrum events as requested or needed. #Scrum #Master Service to the Development Team The #Scrum #Master serves the Development Team in several ways, including: Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value products; Removing impediments to the Development Team's progress; Facilitating #Scrum events as requested or needed; and, Coaching the Development Team in organizational environments in which #scrum is not yet fully adopted and understood. #Scrum #Master Service to the Organization The #Scrum #Master serves in the Organization in several ways, including: Leading and coaching the organization in its #Scrum adoption Planning #Scrum implementations within the organization; Helping employees and stakeholders understand and enact #Scrum and empirical product development; Causing change that increases the productivity of the #Scrum Team; and, Working with other #Scrum Masters to increase the effectiveness of the application of #Scrum in the organization. In the next video we'll be providing an "Introduction to #Scrum Events and the #Sprint" #scrumorg #agile #scrummaster #scrum #productowner #scrumalliance #productmanagement #psm #agilecoach #scaledagileframework #devops #scrumtraining #productmanager #itbusinessanalyst #businessanalyst #agileproblems #itbusinessowner #developmentteam #scrumteam #agileprocess #scrummasters #scrumdotorg #agil #certificacaoscrum #retrospectivas #teambuilding #agiledevelopment --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

Prescribed events are used in #Scrum to create regularity and to minimize the need for meetings not defined in #Scrum. All events are time-boxed events, such that every event has a maximum duration. Once a #Sprint begins, its duration is fixed and cannot be shortened or lengthened. The remaining events may end whenever the purpose of the event is achieved, ensuring an appropriate amount of time is spent without allowing waste in the process. Other than the #Sprint itself, which is a container for all other events, each event in #Scrum is a formal opportunity to inspect and adapt something. These events are specifically designed to enable critical #transparency and inspection. Failure to include any of these events results in reduced #transparency and is a lost opportunity to inspect and adapt. That being said, the #Sprint is the heart of #Scrum. A Sprint is a time-box of one month or less during which a "#Done," usable, and potentially releasable product #Increment is created. #Sprints have consistent durations throughout a development effort. A new #Sprint starts immediately after the conclusion of the previous #Sprint. #Sprints contain and consist of the #Sprint Planning, Daily #Scrums, the development work, the #Sprint Review, and the #Sprint Retrospective. During the #Sprint: No changes are made that would endanger the #Sprint Goal Quality goals do not decreases; and, The scope may be clarified and re-negotiated between the #Product #Owner and #Development Team as more is learned. Each #Sprint may be considered a project with no more than a one-month horizon. Like projects, #Sprints are used to accomplish something. Each #Sprint has a goal of what is to be built, a design and flexible plan that will guide building it, the work, and the resultant product #Increment. #Sprints are limited to one calendar month. When a #Sprint's horizon is too long, the definition of what is being built may change, complexity may rise, and risk may increase. #Sprints enable predictability by ensuring inspection and adaptation of progress toward a #Sprint Goal at least every calendar month. #Sprints also limit risk to one calendar month of cost. In the next video, we'll be talking about "Cancelling the #Sprint" #Aleph Technologies is a premier IT #training and staffing group with state-of-the-art facilities based in Dallas, Texas. #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, Scaled #Agile #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. Reap the benefits of #Aleph Technologies' expertise applying #Agile methods and solutions. We will be your guide and mentor through your business's #Agile transformation and align you with a trajectory of growth that maintains strategic priorities. The benefits of an #Agile transformation include dramatic improvements to delivery effectiveness, shortened time cycles, and heightened responsiveness to change. Work in tandem with #Aleph Technologies to develop a practical plan of action, #implement necessary changes, and move your company to new heights with a culture of learning, innovation, and growth throughout your organization. #scrumorg #agile #scrummaster #scrum #productowner #scrumalliance #productmanagement #psm #agilecoach #scaledagileframework #devops #scrumtraining #productmanager #itbusiness --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

The #Scrum #Master is responsible for promoting and supporting #Scrum as defined in the #Scrum Guide. #Scrum Masters do this by helping understand #Scrum theory, practices, rules, and values. The #Scrum #Master is a servant-leader for the #Scrum Team. The #Scrum #Master helps those outside the #Scrum Team understand which of their interactions with the #Scrum Team are helpful and which aren't. The #Scrum #Master helps everyone change these interactions to maximize the value created by the #Scrum Team. #Scrum #Master Service to the #Product #Owner The #Scrum #Master serves the Product Owner in several ways, including: Ensuring the goals, scope, and product domain are understood by everyone on the #Scrum Team as well as possible; Finding techniques for effective Product Backlog; Ensuring the Product Owner knows how to arrange the Product Backlog to maximize value; Understanding and practicing agility; and, Facilitating #Scrum events as requested or needed. #Scrum #Master Service to the Development Team The #Scrum #Master serves the Development Team in several ways, including: Coaching the Development Team in self-organization and cross-functionality; Helping the Development Team to create high-value products; Removing impediments to the Development Team's progress; Facilitating #Scrum events as requested or needed; and, Coaching the Development Team in organizational environments in which #Scrum is not yet fully adopted and understood. #Scrum #Master Service to the Organization The #Scrum #Master serves in the Organization in several ways, including: Leading and coaching the organization in its #Scrum adoption Planning #Scrum implementations within the organization; Helping employees and stakeholders understand and enact #Scrum and empirical product development; Causing change that increases the productivity of the #Scrum Team; and, Working with other #Scrum #Masters to increase the effectiveness of the application of #Scrum in the organization. In the next video, we'll be providing an "Introduction to #Scrum Events and the Sprint" #Aleph Technologies is a premier IT #training and staffing group with state-of-the-art facilities based in Dallas, Texas. #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, Scaled #Agile #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. Reap the benefits of #Aleph Technologies' expertise applying #Agile methods and solutions. We will be your guide and mentor through your business's #Agile transformation and align you with a trajectory of growth that maintains strategic priorities. The benefits of an #Agile transformation include dramatic improvements to delivery effectiveness, shortened time cycles, and heightened responsiveness to change. Work in tandem with #Aleph Technologies to develop a practical plan of action, #implement necessary changes, and move your company to new heights with a culture of learning, innovation and growth throughout your organization. #scrumorg #agile #scrummaster #scrum #productowner #scrumalliance #productmanagement #psm #agilecoach #scaledagileframework #devops #scrumtraining #productmanager #itbusinessanalyst #businessanalyst #agileproblems #itbusinessowner #developmentteam #scrumteam #agileprocess #scrummasters --- Send in a voice message: https://anchor.fm/aleph-global-scrum-team/message

Brian Orlando and Om Patel go back to basics in part one of our walkthrough of each of the Scrum Events! In this episode, we talk about the Daily Scrum and the Sprint Retrospective. We discuss our experiences and the different ways to approach and facilitate each event.0:00 Daily Scrum - 3 Questions13:36 Daily Scrum - Walk the Board19:37 Why Do the Daily Scrum at All?28:47 Daily Scrum for a New Team33:44 Retrospectives42:45 On-Demand Retro May Have Helped51:00 Faux Statuses56:06 Stopping the Line1:03:43 Retro Topic WrapAlso available on Youtube: https://www.youtube.com/watch?v=fHxmvad9W50

Brian Orlando and Om Patel go back to basics in part two of our walkthrough of each of the Scrum Events! In this episode, we talk about the Sprint Review and Sprint Planning. We discuss our experiences and the different ways to approach and facilitate each event. We also briefly discuss Backlog Refinement which it totally not an "event."0:00 Design Thinking & the Sprint Review10:48 Musings on the Sprint Review Purpose17:40 Summarizing the Sprint Review27:27 Mainly Nonsensical Banter28:21 Sprint Planning - the Methods33:54 Sequencing/Prioritizing Work39:39 Detour through Micromanagement City46:56 Refinement Types52:38 Ideal Refinements56:00 Topic WrapAlso available on Youtube:https://www.youtube.com/watch?v=gxeu3OzPdOE

Today's question is about how a Scrum Team should only have one Sprint Goal. Todd and Ryan break down why one Sprint Goal is essential and the issues that come when this advice is ignored. The big lesson here: FOCUS! and get something done. How does your Scrum Team handle sprint goals? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand why a Scrum Team should only have one sprint goal? These Scrum Master day-in-the-life questions can be tricky. The backlog refinement meeting is important. 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/3b96j0A​​​​​​ // Join Ryan and Todd in a Professional Scrum Master course: Visit https://agileforhumans.com/​​​​​​ for a list of upcoming courses. 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. 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. #scrumSee omnystudio.com/listener for privacy information.

Dan and Prateek talk about the use of flow metrics during Scrum events. They dive into how metrics, usually associated with Kanban are very useful for Scrum teams and can help teams level up their agile implementation.

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.

Das Sprint Review ist ein Zusammentreffen, initiiert vom Produktverantwortlichen (=Produkt Owner), zur Überprüfung des aktuellen Standes eures Produktes (=Inkrement) zusammen mit den Auftraggebern (=Stakeholdern) und dem Entwicklungsteam (=Developers). Dabei wird gemeinsam entschieden, was die nächsten Aufgaben (=Backlog items) für den nächsten Sprint (=Arbeitswoche/n) sind. Das ganze Treffen hat einen Moderator (=SCRUM Master), damit die Prinzipien und Rahmenbedingungen eines guten SCRUM Events eingehalten wird. Extra für dich macht David den Realitätscheck und geht auf Fragen ein wie: Macht es Sinn, dass Sprint Review zu machen, wenn es nix zu zeigen gibt? Ist das Sprint Review ein Gate, bevor wir an den Kunden ausliefern? Sind die wirklichen Nutzer im Sprint Review und wie beeinflusst das die Motivation des Teams? Wer hat die Vision und damit das Sprint Ziel klar vor Augen? Ist das Sprint Review in Wirklichkeit nur eine Rechtfertigung vorm Kunden? Darf das Sprint Review Spaß machen? ------------------------ Vollständige Theorie zum Sprint Review gibt's hier: https://scrumguides.org/docs/scrumguide/v2020/2020-Scrum-Guide-German.pdf SCRUM Insights for Practioners https://www.goodreads.com/book/show/33230369-scrum-insights-for-practitioners ------------------------ Sobald du Fragen, Feedback oder Wünsche hast: podcast@wir-muessen-reden.net Sei neugierig auf David Symhoven: www.david-symhoven.de Lass dich begeistern von De Long Iu: www.delong-iu.de/#links Folge uns gespannt auf LinkedIn: https://www.linkedin.com/company/wirmuessenreden/

Today's question is all about the dangers of context switching. Todd and Ryan take a look at what happens when a Scrum Team isn't able to focus on their work and has to take on multiple projects. Spoiler Alert!!!! Context switching causes a lot of headaches and anti-patterns. How many projects are your Scrum Team's working? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand the tradeoffs of having too much work in process? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about all about the Scrum Master and how many teams they can serve at one time. Ryan and Todd discuss their experience working with many teams and provide some guidance on how to know when a Scrum Master could be taking on too much responsibility. How many teams do you serve? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand the tradeoffs of working with multiple teams? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about how a Scrum Team should handle multiple sprint goals. Todd and Ryan break down their past experiences with teams who insist on having multiple sprint goals and the issues that come with this anti-pattern. The big lesson here: FOCUS! and get something done. How does your Scrum Team handle sprint goals? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand why a Scrum Team should only have one sprint goal? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about how a Scrum Team should handle a request for a project status report. Todd and Ryan break down their past experiences handling this situation and what we can do use a status report as a way to encourage agile behaviors. How does your Scrum Team handle a status report? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand how a status report can help create the behaviors we like to see on Scrum Teams? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about how a Scrum Team should handle bugs and defects. Todd and Ryan break down their past experiences handling the unexpected work that can happen when bugs and defects emerge. The big lesson here: don't turn into bug managers and work on your definition of done! How does your Scrum Team handle bugs and defects? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand why Product Backlog Refinement isn't a Scrum Event? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about Product Backlog Refinement and why it isn't an official Scrum Event. Refinement is a great product management practice for a Product Owner to use to help the Scrum Team gain an understanding of the product and future work. Check out Ryan and Todd's take on this. How does your Scrum Team handle Product Backlog Refinement? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand why Product Backlog Refinement isn't a Scrum Event? These Scrum Master day in the life questions can be tricky. The backlog refinement meeting is important. 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.

Today's question is about the Daily Scrum and whether or not a Scrum Master should attend this Scrum Event. Todd and Ryan discuss situations where it could make sense for a Scrum Master to attend the Daily Scrum, but their stance is clear that the Daily Scrum is by and for the developers. How does your Scrum Team the Daily Scrum? Let us know in the comments! This is one of those Scrum Master interview questions about the Scrum Events that can throw you off. Do you understand the purpose of the Daily Scrum? 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.

Today's question is from Jodie who wants to know about alternatives to the 3 questions when facilitating the Daily Scrum. We are always happy to take questions about the Scrum Events. Todd and Ryan discuss the lean metric "item aging" and how it can be used to help a Scrum Team gain insights into the progress of their work. What is your favorite way to facilitate the Daily Scrum? Let us know in the comments! And don't forget, it's not the daily standup or the daily standup meeting...it's the Daily Scrum! // Want to learn more about Scrum? Buy Fixing Your Scrum: Practical Solutions to Common Scrum Problems - https://amzn.to/3b96j0A // Join Ryan and Todd in a Professional Scrum Master course: Visit https://agileforhumans.com/ for a list of upcoming courses. 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.See omnystudio.com/listener for privacy information.

What if Scrum doesn't fit? If you work as a Scrum Master or Agile Coach, you have probably run into teams where Scrum just doesn't take off. The various Scrum Events feel like a chore, motivation is low and people complain about Scrum.One of the downsides of the popularity of the Scrum Framework is that organizations, teams, consultants, and coaches sometimes try to force Scrum onto problems it isn't designed for. And the resulting tension is often experienced by the teams, making their perceived “resistance” very understandable.In this episode of our podcast, we explore indicators of "bad fit". We also explore how "coherence" is central to the Scrum Framework. Without it, Scrum can easily feel artificial and forced. Even when that coherence isn't there now, that doesn't mean it shouldn't be there. In fact, you may find that creating more coherence makes your team many times more effective. Or you may conclude that it isn't feasible, and Scrum isn't going to fit.This episode is based on this blog-post:https://bit.ly/whenscrumdoesntfitBecome a patron to support and participate in our work:https://bit.ly/supportheliberatorsFollow us on Medium:https://medium.com/the-liberatorsSupport the show (https://bit.ly/supportheliberators)

Scrum Institute, Scrum Framework Episode #14 has been proudly brought to you by International Scrum Institute, https://www.scrum-institute.org You can also listen Scrum Institute’s Podcast from Apple, Spotify, Castbox and Google Play. Listen to Scrum Institute Podcast on AppleListen to Scrum Institute Podcast on Google PlayListen to Scrum Institute Podcast on SpotifyListen to Scrum Institute Podcast on Listen NotesListen to Scrum Institute Podcast on Castbox How To Scale The Scrum Framework (Distributed & Large Scrum Projects)? This Might Surprise You! The Scrum Framework – as described so far – works best for a single Scrum Team in one location. However, in reality, a singular Scrum Team often cannot implement a project entirely, or the team members have to spread over multiple locations. As a consequence, the number of teams has to increase with various distributed teams. In many instances, we have also been observing that those teams are distributed in geographically distant locations or continents. There are numerous reasons which motivate organizations to distribute their teams across different locations: Technical Reasons: Some knowhow to build separate components of the software are not locally available in the headquarters, Expertise Reasons: Some capabilities related to the execution of different software engineering activities are not locally available. For instance, test automation, user interface design, or integration of in-house software to the software of other vendors can require experts outside the headquarters, Size-related Reasons: The project takes more people on board to deliver it to its clients in a predefined timeline. If this is the case, then the project organization will need more members than it can conceivably fit one single Scrum Team. So the Scrum Team has to be distributed,Business-related Reasons: Use of human resources from lower-cost locations or enabling the continuity of work by using engineers from different time-zones could build a good business case. As communication is an integral part of the Scrum Framework, all Scrum Team members should pay attention to overcome the challenges to deal with working within a distributed project environment. Furthermore, all team members should have access to communication tools, including audio/video conferencing and screen sharing tools. These commonly used project management tools support teams to enable healthy and continuous communication. Those can include product backlogs, sprint backlogs, incident lists, knowledge/ news sharing tools, and so on. Project Organization: Multiple Teams The simplest way of expanding the Scrum Framework while working in a larger-scale project setup is to increase the number of teams in the same location. If multiple teams need to work together to implement a project, it is best to grow the number of teams progressively. What does this mean to you? Multiple Teams in a Single Location In most organizations, progressive growth is more manageable than launching ten different new teams in one go. The best practice is to start with a single Scrum Team. After a few successful Sprints, one or two additional Scrum Teams can join the project. Once you ensure that these multiple Scrum Teams work together well, you can keep on adding further Scrum Teams to your distributed project organization. Increasing the Number of Teams There are two typical ways of creating new Scrum Teams:You split an existing Scrum Team into multiple teams and add new Scrum Team members where and when necessary,You construct a new Scrum Team from completely different engineers who haven’t involved the project so far. Splitting an existing Scrum team has the advantage of leveraging the Scrum Team members who are already knowledgeable and who have already experienced with the ongoing project. Therefore, those new teams are usually at least at some degree productive as soon as they’re formed. The major drawback of this scenario is that the existing and fully functional Scrum Team has now been split into two teams. That could always cause some issues with the motivation of Scrum Team members. Especially if those changes are happening without an in advance announcement and justification from senior leadership, and when the team members are mentally and technically unprepared. When adding completely new teams, these already existing teams can continue with their Sprints without any interruption and extra integration effort. However, it will take longer to build up the necessary know-how and momentum to ramp-up the entirely newly formed Scrum teams. Independent from the decision on how you add new Scrum Teams to your organization bear in mind the following principles: Start with a small number of Scrum teams,Increase the number of teams gradually,Ensure the continuity of work and smooth delivery of software and business value during the times of change and growth,If there’re significant problems that hinder productivity and continuity of work, first focus on fixing them rather than the expansion with new Scrum Teams. Project Organization: Distributed Teams The major complexity of multiple teams manifests itself when the new Scrum Teams have to be distributed over various locations. Communication barriers between people, coordination difficulties of work, and misunderstandings of joint project norms across teams are only a few of many when it comes to mentioning this complexity. Multiple Teams in Multiple Locations The consequences of not addressing these challenges are severe. Companies have to count billions of dollars of wasted IT budget because of the lack of their skills in Organizational Leadership andScaled Scrum Expertise. There are four critical suggestions for you to cope with these challenges: You ensure that new Scrum Team members are trained in the Scrum Framework as a Scaled Scrum Expert,You ensure that new Scrum Team members are introduced to the project adequately, so they have a proper understanding of what they’re serving for. Not only technically but also from a professional business value point of view, so they can make decisions in their work to increase the value of their contribution,You ensure that the project norms are established. Similar to a single Scrum Team, which has its norms of how to communicate, how to plan, how to get the work done, a multiple project team organization should have its higher-level norms too. So these teams can communicate, plan, operate, solve problems, and deliver client and business value together.You ensure that the new team members do at least temporarily work together with the experienced project members. That could require remote site visits and on-the-job training. That’s totally fine and even desired. Thanks to this approach, the knowhow can be smoothly transferred, and the two-ways and personal dialog between people in different teams and locations can be established. Virtual Teams Another option of a distributed Scrum Team is having its members spread over multiple locations. Such a team is called a “Virtual Team”. The main challenge here is to ensure flawless communication among the team members. Scrum Team members must still need to conduct all Scrum Rituals (Scrum Events) to coordinate their work, but now they have to do this while not all of them are present in the same room. Virtual Teams Scrum Team members co-located in the same location should still work together in the same room. And yet, they now have to rely more on the use of collaboration and communication tools. They can join the Scrum Events from the same meeting room to connect to the other half of the virtual team via video conferencing technologies. Scrum Product Owner Team As we have covered many times in this material so far, regular communication between the Scrum Product Owner and the Scrum Team is crucial for the successful delivery of a project. We need to ensure that the Scrum Product Owner is always available to Scrum Teams located in different locations. Therefore, it is often necessary to have multiple Scrum Product Owners working together. Ideally, there is one dedicated Scrum Product Owner for each team. The Scrum Product Owners should then build a dedicated “Scrum Product Owner Team” to work together effectively. One of the Scrum Product Owners should be assigned to the role of the “Chief Scrum Product Owner”. He or she is responsible for ensuring that: The correct product is built to satisfy the demands of its client,All Scrum Product Owners collaborate efficiently, and they enable their teams to build the business and technical value for their clients. Since the Scrum Product Owner Team is responsible for the complete requirement engineering, it is beneficial to have other competencies and stakeholders in this team. Those can include the representatives of the business case, relevant stakeholders, enterprise architects, and technology architects. All Scrum Product Owners should work within a single large Scrum Product Backlog containing all stories relevant for the project. Each Scrum Team is responsible for delivering some of these user stories. And yet there will be still instances of specific user stories that require the attention and deliverables from multiple Scrum teams. Component vs Feature Teams When distributing work among different teams, we can make the teams accountable for specific software components or features. That is why we call them “Component Team” or “Feature Team.” Component Teams When using Component Teams, each team is only responsible for the implementation of dedicated components from the overall system. To finish a user story, it is usually necessary to split the user stories into smaller pieces to implement them within a single component. The dependencies between the components of these Component Teams make continuous integration an inevitable part of successful deliveries. Scrum Product Owner Team Thus, a feature cannot be usually delivered within a Sprint because its implementation depends on the deliverables from user stories of other teams. That results in increasing batch sizes and lead times of ongoing, not yet integrated work. That doesn’t sound so good, because Scrum Teams should target delivering shippable software increment in smaller batch sizes and shorter lead times. The advantage of component teams is that they make it easier to focus on and build expertise about architectural and design details of particular components. That could be massively beneficial for components that require discovery and innovation. On the other hand, the members of component teams do only specialize in individual components of the whole system. They could lose their bird-eye view and business necessity of features. Keep in mind that our clients do not compensate us to deliver components, but features with which they will execute their businesses. Without this relentless focus on features, overall optimization, and integration of software might take extra time. Since decisions of component teams tend to optimize single components, those decisions can construct invisible bottlenecks for the success and performance of the overall solution. Component Teams Feature Teams Feature teams are fully responsible for the implementation of user stories as they’re specified within the Product Backlog.The teams do no longer need to be divided for various components. Each Feature Team is responsible for delivering a fully-functional feature and a business value associated with this feature. Feature Teams Members of feature teams possess cross functional skills. They act as autonomous as it is possible to deliver fast. The advantage of feature teams is that the team maintains the system-knowledge, and this makes it easier for them to integrate their features with the rest of the system. However, for feature teams, it may become more challenging to build sufficient know-how about components. Furthermore, bringing up an autonomous feature team that can deliver fast and independently takes time as building an interdisciplinary functional team is not that easy. And yet, these are the high-performer teams which get the job done in most organizations, probably including yours. How Do We Choose Component Teams vs Feature Teams? In practice, most of the large organizations use both dedicated Component Teams and Feature teams too. Component and Feature Teams Team C, on the chart, is a Component Team. It provides planned and on-demand infrastructure services to other teams that function as Feature Teams. Team C does not directly implement end-to-end user stories per se. They deliver the requirements of the user stories committed by the Feature Teams. That allows the minimization of the number of qualified people in Feature Teams with the know-how of those components. The Scrum Master In The Distributed Project Environment In a distributed project environment, the role of the Scrum Master is even more essential. In those project configurations: There will be extra effort required to align the teams on the values of the Scrum Framework,It will take longer to establish individual team and project norms (standards) which influences numerous teams,Last but not least, there will be many impediments due to the increased number of dependencies between teams and their deliverables. One important rule to bear in mind that the Scrum Master should physically locate where his or her team is. Otherwise, it will be almost impossible for the Scrum Master: To remove the impediments for his team,To Establish their norms, andTo help them to improve their use of the Scrum Framework. The best practice is to have a Lead (Primary) Scrum Master to guide the overall use of the Scrum Framework across multiple teams. In other unit Scrum teams, which form the larger Scrum organization, someone should be acting as a local Scrum Master too.