Podcasts about software delivery

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereDaniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & AssociatesJulian Wood - Serverless Developer Advocate at AWSRESOURCESDanielhttps://bsky.app/profile/tastapod.comhttps://www.linkedin.com/in/tastapodhttps://github.com/tastapodhttps://mastodon.social/@tastapodhttp://dannorth.net/blogJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodhttps://s12d.com/gotoDESCRIPTIONDaniel Terhorst-North and Julian Wood share decades of experience to offer a nuanced view of programming, governance, and product delivery. By framing programming as a socio-technical activity, they emphasize the critical role of collaboration, feedback, and sustainable practices.The conversation challenges traditional governance models, advocating for hypothesis-driven product management and continuous feedback mechanisms. Through humorous anecdotes and hard-won wisdom, Terhorst-North inspires people to look beyond technical expertise to the broader ecosystem of teams, culture, and organizational alignment. [...]RECOMMENDED BOOKSJez Humble & David Farley • Continuous DeliveryNicole Forsgren, Jez Humble & Gene Kim • AccelerateKim, Humble, Debois, Willis & Forsgren • The DevOps HandbookJez Humble, Joanne Molesky & Barry O'Reilly • Lean EnterpriseHeidi Helfand • Dynamic ReteamingHeidi Helfand • How to Change Your TeamsCarl Larson & Frank M J LaFasto • TeamworkGene Kim & Steve Spear • Wiring the Winning OrganizationMatthew Skelton & Manuel Pais • Team TopologiesBlueskyTwitterInstagramLinkedInFacebookCHANNEL MEMBERSHIP BONUSJoin this channel to get early access to videos & other perks:https://www.youtube.com/channel/UCs_tLP3AiwYKwdUHpltJPuA/joinLooking for a unique learning experience?Attend the next GOTO conference near you! Get your ticket: gotopia.techSUBSCRIBE TO OUR YOUTUBE CHANNEL - new videos posted daily!

(06:49) Brought to you by Lemon.io⁠Lemon.io⁠ is your go-to platform for hiring top-tier, pre-vetted software engineers from Europe and Latin America. You'll get matched with your developer in just 48 hours.Tech Lead Journal listeners get 15% off your first 4 weeks of work at ⁠lemon.io⁠.Want to learn the key principles and future of DevOps that can help you ship code faster and more reliably?In this episode, I sit down with Yevgeniy Brikman, co-founder of Gruntwork and author of “Terraform: Up & Running,” to discuss his upcoming book, “The Fundamentals of DevOps and Software Delivery.”We explore:- Common pitfalls and anti-patterns in DevOps implementations- The concept of “minimum effective dose” and "incrementalism" in adopting technologies- Why application developers should understand infrastructure and software delivery- The future of DevOps, including “infrastructureless” and the impact of GenAI- The importance of “secure-by-default” practices in modern software development- Recent changes in open source licensing and their impact on the tech industry- The power of continuous learning and sharing knowledge in tech careersListen out for:(00:02:15) Career Turning Points(00:08:32) Deliberate Time for Learning(00:16:27) Transitioning from App Dev to Infra (00:24:19) Understanding How to Deliver Software(00:32:05) Minimum Effective Dose(00:40:34) DevOps Antipatterns(00:44:02) Incrementalism(00:49:37) The Future of DevOps and Software Delivery(01:10:39) Recent Trend in Open Source License Changes(01:20:32) 3 Tech Lead Wisdom_____Yevgeniy Brikman's BioYevgeniy (Jim) Brikman loves programming, writing, speaking, traveling, and lifting heavy things. He does not love talking about himself in the 3rd person. He is the co-founder of Gruntwork, a company that offers products & services for setting up world-class DevOps Foundations. He's also the author of three books published by O'Reilly Media: Fundamentals of DevOps and Software Delivery, Terraform: Up & Running, and Hello, Startup. Previously, he spent more than a decade building infrastructure and products that served hundreds of millions of users while working as a software engineer at LinkedIn, TripAdvisor, Cisco Systems, and Thomson Financial.Follow Yevgeniy: LinkedIn – linkedin.com/in/jbrikman X / Twitter – @brikis98 Website – ybrikman.com

