Podcast appearances and mentions of Ron Jeffries

On this episode, Clay Birkeland talks with Ron Jeffries, General Manager of the Black Hills Stock Show about all the news and happenings at this year's event. Hosted on Acast. See acast.com/privacy for more information.

Melissa Perri is the founder of Product Institute, author of Escaping the Build Trap, and host of the Product Thinking Podcast. She has worked with startups, Fortune 50 companies, and everything in between to help them build better products and level up their product teams. In our conversation, we discuss:• The history of the product owner role• The differences between product owners and product managers• How to transition from product owner to product manager• The evolution of and problems with the SAFe framework• How large non-tech companies can improve their product practices• Much more—Brought to you by:• Pendo—The only all-in-one product experience platform for any type of application• OneSchema—Import CSV data 10x faster• Coda—The all-in-one collaborative workspace—Find the transcript at: https://www.lennysnewsletter.com/p/product-owners-melissa-perri—Where to find Melissa Perri:• X: https://twitter.com/lissijean• LinkedIn: https://www.linkedin.com/in/melissajeanperri/• Website: https://melissaperri.com/• Product Institute: https://productinstitute.com/• Podcast: https://www.produxlabs.com/product-thinking—Where to find Lenny:• Newsletter: https://www.lennysnewsletter.com• X: https://twitter.com/lennysan• LinkedIn: https://www.linkedin.com/in/lennyrachitsky/—In this episode, we cover:(00:00) Melissa's background(02:12) The rise of the product owner role(06:37) Understanding Agile and Scrum(08:27) Challenges in Agile transformations(10:41) The history of the product owner role(13:58) The Scrum Guide(15:43) Product owner responsibilities(21:01) Adopting Scrum in organizations(26:21) The origins and implementation of SAFe(35:20) Why Melissa doesn't recommend SAFe(40:33) Advice for implementing a digital transformation(49:12) An example of SAFe adoption(51:27) The value of experienced product leaders(56:53) Career paths for product owners(01:04:14) Transitioning from product owner to product manager(01:06:41) Be careful relying on certifications(01:11:43) Evaluating existing product owners(01:16:55) Final thoughts on Agile and product management—Referenced:• Escaping the Build Trap: How Effective Product Management Creates Real Value: https://www.amazon.com/Escaping-Build-Trap-Effective-Management/dp/149197379X• Lean UX: https://leanuxnyc.co/• Scrum: https://www.scrum.org/• What is Extreme Programming? https://www.agilealliance.org/glossary/xp/• Capital One: https://www.capitalone.com/• The Agile Manifesto: https://www.atlassian.com/agile/manifesto• Ken Schwaber on X: https://x.com/kschwaber• Jeff Sutherland on X: https://x.com/jeffsutherland• Kanban: https://www.atlassian.com/agile/kanban• What is a kanban board?: https://www.atlassian.com/agile/kanban/boards• Ron Jeffries's website: https://www.ronjeffries.com/• Jeff Patton on X: https://x.com/jeffpatton• The Scrum Guide: https://www.scrum.org/resources/scrum-guide• OpenSky: https://www.openskycc.com/• SAFe: https://scaledagileframework.com/• Dean Leffingwell on LinkedIn: https://www.linkedin.com/in/deanleffingwell/• Capital One scraps 1,100 tech positions: https://www.reuters.com/technology/capital-one-scraps-1100-tech-positions-source-2023-01-19/• Product management theater | Marty Cagan (Silicon Valley Product Group): https://www.lennysnewsletter.com/p/product-management-theater-marty• Marty Cagan on LinkedIn: https://www.linkedin.com/in/cagan/• Jeff Gothelf on X: https://x.com/jboogie• Shruti Patel on LinkedIn: https://www.linkedin.com/in/shruti-patel-32bb573a/• Product Thinking Podcast: Mastering Product Focus: Balancing Legacy and Innovation with Shruti Patel: https://www.produxlabs.com/product-thinking-blog/2024/9/25/episode-190-mastering-product-focus-balancing-legacy-and-innovation-with-shruti-patel• Melissa Douros on LinkedIn: https://www.linkedin.com/in/melissadouros/• Mind the Product: https://www.mindtheproduct.com/• Athenahealth: https://www.athenahealth.com/• McKinsey: https://www.mckinsey.com/—Production and marketing by https://penname.co/. For inquiries about sponsoring the podcast, email podcast@lennyrachitsky.com.—Lenny may be an investor in the companies discussed. Get full access to Lenny's Newsletter at www.lennysnewsletter.com/subscribe

Episode 494 - a Somber News Week Episode Happy Monday, Thieves! We had a heavy news week last week, between the devastating floods that hit the Asheville region and word that famed brewer Ron Jeffries passed away. We sat town to talk about what's happening out there along with a surprise guest and a couple of black glasses. Tune in and let us know what you think.***As always, you can email your questions, complaints, whimpers, or whines to us at stealthisbeerpodcast@gmail.com. We read everything we get and we'll try to respond as quickly as we can. If not online, then on air. And THANKS! You can subscribe to STB on iTunes and PLEASE LEAVE US A REVIEW!!! Co-hosts: Augie Carton & John Holl Producer: Justin Kennedy Engineer: Brian Casse Music: "Abstract Concepts - What Up in the Streets" by Black Ant.

We're reviewing Ron Jeffries article: "Estimation is Evil" from the February 2013 issue of the Pragmatic Programmers magazine.This article is mostly known for being the source most people quote when they say the inventor of story points is sorry he created them, or that the inventor of story points doesn't like story points. We dig into this claim, reading the article and summarizing and pontificating on key points.Join, Enterprise Agility Coach Om Patel and Product Manager Brian Orlando as they time-travel back to the not-so-good old days of 2013 (and before)!The source article:https://ronjeffries.com/articles/021-01ff/estimation-is-evil/0:00 Topic Intro: Estimation is Evil by Ron Jeffries1:14 Article Opening: A Historical Snapshot7:07 Undistinguished Teams8:45 "All Our Requirements" is Wrong11:06 80/20 Rule in Requirements14:11 Forcing the Answer16:05 Contracts in Agile18:11 Forecasting & Stretch Goals24:52 Asking for "Better" Estimates28:28 Financing Software31:41 How Much Do You Want to Spend?35:24 Relative Estimation (the Soundbite Section)40:17 Two Ways to Go44:58 Article Conclusion52:33 Summary54:02 Wrap-Up= = = = = = = = = = = =Watch it on YouTubePlease Subscribe to our YouTube Channel:https://www.youtube.com/@arguingagile= = = = = = = = = = = =Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = = 

Suppose you believed that the ecological/embodied cognitive scientists of last episode had a better grasp on cognition than does our habitual position that the brain is a computer, passively perceiving the environment, then directing the body to perform steps in calculated plans. If so, technical practices like test-driven design, refactoring in response to "code smells," and the early-this-century fad for physical 3x5 cards might make more sense. I explain how. I also sketch how people might use such ideas when designing their workplace and workflow. Books I drew uponAndy Clark, Being There: Putting Brain, Body, and World Together Again, 1997Alva Noë, Action in Perception, 2005Also mentionedGary Klein, Sources of Power: How People Make Decisions, 1998I mentioned a session of the Simple Design and Test conference.The sociology book I contributed to: The Mangle in Practice: Science, Society, and Becoming, 2009, edited by Andrew Pickering and Keith Guzik. My chapter, "A Manglish Way of Working: Agile Software Development", is inexplicably available without a paywall.The MIT AI Lab Jargon FileI believe the original publication about CRC cards is Kent Beck and Ward Cunningham, "A laboratory for teaching object oriented thinking", 1989. I also believe the first book-type description was in Rebecca Wirfs-Brock et. al., Designing Object-Oriented Software, 1990. The idea of "flow" was first popularized in Mihály Csíkszentmihályi's 1990 Flow: The Psychology of Optimal Experience. The idea of the hedgehog and the fox was popularized by Isaiah Berlin in his 1953 book The Hedgehog and the Fox (a wikipedia link).The original developer of the Pomodoro technique describes it here. There was a book about it, but Goodreads has been sufficiently enshittified that I can't find it. Perhaps you might be interested in Reduce PTSD and Depression Symptoms in 21 Days Using the Pomodoro Method instead? Because Goodreads prefers that.The Boy Who Cried World (wikipedia)CreditsI was helped by Steve Doubleday, Ron Jeffries, and Ted M. Young. I took the picture of Dawn in the tango close embrace.

For episode 300 we have a stacked panel in to discuss one of the most precipitous rise and falls in modern craft beer - The American Wild / Sour AleNo punches are pulled as we discuss the origins of these beers, why they became the darling of the craft beer world, and their fall from grace - all with input from people who were there to experience it first hand. Plus we talk about why this fall might ultimately be a good thing, and reasons to feel optomistic about the future of some of the most complex and beautiful beers ever created. Featuring Paul Arney of Ale Apothecary, Vinnue Cilurzo of Russian River, Ron Jeffries of Jolly Pumpkin, and John Laffler of Off Color.  Email Eletters to: Insiders@craftbeertemple.comMailing address: The Beer Temple 3173 N. Elston Ave. Chicago, IL 60618Intro/Outro Music: Gorilla Meat by Jogger UYD4L!

The final episode of "the Foucault trilogy". Ways of evaluating humans that became common during the ~1750-1850 period. Bentham's Panopticon as a metaphor. Self-improvement via exhibitionism. Final reflections on Foucault.SourcesMichel Foucault, Discipline and Punish: the Birth of the Prison, 1975.C.G. Prado, Starting With Foucault (2/e), 2000.Ian Hacking, The Social Construction of What?, 1999.Other sourcesMississippi State University Extension, "Dairy Cattle Judging".Jeremy Bentham: The Panopticon Writings (PDF), Miran Božović (ed.), 1995.The Koepelgevangenis panopticon is described in "The Panopticon Effect" podcast episode. (There is no transcript, but there is a longish narrative.)Ron Jeffries, "Big Visible Charts", 2004."Brainless slime mold grows in pattern like Tokyo's subway system", 2022 (video).Contact links (if you want the bonus episode on "Edgelord Foucault")Email: marick@exampler.comMastodon: @marick@social.oddly-influenced.devPicture creditBigVisibleCharts.com (archived), Marty Andrews.

