Podcast appearances and mentions of james shore

In this special episode of Book Overflow, Martin Fowler joins Carter and Nathan to discuss his book Refactoring: Improving the Design of Existing Code. Join them as Martin shares why he wrote Refactoring, how the art of refactoring has changed, and how he views the book's legacy!https://martinfowler.com/-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Refactoring: Improving the Design of Existing Code by Martin Fowler and Kent Beckhttps://amzn.to/4enmuox (paid link)The Art of Agile Development, 2nd Edition by James Shore and Shane Wardenhttps://amzn.to/47TiM3D (paid link)Make No Law: The Sullivan Case and the First Amendment by Anthony Lewishttps://amzn.to/3zJ3K3O (paid link)----------------00:00 Intro01:58 Motivation for writing the book09:45 Refactoring, Extreme Programming, and testing19:17 Estimating, Unknowns, and Complexity23:40 Trust and High Performing Teams30:32 refactoring in the wild: imitate, assimilate, innovate, best practices and sensible defaults43:39 Legacy of the book and rational for second edition47:35 What are the role of books now? Evergreen content, Long-form content in a world of short-form content.01:03:21 Book Recommendations01:09:12 Closing Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In dieser Episode von Data Science Deep Dive sprechen Mira und Wolf-Gideon über das Agile Fluency Model und dessen Bedeutung im Data-Science-Kontext. Im Fokus stehen die verschiedenen Stufen der Agilität sowie die damit verbundenen Vorteile und notwendigen Investitionen. Wolf-Gideon erklärt, wie man den optimalen Agilitätsgrad für ein Team ermittelt und welche Praktiken dabei relevant sind.    ***Links*** Buch von Henning Wolf und Wolf-Gideon Bleek (2010): Agile Softwareentwicklung: Werte, Konzepte und Methoden (ISBN: 978-3-89864-701-4) it-agile Webseite https://www.it-agile.de/ Mehr Infos zu Wolf-Gideon Bleek auf der Seite von it-agile: https://www.it-agile.de/ueber-it-agile/das-team/dr-wolf-gideon-bleek/ Manifest für Agile Softwareentwicklung https://agilemanifesto.org/iso/de/manifesto.html Agile Fluency Project (EN) https://www.agilefluency.org/ Artikel: The Agile Fluency Model - A Brief Guide to Success with Agile von James Shore & Diana Larsen (EN) https://martinfowler.com/articles/agileFluency.html Buch: Company-wide Agility with Beyond Budgeting, Open Space & Sociocracy von Jutta Eckstein & John Buck https://www.agilebossanova.com/ Feedback, Fragen oder Themenwünsche? Schreib uns gern an podcast@inwt-statistics.de

One of the standout stars from The Secret, self-help author James Arthur Ray had it all; fame, a thriving business and a life of travel and wealth. With guest spots on Oprah, Larry King and some of the top media outlets in the world, it seemed as though Ray was on top of the world. It all came crashing down in 2009, during his Spiritual Warrior Retreat outside Sedona, AZ. In a heat endurance test in a sweat lodge exercise James unknowingly and unintentionally pushed his attendees perhaps a bit too far...and James Shore, Liz Newman and Kirby Brown died of chemical asphyxiation and organ failure. James was sent to prison for negligent homicide. Battered and broken, $20 million in debt, and 2 years in prison, James Arthur Ray was released. James Arthur Ray opens up on the powerlessness he felt, how his own arrogance cost him, and how those three people will be forever linked to his name...and how his wife, Bersabeh came into his life while CNN was filming the documentary Enlighten Us. Homeless with $20M in debt at one point, James shares his work to build back his life, and how his now wife, Bersabeh helped him pick himself back up. This is a raw episode as there are no punches pulled, and Ray opens up about his regrets, and the business of redemption. James Arthur Ray & Bersabeh Ray Biographies James Arthur Ray: James Arthur Ray is a New York Times bestselling author, philosopher, and consultant who has worked with over 1 million people from 146 countries through his coaching and leadership programs. He is the author of six books, including the New York Times bestseller, Harmonic Wealth, and has appeared on numerous TV shows including Oprah, Larry King and the Today Show. In 2009, he lost everything after a tragic accident and became homeless with $20M in debt. He has since rebuilt his life using the same strategies he teaches his clients. His story is told in the CNN documentary, Enlighten Us. Ray is on a mission to positively impact a minimum of one billion lives and businesses worldwide. Bersabeh Ray Biography: Bersabeh Ray was born in Iran in 1981 during the Iran-Iraq War. Growing up, her childhood disappeared into a cloud of death, violence, and instability. She experienced many traumatic events such as witnessing the military force take her parents when she was only four years old. Her family escaped to Pakistan when she was seven and eventually smuggled themselves to the United States. She faced many challenges growing up, such as not speaking English, falling into gang behavior and drug culture. Bersabeh was in abusive relationships for years before finding the self-confidence and courage to leave. In 2013 she met James Arthur Ray and she helped him rebuild his life after he lost everything. As an intuitive consultant, Bersabeh helps people heal from their past and take their power back. Host: Brad Szollose --- Support this podcast: https://podcasters.spotify.com/pod/show/awakenednation/support

Recorded on-stage at Øredev 2023 just after her keynote, Fredrik chats to Diana Larsen about leadership and building good teams. How to get into leaderhip? Often it’s more about picking up expectations than getting a formal onboarding Learning to not do things yourself when you start leading - everything you do is one less thing the team learns to do for itself Leadership roles are on different levels, and on a different level than non-leadership positions. A lot of thing can become invisible to people on other levels. Some things should be, others should be made visible. People want to be understood, and understand what other people in the organization are doing and what challenges they have. And everything doesn’t have to be a formal meeting with agendas and stuff. Power dynamics - hard to percieve and to talk about. Even what location you are in can become part of the power dynamics and important to take into consideration. Teams - they also exist on different levels. They don’t have to be static. 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! You can also support the podcast by buying us a coffee (or two!) through Ko-fi. Links Øredev The Øredev 2023 video playlist on Youtube Diana Diana’s keynote is not out yet Diana’s other presentation is also not yet out Diana’s books: Agile retrospectives Liftoff The five rules of accelerated learning Chris Corrigan - “Everything you do for the group is one less thing they know they can do for themselves” (in the lower half of the page) James Shore The Agile fluency game Circles & soup retro Scrum Mob programming Titles Leaders and followers Starting with courage Learning is okay here We can’t know it all Unknown power Strong three-person teams

What is project success? On time and under budget? Really? Here in this episode we explore the possibility of more. Of Value that a project can drive and we use the analogy of a software development project. We talk Agility and we talk EA. The book mentioned in the project is the Art of Agile by James Shore.   LinkedIn: https://www.linkedin.com/in/nilotpaldas/ Twitter: @EntArchRadio Email: nilotpaldas@hotmail.com Telegram Group: https://t.me/EnterpriseArchitectureRadio Music: Music by tobylane from Pixabay

This week, Dan Neumann is delighted to be joined by a new guest, James Shore, the author of The Art of Agile Development and co-creator of the Agile Fluency Project with Diana Larsen. His contribution is invaluable to the Agile field.   In this episode, James talks about the second edition of The Art of Agile Development, which was published in 2021. This edition is a fully rewritten version that shows the influence of the Agile Fluency Model, including the different zones Agile Teams can occupy, such as Focusing, Delivering, Optimizing, and Strengthening, and practices for Teams to become fluent in each area.   Key Takeaways ● James rewrote The Art of Agile Development for its second edition. ○ He rewrote the book around the ideas of the Agile Fluency Model. ○ It includes updated practices. ○ In the book, you can find out how to influence people to make a change, to try Agile ideas, and even advice when you are in a situation where you are not very Agile. ● What is the Agile Fluency Model? ○ There are four different zones that teams or organizations can occupy: Focusing, Delivering, Optimizing, and Strengthening. A Team can exhibit fluency in any of these zones. ○ A behavior is fluent when you can perform it unconsciously, naturally, as a default behavior. ○ A Team can demonstrate fluency but only the Organization can make it possible. ○ It is not a maturity model, you can be fluent in one of the zones and not the others. ● The Agile Goal: ○ For many organizations, it may be Focusing plus Delivering together. ● James talks about the structure of the book. ○ The first part of the book is about how to introduce Agile ideas. ○ Most of the book is about the practices for the Focus and the Delivery zone. ○ Alternatives and experiences can be found at the end of every practice. ● Learn the rules, break the rules, and then, ignore the rules. ○ After learning the rules you have to experiment because every Agile Team goes through a unique situation and process. ● How long does it take to achieve a level of fluency? ○ It takes time to become fluent. ○ In general, it takes two to six months to reach Focusing fluency. Have under consideration that there is a one-to-four-month period of decrease in performance while people learn. ○ During two to six months, performance will be affected while trying to reach fluency in Delivering in an expected period from three to 20 months. ○ When Optimizing fluency it takes one to two months of performance affectedness and three to nine months for reaching fluency in this area. ○ It takes one or two years to deliver reliably. ○ All these time frames overlap.   Mentioned in this Episode: Follow James Shore. Check the second edition of The Art of Agile Development. Agile Fluency Project FAST Agile   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

This week, Dan Neumann is joined by Eric Landes, Andrea Floyd, Alba Uribe, Erica Menendez, and Justin Thatil. In today's episode, they are celebrating Halloween by talking about some scary good Agile Stories, unlike previous Halloween episodes where the lessons learned after challenges and difficulties were addressed, this time, you will hear about crazy great Agile experiences that are worth sharing.   Key Takeaways Do you want to hear something scary? Doing Agile without digital tools! Feel the transformation. Don't forget what Agile looks like from the interpersonal relationship aspect. Focus on the toolset that you have and your perspective will get wider. Sometimes taking a small step into something that you are uncomfortable with is the beginning of growth. The failing product story: Justin tells the story when after a long time working trying to get a product right and being at the point of almost reaching the so-wanted outcome, the executive Team decides to cancel the project. A Scrum-But Situation: The state of the Team was the scariest at the beginning, there were problems releasing, and they were not finishing on time. This Team was doing Scrum, but poorly. Eric and Dan were part of the engagement part of this Team, they talked with the client, and the outcome was good. The client went beyond what was suggested and better Scrum was starting to happen. When Agility sneaks up on you! Andrea was working with a client, and there was a pause when she stepped away for the client to continue the journey alone, but then she was invited back. When she resumed work with the client she found that a reset had happened; she was asked very basic questions and even doubted if it was Agile that they were really doing. Andrea decided to stay curious and realized the Team was doing great things respecting the principles and practices of Agile, which are very foundational. They were, in fact, mastering Agile! The Team start to self-identify Agile improvements by looking for the what and the why behind what they were doing and the outcomes. Enabling communication and transparency can create a scary amazing effect on a Team. There was an organization that went 100% into Agile, it covered the organization, the Team, and also the physical location. Everything the Team needed was in place, they even have an additional TV to track progress on releases. They worked on the proof of concepts. Scary good collaboration! No one is taking the lead and everyone knows what they need to do. The lead is there to answer questions, it is so scary good when the leader does not know what to do because everyone is doing so great!   Mentioned in this Episode: Lead without Blame: Building Resilient Learning Teams, Diane Larsen and Tricia Broderick Agile Retrospectives: Making Good Teams Great, Diane Larsen The Art of Agile Development, James Shore and Shane Warden   Want to Learn More or Get in Touch? Visit the website and catch up with all the episodes on AgileThought.com! Email your thoughts or suggestions to Podcast@AgileThought.com or Tweet @AgileThought using #AgileThoughtPodcast!

James Shore: website, The Art of Agile Development, AOAD book club, twitterMentionedSusan Leigh Star, This is Not a Boundary Object: Reflections on the Origin of a Concept, 2010 Jeff Patton: website, story mapping articles, story mapping book, twitterGojko Adzic: website, book on impact mapping, impact mapping website, twitterDiana Larson: website, twitterAlistair Cockburn: website, twitterJessica Kerr: website, twitter, symmathesyMichael Feathers: website, twitterMiro collaboration appGather.town a collaboration app mimics more properties of physical spacePicturesA Patton-style story mapAn Adzic-style impact mappingA Shore-style cluster mapA sequence diagramCreditsShoreline image by Flickr user dronepicr, CC BY 2.0