In this episode of Game Changers for Government Contractors, host Michael LeJeune dives into the innovative concept of Continuous Authority to Operate (CATO) with Bryon Kroger, founder of Rise8. Bryon explains how CATO enables faster, more secure software delivery, aligning with modern DevOps practices while ensuring compliance with NIST RMF standards. Learn how this approach transforms the traditional ATO process, the benefits for government contractors and end users, and the critical role of collaboration between developers, assessors, and end-users. Bryon also shares actionable strategies for implementing CATO, overcoming challenges, and scaling operations. Whether you're navigating compliance or looking to improve your software delivery speed, this episode is packed with valuable insights to help you succeed in the GovCon space. ----- Frustrated with your government contracting journey? Join our group coaching community here: federal-access.com/gamechangers Grab my #1 bestselling book, "I'm New to Government Contract. Where Should I Start?" Here: amzn.to/4c5Vb0d

Small Batches will return in 2025. Until then, I recommend checking out the Complexity Lounge on YouTube, hosted by my friend Jocko Selberg. ★ Support this podcast on Patreon ★

In this episode, Adam reads haikus from The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book.Want more?

In this episode, Adam reads book four in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features koans from the fabled zen Master Lan-Hsi.Want more?

Send us a textWhy do even successful agile teams struggle to maintain their improvement momentum?In this compelling episode, Peter Maddison and David Sharrock answer this question and challenge the myth that continuous improvement is "just a mindset." Drawing from both scientific research and hands-on experience, they reveal why sustaining improvement is physically and mentally taxing, and why the journey becomes increasingly difficult after the initial quick wins. Through insights from sports coaching and real-world software delivery, they offer a fresh perspective on making continuous improvement truly sustainable.This week´s takeaways: Continuous Improvement Needs Constant NurturingSmall Steps Lead to Big ChangesMake Progress Visible and Achievable Want more practical insights on scaling agile and DevOps practices? Join Peter and Dave as they unpack the complexities of modern software delivery and organizational transformation. Subscribe to Definitely Maybe Agile wherever you get your podcasts, and share your thoughts at feedback@definitelymaybeagile.com.

In this episode, Adam reads book three in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features analects from the fabled zen Master Rinzai.Want more?

In this episode, Adam reads book two in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features folktales from the fabled zen Master Noa-Op.Want more?

In this episode, Adam reads book two in The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. This episode features chronicles from the fabled zen Master Ninjei.Want more?

In this episode, Adam reads the preface, forward, and introduction to The Zen of Programming (1988) by Geoffrey James. This book is unlike any programming book you've encountered. So, let's try something new for the podcast to showcase this poignant, accurate, and funny book. Want more?

In this episode, Adam welcomes Dan Slimmon, an experienced Site Reliability Engineer (SRE) to discuss aspects of incident response and troubleshooting in software engineering. Dan explains his methodology for clinical troubleshooting, the importance of maintaining a common mental model, and techniques for leading effective incident response efforts. They also delve into the value of continuous ops reviews and ongoing mental model updates to prevent issues, emphasizing the need for structured processes and effective communication.Want more?

In this episode of Small Batches, host Adam Hawkins welcomes Alex Nesbitt, a strategy expert and member of the Flow Collective, to delve into the nuances of strategic thinking. The discussion covers different types of strategies, pro-tips on strategic thinking, and how strategy relates to the concept of flight levels. Nesbitt shares insights from his extensive consulting career, touching on topics like identifying leverage points, the relationship between strategy and tactics, and why being strategic is often more critical than having a strategy. The episode also stresses the importance of having a clear vision, enabling organizational constraints, and the roles of resilience and maintenance in strategic planning. Alex mentions practical examples, resources, and tips to help software and business leaders enhance their strategic approach.Want more?

Adam discusses strategy in preparation for the next episode.Want more?

Adam discusses three (new-ish) ideas from time on a new gemba. Want more?

Adam describes using Hexagonal Architecture, also known as Ports and Adapters, for software delivery excellence.Want more?

