…Lawrence Mountain Goat Software Agile Mentors Community Scrum Alliance Subscribe to the Agile Mentors Podcast on Apple Podcasts Want to get involved? This show is designed for you, and we'd love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we…

…one. ● Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day…

…an important part of agile and how to use this meeting to help teams to improve continuously. Overview In this episode, Brian Milner is joined by guest co-host Scott Dunn, Certified Enterprise Coach and Scrum Trainer, to get insights into delivering retrospective sessions that energize and inform the whole team…

…role it plays in agile today. Mike Cohn has trained more than 30,000 Scrum Masters and shares his experience of the challenges he faced early on helping project managers to transition to effective Scrum Masters. Brian and Mike discuss the distinction and overlap between traditional project management styles and the…

…George Costanza School of Agile Leadership,” Brian designed an interactive workshop to encourage you to turn your idea of leadership on its head to perhaps reveal a much better way to lead. Listen now to discover: 02:33 - Daily Scrums Suck - a teaser about Brian’s first session 03:45 -…

…next stage of becoming agile? Or is it something that should drive an agile transformation in the first place? In this episode Scott and Brian discuss their definitions of what it means to be product-centric, and whether this is different to being customer-focused. They also look at the limitations that…

…this episode of the Agile Mentors podcast, Woody Zuill, a 40-year veteran software developer specializing in team interaction, joins Brian to explore the concept of Mob Programming. Woody shares the benefits of working together rather than separating tasks in software development and how removing things like queuing, multitasking, and context…

…audience. Most work an agile development teams will pursue will be valuable to users. But other work may be valuable just to the team itself. Still other work may be to users, stakeholders, and team members. For example, consider refactoring: improving the structure but not the behavior of code. Because…

…a particular member. An agile or Scrum team alone should not have the right to remove someone from the team. As I detailed in Chapter 12 of Succeeding with Agile, self-organization does not occur in a vacuum. The right preconditions must be in place for self-organization to occur. Individuals then…

…to creating estimates for agile planning, people are simultaneously your greatest asset and greatest obstacle. Better Estimates Are Built on Better Understanding Estimating is a human task, and humans can be complicated. No matter how clearly you define and explain the process, estimates are influenced by bias, background, and individual…

…daily meetings of high-performing agile teams should run themselves as well. Although that may sound easy, it’s not. Many subtle decisions you make along the way will point a team toward ownership of this event or let them fall back knowing that you are in charge instead. New Teams Need…

…teams that believe that agile can help them navigate these challenges, but they find themselves frustrated. They attend meetings, follow Scrum practices, and yet, they aren’t seeing the promised improvements in predictability, collaboration, and efficiency. What I see is a fundamental challenge: How do we ensure that everyone on the…

An essential part of agile is continuous improvement. No matter how good an agile team is today, its team members feel compelled to seek ways to become even better in the future. This search for continual improvements is the purpose of the iteration retrospective. Unfortunately, not all retrospectives are perfect.…

…any given time, an agile product backlog will contain a prioritized list of desired features, each sized differently and written at varying levels of detail. Because the product backlog is prioritized, the smaller, high priority items reside at the top of the list, while the larger, less urgent items fall…

…Jim York #171: Why Agile Teams Succeed—or Don’t with Colin Fisher Subscribe to the Agile Mentors Podcast Want to get involved? This show is designed for you, and we’d love your input. Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read…