How do you have good software design? How does this scale over time? How do you have good organizations and teams? Can this scale? If so, how? Join Chris and Austin as they discuss "Scaling Organizations and Design" with James Shore. James starts out by sharing about the Mob Programming chapter in his book The Art of Agile Development. Then they discuss scaling orgs with the FAST framework and scaling code with evolutionary design. Lastly, they talk about testing without mocks and Classicist vs. Mockist TDD. Video and show notes: https://youtu.be/duF4e3CwW9k 

Continued conversation with one of our favourite authors, James Shore, who joins us to discuss the new edition of his semnal book, The Art of Agile Development. SHOW LINKS: - Twitter: https://twitter.com/jamesshore - Website: https://www.jamesshore.com - AOD2: https://www.jamesshore.com/v2/books/aoad2 - Bookclub: https://www.jamesshore.com/v2/books/aoad2/book_club - Book: Accelerate: https://itrevolution.com/book/accelerate/ - Blog: Why I hate CruiseControl: https://www.jamesshore.com/v2/blog/2005/why-i-dont-like-cruisecontrol - Tilted Slider: https://agileconversations.com/blog/dont-add-more-metrics/ --- Our new book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com

One of our favourite authors, James Shore, joins us to discuss the new edition of his seminal book, The Art of Agile Development. SHOW LINKS: - Twitter: https://twitter.com/jamesshore - Website: https://www.jamesshore.com - AOD2: https://www.jamesshore.com/v2/books/aoad2 - Bookclub: https://www.jamesshore.com/v2/books/aoad2/book_club - Book: Accelerate: https://itrevolution.com/book/accelerate/ - Blog: Why I hate CruiseControl: https://www.jamesshore.com/v2/blog/2005/why-i-dont-like-cruisecontrol - Tilted Slider: https://agileconversations.com/blog/dont-add-more-metrics/ --- Our new book, Agile Conversations, is out now! See https://agileconversations.com where you can order your copy and get a free video when you join our mailing list! We'd love to hear any thoughts, ideas, or feedback you have about the show. Email us at info@agileconversations.com

Working longer hours does not result in greater or higher quality output. Rather, it is often how we spend our time outside of working hours that plays the biggest role in our performance from nine to five. These ideas are well captured in the principle of ‘energized work' found in James Shore's The Art of Agile. Today on the show we dive into the meaning of energized work and discuss our individual methods of attaining it. We are also lucky enough to have Raymond Lam, Principal Software Engineer at Ginkgo Bioworks, join us for the ride! We begin our conversation with the actual definition of energized work as it appears in The Art of Agile. The text also describes the concept in the form of a Haiku poem, and we make sure to include that in our discussion. We move on to speak about how workers laid the foundations for energized work before social distancing and how leaders can manage their teams in ways that encourage it in our current situation. Our conversation draws to a close with Dave, Michael, and Raymond's personal rituals for winding down, with a highlight being that Dave's dog does most of his scheduling for him!

A Little Bit Culty –In 2009, Laura Tucker attended a Sedona spiritual retreat and sweat lodge hosted by charismatic spiritual teacher James Arthur Ray. It all went tragically wrong, resulting in the deaths of fellow attendees Liz Neuman, Kirby Brown and James Shore. On this episode, Laura chats with Sarah and Nippy about her experience, what it means to practice safe spiritual seeking, and the dark side of self help.More about today's guest: Laura Tucker is the host of the Free Your Inner Guru® Podcast, a photographer, writer, and a self-described ‘recovering coach.' A creative at heart, Laura likes to explore, figure things out, create stunning visuals, and nuanced conversations. As an insight provoking leader and speaker, Laura has helped hundreds of entrepreneurs and business leaders become more self aware so they can lead more intuitively. She is a former high school teacher, trainer, sales professional, multi entrepreneur, consultant and leadership coach. She survived the 2009 fatal “sweat lodge” at a self help retreat in Sedona. You may recognize her from Enlighten Us, a CNN Films/Netflix documentary about the self help industry and the Wondery Podcast Guru: The Dark Side of Enlightenment. She has also appeared on CNN Newsroom with Brooke Baldwin and William Shatner's The UnXplained. Laura shares personal writing and nature inspired photography at lauratucker.com. Free Your Inner Guru® podcast episodes are released bi-weekly at freeyourinnerguru.com.~The views and opinions expressed on A Little Bit Culty do not necessarily reflect the official policy or position of the podcast. Any content provided by our guests, bloggers, sponsors or authors are of their opinion and are not intended to malign any religion, group, club, organization, business individual, anyone or anything.~A Little Bit Culty is proud to support the #IGOTOUT project, which empowers survivors of cultic abuse to share their stories online as a catalyst for education, prevention, and healing. Learn more at igotout.org~For more information on A Little Bit Culty and co-hosts Sarah Edmondson and Nippy “Anthony” Ames, visit our official website at alittlebitculty.com. Follow us on Instagram & Twitter @alittlebitculty~CREDITS: Executive Producers: Sarah Edmondson & Anthony AmesProduction Partner: Citizens of Sound Producer: Will RetherfordAssociate Producer: Jess TardyTheme Song: “Cultivated” by Jon Bryant co-written with Nygel AsselinAdditional Music Score by Will Retherford See acast.com/privacy for privacy and opt-out information.

  James teaches, writes, and consults on Agile software development. He is co-author of the classic Agile how-to guide, The Art of Agile Development. He is also co-creator of the Agile Fluency® Model, a highly-regarded guide for Agile adoption. He's a recipient of the Agile Alliance's Gordon Pask Award for Contributions to Agile Practice.   Links https://www.jamesshore.com/ https://twitter.com/jamesshore https://www.linkedin.com/in/james-shore-7475b6/ https://github.com/jamesshore   Resources https://www.letscodejavascript.com/ The Art of Agile Development 2nd Edition More Fearless Change "Tempting Time" by Animals As Leaders used with permissions - All Rights Reserved × Subscribe now! Never miss a post, subscribe to The 6 Figure Developer Podcast! Are you interested in being a guest on The 6 Figure Developer Podcast? Click here to check availability!  

James Shore is the author of The Art of Agile Development. Today, he is announcing the generally availability of the book and shares what you will learn. In the text below, you will find the description of the book, including a link to get a copy for yourself.   Most companies developing software employ something they call "Agile." But there's widespread misunderstanding of what Agile is and how to use it. If you want to improve your software development team's agility, this comprehensive guidebook's clear, concrete, and detailed guidance explains what to do and why, and when to make trade-offs.   In this thorough update of the classic Agile how-to guide, James Shore provides no-nonsense advice on Agile adoption, planning, development, delivery, and management taken from over two decades of Agile experience. He brings the latest ideas from Extreme Programming, Scrum, Lean, DevOps, and more into a cohesive whole. Learn how to successfully bring Agile development to your team and organization--or discover why Agile might not be for you.   This book explains how to:   Improve agility: create the conditions necessary for Agile to succeed and scale in your organization Focus on value: work as a team, understand priorities, provide visibility, and improve continuously Deliver software reliably: share ownership, decrease development costs, evolve designs, and deploy continuously Optimize value: take ownership of product plans, budgets, and experiments--and produce market-leading software Get your copy of The Art of Agile Development, 2nd Edition: Book James' LinkedIn: LinkedIn James' Twitter: Twitter Contact James: Website Fast Agile: Website LESS, large scale SCRUM: Website  

Today, James Shore joins The Azure DevOps Podcast! James teaches, writes, and consults on Agile software development. He is co-author of the classic Agile how-to guide, The Art of Agile Development, and is the co-creator of the Agile Fluency® Model; a highly-regarded guide for Agile adoption. He is also the recipient of the Agile Alliance's Gordon Pask Award for Contributions to Agile Practice.   James' book, The Art of Agile Development, first came out in late 2007. This year (late 2021), the second edition is coming out. A lot has changed with Agile development during this time and in this episode, James highlights what some of these key differences are and his advice to veteran, intermediate, and beginner programmers alike.   Topics of Discussion: [:36] About The Azure DevOps Podcast, Clear Measure; the new video podcast Architect Tips; and Jeffrey's offer to speak at virtual user groups. [1:11] About today's episode with James Shore. [1:39] Jeffrey welcomes James to the podcast. [1:44] Jeffrey congratulates James on the second edition of his book,  [2:01] James shares some of the highlights of his career and his journey as a programmer. [7:57] James discusses the history of test-driven development. [8:57] James highlights the mainstays from the first edition to the second edition of his book, The Art of Agile Development. [12:17] Why and how programming should stay fun. [13:50] James shares his perspective around what an Agile team looks like, structurally. [17:23] James elaborates on the fluidity of Agile and why it is a philosophy; not a method. [19:20] A word from Azure DevOps Podcast's sponsor: Clear Measure. [19:57] What needs to be in place in order for Agile to succeed. [23:13] How to answer the question of, “When is it going to be done?” with Agile. [26:22] How to be more predictive in an Agile team. [28:48] James speaks about engineering practices that are general rules of thumb for teams employing Agile. [32:23] Where Kanban fits into the Agile picture and what James recommends for new teams. [35:47] James gives advice to programmers and companies when it comes to working remotely. [39:14] Where to find James, his work, and his book online. [40:53] Jeffrey congratulates James once again on the 2nd edition of his book and thanks him for joining the podcast and sharing his insights!   Mentioned in this Episode: Architect Tips — New video podcast! Azure DevOps Clear Measure (Sponsor) .NET DevOps for Azure: A Developer's Guide to DevOps Architecture the Right Way, by Jeffrey Palermo — Available on Amazon! bit.ly/dotnetdevopsebook — Click here to download the .NET DevOps for Azure ebook! Jeffrey Palermo's YouTube Jeffrey Palermo's Twitter — Follow to stay informed about future events! DEVintersection Conference — Dec. 7th‒9th in Las Vegas, Nevada (Use discount code: PALERMO) James Shore's Website James Shore's Twitter @JamesShore The Art of Agile Development, by James Shore and Shane Warden (2nd Edition, 2021) Dreyfus Learning Model Agile Fluency Miro Mural Mythical Man-Month, The: Essays on Software Engineering, by Frederick Brooks Jr.   Want to Learn More? Visit AzureDevOps.Show for show notes and additional episodes.

Today, I speak with James Shore, author of The Art of Agile, Development. We talk about the Agile Fluency Model he developed alongside Diana Larsen. When you re-organize teams with a focus on agility, changes will not happen overnight. Teams will have to get used to new tools, processes, and interpersonal dynamics. Bruce Tuckman created a model that recognizes specific team dynamics. The model proposes that teams go through several stages: forming, storming, norming, and performing.  If you have ever been in a large team meeting to make critical business changes or are part of a re-org, you will be familiar with that model. Re-structuring for agility means you will not only see the four phases of the Tuckman model but another as well. That is where James Shore and Diana Larsen come in. They designed a model to appreciate the cultural shift in how your teams gain fluency in delivering more value faster, and they call it the Agile Fluency Model.

In 2008, at the height of the ‘great recession', Laura was at a personal and professional cross-roads. She became involved in the self-help industry, first as a client, then as a coach. Her path took a tragic turn. On October 8, 2009, she was present at what became know as the fatal “sweat lodge incident” near Sedona run by James Arthur Ray. Three fellow workshop participants, James Shore, Kirby Brown and Liz Neuman lost their lives, and dozens more were injured. She was asked to relive it through the criminal trial, CNN's Enlighten Us documentary and Wondery's podcast series, “Guru - The Dark Side of Enlightenment”, exploring that fateful night. In 2017 she created Free Your Inner Guru®, a podcast for ethical leaders and discerning seekers. Links: Podcast: https://www.freeyourinnerguru.com/ (https://www.freeyourinnerguru.com) And Laura's Leadership Community: https://freeyourinnerguru.com/leadership-community/ (https://freeyourinnerguru.com/leadership-community/) Website: https://www.lauratucker.com/ (https://www.lauratucker.com) - where you'll find her blog and photography Insta: @freeyourinnerguru and @lauraatucker ____ And host Linda McLachlan can be found via: www.thearena-podcast.com or on her coaching website: www.lindamclachlan.com You can follow her on Instagram & Facebook @arenalivcourage or on Twitter: @Arena_LivCour Leave a rating or review at: https://www.lovethepodcast.com/thearena This podcast uses the following third-party services for analysis: Chartable - https://chartable.com/privacy