In this episode we dive into the exciting release of Elixir 1.17.0-rc.1 and other news from the community. Our main segment features an in-depth interview with Ellie Fairholm and Josep Giralt D'Lacoste about their new Elixir book "Engineering Elixir Applications - Navigate Each Stage of Software Delivery with Confidence." We explore their professional experiences, the concept of "BeamOps," and the unique DevOps challenges and advantages in the BEAM ecosystem. Ellie and Josep share insights about the writing process, their collaboration, and what's next for the book. Tune in to hear all this and more! Show Notes online - http://podcast.thinkingelixir.com/206 (http://podcast.thinkingelixir.com/206) Elixir Community News - https://x.com/josevalim/status/1797607009715691637 (https://x.com/josevalim/status/1797607009715691637?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim announces the release of Elixir 1.17.0-rc.1. - https://hexdocs.pm/elixir/1.17/gradual-set-theoretic-types.html (https://hexdocs.pm/elixir/1.17/gradual-set-theoretic-types.html?utm_source=thinkingelixir&utm_medium=shownotes) – Introduction to gradual set-theoretic types in Elixir 1.17. - https://github.com/elixir-lang/elixir/blob/v1.17/CHANGELOG.md (https://github.com/elixir-lang/elixir/blob/v1.17/CHANGELOG.md?utm_source=thinkingelixir&utm_medium=shownotes) – Detailed changelog of Elixir 1.17.0-rc.1. - Added mix profile.tprof profiler in Erlang/OTP 27+ and Deprecated mix profile.cprof and mix profile.eprof. - https://2024.elixirconf.com/ (https://2024.elixirconf.com/?utm_source=thinkingelixir&utm_medium=shownotes) – Information about ElixirConfUS 2024, including keynotes, speakers, and training. - David speaking on “Dancing with Data, Guide to ETLs” at ElixirConfUS 2024. - Mark speaking on “Elixir & AI - Creating Autonomous Agents with LangChain” at ElixirConfUS 2024. - https://dashbit.co/blog/elixir-ml-s1-2024-mlir-arrow-instructor (https://dashbit.co/blog/elixir-ml-s1-2024-mlir-arrow-instructor?utm_source=thinkingelixir&utm_medium=shownotes) – José Valim's post on the Dashbit blog discussing the state of ML in Elixir in 2024. - https://mlir.llvm.org/ (https://mlir.llvm.org/?utm_source=thinkingelixir&utm_medium=shownotes) – Introduction of MLIR (Multi-Level Intermediate Representation) in Elixir's ML projects. - Broader ML/AI community and new projects in Elixir, including instructor_ex and Elixir LangChain. - https://x.com/germsvel/status/1796127412511551857 (https://x.com/germsvel/status/1796127412511551857?utm_source=thinkingelixir&utm_medium=shownotes) – German Velasco's video showcasing new OTP 27 process labels feature. - https://www.youtube.com/watch?v=XNQhDl4a9Ko (https://www.youtube.com/watch?v=XNQhDl4a9Ko?utm_source=thinkingelixir&utm_medium=shownotes) – Google algorithm leak exposed through a GitHub project explained using Elixir. - https://x.com/akoutmos/status/1796637514704273870 (https://x.com/akoutmos/status/1796637514704273870?utm_source=thinkingelixir&utm_medium=shownotes) – Akoutmos discusses the Google algorithm leak and its analysis using Elixir. - https://hexdocs.pm/googleapicontent_warehouse/api-reference.html (https://hexdocs.pm/google_api_content_warehouse/api-reference.html?utm_source=thinkingelixir&utm_medium=shownotes) – Hexdocs publish the Google algorithm API reference. - https://ipullrank.com/google-algo-leak (https://ipullrank.com/google-algo-leak?utm_source=thinkingelixir&utm_medium=shownotes) – Analysis of Google's algorithm leak and relevancy to Elixir. - https://x.com/PJUllrich/status/1796198764681506898 (https://x.com/PJUllrich/status/1796198764681506898?utm_source=thinkingelixir&utm_medium=shownotes) – Introducing Crawly, an application framework for web crawling and data extraction. - https://github.com/elixir-crawly/crawly (https://github.com/elixir-crawly/crawly?utm_source=thinkingelixir&utm_medium=shownotes) – GitHub repository for the Crawly web crawling framework. Do you have some Elixir news to share? Tell us at @ThinkingElixir (https://twitter.com/ThinkingElixir) or email at show@thinkingelixir.com (mailto:show@thinkingelixir.com) Discussion Resources - https://pragprog.com/titles/beamops/engineering-elixir-applications/ (https://pragprog.com/titles/beamops/engineering-elixir-applications/?utm_source=thinkingelixir&utm_medium=shownotes) – PragProg book listing - https://twitter.com/pragprog/status/1779253657097117890 (https://twitter.com/pragprog/status/1779253657097117890?utm_source=thinkingelixir&utm_medium=shownotes) - https://twitter.com/sm_debenedetto/status/1779558393373409481 (https://twitter.com/sm_debenedetto/status/1779558393373409481?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.hashicorp.com/ (https://www.hashicorp.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://www.erlang-solutions.com/ (https://www.erlang-solutions.com/?utm_source=thinkingelixir&utm_medium=shownotes) - https://opentofu.org/ (https://opentofu.org/?utm_source=thinkingelixir&utm_medium=shownotes) - https://xkcd.com/927/ (https://xkcd.com/927/?utm_source=thinkingelixir&utm_medium=shownotes) - https://en.wikipedia.org/wiki/Blue%E2%80%93green_deployment (https://en.wikipedia.org/wiki/Blue%E2%80%93green_deployment?utm_source=thinkingelixir&utm_medium=shownotes) - https://docs.docker.com/engine/swarm/ (https://docs.docker.com/engine/swarm/?utm_source=thinkingelixir&utm_medium=shownotes) Find us online - Message the show - @ThinkingElixir (https://twitter.com/ThinkingElixir) - Message the show on Fediverse - @ThinkingElixir@genserver.social (https://genserver.social/ThinkingElixir) - Email the show - show@thinkingelixir.com (mailto:show@thinkingelixir.com) - Mark Ericksen - @brainlid (https://twitter.com/brainlid) - Mark Ericksen on Fediverse - @brainlid@genserver.social (https://genserver.social/brainlid) - David Bernheisel - @bernheisel (https://twitter.com/bernheisel) - David Bernheisel on Fediverse - @dbern@genserver.social (https://genserver.social/dbern) - Dave Lucia - @davydog187 (https://twitter.com/davydog187)

