Agile Mentors Podcast

Lance Dacy joins Brian to dig into cross-functionality. Overview You will often hear people say that Scrum teams are cross-functional. But what do we mean when we say that? Are we talking about a jack of all trades but master of none? Do we want team members who can do anything? How does a cross-functional team actually work together and what should we do as agilists to support and nurture cross-functionality in our teams? Join as we discuss these and other aspects of cross-functional teams. Listen now to discover:  02:00 Lance tells us how he defines cross-functional teams 04:34 Brian compares cross-functional teams to the A-Team 08:58 Lance talks about generalists vs specialists 12:39 Brian talks about T-shaped individuals 18:05 Brian discusses the Equity Couch 24:10 Brian describes the Market of Skills tool 27:45 Lance talks about personality profiles 29:20 Brian asks Lance about how to handle cross-functionality on specialist teams Listen next time when we’ll be discussing…  Scott Dunn joins us again to discuss the term ‘product-centric.’  References and resources mentioned in the show The A-Team Market of Skills by Lyssa Adkins OSEMN Process What does Scrum mean by Cross-functional? Want to get involved? This show is designed for you, and we’d love your input. ●      Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ●      Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.  Lance Dacy is a Certified Scrum Trainer®, Certified Scrum Professional®, Certified ScrumMaster®, and Certified Scrum Product Owner®. Lance brings a great personality and servant heart to his workshops. He loves seeing people walk away with tangible and practical things they can do with their teams straight away. Show edited by Rhett Gill.

In this episode, Kert Peterson, an expert in Kanban and agile methodologies, joins Brian to discuss the origin and principles of Kanban, common misconceptions, the five pillars of Kanban, and how to get started and improve your Kanban process.

Brian and Mike talk about why and how to use Story Points in estimating. Overview  To estimate or not to estimate. There are many different views on the matter. It’s important then to start with why. Why would we spend time estimating in the first place? What is the benefit of that effort? Do all Agile teams need to estimate? Join Brian Milner and Mike Cohn as they discuss estimating using Story Points in order to plan for things such as releases. Listen now to discover:  1:51 - Mike talks about the 3 reasons why would we estimate in the first place? 4:30 - Brian asks about the #NoEstimates movement 8:00 - Brian talks about the marketing aspect of his conference talk this year 9:42 - Mike defines what a Story Point is 14:30 - Mike talks about using Story Points as a performance metric 21:20 - Mike talks about consistency in point scales across teams 25:58 - Mike talks about working with contractual constraints when using Story Points Listen next time when we’ll be discussing…  Join us as we dive into Kanban with Kert Peterson. We’ll talk about this close relative to Scrum and discuss how these two can coexists in today’s Agile world. References and resources mentioned in the show Agile Estimating and Planning by Mike Cohn Agile Estimating and Planning online ecourse by Mike Cohn Woody Zuill of the #noestimates movement (and Mob Programming) Want to get involved? This show is designed for you, and we’d love your input. ●      Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ●      Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.  Mike Cohn is co-founder of the Scrum Alliance, and founder of Mountain Goat Software. He’s a veteran of applying Scrum and agile principles and practices to help organizations build better products, and ship them on time. Show edited by Rhett Gill

Brian and Mike talk about how to capture requirements with User Stories. User Stories are not native to Scrum. We actually borrow the practice from XP. Traditionally, requirements were gathered in huge binders that were very detailed and complex. These were considered complete and were locked down when development began. Teams quickly found that change was a constant and this method of capturing requirements didn’t allow for requirements to emerge. Enter User Stories.  Listen now to discover:  2:15 - Mike talks about the history of User Stories 4:00 - Mike discusses the problem User Stories is attempting to solve 4:58 - Mike talks about making lunch 7:30 - Mike talks about when NOT to use User Stories 10:26 - Mike and Brian talk about The Beatles 14:00 - Is As a User an ok way to start a User Story? 15:00 - Mike talks about Job Stories 19:55 - Mike talks about some common mistakes people make with User Stories 23:00 - Is the So That clause needed? Listen next time when we’ll be discussing…  Mike Cohn returns to discuss Estimating with Brian. Mike has written a book about this (Agile Estimating and Planning) and will share his insights on this important topic. References and resources mentioned in the show User Stories Applied - by Mike Cohn Better User Stories course - by Mike Cohn Billboard interview with Paul McCartney where he talks about using personal pronouns Intercom who makes chatbots Want to get involved? This show is designed for you, and we’d love your input. ●      Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ●      Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.  Mike Cohn is co-founder of the Scrum Alliance, and founder of Mountain Goat Software. He’s a veteran of applying Scrum and agile principles and practices to help organizations build better products, and ship them on time. Show edited by Rhett Gill.