Das Agile Fluency Model ist ein sehr interessantes Hilfsmittel für Softwareentwicklungsteams, die "agiler" werden wollen. Entwickelt von Diana Larsen und James Shore ist es noch recht neu, aber ich finde es sehr nützlich. Ich habe im Frühjahr einen Kurs belegt und lasse Euch ein bisschen daran teilhaben.

The new normal has accelerated the need for companies to adopt more modern, flexible, and scalable workplace solutions providing employees with a superior working environment while ensuring the security of the organization and its intellectual property. In this two-part podcast series, Capgemini’s Digital Workplace Services expert Gary Taylor talks to James Shore and James O'Regan from IGEL, while they share their deep insights into the Windows Virtual Desktop on Linux-based operating systems and devices which has grown in popularity due to the demand for work-from-home options In part one, Gary along with James will delve into the technical aspects, covering: 1.What are the Linux-based Windows Virtual Desktop Solutions? 2.What are the benefits of Interacting with Windows Virtual Desktop via a Linux-based operating system? 3.What are the options of deployment and managing Solution? Connect with subject-matter experts: Gary Taylor: (https://www.linkedin.com/in/gary-taylor-3779ba11/) James Shore: (https://www.linkedin.com/in/shorejames/) James O'Regan: (https://www.linkedin.com/in/southcirc/) To know more about Digital Workspace, do visit our Connected Employee Experience https://www.capgemini.com/service/technology-operations/infrastructure-services/connected-workspace/ https://www.capgemini.com/service/technology-operations/infrastructure-services/connected-employee-experience/ Subscribe to Designing Momentum: Subscribe on Apple Podcasts: podcasts.apple.com/us/podcast/desi…um/id1531934072 Subscribe on Spotify: open.spotify.com/show/5lFmAQhVoRkcV05itP1UEz Subscribe on Google Podcasts: www.google.com/podcasts?feed=aHR…yLmZtL21vbWVudHVt

The new normal has accelerated the need for companies to adopt more modern, flexible, and scalable workplace solutions providing employees with a superior working environment while ensuring the security of the organization and its intellectual property. In this two-part podcast series, Capgemini’s Digital Workplace Services expert Gary Taylor talks to James Shore and James O'Regan from IGEL, while they share their deep insights into the Windows Virtual Desktop on Linux-based operating systems and devices which has grown in popularity due to the demand for work-from-home options In part one, Gary along with James will delve into the technical aspects, covering: 1.What are the Linux-based Windows Virtual Desktop Solutions? 2.What are the benefits of Interacting with Windows Virtual Desktop via a Linux-based operating system? 3.What are the options of deployment and managing Solution? Connect with subject-matter experts: Gary Taylor: (www.linkedin.com/in/gary-taylor-3779ba11/) James Shore: (www.linkedin.com/in/shorejames/) James O'Regan: (www.linkedin.com/in/southcirc/) To know more about Digital Workspace, do visit our Connected Employee Experience www.capgemini.com/service/technolo…ected-workspace/ www.capgemini.com/service/technolo…oyee-experience/ Subscribe to Designing Momentum: Subscribe on Apple Podcasts: podcasts.apple.com/us/podcast/desi…um/id1531934072 Subscribe on Spotify: open.spotify.com/show/5lFmAQhVoRkcV05itP1UEz Subscribe on Google Podcasts: www.google.com/podcasts?feed=aHR…yLmZtL21vbWVudHVt

In this episode, Richard talks with James Shore. James is an Agile software development teacher, writer, and consultant. He is the co-author of the book The Art of Agile Development, a seminal work in the Agile community. He also co-created with Diana Larsen the Agile Fluency Model, a highly-regarded guide for Agile adoption. James tells us about his first encounter with Extreme Programming, what he learned from that experience, and why he has been on the mission ever since to recreate the joy he felt with this team. When you finish listening to this podcast, make sure to connect with James on Twitter at https://twitter.com/jamesshore and LinkedIn at https://www.linkedin.com/in/james-shore-7475b6/, visit his website at https://www.jamesshore.com, and read his book The Art of Agile Development. You can read the full transcript of the episode at: https://kasperowski.com/podcast-58-james-shore/.

Agile Fluency® Project Consultant & Co-Founder James Shore talks about what being agile truly means for software development and how cross-functional teams within the organization help implement agile development. He also shares how businesses can address the challenges associated with adopting the philosophy of being agile in changing the habits and behaviors of team members, managers, and stakeholders.

Psychic and spiritual advisor Julie Min is back for a deep dive into the role of personal responsibility in our healing journey. Julie Min is a psychic, spiritual counselor, and a survivor of childhood sexual abuse and the fatal sweat lodge led by James Arthur Ray. It's hard to believe it's been three years since Julie's first visit to Free Your Inner Guru. She is back to share wisdom gained from her life experience and commitment to the healing journey.  In this deep dive, Julie shares her backstory and throws the doors open on the life and thoughts of someone who has psychic ability. Conversation highlights: Julie's opinion of the Wondery podcast Guru: The Dark Side of Enlightenment. Why the being labeled a victim can be uncomfortable and unhelpful. What it means to "willingly give your power away." How personal responsibility is a key strategy in Julie's response to childhood sexual abuse. Red flags and psychic warnings leading up to the tragedy of the Sedona sweat lodge. Julie's key strategy to connect to your inner wisdom. Choose love now:  Julie's tribute to Kirby Brown, James Shore, and Liz Neuman. Memorable quotes from Julie Min: "Part of the conscious path, the spiritual path, is recognizing where other people have responsibility and where we have responsibility in the choices we’ve made." "If I could take personal responsibility, then I had an action plan. Even though it was going to be hard, there was something I could do." "The only way we can trust ourselves is to actually trust ourselves. We have to act on the knowledge we have been given." Mentioned in this episode Julie's first visit to Free Your Inner Guru - Episode 20 - Julie Min:  From Tragedy and Survivor's Guilt to Forgiveness, Happiness, and Love Julie Min on Facebook Want more big conversations in your life? Support the podcast and join the Free Your Inner Guru® Leadership Community at patreon.com/freeyourinnerguru

We can all do better than uphold the status quo. Laura Tucker reflects on her involvement in the Wondery podcast Guru: The Dark Side of Enlightenment. In this episode I share what it was like to participate in this huge podcast and why I lend my voice to projects that tell the story about what happened at James Arthur Ray's Spiritual Warrior retreat in October 2009 when Kirby Brown, James Shore, and Liz Neuman died after a "sweat lodge" ceremony gone wrong. I am so grateful to everyone who has become emotionally invested in this story, and who want more and want better for the industry that has sprung up around being your best self. Mentioned in this episode: Wondery's Guru: The Dark Side of Enlightenment on Apple Podcasts on Spotify At lauratucker.com Laura's Daily Letters Articles and podcast episodes related to Spiritual Warrior and Guru For Members Only - Read weekly installments of my memoir in progress. Want more big conversations in your life? Support the podcast and join the Free Your Inner Guru® Leadership Community at patreon.com/freeyourinnerguru

Laura Richards, Jim Clemente and Lisa Zambetti talk with Ginny Brown whose daughter, Kirby Brown, died at a New Age "Spiritual Warrior" retreat led by JAR in Sedona Arizona.James Shore and Liz Neuman also died at the same event. Ginny talks about her daughter Kirby's zest for life, the day her life changed forever, the impact on family and friends, the ongoing battle she is fighting to ensure accountability and safety. Laura and Jim discuss whether this was a cult. Please read the book The Sweet Life: How We Lived After Kirby Died by Ginny Brown and Jean Brown. https://www.amazon.com/dp/0578708795/ref=cm_sw_r_tw_dp_x_Bsm.Eb8H07NED via @amazon #HerNameWasKirbyBrown#HerNameWasLizNeuman#HisNameWasJamesShoreTHANK YOU TO OUR SPONSORSNATIVEMake the switch to Native today by going to NativeDeo.com/RealCrime or use Promo Code RealCrime at check out for 20% off of your first orderLUMINESSGo to TrySilk.com/REALCRIME to get 60% off your Luminess Silk 4-in-1 Airbrush system.FUNCTION OF BEAUTYVisit FUNCTIONOFBEAUTY.com/RealCrime to save 20% off of your first order

Laura Richards, Jim Clemente and Lisa Zambetti continue their discussion about the Wondery podcast "Guru" and discuss the deaths of Kirby Brown, Liz Neuman and James Shore on October 8, 2009 at a New Age "Spiritual Warrior" retreat conceived and hosted by JAR at the Angel Valley Retreat Center in Yavapai County near Sedona, Arizona.Eighteen others were hospitalized after suffering burns, dehydration, breathing problems, kidney failure, or elevated body temperature.The Death Dealer - An Article by Matt Stroud for The Verge.comhttps://www.theverge.com/2013/12/4/5038930/the-death-dealer-james-arthur-sweat-lodge-deaths-in-sedona#HerNameWasKirbyBrown#HerNameWasLizNeuman#HisNameWasJamesShoreTHANKS TO OUR SPONSORSBEST FIENDSDownload for Free at the Apple App Store or Google PlayINTELLIWHITEGet $50 off the new INDIGLOW Teeth Whitening System. Go to TryIndiglow.com and use promo code REALCRIME

Laura Richards, Jim Clemente and Lisa Zambetti discuss the Wondery podcast "Guru" and break down the dark side of enlightenment. We discuss how someone with no qualifications or credentials can influence and manipulate so many as well as the enablers.#HerNameWasKirbyBrown#HerNameWasLizNeuman#HisNameWasJamesShoreTHANKS TO OUR SPONSORSBEST FIENDSDownload for Free at the Apple App Store or Google PlayINTELLIWHITEGet $50 off the new INDIGLOW Teeth Whitening System. Go to TryIndiglow.com and use promo code REALCRIME

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

In this episode, I speak with Diana Larsen about Agile Retrospectives, especially in the context of the virtual teams. We talked about a few helpful tips and tricks for teams that work from home during the corona virus. We also talk about the first and last zone of the agile fluency model which she created a few years ago with James Shore.

Dr. Dave: So I sent you a few questions today. Let’s just begin. Let’s start talking about, tell us about your role in Agile Fluency, and the Agile Fluency model. What is, yeah.   Diana: Well, so I’m a co-creator, co-developer of the model. James Shore and I a number of years ago were noticing… The post EAFH23: Delivery Value with Diana Larsen, Agile Fluency Model appeared first on Leaders share how-to practices - KnolShare with Dr. Dave Podcast on GrokShare.com.

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: James Shore Episode Summary James Shore, the author of the book, “The Art of Agile Development” and a thought leader in the Agile software development community, talks about his journey in Agile development. James and Charles discuss how Agile has transformed software development process and the traits that a good software developer should have. James talks about his contributions to the developer community, his CSS testing tool quixote and the Agile Fluency Project. Links JavaScript Jabber 360: Evolutionary Design with James Shore JavaScript Jabber 349: Agile Development – The Technical Side with James Shore My Angular Story 061: James Shore The Art Of Agile Development By James Shore James Shore’s Website   James Shore Twitter James Shore’s GitHub  https://www.agilefluency.org/ Agile Fluency Join The Conversation https://www.facebook.com/DevChattv Picks James Shore: Neil Killick Twitter http://vihart.com Charles Max Wood: ng-conf Ready Player One (2018)    

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: James Shore Episode Summary James Shore, the author of the book, “The Art of Agile Development” and a thought leader in the Agile software development community, talks about his journey in Agile development. James and Charles discuss how Agile has transformed software development process and the traits that a good software developer should have. James talks about his contributions to the developer community, his CSS testing tool quixote and the Agile Fluency Project. Links JavaScript Jabber 360: Evolutionary Design with James Shore JavaScript Jabber 349: Agile Development – The Technical Side with James Shore My Angular Story 061: James Shore The Art Of Agile Development By James Shore James Shore’s Website   James Shore Twitter James Shore’s GitHub  https://www.agilefluency.org/ Agile Fluency Join The Conversation https://www.facebook.com/DevChattv Picks James Shore: Neil Killick Twitter http://vihart.com Charles Max Wood: ng-conf Ready Player One (2018)    

Sponsors Sentry use the code “devchat” for 2 months free on Sentry small plan CacheFly Host: Charles Max Wood Joined By Special Guest: James Shore Episode Summary James Shore, the author of the book, “The Art of Agile Development” and a thought leader in the Agile software development community, talks about his journey in Agile development. James and Charles discuss how Agile has transformed software development process and the traits that a good software developer should have. James talks about his contributions to the developer community, his CSS testing tool quixote and the Agile Fluency Project. Links JavaScript Jabber 360: Evolutionary Design with James Shore JavaScript Jabber 349: Agile Development – The Technical Side with James Shore My Angular Story 061: James Shore The Art Of Agile Development By James Shore James Shore’s Website   James Shore Twitter James Shore’s GitHub  https://www.agilefluency.org/ Agile Fluency Join The Conversation https://www.facebook.com/DevChattv Picks James Shore: Neil Killick Twitter http://vihart.com Charles Max Wood: ng-conf Ready Player One (2018)    

Sponsors Triplebyte $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel Aaron Frost AJ O’Neal Joe Eames Aimee Knight Chris Ferdinandi Joined by special guest: James Shore Episode Summary Special guest James Shore returns for another episode of JavaScript Jabber. Today the panel discusses the idea of evolutionary design. Evolutionary design comes from Agile development. It is based on the principles of continuous integration and delivery and test driven development. In short, evolutionary design is designing your code as you go rather than in advance. The panelists discuss the difficulties of evolutionary design and how to keep the code manageable.  James Shore introduces the three types of design that make up evolutionary design, namely simple design, incremental design, and continuous design. They talk about the differences between evolutionary design and intelligent design and the correlations between evolutionary design increasing in popularity and the usage of Cloud services. They talk about environments that are and are not conducive to evolutionary design and the financial ramifications of utilizing evolutionary design. The panelists talk about the difficulties of planning what is needed in code and how it could benefit from evolutionary design. James enumerates the steps for implementing evolutionary design, which are upfront design, reflective design, and refactoring . The team ends by discussing the value of frameworks and how they fit with evolutionary design. Links Agile Angular API CRC cards (class responsibility collaborators) Ember IntelliJ NPM React Redux Scrum Waterfall XJS Picks AJ O’Neal: Spiderman: Into the Spider-Verse Pre-gap tracks album list QuickChip remover alloy Aimee Knight: Puns.dev Bouldering James Shore: Spiderman: Into the Spider Verse Pandemic Legacy Aaron Frost: Easter Candy, especially Nerd Jelly beans Cadbury Mini Eggs Fun D&D moments Joe Eames: Chronicles of Crime board game

Sponsors Triplebyte $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel Aaron Frost AJ O’Neal Joe Eames Aimee Knight Chris Ferdinandi Joined by special guest: James Shore Episode Summary Special guest James Shore returns for another episode of JavaScript Jabber. Today the panel discusses the idea of evolutionary design. Evolutionary design comes from Agile development. It is based on the principles of continuous integration and delivery and test driven development. In short, evolutionary design is designing your code as you go rather than in advance. The panelists discuss the difficulties of evolutionary design and how to keep the code manageable.  James Shore introduces the three types of design that make up evolutionary design, namely simple design, incremental design, and continuous design. They talk about the differences between evolutionary design and intelligent design and the correlations between evolutionary design increasing in popularity and the usage of Cloud services. They talk about environments that are and are not conducive to evolutionary design and the financial ramifications of utilizing evolutionary design. The panelists talk about the difficulties of planning what is needed in code and how it could benefit from evolutionary design. James enumerates the steps for implementing evolutionary design, which are upfront design, reflective design, and refactoring . The team ends by discussing the value of frameworks and how they fit with evolutionary design. Links Agile Angular API CRC cards (class responsibility collaborators) Ember IntelliJ NPM React Redux Scrum Waterfall XJS Picks AJ O’Neal: Spiderman: Into the Spider-Verse Pre-gap tracks album list QuickChip remover alloy Aimee Knight: Puns.dev Bouldering James Shore: Spiderman: Into the Spider Verse Pandemic Legacy Aaron Frost: Easter Candy, especially Nerd Jelly beans Cadbury Mini Eggs Fun D&D moments Joe Eames: Chronicles of Crime board game

Sponsors Triplebyte $1000 signing bonus Sentry use the code “devchat” for $100 credit CacheFly Panel Aaron Frost AJ O’Neal Joe Eames Aimee Knight Chris Ferdinandi Joined by special guest: James Shore Episode Summary Special guest James Shore returns for another episode of JavaScript Jabber. Today the panel discusses the idea of evolutionary design. Evolutionary design comes from Agile development. It is based on the principles of continuous integration and delivery and test driven development. In short, evolutionary design is designing your code as you go rather than in advance. The panelists discuss the difficulties of evolutionary design and how to keep the code manageable.  James Shore introduces the three types of design that make up evolutionary design, namely simple design, incremental design, and continuous design. They talk about the differences between evolutionary design and intelligent design and the correlations between evolutionary design increasing in popularity and the usage of Cloud services. They talk about environments that are and are not conducive to evolutionary design and the financial ramifications of utilizing evolutionary design. The panelists talk about the difficulties of planning what is needed in code and how it could benefit from evolutionary design. James enumerates the steps for implementing evolutionary design, which are upfront design, reflective design, and refactoring . The team ends by discussing the value of frameworks and how they fit with evolutionary design. Links Agile Angular API CRC cards (class responsibility collaborators) Ember IntelliJ NPM React Redux Scrum Waterfall XJS Picks AJ O’Neal: Spiderman: Into the Spider-Verse Pre-gap tracks album list QuickChip remover alloy Aimee Knight: Puns.dev Bouldering James Shore: Spiderman: Into the Spider Verse Pandemic Legacy Aaron Frost: Easter Candy, especially Nerd Jelly beans Cadbury Mini Eggs Fun D&D moments Joe Eames: Chronicles of Crime board game

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

Sponsors KendoUI Sentry use the code “devchat” for $100 credit Clubhouse Panel AJ O’Neal Aimee Knight Joe Eames Charles Max Wood Special Guest: James Shore Episode Summary James Shore is a developer who specializing in extreme programming, an Agile method. He also used to host a screencast called Let’s Code Test-Driven JavaScript. They begin by discussing the core of Agile development, which James believes is being responsive to customers and business partners in a way that’s sustainable and humane for the programmers involved. It prioritizes individuals and interactions over processes and tools. More can be found in The Agile Manifesto. James delves into the historical context of the immersion of Agile and how things have changed from the 90’s. Now, the name Agile is everywhere, but the ideals of agile are not as common. There is a tendency to either take Agile buzzwords and apply them to the way it was done long ago, or it’s absolute chaos. James talks about ways to implement Agile in the workplace. He believes that the best way to learn Agile is work with someone who knows Agile, or read a book on it and then apply it. James recommends his book The Art of Agile Development: Pragmatic Guide to Agile Software Development for people who want to started with Agile development. The panelists talk about where people often get stuck with implementing Agile. The hosts talk about their own processes in their company. They discuss how people involved in the early days of Agile are disappointed in how commercial it has become.They agree that what’s really the most important is the results. If you can respond to a request to change direction in less than two weeks and you don’t have to spend months and months preparing something, and you do that in a way where the people on the team feel like their contributing, then you’re doing Agile. James thinks that the true genius of Agile is in the way the actual work is done rather than in the way your organize the work. Links Agile Scrum Waterfall Feature Driven Development Extreme Programming (XP) Jira Bamboo Confluence Atlassian stack Cowboy Mock objects Grows Method by Andy Hunt Picks AJ O’Neal: Origin by Dan Brown Searching Aimee Knight: Hacker News Interview Questions Thread. Joe Eames: The Ballad of Buster Scruggs on Netflix Charles Max Wood: Getting up early John Sonmez Kanbanflow video Drip James Shore: Lost in Space on Netflix Star Citizen PC game Jame’s Agile book online

Panel: Charles Max Wood Guest: James Shore This week on My Angular Story, Charles speaks with James Shore who is the author of the book, “The Art of Agile.” James is a thought leader in the Agile software development community. He combines deep technical expertise with whole-system thinking to help development teams worldwide achieve great things! Check out his complete biography here! Chuck and James talk about Agile development, James’ background, and future projects! In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 0:48 – Chuck: Welcome! James was on a past episode, which was show 205! Give us an introduction, please! 1:05 – James: I have been involved with the software industry since 1991. I have written a book and it’s fairly evergreen. 1:30 – Chuck: Yeah, I remember that’s when the Agile development was getting really, really hot! 2:09 – James: Yeah in the early 2000s there was this energy to do software really well, and it seems like it’s turned into this bureaucracy. I find that to be depressing a tiny bit. 2:50 – Chuck: Yeah, I agree. 3:01 – James: Going back to a perspective where excellence is no longer the priority; excellence in your craft. 3:31 – Chuck. 3:34 – James: Yeah that was Bob Marten.  James talks about the Agile movement. 4:22 – Chuck: This show is a walk back throughout your story. Let’s talk about HOW you got into this stuff. 4:40 – James talks about his background. 4:58 – Chuck talks about his Grandpa and his experience with technology when he was young. 5:10 – James: ...it had a whopping 2K of memory! That’s really how I got involved into programming. Later on I got a Trash 80 then an Apple 2, so I had programming in through my blood. 6:01 – Chuck. 6:08 – James talks about switching between computer and antenna, and his black and white T.V. He also talks about the electrical engineering program at the university. 7:16 – Chuck: I studied ad received my computer science degree. 7:28 – James. 7:34 – Chuck: You have been in the industry since 2001 and you are a bit older than me. 7:50 – James: My first job was in 1994. Then I wrote some things with Fido Net. Fido Net was this early online form thing. Sort of like Used Net / Used Groups (online bulletin web forms) via the telephone dial-up. They were hobbyists running this out from their home. It was basically chat forms. Once you have some experience (doesn’t matter your degree) – it’s...have you done this before? 9:30 – Chuck: This is RIGHT in-line with what I say in my eBook that I am developing now. 10:00 – James: I didn’t even post that I was looking for a job, but I got very lucky. 10:15 – Chuck: What is your journey look like and how did you get into Agile development? 10:30 – James talks about his Kickstarter, knowledge in JavaScript, programming experience, and more here – check it out! 13:16 – Chuck: How did you get to Agile development? 13:31 – James: I was programming throughout my teens. I was working on a really complicated project. I still play Dungeons and Dragons (D&D). It was the most complicated program that I built at that point. I had it in my head and then I didn’t understand it anymore. The program collapsed. To me that was really transformative b/c it’s not writing the algorithms but how it all works together. Then this taught me how to communicate the design to the other members on the team to make it work. 15:50 – James: Have you heard of Rational Rose? You don’t hear about it anymore b/c it was a complete flop. 17:20 – Chuck: Wow! 17:33 – James: It was actually detrimental to get it done. It really was a crisis of faith. I ran into this book: Object Modeling in Color by Peter Coad. Extreme Programming is mentioned, too, by James’ coworker! 21:10 – Chuck: It’s so interesting to me. We focus so much on the technological side, we forget to talk about the people, and the other sides to this. It’s easy to overlook this other stuff. 21:47 – James: There is so much silver bullet thinking within this industry. The original communication from person-to-person is so crucial. It’s so important to software development. Ultimately, the computer doesn’t care, but the collaboration is the real trick and the real challenge. 23:10 – Chuck talks about his brother and his computer science courses experience. 24:27 – James: It could be that 1 team could solve a problem but nowadays it’s working with multiple teams. People want to water things down to help facilitate – but don’t do that. There is a huge large scale Agile that is large interdependent teams. 25:19 – Chuck: MFCEO is a podcast that I am listening to now. He says that nobody wants to sit down and dictate what each member will be responsible for. Chuck reads a quote from an episode from MFCEO – check it out! 26:54 – James: It’s something that people have lost track of. I still program daily even though I do this Agile stuff as well. I have been programming for 25 years and Extreme Programming was the most effective thing for me throughout my career. James: I think XP is the time (now) to have a comeback! 29:41 – Chuck: That was my experience, too. We pushed one team to go to Agile, and then we went to our boss. Chuck: We’d sit down every two weeks and have an Agile-Perspective (what is working and what isn’t working). We are talking about HOW we are writing the software, and that is really what we are after. 30:54 – James: You are building the TEAM that builds the project. Of course, you need to have consistencies across the team, and every team is different b/c every member has different personalities. Mod Programming is we are going to work as a whole group around a screen. Personally, that is not my style but I would TRY it. If it worked for that team then I would do it. 32:00 – Chuck: That is the beauty of it. With this set of programmers x, y, and z may or may not work, and that is O.K. 32:25 – James: I heard about Extreme Programming and I thought it was nuts!! 32:40 – Chuck. 32:44 – James: The more I tried it, and the more it worked. Try Extreme Programming b/c it’s totally a different experience. It’s my book that I wrote 10 years ago but it still is applicable today. Try it for a few months (3 months) or so, b/c it takes time to figure out the different terms and such. Go try out a bunch of new different things, but figuring out HOW to make it work for me. 34:05 – Chuck: Yeah, you need data. Look at the data. Go experiment. 34:47 – James: Try it for real. Check out this essay: “We tried baseball, and it didn’t work.” James: Many things only work in context!  What we do is we change the context in Agile. 35:58 – Chuck: What are you working on now? 36:00 – James: I am actually working on AgileFluency.org. It’s a set of tools for coaches and leaders to CHANGE their context. How can you find those constraints and invest on changing those. 36:31 – Chuck: Where do they go to find you? 36:40 – James: My website - it’s the ugliest website, but it’s been working since 2003. 36:54 – Picks! 37:05 – Fresh Books! END – CacheFly Links: jQuery Angular JavaScript Vue React Slack Zone.js GitHub – Zone.js Chuck’s Twitter Chuck’s E-mail: chuck@devchat.tv Timex Sinclair FidoNet VHDL Book: Java Modeling Color with UML Pivotal Labs Book: The ART OF AGILE DEVELOPMENT BY JAMES SHORE James Shore’s Website Sponsors: Get A Coder Job Fresh Books Cache Fly Picks: Chuck Podcast: MFCEO James Package Management Tool: Nix.org

Panel: Charles Max Wood Guest: James Shore This week on My Angular Story, Charles speaks with James Shore who is the author of the book, “The Art of Agile.” James is a thought leader in the Agile software development community. He combines deep technical expertise with whole-system thinking to help development teams worldwide achieve great things! Check out his complete biography here! Chuck and James talk about Agile development, James’ background, and future projects! In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 0:48 – Chuck: Welcome! James was on a past episode, which was show 205! Give us an introduction, please! 1:05 – James: I have been involved with the software industry since 1991. I have written a book and it’s fairly evergreen. 1:30 – Chuck: Yeah, I remember that’s when the Agile development was getting really, really hot! 2:09 – James: Yeah in the early 2000s there was this energy to do software really well, and it seems like it’s turned into this bureaucracy. I find that to be depressing a tiny bit. 2:50 – Chuck: Yeah, I agree. 3:01 – James: Going back to a perspective where excellence is no longer the priority; excellence in your craft. 3:31 – Chuck. 3:34 – James: Yeah that was Bob Marten.  James talks about the Agile movement. 4:22 – Chuck: This show is a walk back throughout your story. Let’s talk about HOW you got into this stuff. 4:40 – James talks about his background. 4:58 – Chuck talks about his Grandpa and his experience with technology when he was young. 5:10 – James: ...it had a whopping 2K of memory! That’s really how I got involved into programming. Later on I got a Trash 80 then an Apple 2, so I had programming in through my blood. 6:01 – Chuck. 6:08 – James talks about switching between computer and antenna, and his black and white T.V. He also talks about the electrical engineering program at the university. 7:16 – Chuck: I studied ad received my computer science degree. 7:28 – James. 7:34 – Chuck: You have been in the industry since 2001 and you are a bit older than me. 7:50 – James: My first job was in 1994. Then I wrote some things with Fido Net. Fido Net was this early online form thing. Sort of like Used Net / Used Groups (online bulletin web forms) via the telephone dial-up. They were hobbyists running this out from their home. It was basically chat forms. Once you have some experience (doesn’t matter your degree) – it’s...have you done this before? 9:30 – Chuck: This is RIGHT in-line with what I say in my eBook that I am developing now. 10:00 – James: I didn’t even post that I was looking for a job, but I got very lucky. 10:15 – Chuck: What is your journey look like and how did you get into Agile development? 10:30 – James talks about his Kickstarter, knowledge in JavaScript, programming experience, and more here – check it out! 13:16 – Chuck: How did you get to Agile development? 13:31 – James: I was programming throughout my teens. I was working on a really complicated project. I still play Dungeons and Dragons (D&D). It was the most complicated program that I built at that point. I had it in my head and then I didn’t understand it anymore. The program collapsed. To me that was really transformative b/c it’s not writing the algorithms but how it all works together. Then this taught me how to communicate the design to the other members on the team to make it work. 15:50 – James: Have you heard of Rational Rose? You don’t hear about it anymore b/c it was a complete flop. 17:20 – Chuck: Wow! 17:33 – James: It was actually detrimental to get it done. It really was a crisis of faith. I ran into this book: Object Modeling in Color by Peter Coad. Extreme Programming is mentioned, too, by James’ coworker! 21:10 – Chuck: It’s so interesting to me. We focus so much on the technological side, we forget to talk about the people, and the other sides to this. It’s easy to overlook this other stuff. 21:47 – James: There is so much silver bullet thinking within this industry. The original communication from person-to-person is so crucial. It’s so important to software development. Ultimately, the computer doesn’t care, but the collaboration is the real trick and the real challenge. 23:10 – Chuck talks about his brother and his computer science courses experience. 24:27 – James: It could be that 1 team could solve a problem but nowadays it’s working with multiple teams. People want to water things down to help facilitate – but don’t do that. There is a huge large scale Agile that is large interdependent teams. 25:19 – Chuck: MFCEO is a podcast that I am listening to now. He says that nobody wants to sit down and dictate what each member will be responsible for. Chuck reads a quote from an episode from MFCEO – check it out! 26:54 – James: It’s something that people have lost track of. I still program daily even though I do this Agile stuff as well. I have been programming for 25 years and Extreme Programming was the most effective thing for me throughout my career. James: I think XP is the time (now) to have a comeback! 29:41 – Chuck: That was my experience, too. We pushed one team to go to Agile, and then we went to our boss. Chuck: We’d sit down every two weeks and have an Agile-Perspective (what is working and what isn’t working). We are talking about HOW we are writing the software, and that is really what we are after. 30:54 – James: You are building the TEAM that builds the project. Of course, you need to have consistencies across the team, and every team is different b/c every member has different personalities. Mod Programming is we are going to work as a whole group around a screen. Personally, that is not my style but I would TRY it. If it worked for that team then I would do it. 32:00 – Chuck: That is the beauty of it. With this set of programmers x, y, and z may or may not work, and that is O.K. 32:25 – James: I heard about Extreme Programming and I thought it was nuts!! 32:40 – Chuck. 32:44 – James: The more I tried it, and the more it worked. Try Extreme Programming b/c it’s totally a different experience. It’s my book that I wrote 10 years ago but it still is applicable today. Try it for a few months (3 months) or so, b/c it takes time to figure out the different terms and such. Go try out a bunch of new different things, but figuring out HOW to make it work for me. 34:05 – Chuck: Yeah, you need data. Look at the data. Go experiment. 34:47 – James: Try it for real. Check out this essay: “We tried baseball, and it didn’t work.” James: Many things only work in context!  What we do is we change the context in Agile. 35:58 – Chuck: What are you working on now? 36:00 – James: I am actually working on AgileFluency.org. It’s a set of tools for coaches and leaders to CHANGE their context. How can you find those constraints and invest on changing those. 36:31 – Chuck: Where do they go to find you? 36:40 – James: My website - it’s the ugliest website, but it’s been working since 2003. 36:54 – Picks! 37:05 – Fresh Books! END – CacheFly Links: jQuery Angular JavaScript Vue React Slack Zone.js GitHub – Zone.js Chuck’s Twitter Chuck’s E-mail: chuck@devchat.tv Timex Sinclair FidoNet VHDL Book: Java Modeling Color with UML Pivotal Labs Book: The ART OF AGILE DEVELOPMENT BY JAMES SHORE James Shore’s Website Sponsors: Get A Coder Job Fresh Books Cache Fly Picks: Chuck Podcast: MFCEO James Package Management Tool: Nix.org

Panel: Charles Max Wood Guest: James Shore This week on My Angular Story, Charles speaks with James Shore who is the author of the book, “The Art of Agile.” James is a thought leader in the Agile software development community. He combines deep technical expertise with whole-system thinking to help development teams worldwide achieve great things! Check out his complete biography here! Chuck and James talk about Agile development, James’ background, and future projects! In particular, we dive pretty deep on: 0:00 – Advertisement: Get A Coder Job! 0:48 – Chuck: Welcome! James was on a past episode, which was show 205! Give us an introduction, please! 1:05 – James: I have been involved with the software industry since 1991. I have written a book and it’s fairly evergreen. 1:30 – Chuck: Yeah, I remember that’s when the Agile development was getting really, really hot! 2:09 – James: Yeah in the early 2000s there was this energy to do software really well, and it seems like it’s turned into this bureaucracy. I find that to be depressing a tiny bit. 2:50 – Chuck: Yeah, I agree. 3:01 – James: Going back to a perspective where excellence is no longer the priority; excellence in your craft. 3:31 – Chuck. 3:34 – James: Yeah that was Bob Marten.  James talks about the Agile movement. 4:22 – Chuck: This show is a walk back throughout your story. Let’s talk about HOW you got into this stuff. 4:40 – James talks about his background. 4:58 – Chuck talks about his Grandpa and his experience with technology when he was young. 5:10 – James: ...it had a whopping 2K of memory! That’s really how I got involved into programming. Later on I got a Trash 80 then an Apple 2, so I had programming in through my blood. 6:01 – Chuck. 6:08 – James talks about switching between computer and antenna, and his black and white T.V. He also talks about the electrical engineering program at the university. 7:16 – Chuck: I studied ad received my computer science degree. 7:28 – James. 7:34 – Chuck: You have been in the industry since 2001 and you are a bit older than me. 7:50 – James: My first job was in 1994. Then I wrote some things with Fido Net. Fido Net was this early online form thing. Sort of like Used Net / Used Groups (online bulletin web forms) via the telephone dial-up. They were hobbyists running this out from their home. It was basically chat forms. Once you have some experience (doesn’t matter your degree) – it’s...have you done this before? 9:30 – Chuck: This is RIGHT in-line with what I say in my eBook that I am developing now. 10:00 – James: I didn’t even post that I was looking for a job, but I got very lucky. 10:15 – Chuck: What is your journey look like and how did you get into Agile development? 10:30 – James talks about his Kickstarter, knowledge in JavaScript, programming experience, and more here – check it out! 13:16 – Chuck: How did you get to Agile development? 13:31 – James: I was programming throughout my teens. I was working on a really complicated project. I still play Dungeons and Dragons (D&D). It was the most complicated program that I built at that point. I had it in my head and then I didn’t understand it anymore. The program collapsed. To me that was really transformative b/c it’s not writing the algorithms but how it all works together. Then this taught me how to communicate the design to the other members on the team to make it work. 15:50 – James: Have you heard of Rational Rose? You don’t hear about it anymore b/c it was a complete flop. 17:20 – Chuck: Wow! 17:33 – James: It was actually detrimental to get it done. It really was a crisis of faith. I ran into this book: Object Modeling in Color by Peter Coad. Extreme Programming is mentioned, too, by James’ coworker! 21:10 – Chuck: It’s so interesting to me. We focus so much on the technological side, we forget to talk about the people, and the other sides to this. It’s easy to overlook this other stuff. 21:47 – James: There is so much silver bullet thinking within this industry. The original communication from person-to-person is so crucial. It’s so important to software development. Ultimately, the computer doesn’t care, but the collaboration is the real trick and the real challenge. 23:10 – Chuck talks about his brother and his computer science courses experience. 24:27 – James: It could be that 1 team could solve a problem but nowadays it’s working with multiple teams. People want to water things down to help facilitate – but don’t do that. There is a huge large scale Agile that is large interdependent teams. 25:19 – Chuck: MFCEO is a podcast that I am listening to now. He says that nobody wants to sit down and dictate what each member will be responsible for. Chuck reads a quote from an episode from MFCEO – check it out! 26:54 – James: It’s something that people have lost track of. I still program daily even though I do this Agile stuff as well. I have been programming for 25 years and Extreme Programming was the most effective thing for me throughout my career. James: I think XP is the time (now) to have a comeback! 29:41 – Chuck: That was my experience, too. We pushed one team to go to Agile, and then we went to our boss. Chuck: We’d sit down every two weeks and have an Agile-Perspective (what is working and what isn’t working). We are talking about HOW we are writing the software, and that is really what we are after. 30:54 – James: You are building the TEAM that builds the project. Of course, you need to have consistencies across the team, and every team is different b/c every member has different personalities. Mod Programming is we are going to work as a whole group around a screen. Personally, that is not my style but I would TRY it. If it worked for that team then I would do it. 32:00 – Chuck: That is the beauty of it. With this set of programmers x, y, and z may or may not work, and that is O.K. 32:25 – James: I heard about Extreme Programming and I thought it was nuts!! 32:40 – Chuck. 32:44 – James: The more I tried it, and the more it worked. Try Extreme Programming b/c it’s totally a different experience. It’s my book that I wrote 10 years ago but it still is applicable today. Try it for a few months (3 months) or so, b/c it takes time to figure out the different terms and such. Go try out a bunch of new different things, but figuring out HOW to make it work for me. 34:05 – Chuck: Yeah, you need data. Look at the data. Go experiment. 34:47 – James: Try it for real. Check out this essay: “We tried baseball, and it didn’t work.” James: Many things only work in context!  What we do is we change the context in Agile. 35:58 – Chuck: What are you working on now? 36:00 – James: I am actually working on AgileFluency.org. It’s a set of tools for coaches and leaders to CHANGE their context. How can you find those constraints and invest on changing those. 36:31 – Chuck: Where do they go to find you? 36:40 – James: My website - it’s the ugliest website, but it’s been working since 2003. 36:54 – Picks! 37:05 – Fresh Books! END – CacheFly Links: jQuery Angular JavaScript Vue React Slack Zone.js GitHub – Zone.js Chuck’s Twitter Chuck’s E-mail: chuck@devchat.tv Timex Sinclair FidoNet VHDL Book: Java Modeling Color with UML Pivotal Labs Book: The ART OF AGILE DEVELOPMENT BY JAMES SHORE James Shore’s Website Sponsors: Get A Coder Job Fresh Books Cache Fly Picks: Chuck Podcast: MFCEO James Package Management Tool: Nix.org

Today, Phil chats with James Shore. James teaches, writes and consults on Agile development processes. He is a recipient of the Agile Alliance’s Gordon Pask Award for Contributions to Agile Practice, co-creator of the Agile Fluency Model, and co-author of “The Art of Agile Development”. James has also been named as one of “the most influential people in Agile” by InfoQ. KEY TAKEAWAYS: ­­­(0.31) – Phil started by asking James to tell everyone a bit more about himself. James explained that he started his I.T. career as a programmer. In 1999, he was introduced to what was known as Extreme Programming (XP), which is the most prominent of the Agile software development methodologies. At first, James was not convinced, but when he tried it, he was hooked. So much so, that he decided he could not work any other way. At the time, he could not find anybody else working the XP way, so he decided to teach the method himself. That is how he became an Agile consultant. (2.45) – Phil and James discuss the fact that Agile is not new. It has been around for just over 20 years now and the movement is really gathering pace. However, James does point out that “a lot of what people call Agile is not really Agile.” The quality of implementation varies quite a bit. (3.26) – Phil asks James to share a unique IT career tip. James responded by saying you need to “make a point of understanding the business impact of what you're doing." He went on to remind everyone that a typical software team costs circa $1 million to run. A cost that has to be covered by the value the team adds to the business. He highlighted the fact that a 5% improvement in a team’s performance is worth at least $50,000. When you ask for something to improve efficiency remember to make the business case and explain the cost savings clearly. (4.44) – Phil asked James to share a business experience from which he learned something important. For James that happened 20 years ago. At the time he was working for the firm that provided the robots used by Intel to move silicone around on its chip production line. James was part of a team who worked on a distributed system that had multiple services running on different computers. Each service worked in its own environment, but when they hooked it all up the problems began. At the time, the waterfall or phase gate development method was the norm for software development. It was supposed to be a flawless development process. But, in reality, it was not. That project and several others James worked on that followed the standard “waterfall” method were disasters. At that point, James realized the futility of a development method that tried to predict everything in advance, lock things down and come up with the entire design. He also saw how dangerous it was to wait to the very end to validate the work and make the biggest decisions. It was then he understood the flaws of the way development was managed 20 years ago. It was this experience that helped him to recognize the true value of Agile development methods when he was introduced to them. (8.51) – Phil asks what James considered to be his best career moment. James explained that about two years ago he consulted for a start-up that had just gone public and had growing pains. They had 40 teams, so keeping tabs on what they were all doing was impossible. Plus, there was a lot of interdependency between teams, so everything took forever. James discovered that waiting around for another team to do something was causing 95% of the delays. On one project, during a 3-month period, only 3 or 4 days of real work could be done. This stop-start, multitasking way of working, was terrible for focus too. James minimized the teams and got the firm to start by working on the smallest projects that added value, first. These changes minimized the amount of inter-team dependency and got everyone working together and actually delivering working projects fast. He also encouraged teams to solve more of their problems internally. The net result of his changes was that they reduced the delays from 95% to 0%. Most MMFs were completed in just a week or two. The company thrived and grew very quickly. (12.49) – Phil wants to know what excites James about the future for the IT industry. James explains that the fact the industry is so young is exciting because it means change is possible and can happen quickly. Agile is the exact opposite of the Waterfall way of working, yet in less than 20 years people have adopted this new way of working. That is a 180-degree change. In an older industry that just would not happen. In I.T you can suggest new ideas and people will actually be willing to try them.  (15.05) – What is the best career advice you have been given? James responded with three words “be well-rounded”. (15.11) Phil asks if you were to begin your I.T. career again, right now, what would you do? James says that he would focus on networking and finding a mentor. (15.20) – Phil asks James what he is focusing on, right now. James says he is really focused on his business The Agile Fluency project. (15.29) – What is your most important non-technical skill, the one that has helped you the most in your career, so far? James says my “curiosity, flexibility, and a desire and willingness to experiment.” (15.40) – Phil asks James to share a final piece of career advice. James says that if you are working somewhere that does not enable you to do your best work you should try to change that from within. If you discover that is not possible, you need to move on and work for another organization. BEST MOMENTS:  (3.13) - James - “A lot of what people call Agile is not really Agile.” "The actual implementation tends to vary in quality by quite a bit." (3.25) - James - "One of the most valuable things that you can do for your career is to make a point of understanding the business impact of what you're doing." (11.50) - James - "We went from 95% delay for most teams we got it down to zero delays, no delay at all." (12.12) - James - "It's a big cultural mindset change. And making that sort of change requires making sure that everybody's involved and understands how they benefit from this change." (13.15) - James - "Every single company of any size whatsoever needs software. Anybody that's larger than tiny needs custom software." (13.25) - James - "It's a young industry. It's open to new ideas and ways of working." (13.37) - James - "Best practices, at the time, was waterfall, which is basically the exact opposite of agile and now 20 years later, agile has taken over the world." (16.08) - James - "Don't put up with mediocrity. Don't put up with a lousy work environment, just because it's got a great salary."   CONTACT JAMES SHORE:   Linkedin – https://www.linkedin.com/in/james-shore-7475b6/ Twitter – https://twitter.com/jamesshore@jamesshore Website – www.agilefluency.org Personal Website – www.jamesshore.com  

There's no "one right way" to implement Agile. Diana Larsen believes that software is built in the context of a "more diverse and beautiful world" that meets teams where they are and helps them achieve goals that are best for them. Together, with James Shore, she developed the Agile Fluency Model; a framework that helps chart a course for the team, create alignment with management, and secure organizational support for improvement. You can learn more about the model at https://www.agilefluency.org. 

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

Panel: Charles Max Wood Alyssa Nicholl Joe Eames Special Guests: James Shore In this episode, the Adventures in Angular panel talks about Agile Fluency with James Shore. James is one of Charles’ favorite people to talk to about Agile development because he is one of the people who really understands how people work, instead of the methodology proliferation that is more common. They talk about how Agile got started, the Agile Fluency Project, and how Agile has changed over the years. They also touch on TDD, the things people can do to solve the problems with Agile misconceptions, and more! Show Topics: 1:10 – James has been on the shows previously on Ruby Rogues Episode 275 and My Ruby Story Episode 48. 2:00 – He does a lot of work with agile, but actually got started with something called Extreme Programming. 3:14 – When Agile started, it was a reaction to the management belief that the right way to develop software was to hire armies of replaceable programmers and a few architects to design something that was then sent off for these programmers to work. 4:34 – Agile is turning into the “everything” thing. It is being used in many different spaces and leaving developers behind in the process. This goes along with “the law of raspberry jam.” 6:55 – The agile manifesto states that they value “Individuals and interactions over processes and tools.” 7:28 – The Agile Fluency Project is focused on software teams and they created the Agile Fluency Model, which is a way to describe how teams tend to learn Agile over time. They want people to be able to see what all they can really get out of Agile through this project. 10:05 – Alyssa is more confused on the subject of Agile development and is interested more in what people lost by not using Agile anymore. 11:45 – Agile changed from a grassroots movement driven by developers to a management structure that programmers ignore unless it affects their day-to-day. 14:18 – Test driven development is a way of writing your code so that you have confidence to change it in the future not a way you can get unit test code coverage. 17:36 – Joe defines TDD as a way to help him design better code and he finds value in using TDD and then once the code is done, throwing out the test and still find value in it. 19:50 – TDD creates better code by forcing you to think about the client who will be using it and it forces you writing code that is inherently testable, and therefore, better code. 22:22 – The values of Agile development have not been communicated to the programmers who are forced to use it, which accounts for the push back against it. 24:40 – The issue across the board is when people take and idea and think they can read a headline and understand it fully. 28:17 – The way to combat this problem is to dig into some of the things that was happening 15-20 years ago and you can look into DevOps. You can also look into the Agile Fluency Project and the Agile Fluency Model. 31:24 – To get started with talking about how you should do Agile from the trenches, you can look into the books Fearless Change by Mary Lynn Manns and More Fearless Change by Mary Lynn Manns to help you to learn how to make change within your organization. 35:18 – Planting seeds allows you to make change within your organization and make a difference in a small way. 36:10 – The easiest way to remove some of these obstacles is to get together with your team and get them to agree to a trial period. There are more ways as well to get over obstacles. 43:07 – The reason he became an Agile developer is because after his first job working with it, he never wanted to work any way else. So, he decided to start teaching Agile in order to keep working with it in his career. Links: Ruby Rogues Episode 275 My Ruby Story Episode 48 Extreme Programming Agile Fluency Project Agile Fluency Model Smalltalk Best Practice Patterns by Kent Beck Refactoring by Martin Fowler UML Distilled by Martin Fowler Fearless Change by Mary Lynn Manns More Fearless Change by Mary Lynn Manns The Art of Agile Development by James Shore jamesshore.com @jamesshore James’ GitHub Sponsors Angular Boot Camp Digital Ocean Get a Coder Job course Picks: Charles Get a Coder Job Course DevChat Merchandise Code Badges DevChat.tv YouTube Joe Framework Summit Pluralsight James Deliver:Agile Testing Without Mocks: A Pattern Language Jake (build tool) The High-Performance Coach The Expanse by James S. A. Corey

Panel: Charles Max Wood Guest: James Shore This week on My Ruby Story, Charles talks to James Shore about his background, how he got into programming, pitfalls that happened along the way, and his Agile story. James Shore is a thought leader in the Agile software development community. He was an early adopter of Agile development and he continues to lead, teach, write, and consult on Agile development processes. In particular, we dive pretty deep on: James Shore’s background: Consultant, practitioner, and coauthor of “The Art of Agile.” How did you get into programming? Began an interest at 15 years old. How did you go from hobbyist to a professional? Modem background. FidoNet Software and technical design to the agile field. Agile field & development Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb A lot of time we don’t look for these solutions unless we go through the pain. This is so true. In many ways the best learning comes through failure. Design standards. JavaScript If you see a different style – and you can’t get past X, Y, Z – that’s a real sign of immaturity. See past the different styles and find what you could “steal.” Intellectual laziness. Human condition is to not feel inferior. Of course, not every idea is good, but try and see what is the root.  What do you feel like you’ve contributed to the programming industry? And much more! Links: James Shore’s LinkedIn James Shore’s Website James Shore’s Twitter James Shore’s GitHub James Shore’s Book, “The Art of Agile Development...” FreshBooks FidoNet Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb Digital Ocean, LLC JavaScript CacheFly Sponsor: Digital Ocean, LLC Picks: Charles Ready Player One – Movie NG Conf Interviews James Neil Killick Vihart – Mathematics Videos

Panel: Charles Max Wood Guest: James Shore This week on My Ruby Story, Charles talks to James Shore about his background, how he got into programming, pitfalls that happened along the way, and his Agile story. James Shore is a thought leader in the Agile software development community. He was an early adopter of Agile development and he continues to lead, teach, write, and consult on Agile development processes. In particular, we dive pretty deep on: James Shore’s background: Consultant, practitioner, and coauthor of “The Art of Agile.” How did you get into programming? Began an interest at 15 years old. How did you go from hobbyist to a professional? Modem background. FidoNet Software and technical design to the agile field. Agile field & development Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb A lot of time we don’t look for these solutions unless we go through the pain. This is so true. In many ways the best learning comes through failure. Design standards. JavaScript If you see a different style – and you can’t get past X, Y, Z – that’s a real sign of immaturity. See past the different styles and find what you could “steal.” Intellectual laziness. Human condition is to not feel inferior. Of course, not every idea is good, but try and see what is the root.  What do you feel like you’ve contributed to the programming industry? And much more! Links: James Shore’s LinkedIn James Shore’s Website James Shore’s Twitter James Shore’s GitHub James Shore’s Book, “The Art of Agile Development...” FreshBooks FidoNet Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb Digital Ocean, LLC JavaScript CacheFly Sponsor: Digital Ocean, LLC Picks: Charles Ready Player One – Movie NG Conf Interviews James Neil Killick Vihart – Mathematics Videos

Panel: Charles Max Wood Guest: James Shore This week on My Ruby Story, Charles talks to James Shore about his background, how he got into programming, pitfalls that happened along the way, and his Agile story. James Shore is a thought leader in the Agile software development community. He was an early adopter of Agile development and he continues to lead, teach, write, and consult on Agile development processes. In particular, we dive pretty deep on: James Shore’s background: Consultant, practitioner, and coauthor of “The Art of Agile.” How did you get into programming? Began an interest at 15 years old. How did you go from hobbyist to a professional? Modem background. FidoNet Software and technical design to the agile field. Agile field & development Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb A lot of time we don’t look for these solutions unless we go through the pain. This is so true. In many ways the best learning comes through failure. Design standards. JavaScript If you see a different style – and you can’t get past X, Y, Z – that’s a real sign of immaturity. See past the different styles and find what you could “steal.” Intellectual laziness. Human condition is to not feel inferior. Of course, not every idea is good, but try and see what is the root.  What do you feel like you’ve contributed to the programming industry? And much more! Links: James Shore’s LinkedIn James Shore’s Website James Shore’s Twitter James Shore’s GitHub James Shore’s Book, “The Art of Agile Development...” FreshBooks FidoNet Waterfall Rational Rose “UML Distilled” by Martin Fowler “Java Modeling in Color with UML” by Peter Coad WikiWikiWeb Digital Ocean, LLC JavaScript CacheFly Sponsor: Digital Ocean, LLC Picks: Charles Ready Player One – Movie NG Conf Interviews James Neil Killick Vihart – Mathematics Videos

In episode 5 of Troubleshooting Agile we discuss the Third Agile Principle: 'Deliver working software frequently, from a couple of weeks to a couple of months, with a preference to the shorter timescale.' Evolution in our thinking, since the Agile Manifesto was written back in 2001, makes what was once considered 'shorter timescales' seem laughable now, but, when retrospecting, 'working software frequently' remains one of the core agile disciplines. But, as Squirrel and Jeffrey highlight through various client stories, it is far from easy to implement continuously. We hear where, why and how so many companies fail to fully employ this principle, and Squirrel and Jeffrey discuss some interesting techniques to overcome common problems - from slicing up elephant carpaccio to employing continuous integration with nothing more than a rubber chicken. *We apologise for a few sound difficulties at the start of the episode with Jeffrey's mic. Stick with it and they soon pass.* *** Squirrel and Jeffrey have told us which common obstacles they regularly witness that prevent organisations from delivering working software frequently. Now we want to hear from you guys on the matter. You can leave your answers in the comments below, you can email us at agile@troubleshootingagile.com, or you can find a poll on our Twitter feed @TShootingAgile. What are the obstacle for your organisation to delivering working software frequently? 1. The tech team aren't offering to do this, or don't know how. 2. Customers (external or internal or both) don't know it's possible or how to use it if offered. 3. Both 1. and 2. 4. Neither - we already deliver frequently! *** SHOWNOTES: -Agile Manifesto Principles - http://agilemanifesto.org/principles.html -Continuous Delivery, by Jez Humble and David Farley - https://martinfowler.com/books/continuousDelivery.html -Continuous Delivery - https://continuousdelivery.com -CITCON - https://citconf.com -James Shore's blog: "Continuous Integration on a Dollar a Day - http://www.jamesshore.com/Blog/Continuous-Integration-on-a-Dollar-a-Day.html -Alistair Cockburn's blog: "Elephant Carpaccio" - http://alistair.cockburn.us/Elephant+carpaccio *** We'd love to hear any thoughts, ideas or feedback you have regarding the episode (or regarding anything else for that matter). You can email us, here: agile@troubleshootingagile.com Or send us a tweet, here: twitter.com/TShootingAgile Or you can find our website, here: troubleshootingagile.com/ Also, here is a link to our iTunes: itunes.apple.com/gb/podcast/troub…d1327456890?mt=2 If you feel like liking, Sharing and/or Subscribing, we'd really appreciate it.

At Agile 2017 Diana Larsen sat down with Dave Prior to talk about the Agile Fluency model. In this interview she explains what it is (a way of thinking about what benefits an organization needs to get from it’s teams) and how she and James Shore co-founded the Agile Fluency Project with the hope of moving past the question of whether or not a given team, practice, etc. was Agile or not. They wanted to shift the focus to a more positive approach that would help teams develop routine, skillful ease as they move further down the path of adopting agile practices with the ultimate goal of providing enough benefit to the organization so that they, in turn, receive the organizational support for continuous improvement. If you’d like to learn more about Agile Fluency, please check out the following:Your Path through Agile Fluency https://www.martinfowler.com/articles/agileFluency.htmlThe Agile Fluency Project http://agilefluency.orgAnd if you’d like to learn more about Diana Larsen check out:FutureWorks Consulting - https://www.futureworksconsulting.comHer books on Amazon: https://www.amazon.com/Diana-Larsen/e/B002BM7U7QDiana on Twitter: https://twitter.com/DianaOfPortland

SPaMCAST 453 features our interview with James Shore.  We began with a discussion of the Agile Fluency Model, including the concepts and ideas that led to the model and then got into topics such as whether Agile can ever be method agnostic. James’s bio: James Shore teaches, writes, and consults on Agile development processes. He is a recipient of the Agile Alliance's Gordon Pask Award for Contributions to Agile Practice, co-creator of the Agile Fluency™ Model, co-author of /The Art of Agile Development/, and host of “Let's Code: Test-Driven JavaScript.” InfoQ has named him one of the “most influential people in Agile.” You can find his screencasts at letscodejavascript.com, essays at jamesshore.com, and more about the Agile Fluency Project at agilefluency.org. Re-Read Saturday News Today we continue re-reading The Science of Successful Organizational Change led by Steven Adams.  This week Steven addresses the introduction to Part 1 and Chapter 2. In the introduction to Part 1 Gibbon’s tells us that we live in a world of volatility, uncertainty, complexity, and ambiguity (VUCA)  and in Chapter 2 that we have to transition from change fragility to change-agility. Remember to buy your copy.    Previous installments: Week 1: Game Plan Week 2: Introduction    Week 3: Failed Change Week 4:  Introduction to Part 1 and Fragility to Change-Agility A Call To Action We are often asked how listeners can help the Software Process and Measurement Cast.  The simplest and effective way you can help is to give the SPaMCAST a short, honest review in iTunes, Stitcher or wherever you are listening.  If you leave a review, please send a copy to spamcastinfo@gmail.com.  Reviews help guide people to the cast! Next SPaMCAST SPaMCAST 454  will feature our essay and checklists for iteration planning. Starting well and ending well are highly related!  We will also have columns from Gene Hughson (Form Follows Function)  and Jeremy Berriault (QA Corner). Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book here. Available in English and Chinese.

SPaMCAST 452 features our essay on personal process improvement.  We are responsible for our own path in life. Stepping back and reviewing where we are today and where we want to be tomorrow is a form of a retrospective.  Just like any other retrospective, the goal is to change the trajectory of the path you are on.    Kim Pries, the Software Sensei, discusses ethics in software. Ethics guide (or they don’t) practitioners of all types.  Many certification organizations include ethics statements but rarely have the teeth to enforce those ethics.  Kim asks whether this approach makes sense. Anchoring the cast is Jon M Quigley with his Alpha and Omega of Product Development column.  Jon is beginning a three column theme on the impact of people and learning on product development. One of the places you can find Jon is at Value Transformation LLC. Re-Read Saturday News Today we continue re-reading The Science of Successful Organizational Change led by Steven Adams.  THis week we dive into Chapter One titled Failed Change:  The Greatest Preventable Cost to Business?  The frightening part of this chapter is how intimately it resonates based on personal observation. Remember to buy your copy.    Previous installments: Week 1: Game Plan Week 2: Introduction    Week 3: Failed Change A Call To Action You can help share the Software Process and Measurement Cast!  If you even got a single new idea this week while listening to the podcast, please give the SPaMCAST a short, honest review in iTunes, Stitcher or wherever you are listening.  If you leave a review somewhere, please send a copy to spamcastinfo@gmail.com.  Reviews help guide people to the cast! Next SPaMCAST SPaMCAST 453  will feature our interview with James Shore.  We began with a discussion of the Agile Fluency Model, the concepts, and ideas that led to the model and then got into topics such as whether Agile can ever be method agnostic.   Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book here. Available in English and Chinese.

SPaMCAST 450 features our essay on Product Roadmaps.  Roadmaps link an organization’s strategy to action. Product roadmaps are directional and answer the question of where we are going and why. As with any powerful tool, roadmaps giveth when used wisely and taketh away when used less wisely. We also visit with Gene Hughson.  Gene brings his great Form Follows Function blog to the podcast.  We discussed the entry Holistic Architecture – Keeping the Gears Turning.  After you listen to our conversation remember that roadmaps are a way to avoid your products not to resemble a bunch of spare parts flying in close formation. Re-Read Saturday News Today we will begin the next book in the Re-read Saturday Series, The Science of Successful Organizational Change. Steven Adams (SPaMCAST 437, SPaMCAST 412 and nearly every entry in the Re-read Saturday series) will lead this re-read.   Remember to use the link to buy a copy to support the podcast and blog. Steven begins the re-read by describing how he found the Paul Gibbon’s book “The Science of Successful Organizational Change” (get your copy) searching “Agile Change Management” on Amazon.   A Call To Action You can help the podcast. If you even got a single new idea this week while listening to the podcast, please give the SPaMCAST a short, honest review in iTunes, Stitcher or wherever you are listening.  If you leave a review somewhere, please send a copy to spamcastinfo@gmail.com.  Reviews help guide people to the cast! Next SPaMCAST SPaMCAST 451  will feature our interview with James Shore.  We began with a discussion of the Agile Fluency Model, the concepts, and ideas that led to the model and then got into topics such as whether Agile can ever be method agnostic.   Shameless Ad for my book! Mastering Software Project Management: Best Practices, Tools and Techniques co-authored by Murali Chematuri and myself and published by J. Ross Publishing. We have received unsolicited reviews like the following: “This book will prove that software projects should not be a tedious process, for you or your team.” Support SPaMCAST by buying the book here. Available in English and Chinese.

00:30 Introducing Andy Hunt Website Twitter The Pragmatic Bookshelf GROWS Method 5:25 - GROWS Method Dreyfus Model of Skill Acquisition 13:20 - How GROWS solves Agile’s shortcomings 19:50 - GROWS for executives 22:50 - Marketing Ruby Faker Gems Fakercompany.bs 25:30 - GROWS and laying framework for change 29:00 - How empirical is GROWS? 33:35 - How expectations from the Agile Manifesto have changed 36:10 - Prescribing practices that work 40:00 - Getting feedback Burnup and Burndown charts 42:40 - Human limitations 46:00 - Meaning behind GROWS name 50:05 - Knowing when to scale up 53:00 - Agile Fluency Agile Fluency Model by Diana Larson and James Shore 57:30 - The future of GROWS   Picks: Going camping in your front yard (Jessica) California Academy of Sciences in San Francisco (Sam) Exploratorium in San Francisco (Sam) Shoe Dog by Phil Knight (Saron) Espresso Pillows (Saron) “It’s Darkest Before Dawn” DjangoCon 2016 talk by Timothy Allen (Saron) Ruby Book Club Podcast (Saron) Investing in yourself (Andy)

00:30 Introducing Andy Hunt Website Twitter The Pragmatic Bookshelf GROWS Method 5:25 - GROWS Method Dreyfus Model of Skill Acquisition 13:20 - How GROWS solves Agile’s shortcomings 19:50 - GROWS for executives 22:50 - Marketing Ruby Faker Gems Fakercompany.bs 25:30 - GROWS and laying framework for change 29:00 - How empirical is GROWS? 33:35 - How expectations from the Agile Manifesto have changed 36:10 - Prescribing practices that work 40:00 - Getting feedback Burnup and Burndown charts 42:40 - Human limitations 46:00 - Meaning behind GROWS name 50:05 - Knowing when to scale up 53:00 - Agile Fluency Agile Fluency Model by Diana Larson and James Shore 57:30 - The future of GROWS   Picks: Going camping in your front yard (Jessica) California Academy of Sciences in San Francisco (Sam) Exploratorium in San Francisco (Sam) Shoe Dog by Phil Knight (Saron) Espresso Pillows (Saron) “It’s Darkest Before Dawn” DjangoCon 2016 talk by Timothy Allen (Saron) Ruby Book Club Podcast (Saron) Investing in yourself (Andy)

00:30 Introducing Andy Hunt Website Twitter The Pragmatic Bookshelf GROWS Method 5:25 - GROWS Method Dreyfus Model of Skill Acquisition 13:20 - How GROWS solves Agile’s shortcomings 19:50 - GROWS for executives 22:50 - Marketing Ruby Faker Gems Fakercompany.bs 25:30 - GROWS and laying framework for change 29:00 - How empirical is GROWS? 33:35 - How expectations from the Agile Manifesto have changed 36:10 - Prescribing practices that work 40:00 - Getting feedback Burnup and Burndown charts 42:40 - Human limitations 46:00 - Meaning behind GROWS name 50:05 - Knowing when to scale up 53:00 - Agile Fluency Agile Fluency Model by Diana Larson and James Shore 57:30 - The future of GROWS   Picks: Going camping in your front yard (Jessica) California Academy of Sciences in San Francisco (Sam) Exploratorium in San Francisco (Sam) Shoe Dog by Phil Knight (Saron) Espresso Pillows (Saron) “It’s Darkest Before Dawn” DjangoCon 2016 talk by Timothy Allen (Saron) Ruby Book Club Podcast (Saron) Investing in yourself (Andy)

Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)

Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)