Adam welcomes Steve Pereira and Andrew Davis to discuss their new book, Flow Engineering. They discuss the book's origin story and the use of cybernetics to drive effective action.Want more?

Welcome back to another episode of Building Better Developers. Today, we're tackling an issue that every developer faces at some point: panic during software delivery. Whether it's a critical bug or a new feature that isn't functioning as expected, panic can strike anytime your software fails in the hands of a user. Rob and Michael cover handling software delivery panic with practical tips and real-life examples. Listen to the Podcast on Handling Software Delivery Panic The Inevitable Bug: Why Panic Happens Delivering software is a delicate process. Even when you've thoroughly tested your code and believe it to be bulletproof, something can always go wrong. Often, the panic ensues because: Unexpected User Behavior: Users may interact with the software in ways you didn't anticipate. This is particularly common in beta tests or early releases where feedback is crucial. Overlooked Bugs: Some users have a knack for breaking things. These users often find bugs that slipped through your QA processes. Critical Stakeholders: When a manager, CEO, or client encounters a problem, the stakes feel much higher. Their frustration can quickly escalate to panic. Real-Life Panic: A Case Study on Handling Software Delivery Panic Recently, Rob faced this scenario with a technically knowledgeable customer. Despite understanding the development process, the customer encountered a show-stopping bug in an alpha version. Their immediate reaction was that the project was nowhere near completion, creating a sense of panic. During our call, he expressed concerns that none of the features seemed to work. He acknowledged that bugs and design flaws were expected at this stage, but the issue was so severe that it led to a dramatic loss of confidence in the project. Handling Software Delivery Panic Step 1: Stay Calm and Analyze The first and most crucial step when faced with panic is to stay calm. Take a deep breath and focus on understanding the situation: Reproduce the Issue: Identify the user's steps to encounter the bug. Sometimes, it's as simple as a permission issue or an unanticipated input. Prioritize Fixes: Address the most critical issues first, especially those that block user progress. Step 2: Effective Communication Reassure the stakeholders that you're on top of the situation: Acknowledge the Problem: Validate their concerns and show you understand the impact. Outline the Next Steps: Explain how you plan to fix the issue and provide a realistic timeline. Step 3: Learn and Improve Use this experience to strengthen your development and testing processes: Enhance Testing: Incorporate the steps that led to the bug into your testing scenarios. Automated tests can help catch these issues earlier. Add Logging: Improve logging to gather more information if a similar problem arises in the future. Real-Life Tips from Experience Michael shares an insightful story about a shared work experience. Despite rigorous testing, their boss would find bugs within minutes of a release. This constant scrutiny drove home the importance of thorough testing and the psychological pressure of delivering seemingly flawless code. One key takeaway from Michael's story is the value of Test-Driven Development (TDD). By writing tests before the actual code, you ensure that each function meets the specified requirements. This approach not only catches potential issues early but also clarifies the expected behavior for each part of your application. Practical Advice for Developers Before starting on a new feature or bug fix, consider the following: Clarify Requirements: Ensure you have detailed requirements, including user input constraints and expected outputs. Define Acceptance Criteria: Clearly outline what constitutes a successful implementation. Implement Robust Logging: Log critical operations to simplify debugging and provide insights into any issues that arise. Using Static Code Analysis Tools To Handling Software Delivery Panic SonarQube SonarQube Is a code quality assurance tool that performs in-depth code analysis and generates an analysis report to ensure code reliability. Language Support: Java, JavaScript, C#, PHP, Python, C++, and more. Features: Provides comprehensive code quality and security analysis, integrates with CI/CD pipelines, and offers detailed reports. Strengths: Strong community support, extensive plugin ecosystem, and good integration with various development tools. ESLint ESLint statically analyzes your code to quickly find problems. It is built into most text editors and you can run ESLint as part of your continuous integration pipeline. Language Support: JavaScript, TypeScript. Features: Identifies and reports on patterns in JavaScript, customizable rules, and integration with most text editors and build systems. Strengths: Highly customizable, large number of plugins, and widely used in the JavaScript community. PMD PMD is an extensible multilanguage static code analyzer. It finds common programming flaws like unused variables, empty catch blocks, unnecessary object creation, etc. Language Support: Java, JavaScript, Salesforce Apex, PLSQL, XML, XSL. Features: Detects common coding issues like bugs, unused variables, and performance bottlenecks. Strengths: Simple rule configuration, supports multiple languages, and can be integrated into build tools like Maven and Gradle. PyLint Pylint is a static code analyser for Python 2 or 3. The latest version supports Python 3.8.0 and above. Pylint analyses your code without actually running it. It checks for errors, enforces a coding standard, looks for code smells, and can make suggestions about how the code could be refactored. Language Support: Python. Features: Checks for coding standards, errors, and code smells, provides suggestions for code improvements. Strengths: Highly configurable, integrates well with IDEs and CI/CD pipelines, and widely used in the Python community. Final Thoughts on Handling Software Delivery Panic Panic during software delivery is unavoidable, but it's manageable. By staying calm, communicating effectively, and learning from each incident, you can turn these challenging moments into opportunities for improvement. Remember, every bug is a lesson in disguise, pushing you toward becoming a better developer. That's it for today's episode. We hope these insights help you handle panic more effectively and continue building better software. Until next time, keep calm and code on! Stay Connected: Join the Developreneur Community We invite you to join our community and share your coding journey with us. Whether you're a seasoned developer or just starting, there's always room to learn and grow together. Contact us at info@develpreneur.com with your questions, feedback, or suggestions for future episodes. Together, let's continue exploring the exciting world of software development. Additional Resources Code Refactoring: Maintaining Clean, Efficient Code Deciphering Code Chaos: Strategies for Writing Maintainable Code Test-Driven Development – A Better Object Oriented Design Approach Behind the Scenes Podcast Video