In today's episode I'm joined by J. B. Rainsberger for an assessment of what value can be derived from using ChatGPT as a programming tool. We also discuss why you should write your tests backwards, using ChatGPT to make tests pass, and J. B.'s philosophy and approach as a consultant.  Finally, we get into the benefits of joining J. B.'s JBrains Experience mentoring group.Extreme Programming Explained by Kent BeckExtreme Programming Installed by Ron Jeffries, Ann Anderson, and Chet HendricksonPlanning Extreme Programming by Kent Beck and Martin FowlerSwitch by Chip and Dan HeathTest Driven Development at Wiki.C2.comJBrains.ca - J.B. Rainsberger's SiteThe JBrains ExperienceThe Code WhispererBlog.JBrains.caThe World's Best Intro to TDD, Level 1J. B. Rainsberger on Twitter

Key things discussed The connection between business agility and OKRs in private equity The role of OKRs in alignment and focus within an organization The principles shared by various frameworks such as OKRs, Scrum, and SAFe The importance of understanding and implementing frameworks effectively The benefits of dynamic team organization and shuffling based on OKRs The value of discussing outcomes rather than specifying outputs and having conversations about OKRs The dangers of chasing the next shiny thing without fully understanding and implementing it The connection between agile principles and OKR success The role of transparency, collaboration, and psychological safety in creating a successful environment for progress and continuous improvement The challenges and opportunities in improving work environments and creating meaningful progress in organizations. Show Notes [03:04] Yuval walks us through his background in IT and product development and begins using agile practices in his work. After moving to the US in 2015, he started consulting and coaching different types of organizations and began incorporating OKRs into his work with agile processes and helping organizations improve their use of OKRs. [04:33] Yuval walks us through his experience in private equity The role of OKRs and business agility in private equity The investment hypothesis How to apply agility to the process of finding the right way to reshape your go-to-market strategy [09:03] Yuval dives deep on when OKRs are not applicable [11:03] Yuval shares his insights and examples of best applications of OKRsOKRs are an alignment framework [12:43] A look at how Prezi, a presentation software, and their OKR-friendly way of managing the work in their organization [14:47] A look at the different frameworks (OKR, Scrum, SAFe) [16:03] The pitfalls of not getting the value or understanding the different frameworksHow organizations struggle to get value out of OKRs [19:41] High-level overview of Ron Jeffries and Scrum One of the three founders of the Extreme Programming software development and The Agile Manifesto Ron Jeffries' article: “We Tried Baseball and It Didn't Work” [20:35] What makes Scrum great? A relatively simple and lightweight framework that's really laser focused on achieving empiricism The structure of Scrum and how it can be used to develop the business How to create a rhythm of making progress in an environmental uncertainty with Scrum [28:06] Scrum became popular and spread quickly Many people using Scrum did not fully understand the principles and applied it with traditional project management approaches These people saw Scrum as a template rather than a continuous improvement process This led to the development of "Scrum Theater" or "Zombie Scrum" where people were just going through the motions of Scrum without fully understanding and implementing its principles When an approach becomes too popular, the knowledge about it becomes thinned out and there are more people who are just following it because it is popular, leading to more haters of the approach [33:31] Yuval discusses how OKRs should be used for goal alignment and focus on outcomes, in conjunction with evidence-based management. He stresses the importance of empiricism and empowering teams to achieve outcomes. [37:06] Yuval is discussing the concept of empowerment in agile processes and how it leads to better solutions and motivated employees. He emphasizes the importance of providing teams with the necessary knowledge and expertise and allowing them the autonomy to come up with and execute experiments within certain constraints. He also discusses the role of frequent feedback and access to leadership in empowering teams. [42:06] Jenny and Yuval are discussing how empowering teams to achieve a specific goal can lead to innovative solutions and improved business performance. The importance of empowering teams to achieve goals and the motivation and effectiveness of empowered teams The role of constraints in providing direction for teams while still allowing for flexibility and creativity The value of fast feedback loops and cross-functional collaboration in achieving outcomes The dangers of micromanaging and a lack of safety in communication The concept of "scheduled chicken" in which multiple groups work towards a deadline without being transparent about issues or challenges. The use of OKRs to align organizations around goals and focus on outcomes The benefits of using empiricism and focusing on outcomes rather than activities The concept of evidence-based management, which involves continuously evaluating progress and adjusting course as needed [46:25] Quick Fire Questions for Yuval: What's your Dream with a Deadline? Yuval's goal is to help organizations create environments that allow people to have an impact on work processes and to provide more case studies on this topic in the next few years. Can you share an example of a meaty strategy execution challenge, and how did they overcome it? Relevant links: Prezi's product development approach Ron Jeffries, one of the three founders of the Extreme Programming software development Fixing OKR Theater Using Agile/Scrum Principles Ron Jeffries' article on Scrum: “We Tried Baseball and It Didn't Work” Scrum.org Evidence-Based Management Guide Yuval Yeret's article on OKR Theater and OKRs in Name Only  Zombie Scrum, an article by Barry Overeem on Scrum.org "Fixing your OKRs”, an article by Yuval Yeret About Our Guest:Yuval Yeret is an expert on agile methodologies and OKRs, with experience in coaching and consulting a variety of organizations on their agility journey. With a background in IT and product development, he has helped businesses improve value and profitability through private equity deals and digital transformations.Follow Our Guest:Website | LinkedInFollow Dreams With Deadlines:Host | Company Website | Blog | Instagram | Twitter

John Miller joins Brian to talk about Agile in the classroom. Overview Agile classrooms help students develop skills that will serve them long after they've left the classroom. John Miller is a Certified Enterprise Coach (CEC) and the Chief Empowerment Officer for Agile Classrooms. Today on the show, John joins Brian to share how he started introducing the Agile framework to educators. He walks us through how Agile classrooms help students solve complex problems while developing decision-making skills. He'll share how converting to an Agile classroom creates deeper, more fulfilling student and teacher relationships and the steps teachers can take to make their classroom an Agile classroom. Listen now to discover: [01:27] - Brian introduces John Miller and explains how, as a CEC, he's reached the highest rung on the Scrum Alliance certification ladder. [03:33] - How John got started with bringing Agile to the classroom. [06:09] - The collaboration between John and the educators to achieve the goal of creating a self-managing classroom. [09:45] - John shares how he went from thinking he'd ruined one class's education to watching them become one of the best self-managing groups he's ever seen. [12:16] - How children's lack of preconceived notions about how things are supposed to work helps them create teams that work. [13:48] - How an Agile classroom empowers students of all levels and learning abilities. [14:36] - The five levels of choice in an Agile classroom. [15:44] - John shares the objective of Agile classrooms to help students solve complex problems by developing choice-making skills. [17:55] - Brian shares that "Scrum is a sports analogy." [19:33] - Dark Scrum vs. Bright Scrum. John shares the formula he created using Ron Jeffries' term Dark Scrum. [24:06] - Is Agile dead, or are people just doing it wrong? [25:13] - John shares the levels of classrooms where Agile works best. Plus, which one did he work with that made him more nervous than high-level CEOs? [27:12] - John explains how the different dynamics lead to different success outcomes for incorporating Scrum into the classroom. [28:42] - What size classrooms achieve the most benefits from working with Scrum? [29:44] - John shares the steps teachers can take to make their classroom an Agile classroom. [31:20] - How converting to an Agile classroom creates deeper, more fulfilling teacher-student relationships. [31:53] - How Agile in the classroom acts as a bridge to industry and a life skills primer. References and resources mentioned in the show Agile Mentors Community Scrum Alliance Agile Classrooms Dark Scrum Agile Manifesto McGregor's Theory 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? Please 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. John Miller is a Certified Enterprise Coach (CEC) and the Chief Empowerment Officer for Agile Classrooms. Since 2012, John's mission through Agile Classrooms has been to help educators take a more innovative and creative approach to guiding faculty, managing their schools, and teaching students.

John Miller joins Brian to talk about Agile in the classroom. Overview Agile classrooms help students develop skills that will serve them long after they've left the classroom. John Miller is a Certified Enterprise Coach (CEC) and the Chief Empowerment Officer for Agile Classrooms. Today on the show, John joins Brian to share how he started introducing the Agile framework to educators. He walks us through how Agile classrooms help students solve complex problems while developing decision-making skills. He'll share how converting to an Agile classroom creates deeper, more fulfilling student and teacher relationships and the steps teachers can take to make their classroom an Agile classroom. Listen now to discover: [01:27] - Brian introduces John Miller and explains how, as a CEC, he's reached the highest rung on the Scrum Alliance certification ladder. [03:33] - How John got started with bringing Agile to the classroom. [06:09] - The collaboration between John and the educators to achieve the goal of creating a self-managing classroom. [09:45] - John shares how he went from thinking he'd ruined one class's education to watching them become one of the best self-managing groups he's ever seen. [12:16] - How children's lack of preconceived notions about how things are supposed to work helps them create teams that work. [13:48] - How an Agile classroom empowers students of all levels and learning abilities. [14:36] - The five levels of choice in an Agile classroom. [15:44] - John shares the objective of Agile classrooms to help students solve complex problems by developing choice-making skills. [17:55] - Brian shares that "Scrum is a sports analogy." [19:33] - Dark Scrum vs. Bright Scrum. John shares the formula he created using Ron Jeffries' term Dark Scrum. [24:06] - Is Agile dead, or are people just doing it wrong? [25:13] - John shares the levels of classrooms where Agile works best. Plus, which one did he work with that made him more nervous than high-level CEOs? [27:12] - John explains how the different dynamics lead to different success outcomes for incorporating Scrum into the classroom. [28:42] - What size classrooms achieve the most benefits from working with Scrum? [29:44] - John shares the steps teachers can take to make their classroom an Agile classroom. [31:20] - How converting to an Agile classroom creates deeper, more fulfilling teacher-student relationships. [31:53] - How Agile in the classroom acts as a bridge to industry and a life skills primer. References and resources mentioned in the show Agile Mentors Community Scrum Alliance Agile Classrooms Dark Scrum Agile Manifesto McGregor's Theory 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? Please 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. John Miller is a Certified Enterprise Coach (CEC) and the Chief Empowerment Officer for Agile Classrooms. Since 2012, John's mission through Agile Classrooms has been to help educators take a more innovative and creative approach to guiding faculty, managing their schools, and teaching students.