Brian and Kert talk about the final component of the Scrum Framework - Artifacts.  Overview  The term “artifact” seems a bit strange, doesn’t it? Why would the authors of Scrum include this as a component of the framework? What are the main artifacts that Scrum prescribes? And what are some of the other artifacts that are not required but many teams see as helpful to the running of a Scrum team? In this episode, Brian and Kert will discuss this final component of the Scrum framework in the Scrum Framework series and give you pointers on how to make the most out of the Scrum artifacts. Listen now to discover:  3:45 - hear Kert and Brian talk about the roots of this term 6:15 - Kert talks about his experience with documentation working at NASA 9:15 - Kert talks about the two backlogs in Scrum 12:30 - Brian and Kert talk about what level of detail is needed in backlog items 16:12 - Who is the therapist on a Scrum team? 19:00 Is tasking out everything required for Sprint Planning? 23:41 - Kert talks about how Ken Schwaber called Scrum, “The Art of the Possible” 31:27 Brian and Kert talk about the Definition of Done 33:24 Brian talks about a tool to facilitate the creation of a Definition of Done Listen next time when we’ll be discussing…  Mike Cohn returns to discuss User Stories with Brian. Mike has literally written the book on User Stories (User Stories Applied) and shares his wealth of experience and knowledge on the subject. References and resources mentioned in the show Married at First Site - Lifetime TV Network Larry Maccherone talks about Kanban Metrics David A. Koontz’s exercise for creating a Definition of Done Want to get involved? This show is designed for you, and we’d love your input. ●      Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ●      Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Kert began his professional career as a Software Engineer in NASA's Space Shuttle program, affording him practical insights into the daily challenges faced by engineers, designers, and testers. Driven by the belief that learning unlocks potential, Kert has pioneered educational programs for Dell, Rockwell Collins, Amazon.com, and Capital One Financial. Kert is one of the few trainers world-wide to be actively credentialed as both a Scrum and Kanban trainer by Scrum Alliance and Kanban University, respectively.

Join Brian Milner and guest co-host Scott Dunn as they discuss why the retrospective is 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 — while ensuring they are effective at meeting goals. A sprint retrospective is a great way for teams to reflect on the previous sprint but this meeting can become stale if you sleepwalk your way through the same agenda every time. Brian and Scott discuss the Scrum Master’s responsibility to take ownership of the retrospective and the importance of developing a toolkit of techniques that you can use and adapt to engage and motivate your teams. There are many great retrospective ideas in the Agile community, including variations and additions on the basic questions and creative facilitation techniques. Sharing their experiences and offering advice to Scrum Masters on how to empower their teams, drive participation and unlock creativity, Brian and Scott discuss the importance of innovation and how to establish a culture of trust and accomplishment to maximize the value of this meeting. Listen now to discover: ·       00:03:00 - Why Scrum Masters need to establish safety for retrospectives to work ·       00:07:00 - How to structure a retrospective to motivate teams ·       00:09:00 - Why it is not the Scrum Master’s responsibility to resolve all impediments ·       00:11:00 - How to empower your team to have more agency over the work and make a difference as team members ·       00:13:30 - Why Scrum Masters need to take ownership of the retrospective ·       00:19:00 - Why you need to change up your retrospective to engage your team ·       00:19:30 - How to conduct fun and engaging retrospectives ·       00:23:58 - How to influence and shape your team’s culture ·       00:26:10 - How to get value from a retrospective with an introverted team References and resources mentioned in the show ·       Strengths-based Leadership - Gallup ·       Training from the Back of the Room – Sharon Bowman ·       Marcus Buckingham ·       Agile Retrospectives - Making Good Teams Great - Esther Derby and Diana Larson Want to get involved? This show is designed for you, and we’d love your input. ·       Enjoyed what you heard today? Please leave a rating and a review. It really helps, and we read every single one. ·       Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Scott Dunn is a Certified Enterprise Coach and Certified Scrum Trainer with more than 20 years of experience in management, project management (PMP), engagement management, and software development (MCSD). He is passionate about strengths-based teams and a solutions-based approach to people and organizational issues.

