Podcasts about agile fluency model

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

BONUS: Leading Without Blame, Building Resilient Teams with Tricia Broderick and Diana Larsen In this BONUS episode, leadership experts Tricia Broderick and Diana Larsen explore their latest book, Lead Without Blame, talking about how leaders can create high-performing teams without resorting to blaming. This conversation tackles the key themes from their book, and offers insights on how leaders can foster resilient, learning-focused teams. Understanding "Lead Without Blame" "Leadership isn't about finger-pointing; it's about creating an environment where learning and growth can flourish." Tricia and Diana kick off the conversation by breaking down what it means to lead without blame. They explore the impact of blame in the workplace, particularly how it stifles innovation, and erodes psychological safety. The authors stress the importance of making space for learning and acknowledge that many leaders, even unintentionally, perpetuate a culture of blame. "To lead without blame, focus on building a culture where learning is prioritized over finger-pointing." The Inspiration Behind the Book "Blame has always been a leadership issue, and this book was a way to address it head-on." Tricia and Diana share personal anecdotes that inspired the book. Tricia describes writing the book as therapeutic, reflecting on her past experiences as an executive who lacked the skills to prevent a blame culture. Diana highlights how pervasive blame is in toxic work environments and the urgent need for a shift in leadership approaches to create healthier, more supportive workplaces. "Our goal is to equip leaders with the tools they need to create environments where everyone can thrive without the fear of blame." From Knowledge Work to Learning Work "Learning is the evolution of knowledge work, and it's the foundation of resilient teams." The authors discuss the shift from traditional knowledge work to what they call "learning work." They explain that building resilient teams requires fostering an environment where continuous learning is encouraged and natural. Leaders must embrace the idea that learning is an ongoing process, crucial for adapting to changes like remote work and other modern challenges. "To build resilient teams, leaders must prioritize creating a learning environment where everyone is prepared to adapt and grow." The 4Cs of Learning Leaders "Courage, Compassion, Confidence, and Complexity—these are the pillars of effective leadership in today's world." Tricia and Diana introduce the "4Cs" of Learning Leaders—Courage, Compassion, Confidence, and Complexity. They emphasize that leadership is not just about hierarchical authority but about modeling these qualities at all levels within a team. Leaders must navigate uncertainty and complexity with confidence, showing their teams how to do the same. "True leadership is about embodying the 4Cs—showing courage, compassion, confidence, and understanding complexity in every situation." Leadership Through Learning "Leaders must exemplify the learning process, guiding their teams through growth and change." The authors explore the concept of "Leadership through Learning," where leaders actively engage in and model the learning process. They discuss essential motivators like shared purpose, autonomy, and co-intelligence, which are crucial for fostering a collaborative and innovative team environment. "Leadership through learning means being intentional about creating a space where your team can grow together." The Five Rules for Accelerated Learning In their book, Tricia and Diana outline "Five Rules for Accelerated Learning" that are essential for leaders looking to cultivate high-performing teams. These rules guide leaders in creating environments where learning is continuous, rapid, and deeply integrated into the team's daily work. "Accelerated learning happens when leaders set the right conditions and provide clear, actionable guidance." Managing Conflict with the Escalating Conflict Model "Healthy conflict is a sign of engagement, but it's crucial to recognize when it starts to become destructive." The authors discuss the "Escalating Conflict Model", which helps leaders identify and manage conflict stages within their teams. The model emphasizes recognizing when conflicts move from healthy disagreements to destructive behaviors and provides strategies for keeping conflicts constructive and focused on team goals. "Understanding the stages of conflict helps leaders intervene early and keep team dynamics positive." Maximizing Learning and Adaptation through Retrospectives "Retrospectives are not just about looking back—they're about learning and adapting for the future." Tricia and Diana highlight the importance of retrospectives in team development, emphasizing that these sessions are critical for continuous learning and adaptation. They offer practical advice on how leaders can conduct effective retrospectives that focus on purpose-relevant topics and foster a culture of open, constructive dialogue. "Use retrospectives as a tool to reinforce your team's shared goals and drive continuous improvement." Learn More About the Book The book is Lead Without Blame by Tricia Broderick and Diana Larsen. You can learn more about the book and access additional resources at leadwithoutblame.com. Tricia: Ignite Insight + Innovation Diana: Diana Larsen Both: LinkedIn profiles About Tricia Broderick And Diana Larsen Tricia Broderick, co-author of Lead Without Blame, is a leadership and organizational advisor with over twenty-five years of experience. Her transformational leadership ignites the growth of leaders and resilient high-performing teams to deliver quality outcomes. She is a highly-rated trainer, coach, facilitator, and motivational keynote speaker. In 2020, she founded Ignite Insight + Innovation. You can link with Tricia Broderick on LinkedIn or visit Tricia's website. Diana Larsen is a leadership and team improvement advisor, offering consulting and mentoring services. A sought-after keynote speaker, she has co-authored several books on Agile leadership and co-originated the Agile Fluency® Model. Her book Agile Retrospectives is one of the most mentioned works on this podcast, with the 2nd edition set to release in early 2024. You can link with Diana Larsen on LinkedIn or visit Diana's website.

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!