Join Clay Birkeland, Director of Ag Banking at Pioneer Bank & Trust as he talks with the one man that knows more than just about anyone when it comes to the Black Hills Stock Show and Rodeo, Ron Jeffries. See acast.com/privacy for privacy and opt-out information.

Join Murray Robinson and Shane Gibson in a no-nonsense agile discussion. In this podcast, we discuss Ron Jeffries' recent article “Can scrum be fixed?” We talk about Ron's concerns with the Scrum Industrial complex and Developers issues with Scrum. We talk about what we like and don't like about Scrum and how the gaps we've experienced can be overcome. You can read the podcast transcript over at https://www.ev0lve.work/podcast/is-scrum-broken   Listen to the podcast on your favourite podcast app: | Spotify | Apple Podcasts | iHeart Radio | PlayerFM | Amazon Music | Listen Notes | TuneIn |    Connect with Murray via email or Shane in the Twitter-sphere  @shagility.   The No Nonsense Agile podcast is sponsored by: Simply Magical Data

En este capítulo hablaremos de la deuda técnica en los proyectos de desarrollo de software y mencionaremos 3 maneras de afrontarla a diferentes niveles de abstracción: desde el bajo nivel hasta el alto nivel. Algunos enlaces a las cosas que comentamos en el capítulo: La regla del Boy Scout Consejos de Ron Jeffries para afrontar la deuda técnica Charla sobre cómo decidir en qué invertir el dinero en el desarrollo de software Unidades de medida: WTFs/m

#5amMesterScrum Show #623 Live -  3Cs of Daily Scrum and Why Daily Scrum? - Today's topics: (1) Why Daily Scrum?  Because emails and texts lose the need level for help, and (2) the 3C's of the Daily Scrum borrowed from Ron Jeffries' 3C's of a story from 2001.  The Card, Conversation and Confirmation. 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 #dailyscrum #card #conversation #confirmation #3Cs   5am Mester Scrum Show #623 went live on Youtube at 611pm EST Tuesday 5/18/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) 

CRAFT BEER PODCAST INFO: Josh joins us on the cold Muskegon night to talk about the Big Gretch Beer, brewing under Ron Jeffries and Travis Fritts, low ABV beers and changing the perception of Muskegon one visit at a time.  If you're from the west side of the state or have been hesitant, Josh gives you many good food and drink tips for exploring the city!  00:00- Ads01:00- Introductions05:01- Introduction into Rake Beer Project05:57- Work History08:22- Local Agriculture Programs 09:57- Out Back Counting Stars and Dream Collaborations11:28- The Family (Mug Club)13:05- Reasons for Not Distributing / Changing Muskegon’s Perception16:00- Josh’s Favorite Beer Styles17:19- Modern Beer Styles by Traditional Brewing Methods21:23- Table Beers and Low ABV Beers25:18- Production Brewing at New Holland and Old Nation27:11- Big Gretch Beer (and Josh’s Mom Stops by)34:18- Final QuestionsMICHIGAN SERIES: Having brought in guests from all over the country this past year, we wanted to still be true to our roots, so we have began the Michigan Series. A series of Michigan Brewery owners, employees, brewers, and sales reps, talking about what is happening here in the state and what is happening at their facilities. Join us on this continuing series throughout the rest of the month of December!Sponsors:North Center Brewing - https://northcenterbrewing.com/Zetouna Liquor - https://www.facebook.com/Zetouna-Liquor-Fine-Wine-Cigars-146021445420374/PCI BrandCraft - https://www.pcipromo.com/Join The Michigan Beer Discord - https://discord.gg/vEEDyzwdjTDownload the MI Beer Map - http://www.mibeermap.comSubscribe to Better on Draft - https://plnk.to/BODSpotify - https://open.spotify.com/show/6AlzP1BH0iykayF856bGRc?si=xXZzdd3CTPqgUq_KYTnBKgiTunes - https://podcasts.apple.com/us/podcast/better-on-draft-a-craft-beer-podcast/id1091124740Facebook - https://www.facebook.com/betterondraftUntappd - https://www.untappd.com/bodpodcastYouTube - https://www.youtube.com/c/betterondraftInstagram - https://www.instagram.com/betterondraftTwitter - https://www.twitter.com/betterondraft

The second episode of The Coaching Agile Teams Mini-Series was recorded by Lyssa Adkins and Leslie Morse in August of 2020. During this conversation they explore the inspiration and mission for the mini-series. It is very much an exploratory conversation with moments of laughter counterbalanced with deep and at times vulnerable discussion.Leslie and Lyssa open their hearts and minds in an invitation to listeners as they call on their desire to normalize what it means to be on the journey to becoming an Agile coach. There is quite a bit of range in their conversation. You’ll have the opportunity to hear them to share fun stories such as one Lyssa recalls about Ron Jeffries at the 10-year anniversary of the Agile Manifesto as well as dig into deeper topics that feel more like coaching sessions between the two of them.  Two of our favorite quotes from Lyssa include: “So much of what is in [Coaching Agile Teams] is not being done and I believe that if more of it was being done today we would have far less of the problems I continue to hear about - like on repeat. [They encounter] the same problem over and over and over again, and people are expecting Agile to solve it. It is only actually Agile’s job to reveal.” “Whoa! Hang On! If I’m not solving problems for the team, then what am I doing? And [Coaching Agile Teams] says, here’s what you’re doing.”Reference(s):Book: An Everybody Culture: Becoming a Deliberately Developmental Organization by Robert Kegan and Lisa LaheyYou can learn more about this series of episodes by visiting www.womeninagile.org/cat.  The Women in Agile community champions inclusion and diversity of thought, regardless of gender, and this podcast is a platform to share new voices and stories with the Agile community and the business world, because we believe that everyone is better off when more, diverse ideas are shared.Podcast Library: www.solutionsiq.com/womeningile  Women in Agile Org Website: www.womeninagile.org  Connect with us on social media!LinkedIn: www.linkedin.com/company/womeninagile/Instagram: www.instagram.com/womeninagile/Twitter: www.twitter.com/womeninagileorg Please take a moment to rate and review the Women in Agile podcast on your favorite podcasting platform. This is the best way to help us amplify the voices and wisdom of the talent women and allies in our community! Be sure to take a screenshot of your rating and review and post it on social media with the hashtag #womeninagile. This will get you entered to a monthly drawing for a goodie bag of Women In Agile Org swag!

