Agile Mentors Podcast from Mountain Goat Software

This week, Brian Milner is joined by Julie Chickering to talk about the wild world of Project Management. Overview Brian Milner and Julie Chickering discuss how the world of project management can blend successfully with an Agile approach. There seems to sometimes be an attitude that it’s an either/or decision with these two. In this podcast, we take a look at how to blend them, how project managers fit in, and how these two disciplines can coexist. Julie brings her experience to this discussion having come from the project management realm. Listen now to discover: 3:42 - Brian asks Julie about the general distrust between these communities 6:15 - Julie shares that 50% of the PMP exam now is on Agile practices 8:38 - Julie brings up the dreaded status report - Green / Yellow / Red 12:10 - Julie brings up the politics of Green / Yellow / Red 15:10 - Julie talks about the cost of poor quality 16:26 - Are we in the Agile community making PMs feel wrong? 17:22 - Brian discusses Outcomes vs Output 26:10 - Brian asks about PMs who are in companies making transitions. What happens to the project managers? Listen next time when we’ll be discussing... Brian and Mike Cohn share some of the best questions from their live coaching calls on the Agile Mentors community. References and resources mentioned in the show Monty Python Project Management Institute The Cowman and the Farmer Should be Friends from Oklahoma! HBR article on Output vs Outcomes From Project Manager to Scrum Master - 3 Tips for Making the Transition Agile Project Management by Jim Highsmith The Software Project Manager’s Bridge to Agility by Michele Sliger and Stacia Broderick PM Illustrated: A Visual Learner’s Guide to Project Management by Mike Griffiths - free on Kindle 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.

Lyssa Adkins joins Brian to talk about the wonderful world of Agile coaching. Overview When you think of the term “Agile Coach,” what comes to mind for you? This term has meant many different things over the years. Are we talking about a role or an approach? Lyssa Adkins, author of Coaching Agile Teams, joins Brian to dive into this topic. Lyssa has written and spoken about this topic for years and many would say she had a large hand in defining what we now call agile coaching. Listen now to discover: 02:05 - Brian shares a story about Lyssa from the Vienna Scrum Gathering conference 06:40 - Lyssa answers the question, “What is an Agile Coach?” 08:10 - Lyssa explains the unintended consequence of using the term “coach” in her book 12:02 - Lyssa talks about the “X-Wing Diagram” and the 5 coaching stances 18:50 - Lyssa talks about not colluding when someone in power pushes something you disagree with 27:04 Lyssa talks about coaching in a remote world Listen next time when we’ll be discussing… Project Management with Julie Chickering. References and resources mentioned in the show Coaching Agile Teams by Lyssa Adkins Agile Coach Competency Framework Developing Great Agile Coaches whitepaper describing 5 coaching stances What is an Agile Coach? talk with Lyssa Adkins and Michael Spayd 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. Lyssa Adkins has been one of the foundational voices in the Agile community for years now. Her book Coaching Agile Teams has been a best seller for over 12 years now. She released an audio version of this classic book on its 10th anniversary. In 2010, Lyssa co-founded the Agile Coaching Institute which has developed over 10,000 people in the knowledge, skills, and being-ness needed to yield genuinely competent agile coaching. She is a member of the ICAgile working committee and has served as a reviewer for the Scrum Alliance’s Certified Enterprise Coach certification program. Lyssa is also dedicated to amplifying women’s voices and is a founder of TENWOMENSTRONG #WomenInAgile programs. Show edited by Rhett Gill.

David Hawks joins Brian to discuss the process of an organization becoming Agile. Overview When you read through the Scrum Guide, the picture it paints is of the desired end result - what the team/organization should look like when finished. There’s surprising little said though about how you get from where you are to where you want to eventually be. Enter the topic of Agile Transformations. There is a journey that organizations undertake when they decide to adopt Agile and like any journey, it’s always helpful to have a guide to help you get there who has been through it before. David Hawks joins Brian to share his experience in helping countless organizations make this journey to become Agile. Listen now to discover: 03:10 Brian asks David what the biggest hurdle is that organizations have when adopting Agile? 05:24 David explains that multiple levels the organization needs to focus on in the process 11:00 David talks about “Implementing Practices over Outcomes” 16:30 Brian asks what individuals who aren’t leaders can do to help? 20:20 Brian asks David to explain how his Path to Agility helps address these issues? 29:35 Brian talks about the Spotify Engineering Culture videos example Listen next time when we’ll be discussing… Agile Coaching with Lyssa Adkins! References and resources mentioned in the show Path To Agility & Agile Velocity SAFe and LeSS Yellowstone spinoff 1883 Oregon Trail Spotify Engineering Culture Video 1 and Video 2 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. David Hawks is the CEO of both Agile Velocity and Path to Agility. He is a Certified Scrum Trainer as well as a Certified Enterprise Coach with the Scrum Alliance - their top two certifications. He received his Bachelor of Business Administration in Management Information Systems degree from the University of Texas at Austin. His love for his beloved Longhorns from UT is only eclipsed by his love (and expertise) in tailgating prior to their home games! Show edited by Rhett Gill.