Julie Chickering, an experienced Project Management Professional, and Brian Milner discuss the importance of the Sprint Review in Agile practices, emphasizing collaboration and feedback. They highlight the misconceptions around the event being just a demo and provide tips on making the review more effective. Topics include stakeholder involvement, structuring effective meetings, and managing expectations.

This week, Brian Milner is joined by Julie Chickering to talk about the best practices and common pitfalls to avoid during the Daily Scrum event. Overview Brian Milner and Julie Chickering discuss the true purpose of the Daily Scrum and how to make this 15-minute meeting more efficient. According to the Scrum Guide, the Daily Scrum is to inspect progress towards the Sprint Goal, synchronize activities, and create a plan for the next 24 hours. Debunking the myth that “The Daily Scrum is a Status Meeting”, Julie and Brian share their first-hand experience of this misconception and show Scrum Masters how to transform the Daily Scrum into a purposeful and collaborative planning session led by the Developers, for the Developers. You’ll learn how to get your Daily Scrum under control and discover new approaches to encourage productivity, accountability and collective ownership as well as Daily Scrum formats that encourage teamwork. Finally, Brian and Julie dive deep into the struggles brought by remote working and the many alternatives to tackle this issue. Listen now to discover: -        02:00 - The purpose of the daily scrum and common misconceptions -        11:00 - How to use the sprint backlog to prioritize work -        00:12 - The importance of teamwork and striving for smaller stories that flow -        14:56 - How to encourage developers to take ownership of the Daily Scrum -        00:20 - Suggestions for Daily Scrum formats to encourage teamwork -        00:22 - When to update items on the Sprint Backlog to benefit the Daily Scrum meeting -        00:25 - How to encourage accountability and collective ownership of work -        00:27 - How to monitor and assess unplanned work and forecast velocity -        00:35 - Guidelines for problem identification and problem solving during the Daily Scrum -        00:38 - How to adapt the Daily Scrum for distributed teams in a remote world -        00:44 - The benefits of cross training -        00:45 - The 16th minute concept -        00:47 - Ken Schwaber’s clockwise scrum methodology Listen next time when we’ll be discussing... Julie joins Brian again to explain the true purpose of the Sprint Review and why it is a mistake to call this event a ‘demo’. References and resources mentioned in the show ·       Agile Project Management with Scrum by Ken Schwaber ·       The Scrum Guide Want to get involved? This show is designed for you, and we’d love your input. ·       Enjoyed what you heard today? It would be great if you left a rating and a review. It really helps, and we read every single one. ·       Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Julie Chickering is a certified Scrum Trainer as well as a CST, PMP, PMI-ACP CSM, CSPO, and Path to CSP Educator. She believes that Agile practices are packed with potential — to enable business agility, and breakthrough results. Julie loves to help people implement agile even when the environments are messy, people are complicated, and situations are challenging. She brings real-world experience working with people at all levels to adopt and roll out realistic Agile strategies organization-wide.

In this episode, Scott Dunn and Brian review the key aspects of leading an effective sprint planning meeting: its purpose, how it works, who attends, and ensuring yours are achieving the desired result. Overview Brian Milner and Scott Dunn discuss product ownership and leading a sprint planning meeting. 2020’s Scrum Guide introduced new guidance: sprint planning must go beyond the WHAT and the HOW of product backlog items to the WHY, specifically why is the sprint valuable? Scott shares his firsthand experience of how to run an effective sprint planning meeting, including focusing on the ‘Why?’ plus practical advice on increasing an agile team’s motivation and engagement. You’ll learn why the product owner-development team relationship is the linchpin of sprint-planning success and the primacy of preparation, forward vision, and a value-driven mindset. Final advice includes better communication of expectations with distributed team members and aligning with the evolving nature of the tech landscape through trying new approaches. Listen now to discover: ·       04:00 – How asking ‘Why?’ adds value and motivates, empowers, and engages teams ·       07:00 – Why the relationship between the product owner and development team is the linchpin of success ·       10:00 – What level of detail Scrum teams should be striving for during a sprint planning meeting ·       12:00 – The purpose of a sprint review and what needs to change in order to support inclusive collaboration ·       14:00 – How to leave room for discovery with minimal documentation ·       15:52 – How flexible requirements and ongoing conversation enable collaboration and employee engagement ·       17:00 – How to remain focused on driving value when facilitating sprint planning meetings ·       19:00 – The mindset shift required to define value through conversation and negotiation ·       21:30 – Craig Larman methodology - culture follows structure ·       22:00 – Why assigning work during sprint planning kills collaboration and team spirit ·       26:00 – The purpose of the sprint planning meeting and how to maximize the time allocated ·       27:30 – The restrictions of forward planning and how to find confidence in emergent architecture to align with the changing nature of tech organizations ·       30:00 – How product owners in sprint planning can improve efficiency through preparation ·       34:00 – Tips for distributed teams: adapting to remote working, improving communication, and more effective sprint planning ·       40:30 – The ‘Inspect and Adapt’ concept: the importance of trying new approaches and implementing new methods.  Listen next time when we’ll be discussing . . . Daily scrums with certified Scrum trainer, Julie Chickering. You’ll learn the true purpose of this 15-minute time-boxed event as well as common pitfalls and mistakes to avoid in this meeting. References and resources mentioned in the show: ·       Larman's Laws of Organizational Behavior ·       David Hawks Want to get involved? This show is designed for you, and we’d love your input. ·       Enjoyed what you heard today? Take a second to leave a rating and a review. It really helps, and we read every single one. ·       Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are: Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work. Scott Dunn is a Certified Enterprise Coach and Certified Scrum Trainer with more than 20 years of experience in management, project management (PMP), engagement management, and software development (MCSD). He is passionate about strengths-based teams and a solutions-based approach to people and organizational issues. Show edited by Rhett Gill.