Shawn Johnson of Birds Fly South (https://bfsbeer.com) dreams about brewing. In fact, their solera system for fermenting farmhouse beers came to him one night in a vision of sorts—as Jolly Pumpkin’s Ron Jeffries appeared in a dream with a command to “keep the beer moving.” Funk is always on Johnson’s mind, awake or asleep, and five years in, the brewery continues to adhere to their mantra of “Funk First!” In this episode, Johnson discusses: - Developing and managing their house culture - Maintaining the balance between Brett and Sacch expression in the culture - How different grist bills and mash processes affect the expression of the culture - Pushing higher bitterness (25-35 IBUs) in mixed-culture beers - Using hyped hops in farmhouse beers as a bridge to today’s drinkers - Embracing a bit of lightstruck character by using green bottles - Brewing for different barrel-aging strategies - Exploring flavors in barrel-aged stouts with Belgian yeasts Brewing today means balancing one’s creative vision with consumer demand, educating drinkers, and creating a market rather than simply creating products for an existing one. Birds Fly South has stuck to their guns, building a bridge between classic expression and modern innovation. *This episode is brought to you by: * G&D Chillers (https://gdchillers.com): Nearly 2,000 breweries across the US, Canada & Mexico partner with G&D Chillers. Innovative, Modular Designs and no proprietary parts propel G&D ahead as the premier choice for your glycol chilling needs. Breweries you recognize—Russian River, Ninkasi, Jacks Abby, Samuel Adams, and more—trust G&D to chill the beer you love! Call G&D Chillers to discuss your project today or reach out directly at Gdchillers.com (http://www.Gdchillers.com) BSG (https://bsgcraftbrewing.com/) This episode is brought to you by Rahr North Star Pils. A new base malt to set your compass by. Rahr North Star Pils is crafted for brewers looking for a domestic pilsner malt with low color and low modification. North Star Pils carries overtones of honey and sweet bread, supported by flavors and aromas of hay and nutty character. Suitable for any beer style, but particularly craft brewed versions of classic lagers. Let Rahr North Star Pils guide your craft by visiting BSGCraftbrewing.com (https://bsgcraftbrewing.com/), or contact BSG at 1.800.374.2739. Quantiperm (https://quantiperm.com): Tired of the trial-and-error carbonation processes? Then look at our innovative automated carbonation systems for precise carbonation. These systems handle wide flow ranges to accommodate all your beer, wine, soda, or cider styles. You can even carbonate and directly send the product to a packaging line without tankage! Besides carbonation, QuantiPerm offers robust and economical systems for nitrogenation and water deoxygenation. All our systems have an easy-to-use graphical user interface with reports and graphs that you can pull up on your mobile device. Visit quantiperm.com (https://quantiperm.com) for more information. Grandstand (https://egrandstand.com/catalog/category/view/id/179): Grandstand is your source for the latest trends in branded drinkware, apparel and promotional items. We make your job easy by serving as your one-stop-shop for everything you need to outfit your taproom and fans. Current trends include to-go drinkware, tie dye prints and portable coolers. Visit egrandstand.com/lookbook (https://egrandstand.com/catalog/category/view/id/179) to see what’s trending. ABS Commercial (https://www.abs-commercial.com): ABS Commercial is excited to be a part of today’s Podcast! ABS is a full brewery outfitter offering brewhouses, tanks, keg washers and small parts. ABS wanted to do something fun for the craft beer industry, and gave away an ABS Keg Viking Keg Washer LIVE this past December 7th. Congratulations to Lazy Horse Brewing & Winery in Nebraska who are the new proud owners of a Keg Viking! To make sure you’re on the list for future giveaways, go to www.abs-commercial.com (https://www.abs-commercial.com), click on “Keg Viking” page and fill out the contact form to stay in the know!

Wie arbeitet ihr mit als Product Owner richtig mit Akzeptanzkriterien? Wir starten in dieser Folge mit etwas theoretischem Input und einer Definition von Akzeptanzkriterien. Wir besprechen, wie man gute Akzeptanzkriterien findet und wie man sie sinnvoll einsetzen kann. Auch bei der Abgrenzung zur Definition of Done oder der Relevanz beim Schätzen sowie die Frage, ob es eine "richtige" Anzahl von Akzeptanzkriterien gibt diskutieren wir. Bleibt festzuhalten, dass es nicht um's Schreiben der Akzeptanzkriterien geht, sondern um ihre Formulierung und Nutzung. Das Wichtigste scheint zu sein, mit Akzeptanzkriterien Empathie für den Problemkontext herzustellen, damit ein gemeinsames "mentales Modell" über das zu lösende Problem im Team entsteht. Letztlich sind Akzeptanzkriterien für Product Owner eine super hilfreiche Praktik - auch bei der Arbeit mit Stakeholdern. Wir können allen Product Ownern nur empfehlen, sich damit eingehend zu beschäftigen! Dazu soll diese Episode beitragen. Folgende Quellen werden in der Folge genannt: - Gojko Adzic: Specification by Example - How Successful Teams Deliver the Right Software - CCC-Prinzip von Ron Jeffries (https://ronjeffries.com/xprog/articles/expcardconversationconfirmation/) - Behavior Driven Development (https://de.wikipedia.org/wiki/Behavior_Driven_Development) - Beschreibungssprache Gherkin (https://github.com/cucumber/cucumber)

In this episode we share an interview with the founder of Jolly Pumpkin Artisan Ales, Ron Jeffries.  Ron is a past board member of the guild, and recent recipient of the Tom Burns Award, recognizing the pioneering spirit of the Great Beer State.  www.jollypumpkin.com

As we've reached 240 episodes, we decided to spruce things up a bit, change up the format, and change out how we bring you content.  While this episode is delayed (Sundays will be the new release date), on Tuesdays we will release the news segment.  Both will still be recorded We are live Fridays at 7pm EST on Facebook at https://www.facebook.com/betterondraft. You can also watch us live on YouTube at https://www.youtube.com/betterondraft, on Twitch at https://www.twitch.tv/bodpodcast, or on our website www.betterondraft.tv.SHOW INFO: - We welcome Jeffrey Stuffings from Austin Texas to talk about his decade plus running of Jester King, his aspirations of being a professional basketball player, and his love for Ron Jeffries up at Jolly Pumpkin.  He talks about his travels, the difference between some very close beer styles, and even touches on the situation that occurred when Wicked Weed was purchased by ABI. We hope you enjoy this new 2x Week episodes breaking down the Friday night show.  Support MI Brewing - http://www.supportmibrewing.comSubscribe to Better on Draft - https://plnk.to/BODSpotify - https://open.spotify.com/show/0rofqU5VHPmEjcGLwJbocmiTunes - https://podcasts.apple.com/us/podcast/better-on-draft-a-craft-beer-podcast/id1091124740Subscribe to The Brewz Brothaz -Spotify - https://open.spotify.com/show/31iofThmMV9vHblkod5qK5iTunes - https://podcasts.apple.com/us/podcast/the-brewz-brothaz-better-on-draft/id1443234432Subscribe to The Beer Tour GuySpotify - https://open.spotify.com/show/3enGxubfQFop2ppdQjuVNRiTunes - https://podcasts.apple.com/us/podcast/beer-tour-guy-podcast-better-on-draft/id1266857083https://www.twitter.com/betterondrafthttps://www.facebook.com/betterondrafthttps://www.untappd.com/bodpodcasthttps://www.youtube.com/c/betterondrafthttps://www.instagram.com/betterondraft

Wie man schon am Titel dieses Artikels sehen kann, bin ich kein großer Fan von Story Points. Warum das so ist, erkläre ich Dir hier.  Als "Vater der Story Points" gilt Ron Jeffries. In seinem Artikel Story Points Revisited erklärt er, wie es zu diesem Konzept gekommen ist. Er ist sich allerdings selbst nicht sicher, ob er tatsächlich der Erfinder ist. Er erklärt auch wunderbar, welche alternativen Konzepte er bevorzugt (ja, auch er ist kein Fan von Story Points). Aber was sind Story Points eigentlich? Die ursprüngliche Idee von Story Points ist es, den Schwierigkeitsgrad oder die Komplexität eines Features zu beschreiben. Je schwieriger eine Aufgabe ist, desto mehr Story Points bekommt sie. Es ist eine bisschen wie ein Level in einem Videospiel wie z.B. Tetris. Wenn ich noch nie Tetris gespielt habe, wird mir Level 10 sehr schwer vorkommen. Mit zunehmender Erfahrung fällt mir Level 10 immer einfacher, bis ich am Ende nur noch müde darüber lächeln kann. Das ändert allerdings nichts an der Sache, das Level 10 trotzdem Level 10 bleibt. Für einen unerfahrenen Spieler ist es immer noch eine Herausforderung.  Das gleiche gilt für Features in einem Backlog. Ein erfahrener Entwickler wird mit einem Feature mit 5 Story Points mit Leichtigkeit fertig, während ein Junior Entwickler zumindest anfangs noch seine Schwierigkeiten haben wird. Beide brauchen für die Implementierung unterschiedlich lang. Story Points sagen also NICHTS über den Aufwand aus! Deshalb macht es auch keinen Sinn Story Points z.B. in PTs (Personen Tage) umzurechnen. Wenn ein Team das Thema Agilität ernst nimmt, wird es immer besser im Abarbeiten der Backlog Items. Das bedeutet, dass es ein halbes Jahr später wesentlich mehr Story Points pro Sprint (auch bekannt als Velocity) abgearbeitet werden. Das Team wird immer erfahrener.  Leider fällt es vielen Menschen schwer das Thema "Erfahrung" aus ihren Story Point Schätzungen raus zu halten. Das führt dazu, dass die beiden Dinge vermischt werden. Sobald ich das aber mache, macht es keinen Sinn mehr mit Story Points zu arbeiten. Ich kennen Unternehmen, die haben einen Umrechnungsfaktor für Story Points, z.B. ein Story Point sind drei PTs. In diesem Fall kann man auch gleich in PTs rechnen, da es einfach nur einen weitere Zeiteinheit ist, die am Ende mehr Verwirrung stiftet, als das sie hilft.  Heutzutage gibt es bessere Konzepte, um Projekte zu planen. Eines davon ist z.B. #NoEstimates. Mehr dazu in meinem Podcast mit Vasco Duarte.  R.I.P Story Points...

It is amazing how fast you can churn out code if you do not know what you are doingHolding up a mirror to agile practices, Chris has been in the trenches for 30 years and still coding with passion. From Spectrums and Specifications to R&D in BT and evolving to incremental delivery, whilst learning what not to do with XP, Chris has an opinion based on deep experience.Chris defends the use of user stories - always find the human. And Chris still thinks Coders are not close enough to the customer yet and why it matters. Chris explains what a great Product Owner does and reflects on the mystery of UX practice and how they react with Developers. Chris challenges the view that XP practices are both strong and mainstream, that we still need to get greater exposure to “what good looks like” and outlines how training helps practitioners. He discusses professional standards for developers and the defence of quality and why compromise costs.Architects may want to review their job description.Chris' book recommendations:Books are: Software Engineering, Somerville (note: haven't read the current edition, which mentions "agile"), GOOS by Freeman & Pryce, and Test Driven Development by Example by BeckI should also throw in an honourable mention for XP Explained (also by Beck), since it pulled some threads togetherJust realised the McConnell book I meant was “Rapid Development”, not “Code Complete”, but hey ho...they're both good

In this Episode, Diana joined Shahin to talk about Agile Fluency and other related topics. We conversed about and around the following topics: Agile Fluency® Model (Resources, Community & Game); and it's reference Language Fluency  Group coaching compared to Individual coaching Retrospective Facilitator Gathering & Open Space Technology Continuous Learning & Continuous Improvement; Advice and Tools for newer people to Agile Coaching in the Zones & Improvement Kata We referred to and/or mentioned the following people: Rebecca Wirfs-Brock - Linda Rising - Esther Derby - Klaus Leopold (LeanOnAgile Show with Klaus) - Joshua Kerievsky - Ward Cunningham - Norman Kerth - Allison Pollard - Alistair Cockburn - Ron Jeffries - Arlo Belshee - Martin Fowler - James Shore We cited the following resources: By Diana & Co-Authors: Agile Retrospectives: Making Good Teams Great (Amazon US - Amazon CA) Liftoff: Start and Sustain Successful Agile Teams (Amazon US - Amazon CA) The Five Rules of Accelerated Learning (LeanPub) By Other Authors: Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy: Survive & Thrive on Disruption - Jutta Eckstein & John Buck (Amazon US - Amazon CA) Project Retrospective: A Handbook for Team Reviews - Norman Kerth (Amazon US - Amazon CA) Love is Letting Go of Fear - Gerald Jamposky (Amazon US - Amazon CA) Checklist Manifesto - Atul Gawande (Amazon US - Amazon CA) For more details please visit http://podcast.leanonagile.com. Twitter: twitter.com/LeanOnAgileShow  LinkedIn: linkedin.com/company/lean-on-agile