Mitch Lacey joins Brian to talk about building quality into our work. Overview The Scrum Guide says the developers own quality and that it is both a right and responsibility of the team. What does that look like though? What do we mean when we say quality? How do teams practically go about building quality or is it just “baked in?” Join Brian and Mitch Lacey as they discuss this all important secret ingredient to the Scrum framework and hear why it’s so vital to a team’s success. Listen now to discover: 2:25 Mitch explains what we mean by quality 6:48 Brian asks Mitch how to tell when you are “gold plating” things? 12:30 Brian asks about the developer who thinks the code needs to be perfect before they release 16:55 Brian talks about the last stage of the creative process is releasing 21:25 Mitch relates self-accountability to a recent Soccer(Football) match 22:34 Brian and Mitch discuss the infamous “Squirrel Burger” story Listen next time when we’ll be discussing… David Hawks joins us as we discuss transformations. References and resources mentioned in the show Test Driven Development “Squirrel Burger” story 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. Mitch Lacey is an agile practitioner and trainer. Mitch has been managing projects for over fifteen years & is credited with many plan-driven & agile projects. He is the author of “The Scrum Field Guide,” a book targeting teams adopting agile and Scrum practices. He has published many papers, including “Adventures in Promiscuous Pairing,” “Transitioning to Agile: Key Lessons Learned in the Field,” “The Impacts of Poor Estimating -& How to Fix It,” plus a variety of papers for Microsoft and “Immersive Interviewing -Building Great Agile Software Teams.” Show edited by Rhett Gill.

Brian takes some of the most popular questions about Scrum from Quora.com and answers them. Overview If you are unfamiliar with it, Quora.com is a site people in the technology industry go to to ask and answer questions. For a change of pace, I decided to take a batch of the most popular questions from the site and provide my own answers to them. If you have questions you’d like to include in a similar episode in the future, make sure to email them to podcast@mountaingoatsoftware.com. Listen now to discover: 01:14 Brian explains the premise behind this episode’s topic 02:25 Question 1: Why do iterations in Agile start from Wednesday to Tuesday rather than Monday to Friday? 09:00 Question 2: Are Burndown charts even useful? 16:14 Question 3: Who decides sprint duration in a Scrum project? 18:50 Question 4: As a Scrummaster, how do you deal with people being late or refusing to come to Daily Scrums? 24.32 Question 5: Can a User Story be used for bugs? 26:54 Question 6: Can Agile work without a Scrummaster? Listen next time when we’ll be discussing… Join us next time where we will be discussing the topic of Quality with our guest Mitch Lacey. References and resources mentioned in the show Send your questions for a future episode to podcast@mountaingoatsoftware.com. 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 presenter is: 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. Show edited by Rhett Gill.

Scott Dunn joins Brian to talk about what it means to be product-centric Overview Being product-centric has become a recent buzzword and objective for companies. But what does it mean? Is it the 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 can stop teams from being more focused on the customer and long-term product value, such as being forced to fight those daily fires. Listen now to discover: 00:23 - What does the term product-centric mean? 07:13 - Is there a difference between being product-centric and customer focused? 14:47 - Are nonprofits customer-focused entities? 22:02 - Does product-centric mean putting quality first? 28:23 - How does a disconnect between leadership and teams affect things? Listen next time when we’ll be discussing… Next time, I’ll be answering questions you’ve sent into the show as well as addressing other common agile questions. References and resources mentioned in the show Impact Mapping and Story Mapping The Scrum Guide Kano Model for prioritization 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. Show edited by Rhett Gill.

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.