Adam presents the mental model behind T1 and T2 signals, a necessary lexicon for understanding production operations.Want more?

Adam answers a listener's request of advice on succeeding in high-level company or project environments with seven tips.Want more?

This week, Bonnie is joined by Bryon Kroger, founder and CEO of Rise8, about the pivotal role of software in government and military operations. Bryon shares his insights on the challenges of bridging the gap between acquisitions and operations, the importance of continuous software delivery, and the ethos of fostering a culture of outcomes over outputs. Drawing on the lessons learned from the creation of Kessel Run and his subsequent venture, Rise8, Bryon outlines a new paradigm for agile, user-focused software development and systems integration in the federal space. TIMESTAMPS: (1:37) Bryon's first experience with deadly software (3:59) How Kessel Run changes the game in software delivery (6:07) The secret to continuous software delivery (14:46) Why Bryon founded Rise8 (19:53) Reimagining requirements & user engagement (22:34) How output and behavior impact mission (33:49) Challenge bureaucracy, innovate, and don't feel powerless LINKS: Follow Bryon: https://www.linkedin.com/in/bryon-kroger/ Follow Bonnie: https://www.linkedin.com/in/bonnie-evangelista-520747231/ CDAO: https://www.ai.mil/ Tradewinds AI: https://www.tradewindai.com/ Rise8: https://www.rise8.us/

Adam presents TDD as skill zero, the one that unlocks all the others.Want more?

Adam presents a catch-all episode on ops reviews, visual management, call-to-actions, and SLOs.Want more?