Who doesn't have fond memories of going to "The Fair"? Ron Jeffries, General Manager of Rapid City's Central States Fair, has not only the job of helping create those memories every year for attendees, but he does it all over again every winter by managing the famous Black Hills Stock Show. Get to know Ron this episode. He's a real cowboy with a real great story!

Ron Jeffries in un recente articolo esordisce con la frase: " I like to say that I may have invented story points, and if I did, I’m sorry now." Secondo noi il messaggio che voleva passare è che il loro utilizzo nasconde delle insidie, spesso vengono usati in modo improprio e proprio per questo potremmo provare ad evitarli e non stimare più le user story. Come sappiamo, essere Agile, non vuol dire stimare bene, ma vuol dire trovare le cose più importanti da fare e farle rapidamente. E fare questo significa fare piccole fettine ad alto valore, e iterare rapidamente. Stimare le user story in story points non aiuta molto in questo, no?

Ron Jeffries in un recente articolo esordisce con la frase: " I like to say that I may have invented story points, and if I did, I’m sorry now." Secondo noi il messaggio che voleva passare è che il loro utilizzo nasconde delle insidie, spesso vengono usati in modo improprio e proprio per questo potremmo provare ad evitarli e non stimare più le user story. Come sappiamo, essere Agile, non vuol dire stimare bene, ma vuol dire trovare le cose più importanti da fare e farle rapidamente. E fare questo significa fare piccole fettine ad alto valore, e iterare rapidamente. Stimare le user story in story points non aiuta molto in questo, no?

Allen Holub on Deliver It, Jason Tanner on Drunken PM, Mary and Tom Poppendieck on Unlearn, Saron Yitbarek on Greater Than Code, and Dave Karow and Trevor Stuart on Deliver It. I’d love for you to email me with any comments about the show or any suggestions for podcasts I might want to feature. Email podcast@thekguy.com. This episode covers the five podcast episodes I found most interesting and wanted to share links to during the two week period starting July 8, 2019. These podcast episodes may have been released much earlier, but this was the fortnight when I started sharing links to them to my social network followers. ALLEN HOLUB ON DELIVER IT The Deliver It podcast featured Allen Holub with host Cory Bryan. Cory started out by reviewing an article by Ron Jeffries called “Story Points Revisited.” Allen’s take is that the negatives around story points are more than just the potential for misuse; he believes story points have no value at all. He says the most important thing is to narrow your stories, not estimate them. He says estimates exist because of fear. The software development process is opaque to certain managers and, as a result, they want estimates to alleviate their fear, but when you are delivering every day, you can eliminate the fear without resorting to estimates. Cory asked Allen what product owners need to know about Agile architecture. Allen said that one of the mistakes that he sees product owners make a lot is they try to do a miniature up-front design and expect that to be implemented. When this happens, he says there is too much information captured up-front of what is going to be built during the sprint and not enough information captured during the sprint as a side effect of releasing code to users and getting their feedback. This leads to inappropriate architectures because when you do anything up-front, you start doing everything up-front. Your sprint planning starts involving architecture decisions, UI decisions, and UX decisions that may be wrong and you will not know if you are wrong until you release. In Allen’s view, the most important thing a product owner does is answer questions that come up during the course of development. He uses a “two-minute rule”: if a question comes up during development, the product owner needs to be able to answer within two minutes. Allen talked about how the constraints of a bad architecture can prevent you from ever being Agile. He says, “Agile has nothing to do with standup meetings and backlog grooming and all of those. The important thing is to get stuff into your user’s hands quickly.” Allen says that the architecture has to be focused on the domain. Where systems that are wrong go wrong is that they don’t map to the domain but to the technology. A change at the story level, which is where the majority of changes come from, ends up touching all the modules or layers of your system when your architecture is mapped to your technology instead of your domain. Allen says that when he does a workshop on Agile architecture, people raise their hands about halfway through and say, “All we’re doing is domain analysis!” The fact is, if the domain and code are matched to each other, domain analysis is architecture. One of the questions Allen asks when he gets a bunch of product owners in a class is, “How many of you talk to multiple customers multiple times a day?” Maybe 5% raise their hands. So he says, “Who in the organization does talk to multiple customers multiple times a day?” This is often met with silence. He asks, “What about Sales? What about Tech Support?” He says that if you can’t respond to customer kinds of issues as well as a salesperson or a tech support person could, you don‘t know the domain well enough to be helpful to the engineering team. Cory asked Allen what he thought of the distinction between regular stories and “technical” stories. Allen says that there is no such thing as technical stories. A story describes the users of your system performing some kind of domain level work to achieve a useful outcome. Fixing some technical thing like changing the color of a button in no way makes your end users’ lives easier; it does not help them do their work. Allen says that the role of the architect in an Agile environment is very different from what we traditionally think of, just like the role of a manager in an Agile environment. In Agile environments, the job of people who are in a leadership position is to make sure that you can do your job, not to tell you what to do. They communicate a strategic requirement, provide support, and remove the obstacles. The same, he says, applies to Agile architects. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ep90-agile-architecture-with-allen-holub/id966084649?i=1000441313352 Website link: http://deliveritcast.com/ep90-agile-architecture-with-allen-holub JASON TANNER ON DRUNKEN PM The Drunken PM podcast featured Jason Tanner with host Dave Prior. Dave started out by asking Jason why he believes the daily scrum is broken. Jason said that the daily scrum is broken because, first, most developers hate the daily scrum because most daily scrums take the traditional weekly project status review meeting and do it five times a week with the Scrum Master filling the role of the project manager. Second, he says, is that it is being done backwards. The center of attention should not be the Scrum Master, but the team and the sprint backlog. He says that the purpose of the daily scrum is misunderstood. The three questions don’t result in a plan but result in just an exchange of information. For what real daily planning looks like, he uses an analogy of driving down the road and seeing a bunch of plumbers’ trucks from the same company parked outside of a McDonald’s. Inside, they’re planning things like, “We’re going to the Johnson’s house at noon. Can you come over and meet me because it’s going to be a two-man job.” Jason says he hates the three questions. He says the subject of the sentence is not helping us in collective ownership of the sprint backlog. “I have my user story. I have my Jira ticket. I have five team members and we each have a ticket.” Shifting the subject of the sentence to “we”, he says, changes the behavior dramatically. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/jason-tanner-is-on-a-mission-to-fix-your-daily-scrum/id1121124593?i=1000441958371 Website link: https://soundcloud.com/drunkenpmradio/jason-tanner-is-on-a-mission-to-fix-your-daily-scrum MARY AND TOM POPPENDIECK ON UNLEARN The Unlearn podcast featured Mary and Tom Poppendieck with host Barry O’Reilly. Barry asked Mary and Tom what we may need to unlearn since the Agile movement began. Mary says that Agile started as a reaction to what was going on at the time. The vast majority of people doing software engineering today weren’t around back then. One of the things Agile has to do is grow up to be not a reaction to bad things that happened in the past, but to be something that talks about, “What does it take to do good software engineering?” She contrasted the software engineers she speaks to today that expect to be handed a spec with the engineers she worked with early in her career who treated engineering as problem-solving. Tom talked about how many who are working to make organizations more agile attempt to solve problems with process. This assumes that the organization’s problems are process problems but they are actually architectural problems. This includes problems with the architecture of the applications they are evolving, problems with the structure of the organization, and problems with the structure of the relationships between the supporting groups and those who are benefitting from said groups. Mary talked about how Amazon AWS was one of the early organizations to understand that you need to give teams of smart, creative people problems to solve. As a result of having this insight, they organized the company in such a way as to optimize for this, such as by eliminating a central database which was heresy back in 2005. She called out AWS Lambda in particular because this product did not optimize for short-term shareholder value and would never have been approved at most companies because it reduced what Amazon was charging customers by five times. She attributes this ability to self-disrupt as being essential to Amazon AWS’s success. Tom talked about the fact that when you attempt to scale things up, you reach a point where complexity dominates any future gains and wipes them out. He says you instead need to de-scale: figure out how to do things in little chunks that are independent and don’t require coordination. He says that this is how cities have been organized for thousands of years. Mary said that she has been doing software since 1967 and has never seen anything last two decades and still be current. Agile is two decades old and cannot be current unless it is constantly adapting to what is current today. She brought up continuous delivery as a fundamental change in agile thinking. It changed the way we thought about how we structure organizations and teams and what kinds of responsibilities we should give to them. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/solving-problems-safely-with-mary-and-tom-poppendieck/id1460270044?i=1000442018979 SARON YITBAREK ON GREATER THAN CODE The Greater Than Code podcast featured Saron Yitbarek with hosts Arty Starr, Rein Henrichs, and Chanté Thurmond. They talked about the annual Codeland conference Saron is running and how it offers free on-site childcare this year. Saron says free on-site childcare at conferences today is where codes of conduct were a few years ago. She says that if her conference wasn’t making it easier for parents to attend, it wouldn’t be living up to their promise for inclusion. Chanté asked Saron what she learned in her transition from being a code newbie herself to the present day where she is running two podcasts, a software job, and a conference. Saron said she learned that it is important to be consistent in all your efforts, whether it is community work, your personal projects, or a project at work. Nothing gets built overnight and, for a while, nobody will care what you’re doing. If you want to do something great, it takes persistence and it takes you believing in yourself especially when you’re not getting external validation. Arty asked about what expertise in “newbie-ism” might look like. Saron says that it is about being comfortable in a state of frustration. She pointed to a study on the difference between those who finish a computer science degree and those who quit. The study said that those who finished the degree were comfortable being in a state of confusion: they knew that things were not going to make sense for a while and they were ok with that. A second thing, she says, that helps you become an expert newbie is realizing that almost all problems in coding are solvable. By contrast, in writing, there is no perfect essay. In journalism, there is a search for truth, but is truth attainable? In life sciences, we study nature all around us that we may never fully understand. She also says to keep your frustration external, avoid internalizing your failures, and she says to distance who you are from your work and the things you produce. Saron’s comment on being comfortable in a state of confusion triggered a Virginia Satir quote from Rein: “Do you know what makes it possible for me to trust the unknown? Because I've got eyes, ears, skin. I can talk, I can move, I can feel, and I can think. And that's not going to change when I go into a new context; I've got that. And then I give myself permission to say all my real yeses and noes, because I've got all those other possibilities, and then I can move anywhere. Why not?” Rein asked what Saron learned about teaching. Saron says that teaching is storytelling in disguise. She says that if we frame teaching opportunities as storytelling opportunities we can be better teachers. This reminded me of Josh Anderson’s comment on the Meta-Cast podcast that I referenced way back in episode 3, “Taking The Blue Pill Back To Sesame Street.” Rein brought up a theory of learning called conversation theory. In conversation theory, teaching happens as a conversation between two cognitive entities. You have to come to agreement and build a bridge with that other cognitive entity. It deconstructs the teacher-learner binary. The teacher themselves has to be a learner too. Chanté asked about the ethos at Code Newbie for being a learner and a teacher. Saron says they look to the community to pitch in. When someone asks a question, they encourage the community to answer. She contrasted Code Newbie with Stack Overflow. Code Newbie attempts to teach the learner from where they are and avoid the condescension that is common on Stack Overflow. She said that to create an environment where people are not afraid to ask questions, we have to be unafraid of being vulnerable ourselves. Go first, share your vulnerability, and share what you’re struggling with. The moment you start doing that, other people will be much more likely to raise their hands as well. Chanté asked Saron what resources she recommends for code newbies to learn to code. Saron said that the hard part isn’t finding resources but sticking with them when things get tough or boring. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/135-intentional-learning-with-saron-yitbarek/id1163023878?i=1000442022293 Website link: https://www.greaterthancode.com/intentional-learning DAVE KAROW AND TREVOR STUART ON DELIVER IT The Deliver It podcast featuring Dave Karow and Trevor Stuart with host Cory Bryan. They talked about running experiments to learn about your customer. Cory asked how people can run such experiments at scale. David pointed out that having a way to run the experiment is one thing, but you also need to be able to rapidly make sense of the results in a repeatable, authoritative way. Trevor says it is all about assumptions, hypotheses, and documentation. Before you even start your experiment, you need to understand why you are running it in the first place. In other words, you need to establish what is going to change as a result of the experiment. Trevor says that much of the market is already doing experiments and they don’t know it. They just call it “using feature flags” and rolling things out incrementally. They just need to move one step further to slice and dice their user populations, roll things out for longer time periods to those users, and bring the resulting data into a form that facilitates decision-making. David talked about dog-fooding by starting your rollout of new features with your employee population, giving examples from Microsoft, where it takes a few weeks to go from the employee population to the full customer population, and Facebook, where it takes about four hours for the same kind of rollout. Apple Podcasts link: https://podcasts.apple.com/ca/podcast/ep91-product-experiments-with-trevor-and-dave-from-split/id966084649?i=1000442844631 Website link: http://deliveritcast.com/ep91-product-experiments-with-trevor-and-dave-from-split FEEDBACK Ask questions, make comments, and let your voice be heard by emailing podcast@thekguy.com. Twitter: https://twitter.com/thekguy LinkedIn: https://www.linkedin.com/in/keithmmcdonald/ Facebook: https://www.facebook.com/thekguypage Instagram: https://www.instagram.com/the_k_guy/ YouTube: https://www.youtube.com/c/TheKGuy Website:

Travis, Nick, and Brandon talk about Rule #1 in running software teams: The Software Must Ship. How much of that is on you, the manager? They explore that question and talk about their experiences managing work backlogs, delivery cadences, and giving teams slack to help them go faster. Ron Jeffries's tweet: https://twitter.com/RonJeffries/status/1120486947569446914 Accelerate by Nicole Forsgren, et al. https://www.amazon.com/Accelerate-Software-Performing-Technology-Organizations/dp/1942788339

Fredrik talks to Woody Zuill, writer of the book on mob programming, facilitator of happy teams and thoughtful teller of stories. Woody talks about how he and his team discovered mob programming, how it is evolving, how focusing on the good is the way forward, and how he may have aquired his mindset. Recorded on-stage at Øredev 2018. Thank you Cloudnet for sponsoring our VPS! Comments, questions or tips? We are @kodsnack, @tobiashieta, @oferlund and @bjoreman on Twitter, have a page on Facebook and can be emailed at info@kodsnack.se if you want to write longer. We read everything we receive. If you enjoy Kodsnack we would love a review in iTunes! Links Øredev 2018 Woody Zuill Mob programming Turn up the good - Woody’s presentation at Øredev 2018 No estimates Test-driven development Hunter industries Llewellyn Falco Pair programming Agile alliance George Dinwddie Ron Jeffries Repenning, N. and J. Sterman: Nobody ever gets credit for solving problems that didn’t happen Horticulture Titles I think of myself as a software developer Trying to make a better work environment I don’t believe we can manage people This time of year seven years ago Purely by accident Sitting and thinking at the keyboard alone One member who’s not there Five or six people programming Opening different doors If you open a door, there’s a good chance somebody will welcome you in Superconnectors One of those connector things Oddly, it is working for us Purposeful stumbling I stopped looking for solutions to problems A habit we need to build I just went ahead and did it I’ll discover stuff if I just try it We follow the path that develops in front of us Your job is very important He was extending trust to me These things are not related A gentle way to think about our lives

Ron and Chet's Agile 2018 Session:Ask Us Almost Anything - Ron and Chet Experience Agileis taking place in Lisbon, Portugal on October 1-2 Contact Info:Ron Jeffries: RonJeffries.com/ Twitter Chet Hendrickson: hendricksonxp.com/ Twitter

Hiya! This month on the Cucumber Podcast we speak to Ron Jeffries and Chet Hendrickson. They are probably best known for their association with the Agile Manifesto - Ron, one of the authors, Chet the first signatory. They've both done some other stuff too... This is a wide-ranging conversation hosted by Matt Wynne with fellow Cucumber people Sal Freudenberg, Steve Tooke and Aslak Hellesøy. Show notes Cucumber Clinic - Let us review your scenarios! - https://clinic.cucumber.io/ Transcript of this conversation - https://cucumber.io/blog/2018/06/06/ron-and-chet-podcast Chet on Twitter - https://twitter.com/chethendrickson Ron on Twitter - https://twitter.com/RonJeffries Cucumber on Twitter - https://twitter.com/cucumberbdd

Doc Norton talks about the experimentation mindset. This episode is sponsored by Smartsheet. Show Notes: Slides from Doc’s presentation on the experimentation mindset XP = eXtreme Programming Other methodologies that fall into the "agile" category: Scrum, Lean Kent Beck, Ron Jeffries, and Ward Cunningham were all mentioned. They are all signers of the Agile Manifesto. Chris Argyris was mentioned in regards to single-loop and double-loop learning Book: Escape Velocity by Doc Norton - it has increased in price since the recording. It will now set you back at least 5 entire dollars. Supplemental links from Doc: CTO2 DocOnDev Collaboration Contracts Refactoring Code Smells Video: Experimentation Mindset Mob Programming Learning through experimentation PDF: How Organizations Learn From Harvard Business Review: Collective Genius Argyris: Teaching Smart People how to Learn (and PDF version) A/B Testing and the Experimentation Culture Enlightened Experimentation Smart Business Experiments Evidence Based Management link:http://www.edbatista.com/2008/05/double-loop.html[Ed Batista blog post on double-loop learning Lean Change Book: Scaling Up Excellence Experiential Learning Doc Norton is on Twitter. Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Music is by Joe Ferg, check out more music on JoeFerg.com!

Joe Krebs speaks with Ron Jeffries, one of the 17 signatories of the Agile Manifesto, about Refactoring, Agile Training and People.

Ron is one of the 17 signatories of the Agile Manifesto and author of the infamous book "Extreme Programming Installed (2000)". In this episode, we framed our conversation around a blogpost article he wrote, called Agile Ecology. Ron brings some topics to surface he feels very strongly about, for example "Refactoring", "Agile Training" and "People".

Mike Vizdos is a busy guy. He’s someone whose passion for helping agile change lives extends well beyond coaching traditional organizations and teaching classes. At Agile 2017, Mike stopped by to provide an update on Agile In Education and the work he and others are doing to bring agile to schools and transform the way we learn. This work is taking place e at every level of education - from grade school up through university. It is an inspiring and impressive thing.Mike also talks about the work he’s been doing with Ron Jeffries to create an online community that provides mentoring and support for Agile practitioners and coaches. Here are some of the links mentioned in the interview:AgileMentoring.com http://www.agilementoring.com/Agile in Education: http://www.agileineducation.orgScrum In School http://www.scruminschool.orgThe VCU daVinci Center http://www.davincicenter.vcu.eduAnd if you’d like to learn more about Mike, check out:Web: http://www.michaelvizdos.comTwitter: https://twitter.com/mvizdosLinkedIn: https://www.linkedin.com/in/mvizdos/