Dans cet épisode Nous voyons un modèle d'évolution agile et ses quatre niveaux de maîtrise.00:30 - Introduction03:04 - La focalisation06:18 - La livraison08:46 - L'optimisation10:46 - Le renforcement12:05 - L'Agile Fluency Model et les cadres de travail13:25 - ConclusionNotesLe site web officiel du Agile Fluency modelhttps://www.agilefluency.org/Le ebook en françaishttps://www.agilefluency.org/perch/resources/downloads/agile-fluency-french-version.pdfL'article de Martin Fowlerhttps://www.martinfowler.com/articles/agileFluency.htmlÀ proposJe suis Denis St-Michel, passionné d'agilité depuis 2006. Je possède les certifications PAL, PSM II, PSPO II, PSD et CSSCWB. Je rends les équipes hautement performantes et j'accrois la valeur des produits numériques.Rejoignez-moiSur LinkedIn - https://linkedin.com/in/dstmichelPar courriel - stmichel.denis@gmail.comLa page LinkedIn d'Agilibriumhttps://www.linkedin.com/company/agilibriumMusique originale"Folle", une création personnelle que vous pouvez retrouver sur mon album "Underscore", disponible sur Spotify et Apple Music.Spotify https://open.spotify.com/album/4sfnhseocnThIDf9hOFDUn?si=rVBt3wb7TmSj79bubv8W7A

  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!  

Taler du egentlig agilsk? Og taler i den samme agile dialekt i jeres organisation – ellers misforstår i måske hinanden og hvad det er i gerne vil have ud af jeres agile forandring? Lyt med i dette afsnit hvor vi sammen med Daniel Frøkiær udforsker ”The Agile Fluency Model” der kan hjælpe os med at have nogle helt centrale dialoger om hvad vi ønsker at få ud af vores agile transformation og samtidig styre uden om de mange spørgsmål om hvordan Scrum, Scrum @ Scale eller Spotify skal fungere i jeres organisation. Check: https://www.agilefluency.org/

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.

Braucht Agilität Manager? Tobias "Toby" Baier ist ein solcher - und seit vielen Jahren mit Agilität in Kontakt. Er spricht mit uns über die Rolle einer Führungskraft bei Adobe und seinen persönlichen Lebensweg. Tobias ist ein leidenschaftlicher Verfechter der kontinuierlichen Verbesserung. Leistungsstarke Teams müssen in der Lage sein, sich schnell an Learnings und veränderte Rahmenbedingungen anzupassen. Den höchsten Wert für Kunden zu liefern, muss nachhaltig sein.

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/.

By: Dr. Dave Cornelius You are the co-creator of Agile Retrospective with Esther Derby and now co-founder of the Agile Fluency Model, what are a few fun-facts that you would like to share about yourself? Fun Facts? Perhaps some folks don’t know that I call myself @DianaOfPortland on Twitter for a few reasons. Though I… The post EAFH-32: Diana Larsen, what is going on with Social Justice in Portland, Oregon? appeared first on Leaders share how-to practices - KnolShare with Dr. Dave Podcast on GrokShare.com.

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

This month on the Cucumber Podcast we welcome Diana Larsen a world-renown author, speaker and co-founder of The Agile Fluency Model. Show notes: - CukenFest Remote - June 3rd-4th -https://cukenfest.cucumber.io/ - Agile Fluency - https://www.agilefluency.org/ - Upcoming events - https://www.agilefluency.org/workshops.php - Virtual Open North America - https://www.eventbrite.com/e/virtual-open-north-america-tickets-101659959676 - Books - https://leanpub.com/u/dianalarsenauthor

In this podcast recorded at Agile 2019, Shane Hastie, Lead Editor for Culture & Methods, spoke to Diana Larsen about the origins of what became agile development, where business agility is header and the agile fluency project . Why listen to this podcast: • There is a deep history of business improvement initiatives that predates the agile manifesto • It was a part of a cultural movement that was moving more toward more humane workplaces that could deliver more value • When you give people a good environment and good support to do their work, you get better work and better products • The ideas of business agility predate the work in agile development – engaging support structures in organisations to enable change • You can't change one part of a system without it having effects on other parts of the system • The Agile Fluency Model is a tool to help teams diagnose themselves and to expose the system to leadership More on this: Quick scan our curated show notes on InfoQ https://bit.ly/3acIJwf You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/3acIJwf

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.

In this episode, Ahmed Avais discusses the Agile Fluency Model. He shares what it is, how to use it, and where to go to get more information about it. Here are some of the resources Ahmed recommends https://www.agilefluency.org/ and https://martinfowler.com/articles/agileFluency.html Connect with Ahmed on LinkedIn https://www.linkedin.com/in/ahmedavais --- Support this podcast: https://anchor.fm/tom-henricksen/support

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