AI in der Software-Delivery: Unsere größte Möglichkeit oder purer Hype? - Ein RealitätscheckGenerative AI ist in der Software-Entwicklung allgegenwärtig. Mit Co-Pilot stellt GitHub den Platzhirsch im Bereich Codegenerierung und bewirbt es mit einer 55% Produktivitätssteigerung. Bei solchen Effekten dreht jedes C-Level-Management am Rad. Doch was ist dran am Hype? Sollten wir wirklich alle so aufgeregt sein?Zu dieser Frage bzw. zu einem Realitätscheck sprechen wir mit Birgitta Böckeler, Global Lead for AI-assisted Software Delivery bei Thoughtworks. Sie beschäftigt sich u.a. damit, wozu Generative AI in der Softwareentwicklung genutzt werden kann, welche Einsatzbereiche neben der Codegenerierung existieren, für welche Bereiche Coding Assistenten gut und für welche nicht so gut sind funktionieren aber auch welchen Effekt die ganze AI-Bewegung auf den ganzen Softwareentwicklungsprozess hat.Bonus: Ein Kampf zwischen AI-Fans und Skeptiker**** Diese Episode wird gesponsert von der IU Internationale HochschuleFür dich ist Bildung wichtig und du glaubst an Technologie als Enabler? Kannst du dich mit der Mission der IU “Educate People with the Best Technology" identifizieren?Dann schau doch mal unter https://engineeringkiosk.dev/iu1, wenn du die Bildung von morgen gestalten willst.********Das schnelle Feedback zur Episode:

Dave Mangot returns to discuss his new book "DevOps Patterns for Private Equity". Don't let the title fool you, this is best introduction to DevOps and many related software delivery topics. Buy this book for anyone in leadership.Want more?

Connect with Elias Nogueira: https://linkedin.com/in/eliasnogueira https://eliasnogueira.com https://twitter.com/eliasnogueira Full episode on YouTube ▶️ https://youtu.be/jUQcq8NLxDk Beyond Coding Podcast with ⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠⁠

Adam presents visual management using simple blue, yellow, and black color grading. This is an essential episode.Want more?

On this week's episode, host Conor Bronsdon is joined by Jason Krohn, Global Head of Delivery at Syngenta. Jason delves into how his teams at Syngenta leverage software engineering intelligence to achieve predictable delivery at scale. Jason also explores how aligning work with employees' passions contributes to success and retention at Syngenta. He discusses the challenges and solutions in implementing efficient DevOps processes and ensuring organizational buy-in for the vision. Additionally, Jason highlights the importance of empowering teams with autonomy and providing the necessary tools for proactive decision-making.Whether you're leading a small team or managing an enterprise, Jason's insights offer valuable lessons on driving efficiency, scaling effectively, and fostering a culture of continuous improvement.Episode Highlights: 1:46 Scaling teams that are empowered and autonomous 4:01: The four pillars for retaining talent in tech teams.12:51 Tackling organizational change 18:41 Using metrics to achieve predictable delivery 21:45 Why your engineering teams' need to care about metrics, not just be compliant 26:20 Addressing production delays and DevOps integration28:55 Leadership's role in communicating the 'why'33:05 The Importance of Coaching When Mentoring Show Notes:SyngentaJason KrohnSupport the show: Subscribe to our Substack Leave us a review Subscribe on YouTube Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Get your DORA Metrics free forever

Adam presents a series of questions to understand production operations, plus a method to practice: MMIVM. That's Model-Measure-Instrument-Visualize-Monitor.Want more?

Adam's welcomes Katie Anderson to the show to discuss her book Learning to Lead, Leading to Learn, lean thinking, and the powerful growth mindset.Want more?

Adam's two most common words (verbal ticks even) from 2023. Is it a party foul to bring lean thinking into a New Year's Eve party?Want more?

Adam welcomes John Willis to discuss his new book, Deming's Journey to Profound Knowledge. We discuss why John wrote the book, Deming's career arc, and how we put Deming's ideas into action. The print edition is available now. Listen through to the end for announcements from Adam and John.Want more? ★ Support this podcast on Patreon ★

Adam presents the ideas in Wiring the Winning Organization with a vignette from his time on gemba. Plus, a giveaway!Here's how to win a FREE copy of Wiring the Winning Organization. First, follow me on LinkedIn. Second, post a link to Small Batches podcast episode with what you learned using the #SmallBatchesGiveaway hashtag. The giveaway runs through January 2024. The winner will be announced on February 1st. You can enter as many times as you like.Want more?

Twelve tips for first-time engineering managers. Bonus Tip!