Rails Remote Conference 1:20 - Introducing James Shore Github Flow for Javascript Screen cast Email: jshore@jamesshore.com 1:40 - Freelancing and Consulting 5:20- Co-opting Agile and the movement away from technology/software Agile Alliance Technical Conference Agile Fluency Model 16:20- Evolutionary Design in Agile Ron Jeffries Sudoku Think Like A Git code visualization built with Gource 24:15 - Evolutionary Design for Beginners James Shore - Evolutionary Design Illustrated Stack Overflow 32:30 - Technical Practices and Agile Architecture Procrastinate on Purpose by Rory Vaden 39:10 - Engineering on a Team Level “No Silver Bullet” by Fred Brooks James Shore - Rethinking Scaling 52:10 - Redesigning Team Responsibilities Joy, Inc by Richard Sheridan Picks Sandi Metz “The Wrong Abstraction” blog post (Sam) Why Are Computers podcast by Tom Stewart (Sam) Netstat (Jess) Wood Badge (Charles) Remember the Titans (Charles) Rick Sheridan’s Agile India talk (James) Liftoff by Diana Larsen and Ainsley Nies (James)

In this week's podcast Richard Seroter talks to James Shore, author of The Art of Agile Development and one of the original signatories of the Agile Manifesto. Also on the podcast are Llewellyn Falco, creator of the open source testing tool ApprovalTests and co-founder of Teaching Kids Programming, and Rebecca Wirfs-Brock, inventor of Responsibility-Driven Design, as well as the author of books including Designing Object: Oriented Software and Object Design: Roles, Responsibilities and Collaborations. Why listen to this podcast: - A lot of people know how to do TDD and refactoring for the back end, but not for the font, but the basics are the same. - The basics of Test-Driven Development are the same for the front or back end. - If you don't know what's wrong, you don't know how to fix it. - The most common code smells, according to Llewellyn Falco: Clutter, long lines, long methods, duplication, and inconsistency. - How do we make, in an agile way, the architectural work visible, and not ignore it? - How do you have an incremental architecture and get measurements? If I say to you I'm going to go away for six months and figure it out, that's not very measurable. Notes and links can be found on InfoQ: http://bit.ly/1Pse2r1 1m:10s - The talk 'Agile Engineering for the Web' was about how do you bring typical Agile engineering ideas like TDD and refactoring to the front-end languages. 1m:33s - A lot of people know how to do these things on the back-end, but when you get to the front end a lot of people just throw up their hands. 2m:24s - I see CSS bugs all the time, because it's very hard to refactor CSS without breaking something. Quick scan our curated show notes on InfoQ. http://bit.ly/1Pse2r1 You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. http://bit.ly/24x3IVq