Agile pioneers Ron Jeffries and Chet Hendrickson take us on a roller-coaster ride – in a Delaurian! – through the pervasion of Agile, the evils of meeting big companies where they are, the next evolution of Agile, and treating programmers with human decency, all in the “right side lounge”! Not sure what that means? Neither are we, but we learned a lot and you will, too. Need more incentive? How about these quotes:- “You’re not doing Agile until your teams are shipping software every two weeks.”- “I have in mind a revolution.”- “What is Agile 2.0? It’s teal biomimicry.”- “We coded live during the keynote to prove that we could do it.”- “Everything I learned about Agile, I learned through pair programming.” To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com.Subscribe: bit.ly/SIQYouTube, bit.ly/SIQiTunes, www.solutionsiq.com/agile-amped/Follow: bit.ly/SIQTwitterLike: bit.ly/SIQFacebook

Charles Husemann is collecting data about agile processes. Show Notes: Rational Unified Process (RUP) Waterfall development lifecycle Scrum.org Scaled Agile Framework (SAFe) Extreme Programming (XP) Podcast 042 - Arthur Doler on Retrospectives DREAM: Data Rules Everything Around Me (dolla dolla bill ya'll [mildly NSFW]) NoEstimates: Phew. Where to start. Maybe Ron Jeffries blog post about NoEstimates. Velocity Hawthorne Effect Microsoft research paper about TDD: Realizing quality improvement through test driven development: results and experiences of four industrial teams [PDF] "Uncle Bob" refers to Robert C. Martin The Agile Manifesto Book: Coaching Agile Teams: A Companion for ScrumMasters, Agile Coaches, and Project Managers in Transition Gaming Nexus Charles Husemann is on Twitter Want to be on the next episode? You can! All you need is the willingness to talk about something technical. Theme music is "Crosscutting Concerns" by The Dirty Truckers, check out their music on Amazon or iTunes.

As the 2017 Scrum Gathering in San Diego would down to a close a few weeks ago, Dave Prior and Chris Li began a debate: Is it okay for a Scrum Team to leave the Sprint Planning Meeting with individual work assignments? This is a question that often comes up for both Dave and Chris when they are teaching CSM and CSPO classes. In this podcast you’ll hear them each explain how they respond to this question based their experiences working with teams. You’ll also get to hear what happened when they decided to check in with some experts at the Gathering. SHOW NOTES 00:08 - Podcast Begins 00:26 - How Chris and Dave got into a heated debate about Sprint Planning and went to check with experts 01:50 - Debate setup: During Sprint Planning, is it okay for Team Members to self-assign tasks they will work on during the Sprint? 02:41 - Chris explains his position supporting Team members selection tasks during Sprint Planning 05:30 - Dave explains the reasons why he does not want Team members to leave Sprint Planing with specific work assigned. 08:20 Chris responds to Dave’s position 09:54 - Dave tracks down Diana Larsen to ask for her opinion on the subject 10:39 - Dave asks Ron Jeffries and Chet Hendrickson on the subject 11:52 - “We’re all trying to get to the same place” 13:00 - How to get in touch with Chris 13:53 - Podcast Close CONTACTING CHRIS You can reach Chris on the LeadingAgile site at: https://www.leadingagile.com/guides/chris-li/ On Twitter: https://twitter.com/RealChrisLi On his personal site: http://www.sparkplugagility.com/ CONTACTING DAVE You can reach Dave on the LeadingAgile site at https://www.leadingagile.com/guides/dave-prior/ On Twitter: https://twitter.com/mrsungo Or on his personal site at: https://drunkenpm.blogspot.com/ FEEDBACK/QUESTIONS If you have comments on the podcast, or have questions for the LeadingAgile coaches that you’d like to have addressed in a future episode of LeadingAgile’s SoundNotes, you can reach Dave at dave.prior@leadingagile.com LEADINGAGILE CSM AND CSPO CLASSES For information on LeadingAgile’s upcoming public CSM and CSPO classes, please go to: http://www.leadingagile.com/our-gear/training/ Use the discount code: LA_Podcast to receive a 15% discount on the class.

Episode 7 - Jeff Patton - User Story Maps and the discovery of great products Another one of the greats. I follow his work since years, I integrate lots of what he does in my work. Everyone knowing me or having had a training with me, knows what he does with Story Maps. But having come up with Story Maps and having written the first book around is „this little thing“ to Jeff Patton. Jeff is really deep into product work and he has lots of thoughts to offer on Agile and especially on everything around stories and story thinking. And one of the reasons he knows all about that is because he was already there when it happened. He was in the same building with Kent Beck when Extreme Programming happened and Stories came up. He was coached by Rob Mee of Pivotal Tracker fame. So, this is not just a deep dive on stories and the Story Mapping technique that emerged form it but also some oral history on how and where it all started to happen. Nowadays, Jeff more and more dives into the discovery phase and at the end of the podcast we will hear lots about this and where this might clash with Agile or how it is taught in most cases. But what is so relaxing is that we really don’t talk much process. And I think the reason is that product is much less process than it is orthogonal to process and it is about thinking of quality, what quality means to whom, for whom we’re building things and having empathy for them. Speaking of empathy: Enjoy a nice conversation with a humble, humorous and relaxed Jeff Patton! Chapters 0:02:04 (User) Stories - the base of all 0:13:19 Documents are like vacation stories 0:31:43 Story Maps - what it is, how i emerged 0:43:10 How to teach Story Maps 0:55:34 Struggling with the backlog as a prioritised list 0:57:54 Products we like: A BMW 335 convertible, Netflix and Spotify, an EV 320 Microphone and a Sonos speaker 1:04:34 Why have (Agile) things gotta be so complicated? 1:11:44 Is software harder than software and: First off, no process is going to help you Chapter Notes 2:04 (User) Stories - the base of it all Going down memory lane, meeting lots of now famous people, e.g. Kent Beck "People have gotten User Stories wrong from the beginning" "When I first heard the term "Stories" I thought it was stupid - what we’re doing is important stuff. Stories  … that sounds like fantasy or fiction … it doesn’t sound serious at all" "What Kent meant with stories was really stories. We should be talking with each other and telling stories about the products" "The goal is building shared understanding" "What we are talking about isn’t what to build. What we’re talking about with each other is: who’s using this product and why and what benefit they get. and understanding that we can then talk about together about what to build." "Where things go horribly wrong is when people use stories and try to do what they used to do." "So, people try to use stories as an alternative to other specification algorithms, when that’s not what they were meant to be" How stories are not precise and complete 8:22 Comparing stories and UML The promise with UML was that you had to learn UML and then you had to talk to someone who knew UML. Stories fix all this. "Stories fix all kind of crappy documentation. Because know we have humans to talk to to explain things" "I keep telling people that if you’re using stories, you have to change your process"  "The problem stories don’t solve is the way you specify. … If you’re using stories, you still have to figure out ways to specify." "I think people write documents because they don’t like to talk to each other." 11:15 Documents are like vacation photos  „The minute you write stories and hand them over without having a conversation, that’s the moment when things start to go wrong.“ 17:14 How Kent Beck never called "stories" "user stories" Rumors and misconceptions on stories and sizes and templates  How somehow people and many Scrum Master are spreading the rumor of „we have to use (User) Stories all the way   "The way Agile works is we build little things, and we work in short cycles. … But the problem is that when we build a product that is supposed to go to the market and create value it is not something we build in days." "Those things we can build in a few days hardly have value and it becomes hard to tell a story about those things" "I learned these things around 2000 and we called them stories and not user stories, and we didn’t use the term epic and you know, the user story template - we certainly didn’t use that." 23:14 How the founder of Pivotal Tracker, Rob Mee, was Jeff’s XP coach, refused using the template in his tool and now it does anyway: "I’m never gonna put that stupid template inside of Tracker … well, it’s in there now. And I’m sure not because Rob thinks it’s a good idea." "But the template falls apart super easy. … The conversations we need to have are far more sophisticated than that." "As a user I want just dumbs down all the rich conversations we need to have …" The three (or five?) C’s of stories Ron Jeffries 3 C’s: Card Conversation, Confirmation "The conversation is not about the acceptance criteria but about Who, What and Why! … It’s meant to be a bit of a back and forth." "What I see people doing these days is: Card -> Conformation" Documents are contracts and with stories "we finally recognise that documents are never gonna be good enough, they’re never gonna be precise enough and what matters is understanding and the only way we get it is by talking to each other." "Shared documents aren’t shared understanding" and that will make a lot of people uncomfortable. 31:43 Story Maps - what it is, how it emerged A solution for breaking big things down that take weeks and weeks to build into little things we can build in days. The metaphor of rocks that when you break them, remain rocks … just: little rocks. Just like big stories (no matter if you call them epics or not) that when you break them down just remain … stories. "Story mapping is the thing that I used to do to get from a big idea to break it down into small parts." How story maps emerged from the technique called "User Task Model" over "Span Plan" (influenced by the Poppendiecks) to Story Maps (which name came up in a discussion with Alistair Cockbourn). How Jeff wanted to write a huge book on everything outside of Agile, but then Story Maps took off and then the small book on story Maps got bigger and bigger. A next book is planned. Jeff is not afraid, and still has lots to say. It’ll be easy. Ha! Jeff’s book has three forewords. It reflects the mantra of product work, being credited to Marty Cagan, that it’s all about the intersection between valuable, usable and feasible. The three forewords represent that by having representatives from UX - Alan Cooper, development - Martin Fowler and finally product itself - Marty Cagan. That trinity is called a Core Team and is still widely used. 43:10 How to teach Story Maps Two good ways: Simply mapping something live and lead discussions, conversations. Mapping a morning from waking up to getting to work, then let a group mix the individual morning stories and change it, because some strange event happened, like: Getting up too late. These are ways that lets people focus on writing down activities rather than things or functionalities. Also, it makes obvious that different people behave differently. Further it teaches how to slice and cut things away, e.g. because there is less time than usual. some things can not be sliced out (morning hygiene) but need to be thinned out. Maps are useful for still seeing the whole while we flesh out the small things. "We need details when we go into the next sprint, but we still need to be able to see the whole. Because it’s the whole that has value. That’s the real value of a map." An application in a workshop: Planning the first release of a wine shop. 55:34 Struggling with the backlog as a prioritised list "There’s a lot of things I disagree with on how Agile gets taught and used and abused. One of the things I struggle with is the way it is taught that a backlog needs to be a prioritised list." "If you think of a new product … it would be completely impossible to understand what it is … based on a prioritised list of features." "It is so valuable to see the whole. And you don’t get that in a flat backlog." "When you talk about parts of a thing, you normally need all of them." 57:54 Products we like: A BMW 335 convertible, Netflix and Spotify, an EV 320 Microphone and a Sonos speaker Trying to find out why we like them. For starters, the BMW is super impractible for where Jeff lives, as they have lots of snow. He still loves it. Netflix now works for Jeff as a traveler, because downloads are possible. "Why we encourage people to talk about why they like a product is because why you like a product has a lot to do with who you are." "The toughest choices are not what features your product has, the toughest choice is who your product is for and the really hard choice is who your product is not for." "If people really love a product, I always ask: "What did you use before?"." "When you’re using a good product, you can sorta smell the thought and care that went into creating the product." "That’s what I really worry about when we talk all about Agile and breaking things into little pieces … that we lose sight of who its for and that we lose sight of all the little things that matter so much … and start working about acceptance criteria." 1:04:34 Why have (Agile) things gotta be so complicated? While teaching discovery (e.g. in 5 day immersion workshops), Jeff realises that people no longer know, see and have empathy with their clients, users, etc. "We have to come with a lot of process junk and waste to help us manage what we’re doing when a little bit of empathy and understanding of who you’re building for goes a long way." "In a lot of contexts it’s not easy to get to the customers. And to what you say, even if we could get to them, we don’t want to. It’s not comfortable talking to those people - and it’s unnerving sometimes." 1:11:44 Is software harder than software and: First off, no process is going to help you When Apple had a problem with a new carrier, it was normal for a developer to linger around at the carrier. "At Apple it was not not unusual, no one was asking: why aren’t you at your desk? Why aren’t you writing code? It was absolutely rational to do that." At a different spot: Q: "If you think of Apple, on a range from 1 to 10 where would you put the quality they ship at Apple?" A: "I’d put it at 9." Q: "Where would you put what you ship here?" A: "About a six." Q: "If you were at Apple and you would ship a six, what do you think would happen to you? You ship 6 here all the time." A: "We celebrate that we ship all the time." Conclusion: "Something has to change around here that is not process" "Everything is becoming more blurred all the time." "The hardware isn’t even the hardware. It’s the software that’s changing it." "More and more you buy a piece of hardware and it’s not like it’s in the box and the partnership with the manufacturer is done. There’s an ownership lifecycle that supports it." "I was at a conference in Australia and the speaker right before was a designer at Lego. and he came up with that idea that they came up with that perfect Lego model that was really testing well but it was too expensive to build. And he said „you know how it is when the perfect solution is too expensive to build and we have to figure out something different.“ And the audience was quiet and the audience was „no, I don’t know what you’re talking about." "I see so many people in the software world arguing for what’s best and not for what’s feasible and not understanding that it’s not about best …" We have to learn again to prototype. "And at times a prototype is more expensive than the real thing." "What’s interesting is that Agile Development has gotten totally effed up when it comes to this prototyping thing. There is all this emphasis on potentially shippable software, there is this emphasis on software being built and tested, but look: we’ve lost our ability to use code to build rough stuff to see if we’re building the right thing." "More and more I talk about learning velocity vs. building velocity." "If you’re trying to learn something the most expensive way is to build production quality software." "Building the wrong thing at high quality is waste." „If there is gonna be a contemporary agile way of building things t’s gonna be this mix of product thinking and customer centric thinking and Agile thinking and I’ll be honest: It’ll break the Agile Manifesto." Great final words "What makes a product better is not more stuff, it’s good stuff." Links Jeff Patton Associates Jeff Patton: User Story Mapping  Kent Beck: Extreme Programming Explained Pivotal Tracker Pivotal CEO Rob Mee Alistair Cockburn

Chet Hendrickson & Ron Jeffries (briefly) take over Agile Amped after (briefly) breaking Howard Sublett. Then the duo reminisce on 20 years of collaboration since the beginning of Extreme Programming (which, you'll remember, is well before the onset of Agile). With decades of experiences in Agile (and its predecessor methodologies), Chet and Ron have lots to say about the state of Agile and aren't above saying it. Of interest: the fact that so many Agile companies focus on the tools for doing Agile and few focus on actually being Agile. On this point, Chet advocates for "more Jenkins, less Jira." Ron says it may be time to return to the roots of Agile and XP and do the unthinkable to get the desired results: change the name. SolutionsIQ's Howard Sublett hosts at Agile2016 in Atlanta, GA. About Agile Amped The Agile Amped podcast series connects the community through compelling stories, passionate people, shared knowledge, and innovative ideas. Fueled by inspiring conversations with industry thoughtleaders, Agile Amped offers valuable content – anytime, anywhere. To receive real-time updates, subscribe at YouTube, iTunes or SolutionsIQ.com. Subscribe: http://bit.ly/SIQYouTube, http://bit.ly/SIQiTunes, http://www.solutionsiq.com/agile-amped/ Follow: http://bit.ly/SIQTwitter  Like: http://bit.ly/SIQFacebook

I recently got the most wonderful opportunity to talk with a couple of legends in the Agile Community - Chet Hendrickson and Ron Jeffries!  They're partnering with Brian Levy to bring a 5-Day, dual certification, public CSD class to Chicago for the week of 14-18 March, 2016. Ron, Chet and Brian discuss many of the XP Practices we grown to love and integrate into our Scrum implementations.  Brian also adds a dash of SAFe to the conversation. The class, in downtown Chicago, combines a 3-day Certified Scrum Developer (CSD) class and a 2-Day SAFe ScrumXP class.  Class attendees will be awarded the CSD via Scrum Alliance (assuming they already have other pre-requisites covered), and the Scaled Practitioner (SP) via Scaled Agile.   Details for the class can be found at these sites   About the Trainers You can find more about Ron Jeffries . You can find more about Chet Hendrickson . You can find more about Brian Levy .

Ron and Chet discuss their conference experience, thoughts on the best sessions so far, trends in the industry and so much more!Buckle up.

Victor is joined by Dale Ellis (@theDigitalDale), Jason Kerney (@JasonKerney), Zach Bonaker (@ZachBonaker) and Garrett Borunda (LinkedIn) at the Cape Rey in Carlsbad for a lively morning of Agile and Coffee. In this episode, our Agile heroes discuss: Agile tools to give Voice to a Teams "Agile is a cancer" Erik Meijer's presentation The Hacker Way - a Rational Alternative for Agile (explicit content) in which he claims that "Agile is a cancer that we have to eliminate from the industry" Agile Is Dead (Long Live Agility) by Dave Thomas (manifesto signatory) The Failure of Agile by Andy Hunt (manifesto signatory) Shu Ha Ri by Alistair Cockburn(manifesto signatory) Should Scrum die in a fire? by Ron Jeffries (manifesto signatory) Good To Great by Jim Collins Coordinating work between teams Power of Success (Mob Programming at Hunter) ACCUSWest 2015 archive at AgileLib.net, courtesy of Tobias Mayer Coming soon is Dr. Dave's 5 Saturdays program's Train the Facilitators workshops: May 30th and June 6th. More info at 5Saturdays.org Reach out to Vic (@AgileCoffee) on Twitter and use the hashtag #tellAgileCoffee to interact with us on an upcoming episode.

We captured this impromptu conversation between some of the greatest minds in the industry and trust us you are going to want to see the magic that ensued. You're welcome. Podcasts are brought to you by SolutionsIQ and the Scrum Alliance.

Chet and Ron discuss hot topics, current trends and future directions of XP, Scrum and the industry in general.

This week we discuss the world class Jolly Pumpkin Artisan Ales with owner and brewer Ron Jeffries! The brewery has long been at the forefront of sour beers in America and they continue to brew phenomenal beers that further push the style into popular culture. Ron is a wealth of information and we have some incredible beers to drink and discuss! This weeks beer lineup from Jolly Pumpkin: Bam Biere Fuego del Otono Calabaza Blanca Maracaibo Especial Madruggada Obscura

Our guest is Jolly Pumpkin Artisan Ales cofounder and brewer, Ron Jeffries. Ron touches on how he got his start in brewing, being the first brewery in the US to produce 100% oak-aged beers, where he finds inspiration, blending, cellaring and Boulevardia. Guest hosts are Beejay Oslon of Pipeworks Brewing Company; Patrick Dawson, author of Vintage Beer; brewer, Brian Sullivan and Jeremy Danner of Boulevard Brewing Company. Music: Radon - Demon Lover

The best people for the cheapest price. The map is not the territory 0:15 The Rise of the Expert Beginner 2:49 Drefus Model of Skill Aquisition 4:29 neovim 11:00 Ron Jeffries 12:00 Dimensionality and the Eternal Haskell Tax 26:40

In this special hiatus episode, we present an edited recording of a hangout the team had on November 24th 2013, in which we discussed ideas for topics and guests in Season 2. It's a chance for listners to meet the new team and get a sense of what's coming up. The Wow! Signal Podcast team members are: Paul Carr, Jim Cavera, Jude Hollingsworth, Ron Jeffries, and Mike Mongo. We hope you'll comment here or join our Google+ community. Links: Icarus Interstellar 100 Year Starship The B612 Foundation

I finally got a chance to talk with Ron Jeffries and Chet Hendrickson at the Simple Design and Testing conference last year.  I have known Ron for a while now but this conference was the first time that I got to talk with Chet.  They both enjoyed the conference and I hope to see them at the next SDT conference if we ever get around to organizing one.-bob payne