ONUS: Rethinking Agile Roles and Structures, With Craig Smith and Michael Huynh   In this episode, we kick things off by revisiting a captivating talk delivered by Michael and Craig at the Agile Online Summit 2023. The duo urged us to reevaluate the roles of the Scrum Master and Product Owner, and even hinted at potential shifts within Agile organizations. This discussion sparked a larger contemplation in my mind, extending beyond the core arguments presented by Michael and Craig. I took to Twitter to ponder the possibility of Agile serving as a foundational change in how we perceive organizational structures and leadership, leading to a potential revolution. What might this mean for you and your organization? Rethinking Agile Roles Before delving into what the future might hold for Agile practitioners, we asked Craig and Michael to provide a concise summary of their main points from the talk. They urged us to go beyond following “agile dogma” Questioning the purpose of Scrum Master and Product Owner roles Refocus on value generation in Agile practices The need for systemic thinking In this episode, we also explore how it's not just Agile roles, but leaders at various levels, that have strayed from the essence of what Agile truly stands for. CTOs and Chief Product Owners find themselves ensnared in a rigid adherence to processes as well, even when those processes go against their stated intent of adopting Agile. Are Agile Roles Overhead? Craig and Michael raise critical questions about Agile roles, challenging their perceived value and longevity within organizations. Is there a risk of losing sight of the original intent behind roles like Scrum Master and Product Owner? Are these positions temporary or do they inadvertently add another layer of complexity? The conversation als touches on the heart of Agile transformation: business agility. How can organizations efficiently deliver value to the market? There's concern that leaders have become disconnected from the actual work done by their teams. The very essence of leadership may be at risk of being diluted or misunderstood. Leadership in Software Organizations: A Glimpse into the Future In this segment, we discuss the Culture, Structure and Process aspects that we need to take into account to keep our organizations truly Agile, no matter what roles we end up having.  Culture: Shaping Behaviors for Success The importance of culture in shaping organizational behavior cannot be overstated. Leaders must adapt to the unique cultures of their organizations, whether they're fast-moving and less structured or operate within a different paradigm. Structure: Redefining Hierarchies In a rapidly evolving technological landscape, do we need traditional hierarchies? Leaders must understand the core of their businesses and ensure they are moving in the right direction, but do they require the conventional structures that have become commonplace? Process: The Evolution Beyond Projects The notion of projects may be antiquated for software businesses. Start-stop methodologies may no longer align with the dynamic nature of the industry. The changes needed pose a significant challenge to the Agile community. Join the Scrum Master Community For those eager to continue the conversation, we invite you to connect with the vibrant Scrum Master community, get your membership here. About Craig Smith and Michael Huynh Craig Smith is a Business Agility Product Lead at SoftEd, and a veteran Agile Practitioner, Coach, and Trainer with 20+ years of experience. He co-hosts "The Agile Revolution" podcast, and is a driving force in the Agile community. Craig excels in Agile training, coaching, and fostering technical excellence, advocating for quality-driven change. You can link with Craig Smith on LinkedIn.    Michael Huynh is a seasoned agile coach and trainer, recognized for guiding organizations in successful agile adoption. With SoftEd, he collaborates with leaders and teams to foster efficient delivery and swift decision-making. Michael's extensive expertise spans Lean, SDLC, XP, SAFe, Scrum, Kanban, and more, enabling him to tailor approaches for each organization's success. As a dedicated contributor to the agile community, he leads and speaks at international conferences. You can link with Michael Huynh on LinkedIn.

Tyler Sweatt, CEO of Second Front Systems | Defense Tech: Transforming Government Software Delivery Join us in the BreakLine Arena for a conversation with Tyler Sweatt, CEO of Second Front Systems, a software startup building the first of its kind DevSecOps platform that accelerates delivery of commercial technology to U.S. warfighters and national security professionals.Tyler shares what drew him to the defense tech space, ositions in the tech industry that are well aligned to veteran skill sets, and how Second Front is “the lattice that stitches the defense tech revolution together.” He talks about the importance of mission when it comes to attracting talent into the space, the value of building a team that is both intellectually and experientially diverse, and his advice for tech companies looking to create what he calls a “human capital flywheel.”“If you're creating space as a leader to enable good ideas, new expectations, and new ways of doing [things] to come up and ultimately get operationalized or institutionalized, that's a human capital flywheel that's pretty magical.”Please like, rate, subscribe, or review our show if you've liked what you've heard! We'd love to hear your thoughts. If you're interested in joining our community, please visit www.breakline.org. If you're interested in exploring partnerships with BreakLine, please visit https://breakline.org/partners/partner-signup/.