In this podcast Shane Hastie, Lead Editor for Culture & Methods, spoke to Steve Holyer about collaboration, culture and teams, and the state of the Agile Fluency projects. Why listen to this podcast: • Diverse lived experiences make people better individuals and team members • How important psychological safety is for teams • We all have unconscious biases and our language reflects this • The value in the Agile Fluency Model is the outcomes we can produce by using it • The Agile Fluency Model helps teams and organisations figure out how to identify value and prioritize work • The product owner as the facilitator of conversations so the shared understanding of value can emerge More on this: Quick scan our curated show notes on InfoQ https://bit.ly/2jUipyu You can also subscribe to the InfoQ newsletter to receive weekly updates on the hottest topics from professional software development. bit.ly/24x3IVq Subscribe: www.youtube.com/infoq Like InfoQ on Facebook: bit.ly/2jmlyG8 Follow on Twitter: twitter.com/InfoQ Follow on LinkedIn: www.linkedin.com/company/infoq Check the landing page on InfoQ: https://bit.ly/2jUipyu

Denna vecka blir det lite annorlunda. Vi kommer istället för att släppa ett långt avsnitt på fredag, släppa fem kortare avsnitt under flera dagar. Avsnitten spelades in inför en levande publik bestående av utvecklare och chefer på Sveriges Radio.I detta första avsnitt pratar vi Agile Fluency Model som vi tidigare tagit upp i avsnitt 7. Sen dess har modellen ändrats något och mer om detta hör du i detta avsnitt.

At the Agile Professional Learning Network - Chicago Chapter's 2017 conference, and I had the opportunity to talk with about the Agile Fluency Project. Ahmed had almost literally just finished his presentation on the Agile Fluency Model when Paul sat him down and asked him about it. Ahmed told Paul about the 4 zones of Fluency Focus on Value Deliver Value Optimize Value Optimize for Systems The Agile Fluency is different than Maturity Models in that one team cannot be compared to another (therefor weaponizing the model) Ahmed also explains Fluency through the Tarzan example. Tarzan matured relative to his environment - swinging on vines hanging from trees, etc. But, his language fluency never quite developed, and his vocabulary very limited - “Me Tarzan. You Jane.” With a larger vocabulary and more practice at speaking to other humans, Tarzan has a chance to communicate with humans. Without the necessary practice he will either continue at his current fluency level, or his fluency could even diminish. You can catch up with Paul Madison on Twitter at @ You can catch up with Ahmed Avais on Twitter at @

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)

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 →

Hosts Ryan Ripley, Tim Ottinger, Don Gray Discussion Ryan Ripley (@RyanRipley) Tim Ottinger (@tottinge) and Don Gray (@donaldegray) got together to talk about the word “enterprise”. Quite a few connotations were thrown around: inertia, masses of people, waterfall. Better, Faster, Cheaper was even discussed. We moved on to talking about the limitations imposed on scaling by Dunbar's Number (150) and then learned about the Rule of the 2nd Floor: “Nobody 2 levels above or below you in the organization really understands what you do for a living.” The discussion then shifted to how we can do Agile with 5,000 people. Typical scaling patterns emerged: Scale by Division:  Dividing people in to functional teams. Scale Out, Not Up:  Group people in to feature teams. Holocracy:  Peer to peer organization. Using Extreme Programming (XP) and other disciplined software engineering practices to improve team outcome were discussed as was an organizationals ability to move up the Agile Fluency Model. We talked about Mike Cottmeyer's recent post about stopping the anti-management rhetoric and finding ways to meet management where they are and help them find the path to an agile organization. The discussion then shifted to how teams can measure their agility and the renaissance of craftsmanship in the software development world. Don walked us through transformation management theory, we asked why organizations should even go “agile” in the first place, and worked on a definition of “agile” in the enterprise. And then…we called it a night. Agile for Humans is brought to you by audible.com – get one FREE audiobook download and 30 day free trial at www.audibletrial.com/agile Resources, Plugs, and More Ryan – https://ryanripley.com Nature of Software Development by Ron Jeffries Holocracy by Brian Robertson Name Calling and Ad Hominem Attacks by Mike Cottmeyer Dan Greening's Agile Base Patterns Tim – http://agileotter.blogspot.com/ Industrial Logic Blog Agile by Example Don – http://donaldegray.com The Art of Thought by Graham Wallas Managing Transitions by William Bridges Jerry Weinberg books on lean pub The Future of Organizations The post AFH 015: The USS Agile Enterprise [PODCAST] appeared first on Ryan Ripley.See omnystudio.com/listener for privacy information.

In our journey to help create "more productive, humane, sustainable work places", we in the Agile community often have a tendency to look for a one-size-fits-all solution. But Agile transformations are as unique as the snowflakes requiring them. Diana Larsen's Agile Fluency model, which the industry veteran and pioneer discussed with us at Agile2015, offers a range of possible ways of operating to suit client and even practitioner needs.But first she wanted to clear up a common misconception: The Agile Fluency model isn't a maturity model. Diana shared. "It's a best-fit model... Getting to the end of the scale isn't necessarily the right place to be." The Agile Fluency model, then, can be thought of as having four bus zones: you have to go through each zone to get to subsequent zones -- but Zone 1 may be the best place for you to be, in which case you get off the bus and thrive there. The Agile Fluency model aims to help organizations identify the benefits and tradeoffs they are willing to make and then help them locate the zone in the model that maps best to the identified criteria.

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