Craig and Tony at the Agile Australia conference sit down with James Shore, best known as for his work as author of “The Art of Agile Development” and co-creator of the Agile Fluency Model and talk about a wide range of Agile topics including: “Java Modeling in Color with UML” book mentioned Feature Driven Development (an Australian … Continue reading →

I detta avsnitt behandlas Agile Fluency Model, en modell som Diana Larsen och James Shore hittat på för att beskriva en grupps färdigheter inom mjukvaruutveckling. Ola och Tobias pratar om själva modellen och nyttan med den. Det blir såklart en inzoomning och två kortkommandon.Modellen finns beskriven här: http://martinfowler.com/articles/agileFluency.htmlNågra hållpunkter:3:30 Tobbe sålde sin bil till…4:30 …och Ola har bott granne med…7:50 Projektledarna får en släng av sleven… igen16:50 Vad är affärsvärdet i att kunna logga in?19:25 Dags att leverera värde23:00 Ola lär oss hemligheterna i dubbel i badminton35:10 Vi tänker på segelbåtar41:50 Ola skämtar för döva öron

E chega o mais novo episódio do nosso podcast!!! Nesta edição falamos um pouco dos eventos que a equipe da TTLabs participou, tais como BrazilJS, Agile Brazil 2012, RS on Rails 2012 entre outros. Então não perca mais tempo e curta abaixo o nosso podcast! Abaixo segue o link dos eventos mencionados no nosso podcast: GUTS Grupo no google-groups: https://groups.google.com/d/forum/guts-rs-sucesu Blog http://guts-rs.blogspot.com.br/ Post sobre o GUTS 20 minutes no blog: http://guts-rs.blogspot.com.br/2012/08/sobre-o-evento-guts-rs-20-minutes.html IASA Grupo no google-groups: https://groups.google.com/d/forum/iasaportoalegre Site da Zenvia: http://www.zenvia.com.br/ Sobre ECA: http://en.wikipedia.org/wiki/Event_condition_action Seminário PMI Site: http://www.seminario.pmirs.org.br/site/home Sobre Lean: http://en.wikipedia.org/wiki/Lean_manufacturing Site do Almyr Klink: http://www.amyrklink.com.br/ BrazilJS Site: http://braziljs.com.br/ Site do @BrendanEich: https://brendaneich.com/ Site do @cowboy: http://benalman.com/ Site do GruntJS: http://gruntjs.com/ Site do @fat: http://byfat.xxx/ Sobre twitter-bootstrap: http://twitter.github.com/bootstrap/ Site do @firt: http://firt.mobi/ Site do @maujor: http://www.maujor.com/ Site do @bernarddeluna: http://bernarddeluna.com/ Startup Dev Rumble Site: http://startupdev.com.br/rumble/pt/ Facebook do Cardapiaria: https://www.facebook.com/Cardapiaria Site RubyOnRails: http://rubyonrails.org/ Site jQuery Mobile: http://jquerymobile.com/ AgileBrazil Site: http://www.agilebrazil.com/2012/ Site da InfoQ: http://www.infoq.com/br Sobre Cecilia Fernandes: http://www.caelum.com.br/instrutores/cecilia-fernandes/ Site do James Shore: http://jamesshore.com/ Livro "The Art of Agile Development": http://bit.ly/PFZ5za Sobre Slack: http://bit.ly/xWCAqz RSOnRails Site: http://rsonrails.com.br/ Startup Dojo Grupo no facebook: https://www.facebook.com/groups/319499808099995/ Sobre Business Canvas: http://www.businessmodelgeneration.com/canvas NoSummit Site: http://nosummit.com/ Post sobre o NoSummit do @dwildt: http://bit.ly/RSn6Bn Twitter do Manoel Pimentel: https://twitter.com/manoelp GUDAY Inscrições: http://www.sucesurs.org.br/eventos/guday/inscricao DevRS.Net Site do evento: http://www.sucesurs.org.br/evento/1o-evento-devrs-net-sucesu-rs

I speak with Diana Larsen and James Shore at the Agile 2012 conference about their recently released Agile Fluency model.  This model looks at team and organizational Agile adoption and provides a framework for looking at where you are and where you want to be. The article is here: http://martinfowler.com/articles/agileFluency.html Comments and input can be given at: http://jamesshore.com/Blog/Your-Path-Through-Agile-Fluency.html http://www.futureworksconsulting.com/blog/2012/08/08/your-path-through-agile-fluency-a-brief-guide-to-success-with-agile/ As usual I loved talking with both of them again and hope you will enjoy listening to their conversation with me. Bob Payne

You may have heard the terms "Fit" and "Fitnesse" bandied about by the software engineering literati. What are they? Are they useful? Are they used at all? Does your testing strategy need some fitnesse? The creator of Fit and the coordinator of the Fit project chat with Scott and answer the hard questions.

I spoke with James Shore about his new book.  I have not yet read it but enjoyed the sample chapter that was provided int the packet.My guess is that it will make it onto my permanent bookshelf.Enjoy-bob payne

James Shore is working on CardMeeting.com.  I love this tool.  I think it has a lot of great potential.  I generally do not like online planning tools since they usually need to be single threaded and do not feel right.  People at a table are better but ......  if you are not in the same room .... Go to the site with several people on different computers and have a blast.-bob