Join Brian Milner and Sherman Gomberg for a discussion of the importance of a Scrum team’s developers and why self-organizing teams are at the heart of agile methodologies like Scrum.  In this episode of the Agile Mentors podcast, Brian Milner and Sherman Gomberg discuss the evolution of one of the Scrum roles: developer. They also explain why self-organizing teams of developers have become critical to all organizations.  On agile projects, developers are the people who “do the work” and while at first glance you may see agile developers as always engineers or other software development professionals, that’s not invariably the case. According to the Scrum Guide, the development team can be composed of all kinds of people including designers, writers, programmers, etc. Using over 25 years of Scrum, agile, and project management experience, Sherman and Brian compare notes on the topic of how to build and sustain agile, self-organizing teams. They share their insights and advice on why empowering individuals to work in cross-functional agile teams leads to greater efficiency, higher rewards, and lower risks.  Listen now to discover:  -       03:38 –How to tell whether your agile team is self-organizing -       05:25 – The advantages of having self-organized teams in agile environments  -       07:10 – Bruce Tuckman’s four stages of team development: Forming, Storming, Norming, and Performing -       09:17 – Advice for Scrum Masters and product owners on how to promote self-organization among team members -       09:60 – The parallels between software teams and sports teams: self-organize and work together to shine  -       13:34 – How and why to build a learning organization  -       18:00 – The definition of “self-managing” as cited by the Scrum Guide -       22:00 – How to address bug-fixing and technical debt during a sprint -       28:00 – The three most valuable practices adopted by developers in a sprint -       37:50 – The importance of understanding the developer role and why all three roles on a Scrum team should take a Scrum developer course -       40:48 – The role of a tech lead in Scrum   -    43:00 – Why it is essential to form a team of equals and how self-organization works to support this  Listen next time when we’ll be discussing… Sprint planning with guest co-host Scott Dunn. You’ll learn about the sprint planning event as described in the Scrum Guide and the 3 essential “Why? What? How?” topics addressed in order to plan successful sprints. References and resources mentioned in the show ●      Scrum Guide ●      The Bruce Tuckman Model ●      The Agile Manifesto       Want to get involved?  This show is designed for you, and we’d love your input.  ●      Enjoyed what you heard today? Don’t forget to rate and review: it really helps!  ●      Got an agile subject you’d like us to discuss or a question that needs an answer? Share your thoughts with us at podcast@mountaingoatsoftware.com This episode’s presenters are:  Brian Milner is SVP of coaching and training at Mountain Goat Software. He’s passionate about making a difference in people’s day-to-day work, influenced by his own experience of transitioning to Scrum and seeing improvements in work/life balance, honesty, respect, and the quality of work.  Sherman Gomberg is CEO at Scrum Adventures, Inc. He is a CTC and has a total of eleven certifications from the Scrum Alliance. He has over 25 years of experience with agile, Scrum, and project management across various industries. He enjoys working with teams during breakout sessions in online courses, where he helps to bring curiosity to valuable discussions and in doing so, moves the needle from training to knowledge obtained to knowledge applied.