Interview with Yaron Perlman, author of the book DevStreams: Scaling Software Delivery. Naturally. He talks about the main ideas of DevStreams - a new paradigm for scaling software delivery. Sign up to the Level-up Engineering newsletter!In this interview we're covering:Defining DevStreamsMain ideas of the book DevStreamsDevStream's impactWhat type of companies benefit most from DevStreamsImplementing DevStreams Common objections regarding DevStreamsExcerpt from the interview:"After publishing the book, some VPs told me they liked the concept, but didn't find it realistic to have streams where everyone does everything proficiently. My answer is, how do you know? Have you tried it?When you start experimenting with the paradigm, you'll see that it's not that far-fetched. Especially with today's technological advancements in AI, it's easier to pick up new skills than it was a year ago. We have so many tools available to make our work more effective, and our technology landscape is changing rapidly that it really merits a new paradigm. "

Welcome to another episode of Category Visionaries — the show that explores GTM stories from tech's most innovative B2B founders. In today's episode, we're speaking with Ori Keren, CEO & Co-Founder of LinearB, a software delivery management solution that's raised over $70 Million in funding. Here are the most interesting points from our conversation: Dual Mandate for Engineering Leaders: LinearB focuses on helping engineering leaders master both operational efficiency and business alignment, a dual mandate critical for modern engineering teams. From Concept to Growth: Ori shared the journey from founding LinearB in 2019 to achieving significant growth, including a 6x revenue increase in 2021 and a 3x increase in 2022. Product Transformation and PLG Motion: In 2020, LinearB transformed its product and go-to-market strategy by adopting a product-led growth (PLG) approach, offering value to both engineering leaders and developers. Investment in Content Marketing: LinearB's podcast, Dev Interrupted, played a crucial role in educating the market and sharing their philosophy on software delivery management, contributing to their early success. Customer-Centric Metrics: Ori emphasized the importance of improving internal engineering metrics, such as reducing cycle time from nine days to less than two, showcasing the value LinearB brings to its users. Vision for the Future: Ori envisions LinearB becoming the orchestrator of the entire software delivery process, integrating with CI, CD, and feature flag vendors to streamline the journey from code to production. //   Sponsors: Front Lines — We help B2B tech companies launch, manage, and grow podcasts that drive demand, awareness, and thought leadership. www.FrontLines.io The Global Talent Co. — We help tech startups find, vet, hire, pay, and retain amazing marketing talent that costs 50-70% less than the US & Europe. www.GlobalTalent.co

AI-assisted software delivery refers to the utilization of artificial intelligence to assist, enhance, or automate various phases of the software development lifecycle. AI can be used in numerous aspects of software development, from requirements gathering to code generation to testing and monitoring. The overarching aim is to streamline software delivery, reduce errors and, ideally, reduce The post AI for Software Delivery with Birgitta Böckeler appeared first on Software Engineering Daily.

AI-assisted software delivery refers to the utilization of artificial intelligence to assist, enhance, or automate various phases of the software development lifecycle. AI can be used in numerous aspects of software development, from requirements gathering to code generation to testing and monitoring. The overarching aim is to streamline software delivery, reduce errors and, ideally, reduce The post AI for Software Delivery with Birgitta Böckeler appeared first on Software Engineering Daily.

Adam presents thinking about boundaries, testing, and software design.Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

Adam presents how he thinks about estimates and delivery. Plus, a special announcement on something new!Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

Adam presents mental model behind lean and agile. The mental model accepts we don't know the path forward, thus we must optimize for learning it.Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

Adam presents the rationale behind choosing a language or tech stack. Spoiler alert: it's irrelevant to software delivery performance. Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

Adam presents thoughts on Sidney Dekker's book "Drift into Failure".  Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

Adam revisits the historic Agile Manifesto.Are you just beginning your path to excellence? Then start here.Already on the path? Continue your self-study with any of these:

If you are building a product for developers, but aren't asking them for feedback via an open source option, you're missing out on some reliable data. It can help to not only improve what you're building, but also garner some goodwill among a community of people who are invested in what you're doing. This week, Faith talks to the CMO at Harness, Scott Sanchez, about how Open Source and AI have helped to deliver a better CI/CD delivery system.https://www.harness.io/ Hosted on Acast. See acast.com/privacy for more information.

Jon Smart, author of the book Sooner Safer Happier: Patterns and Antipatterns for Business Agility, discusses patterns and anti-patterns for the success of enterprise software projects. Host Brijesh Ammanath speaks with him about the various common...