Can an inexperienced development team without any senior members can implement scrum? While there's a debate on the necessity of technical excellence for scrum's foundation, one suggestion is to define a clear DOD (definition of done) to unify the team. By revisiting and evolving this definition, teams can incrementally improve and move towards better technical excellence and adopt more Scrum practices. Join us as we delve into this topic, with Todd showing an optimistic viewpoint and a surprising role reversal on our perspectives.⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, Todd and Ryan discuss what to do if you’re a Scrum Master whose team is performing so well you’re afraid of losing your job. Todd emphasizes analyzing your team under a broader sphere to see where gaps between your team and other teams may be. In addition, Ryan also emphasizes the importance of analyzing your team according to data, product rollout and overall customer satisfaction. Because although some teams appear to function well, it can take only a few sprints to show where the gaps lie. ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 Learn more about your ad choices. Visit megaphone.fm/adchoices

In this episode, Todd and Ryan discuss the do’s and don’ts of new product owners. Todd emphasizes the need to be decisive to ensure your people know who decides the order, and what your expectations are as the product owner. However, Todd also emphasizes the importance of being humble, and having a strong team of developers behind you. ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 Learn more about your ad choices. Visit megaphone.fm/adchoices

Addressing team dysfunction, this chapter focuses on the importance of open communication and collaboration with management and HR to resolve disagreements and create performance plans for developers who consistently break agreements.

A YouTube viewer sent in a question asking about the typical day in the life of a Scrum Master. Todd and Ryan talk about what their days look like when they are in the Scrum Master role and how each day usually looks a little different. Check out the video to learn about the things you'll see as a Professional Scrum Master. Want to learn more about Scrum?⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 Learn more about your ad choices. Visit megaphone.fm/adchoices

Richie Peters, an experienced Scrum Master, discusses the challenges of implementing Scrum in organizations due to a lack of Agile understanding among senior leaders. They explore using metrics to show the effectiveness of Agile practices. The importance of aligning the organization with Agile values and principles is highlighted.

In their conversation, Todd and Ryan discussed some self-study resources for Flow Metrics and Evidence-Based Management (EBM). They suggested starting with their YouTube channel's EBM series and reading Dan Vacanti's book "When Will It Be Done" for a comprehensive dive into Flow Metrics. ProKanban.org was recommended for further information on Flow Metrics and Kanban. They also suggested visiting scrum.org for webinars, white papers, and other resources on EBM. Todd and Ryan hinted that there may be more resources for EBM. Leave us a comment and let us know what you think!⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllcTodd 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=1For 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#facilitation #facilitationskills #ScrumMaster #ScrumMasterTraining #Scrum #ScrumFramework #HowToBecomeAScrumMaster #ScrumMasterCertification #AgileForHumans #FreeScrumMasterCourse #FreeScrumTraining Learn more about your ad choices. Visit megaphone.fm/adchoices

Todd and Thomas introduce The Modern Software Developer Series and examine the Battle Ship codebase. Grab the repo, follow along, and learn new modern software developer techniques.Battleship Case Studies can be found here:https://github.com/proscrumdev⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 Learn more about your ad choices. Visit megaphone.fm/adchoices

Todd and Ryan address a question about handling unplanned work that is not measured in Sprint planning and affects a team's predictability in meeting Sprint goals. They recommend holding back capacity back in Sprint planning to account for the unplanned work and plan realistically rather than at 100% capacity. They suggest cutting capacity in half if about half of the work in a Sprint is unplanned. They also caution against equating predictability with maintaining the same velocity or throughput and recommend measuring unplanned work transparently and gathering data on it.   ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 See omny.fm/listener for privacy information. Learn more about your ad choices. Visit megaphone.fm/adchoices

The video discusses who should facilitate a Sprint review in a Scrum team. Todd and Ryan believe the Product Owner should be involved in the process to ensure the right stakeholders are present to adapt the product backlog. However, the Product Owner doesn't necessarily have to be the one facilitating the Sprint Review but should be responsible for sending invites and ensuring the right people are in attendance. The Sprint review is seen as an underserved event that provides an opportunity to adapt the product backlog.   ⏩ Join Ryan and Todd for a Scrum.org course: https://buytickets.at/agileforhumansllc 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 See omny.fm/listener for privacy information. Learn more about your ad choices. Visit megaphone.fm/adchoices