Podcasts about team topologies

Hoje o papo é sobre topologia de times e o impacto da IA nas organizações! Neste episódio, conversamos com Manuel Pais, coautor do livro Team Topologies, sobre como os times continuam sendo uma peça central para a entrega de valor, mesmo em um cenário de agentes de IA, automação, organizações mais enxutas e novas formas de trabalho. Vem ver quem participou desse papo: Paulo Silveira, o host que arredonda para cima Vinny Neves, cohost, dev e professor na Alura Manuel Pais, coautor do livro Team Topologies Mauricio Aniche, CTO da Alura  Links:  Livro Team Topologies Banco do Brasil Digital Week  Lei de Conway Paulo Silveira Comenta: Da Hierarquia à Inteligência, de Jack Dorsey – Hipsters Ponto Tech #514 Livro Sooner Safer Happier Vá para o Vale do Silício com Paulo Silveira, Marcell Almeida, Fabrício Carraro e Marcus Mendes na “Imersão IA Sob Controle e Alura no Vale do Silício“! Vagas limitadas, corra para reservar a sua. TechGuide.sh, um mapeamento das principais tecnologias demandadas pelo mercado para diferentes carreiras, com nossas sugestões e opiniões. #7DaysOfCode: Coloque em prática os seus conhecimentos de programação em desafios diários e gratuitos. Acesse https://7daysofcode.io/ Produção e conteúdo: Alura Cursos de Tecnologia – https://www.alura.com.br Edição e sonorização: Rede Gigahertz de Podcasts

BONUS: The Communication Tax — Why Your Team Collaborates Too Much and What to Cut First In this BONUS episode, Roman Nikolaev challenges one of the most deeply held beliefs in the agile world: that more collaboration is always better. As Head of Technology at Cambri, Roman has watched teams burn their best hours in meetings and handoffs that create the feeling of productivity without the outcomes. He shares practical tools — from the vacation test to RFC processes — that help teams find the minimum viable level of collaboration. From Senior Engineer to Accidental Manager "I kind of accidentally ended up in management. I didn't want to lead anyone, I wanted to be just a senior engineer doing my stuff. But somehow, four months in the job, I was already leading a team, and then one year after, I was head of technology."   Roman's career in engineering goes back to the early 2000s. When he changed jobs during COVID, he specifically didn't want a management role — he wanted to code. But within months he was leading a team, and within a year he was running the entire technical organization at Cambri. That unexpected shift from hands-on engineering to leading teams gave him a front-row seat to how collaboration actually works — and how often it doesn't. What he noticed was that the most important differentiator for technical teams isn't technical knowledge — it's communication, and the tax you pay when communication goes wrong. The Communication Tax Is Real "The communication tax is real. The less we need to pay for communication, the more we can concentrate and own things end to end."   Roman describes a pattern most teams will recognize: stakeholders inside and outside the team — product managers, QA, scrum masters, product owners — and at some point, it becomes a game of telephone. The people doing the actual work don't have the context they need. The result? Unnecessary features, wrong implementations, suboptimal technical solutions that don't scale. His argument isn't that collaboration is bad. It's that every handoff, every meeting, every "quick sync" has a cost — and most teams aren't honest about how much they're paying. Handoffs Aren't Collaboration "If you look at a typical software development lifecycle — a ticket created by a product owner, refinement with the team, development, code review, QA, acceptance — there are quite many handoffs. If we can reduce some of this, we get a more effective workflow."   Roman walks through the standard ticket lifecycle and counts the handoffs: PO creates ticket, team refines, developer picks it up, code review with other developers, QA phase, acceptance phase. Each transition is a potential information loss. His provocation: instead of involving more people when someone struggles with a task, give the person working on it the tools and knowledge to complete it independently. The trigger for his thinking was a real team conversation where someone suggested everyone should "jump on the ticket" to help. Roman's response: wouldn't it be better to equip the individual rather than create more dependencies? Async Tools That Actually Work "Instead of gathering a meeting where people come unprepared or with some raw ideas, we have ownership for a task. Someone takes their time, writes down their thoughts, options in a document, and then we assign people to review it."   Roman shares two async practices his teams use at Cambri. First, the RFC (Request for Comments) process on Confluence — one person owns a decision, writes it up with options, and assigned reviewers sign off asynchronously. It turns out to be more effective at finding better technical solutions while spreading knowledge without requiring synchronous deep-dives. Second, his Monday written updates: every week, he spends about 90 minutes writing a detailed post covering all project statuses, what happened last week, what's coming, and business context. The team feedback in skip-level meetings is consistently positive, and he fields far fewer questions about business context and priorities than before the practice started. The Vacation Test "One heuristic would be that if one of the team members goes on vacation, the rest of the team can continue working on their task."   Roman learned this the hard way. He went on a typical Finnish one-month vacation. Before leaving, he explained the architecture and intent for a key task to his team. He came back to discover they'd built the completely wrong thing — wasting one month of a two-month project. He spent the remaining time working weekends, on planes, on trains, just to hit the deadline. The lesson wasn't that he needed more collaboration or synchronous communication before leaving. It was that he needed better communication — and a way to test whether shared context actually exists. His heuristic: if Alice goes on vacation, can Bob continue from where she stopped? If not, you don't need more meetings. You need better async context-sharing. Where to Start: Ownership First, Then Cut Meetings "I would probably first look into if a particular initiative, a feature, or some kind of process has an owner and well-defined roles. Usually, if there is no clear owner, that leads to a lot of synchronous meetings."   For Scrum Masters and team leads looking for a practical starting point, Roman offers a two-step approach. First, ensure every initiative, feature, and process has a clear owner with well-defined roles. Without clear ownership, meetings multiply because nobody is sure who's responsible, so everyone attends everything. Second, look at the team calendar starting with the biggest meetings and ask: can this be an RFC? A message? An email? Then experiment — cancel a meeting, replace it with an async channel, and see what happens. You can always bring it back. In the agile world, Roman argues, we should embrace experimentation with our own processes, not just our products. Recommended Resources Roman recommends Team Topologies by Matthew Skelton and Manuel Pais. The book gave him a clear mental model for independent teams that own their area end to end — teams aligned to value streams that own the customer problem completely. For more of Roman's thinking on collaboration, check out his Substack newsletter: Is Your Collaboration Good or Evil? on High Impact Engineering. About Roman Nikolaev Roman Nikolaev is Head of Technology at Cambri. He's spent his career thinking about how teams actually get work done — and his contrarian view that most teams collaborate too much has sparked real debate in the agile community.   You can link with Roman Nikolaev on LinkedIn.

Como criar estruturas que realmente aceleram a entrega de valor? Neste episódio do Love the Problem, Rafaela Fonseca recebe Lucas Freitas e Raphael Montenegro para continuar a conversa sobre organizações orientadas a valor e explorar um tema que gera muitas dúvidas nas empresas: a diferença entre estrutura organizacional, estrutura operacional e topologia. Ao longo da conversa, eles discutem por que mudar apenas o organograma raramente resolve os desafios de execução, como identificar gargalos relacionados a dependências, comunicação e tomada de decisão, e quais mecanismos ajudam a melhorar o fluxo de trabalho sem criar mudanças desnecessárias. O episódio também aborda modelos como Flight Levels, Unfix, Org Topologies e Team Topologies. Eles exploram, além da diferença entre modelos, o papel da governança e da coordenação entre times e as diferentes estratégias para evoluir modelos operacionais de forma sustentável. Se você quer destravar a burocracia e evoluir estruturas de gestão para que elas potencializam os resultados, solta o play e vem com a gente!

Состояние DevOps в 2026: Platform Engineering, AI-агенты и что стало с junior-инженерами. Собрались на кухне с тимлидом системного юнита из большой компании - поговорить что и как сейча. О ЧЁМ ВЫПУСК • DevOps vs SRE в 2026: где проходит граница и почему «you build it, you run it» иногда создаёт больше проблем, чем решает. • War story: упавший Kubernetes во время корпоратива с пивом - классика первых K8s-внедрений. • Момент, когда DevOps ломается: 600 сервисов, 3600 пайплайнов и почему каждый новый инженер пишет 3601-й. • Platform Engineering: зачем нужна платформа, что такое метаплатформы и как устроены слои внутри крупной компании. • Junior + AI = middle: что изменилось с приходом AI-ассистентов и сколько теперь занимает обучение DevOps. • AI в работе DevOps прямо сейчас: мультиагентные помощники для расследования инцидентов, внутренние vs внешние модели. • Реальные AI-катастрофы 2025-2026: Replit дропнул базу и бэкапы, сервис аренды машин ушатал прод. • Multi-agent flow: refiner + архитектор + автономный бот, PR за час вместо недели. • Тимлидам: не носи инженерам PR, которые ты навайпкодил за вечер. • Что реально учить в 2026: Linux, сеть, Kubernetes, один язык программирования и AI-грамотность. • Знать базу vs спрашивать AI: почему без фундамента ты не поймёшь, куда тебя модель направляет. ГОСТЬ В гостях - Андрей Волхонский, руководитель юнита System в Центре разработки инфраструктуры Авито. 13+ лет опыта: от Windows-DevOps в TravelLine и Kaspersky до платформенной инженерии в большой продуктовой компании. ССЫЛКИ

This conversation was recorded at GOTO Copenhagen 2025.https://gotopia.techMarko Klemetti - CTO of EficodeKris Jenkins - Lifelong Computer Geek and Podcast HostORIGINAL TALK TITLERewriting the SDLC Playbook with GenAI: How To Build a GenAI-Augmented Software Organization?RESOURCESMarkohttps://bsky.app/profile/mrako.comhttps://twitter.com/mrakohttps://github.com/mrakohttps://www.linkedin.com/in/mrakohttps://mrako.comKrishttps://bsky.app/profile/krisajenkins.bsky.socialhttps://twitter.com/krisajenkinshttps://www.linkedin.com/in/krisjenkinshttps://github.com/krisajenkinshttp://blog.jenkster.comABSTRACTSpeakers interview each other on topics that matter to them.Expect the unexpected. [...]Read the full abstract here:https://gotocph.com/2025/sessions/3931RECOMMENDED BOOKSMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQForsgren, Humble & Kim • Accelerate: The Science of Lean Software and DevOps • https://amzn.to/3tCz1xOJohn Arundel & Justin Domingus • Cloud Native DevOps with Kubernetes • https://amzn.to/3hKZvI5Wynne, Hellesoy & Tooke • The Cucumber Book • https://amzn.to/3tEUINJSol Rashidi • Your AI Survival Guide • https://amzn.to/3UFYnKCDavid Foster • Generative Deep Learning • https://amzn.to/48ZgP4xPhil Winder • Reinforcement Learning • https://amzn.to/3t1S1VZBlueskyInstagramLinkedInFacebookCHANNEL 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!

Stop burning time and money on agile theater! In this podcast, Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel strip business agility back to its absolute basics: no buzzwords, no frameworks - just the organizational muscles you need to survive. Listen or watch as we introduce and explain the five non-negotiable capabilities: Sensing and Responding (market feedback loops), Speed to Decision Making (decision velocity), Structural Flexibility (reorganizing without chaos), Distributed Authority (decentralizing command and control), and Learning Orientation (continuous evolution).Then stick around as we tear down the agile industrial complex, discuss why one study claims 47% of companies are operating purely under an "illusion" of agility, and discuss how the introduction of AI can amplify and exposes company's bureaucracy.Other topics we discuss are:• How to explain business agility to anyone from CEO to new hire• Why "scaling" agility is a big lie sold to enterprises• Typical bottlenecks to the five core capabilities• Why vanity metrics sabotage competitive advantages• Time to market, cost of delay, customer adoption, and much more...Whether you're in product management, leadership, agile coaching, or team development, this episode helps you truly understand business agility and can give you the confidence to push back or ask critical questions when teams and leadership claim they don't need help.#BusinessAgility #ProductManagement #AgileLeadership["Extreme Ownership by Jocko Willink and Leif Babin", "Team Topologies by Matthew Skelton and Manuel Pais", "Turn the Ship Around by L David Marquet", "The Fearless Organization by Amy Edmondson", "The Lean Startup by Eric Ries", "BCG Study: Why Companies Get Agile Right and Wrong (2024)", "Business Agility Institute 2025 Report", "Organizational Agility: Ill-defined and Somewhat Confusing by Anna Teresa Walter (2020)", "John Boyd's OODA Loop", "Jeff Bezos's One-Way Door vs Two-Way Door Decisions", "Block (Jack Dorsey)", "Arguing Agile Episode 83: Agile Doesn't Work Here"]LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Iryna Stelmakh: When Communication Clarity Matters More Than Technical Complexity, A Healthcare Project That Fell Apart Read the full Show Notes and search through the world's largest audio library on Agile and Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes.   "Communication clarity is more important than technical complexity, because if you do not understand, it's pretty hard to execute." — Iryna Stelmakh   Iryna shares one of her most painful career stories — a project in the healthcare domain focused on cancer treatment research data. When she joined, she was managing around 9 projects simultaneously and agreed to take this one on the condition that a strong technical lead would own the technical direction. The project began with a critical misunderstanding: sales had communicated that the client needed a database redesign, but the client actually needed a migration to a different database type. Similar words, fundamentally different work.   For three months, the team worked through research and discovery phases, trying to understand the actual problem. But communication gaps — compounded by language barriers between the Ukrainian development team and the US-based client — prevented them from identifying the real need in time. Iryna trusted the technical lead's reports that everything was on track. She relied instead of checking. Eventually, the client lost confidence and left. It remains the only project in her career she considers a genuine failure.   The lesson cuts deep: teams must have people who can ask the right questions early. As Vasco observes, the root cause was implicit assumptions that were never discovered or explored by the different people involved.   In this episode, we also talk about the importance of the monitoring and controlling phase in project management.   Self-reflection Question: When you trust a team member's assessment that "everything is fine," what verification steps do you take to confirm that understanding is truly shared across all stakeholders? Featured Book of the Week: Team Topologies by Matthew Skelton and Manuel Pais Iryna recommends Team Topologies by Matthew Skelton and Manuel Pais as a book that changed how she thinks about Agile leadership. "Great agile leadership is not only about frameworks, but it's about communication, influence, and the ability to align people around shared goals," she explains. The book helped her understand that Agile isn't just about team process — it's about organizational structure, team boundaries, and responsibilities. She also recommends Never Split the Difference by Chris Voss for Scrum Masters who want to sharpen their communication and influence tactics. As Iryna puts it, communication is one of the most important skills a Scrum Master must have.   [The Scrum Master Toolbox Podcast Recommends]  

Meta and Amazon are cutting managers, but is it efficiency or chaos?Is de-layering, or flattening your org chart, good for a company, or is it a recipe for destruction?Join Product Manager Brian Orlando and Enterprise Business Agility Coach Om Patel as we wade into the murky pool that is the latest of corporate trends - "un-bossing" or the mass sacrifice of middle management and mid-level coordination roles on the unholy alter of efficiency. While the biggest of big companies are slashing layers to reduce costs and empower the IC (individual contributors), we take a more nuanced look, arguing that without proper system redesign, this approach leads to decision bottlenecks, leadership vacuums, and the collapse of career mobility.Listen or watch as we discuss:- Why firing coordinators doesn't eliminate the need for coordination- The dangers of "spreadsheet-driven development" (SDD™)- How informal hierarchies and politics emerge when formal authority is removed- The impact of removing middle management on mentorship, sponsorship, and career growth- How to actually flatten an org, when necessaryWe're pulling out all the stops (and the research) as we review Google's failed "no manager" experiment from 2002, revisit the book Team Topologies, and discuss the recent trend towards a Chief of Staff type role. If you are a leader considering a reorg or a developer wondering why your meetings are getting more chaotic, this episode is for you!#ProductManagement #Leadership #TeamTopologiesTeam Topologies by Matthew Skelton and Manuel Pais, Google Project Oxygen, Fortune article "Executives are drowning. Blame the vanishing middle management layer" by Lily May Lazarus, Zappos Holacracy, Arguing Agile Episode #67 (Team Topologies), Arguing Agile Episode #250 (AI ROI)LINKSYouTube: https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596INTRO MUSICToronto Is My BeatBy Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

This episode was streamed live from Agile meets Architecture conference. In this episode, we discuss the multi-year journey of Circle K's eMobility organization as it scales to support growth from Norway to European and global markets. The eMobility organization began as a small team focused on validating the electric vehicle (EV) charging business in Norway. However, due to its success, it quickly had to shift from “validating to scaling” and expand to various countries and multiple products in an industry that is still in development. Throughout the episode, Eduardo and Guro will share valuable “mistakes”, lessons learned, experiments, methods, and practices we have employed during this journey. We will particularly emphasize the importance of breaking down functional silos within the organization as a means to support sustainable scaling. Initially, we focused on overcoming the Product and Technology silos. Still, in time, we went further to develop truly cross-functional value streams, also involving and continuously engaging with marketing, sales, operations, and other disciplines, with the goal of defining the best ways to support the activities necessary for rapid and sustainable business growth. Eduardo and Guro have employed various ideas and techniques, including Domain-driven Design, Team Topologies, Wardley Mapping, and others. However, you will see that there are no silver bullets. The secret is embracing this as a continuous improvement process, involving people with knowledge and expertise, maximizing learning, and empowering value streams and their teams to drive the necessary design and decision-making with a clear long-term vision. LinksArchitecture Modernization Enabling Team Independent Service Heuristics (ISH) https://github.com/TeamTopologies/Independent-Service-Heuristics https://teamtopologies.com/news-blogs-newsletters/2024/8/7/newsletter-ish-enhancing-modularity-and-autonomy Core Domain Charts Susanne Kaiser: Architecture for Flow

This episode was streamed live from Agile meets Architecture conference. We all know it - our team has become too big, meetings take too long, half of the conversations don't apply to our work, and the sprint goal is now “finish all stories in the sprint”! The classic textbook and the chatbot are certain: The team should be split! And this is indeed the optimal solution. But real life isn't a textbook, and our resources aren't infinite. What if instead of slicing to be a-two-pizza-team, we asked the question: “What do we actually need to work well together?” After over 4 years working with several large data science and engineering teams that wrestled with multiple variations of the same problem, we've resisted the urge to split by the book. Instead of insisting on the one right way, we want to show you how tuning in, listening, and deliberately choosing the solution, can bring back the fun, ease and coveted efficiency we all are after. That could mean: changing who does what in the team, redrawing team boundaries, or combining pragmatic approaches of multiple organizational design systems like LeSS, Team Topologies, and Fluid Teams. The trick is to stop chasing the perfect model and start designing something that actually fits both the team's culture and unique problem domain. Think of it like tailoring a suit: it has to fit the people wearing it, not just look good on a cover.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/424Susanne Kaiser - Independent Tech Consultant & Author of "Architecture for Flow"James Lewis - Software Architect & Director at ThoughtworksRESOURCESSusannehttps://bsky.app/profile/suksr.bsky.socialhttps://mastodon.social/@suksrhttps://twitter.com/suksrhttps://www.linkedin.com/in/susannekaiser1https://susannekaiser.netJameshttps://bsky.app/profile/boicy.bovon.orghttps://twitter.com/boicyhttps://linkedin.com/in/james-lewis-microserviceshttps://github.com/boicyhttps://www.bovon.orgLinkshttps://susannekaiser.net/the-architecture-for-flow-canvashttps://susannekaiser.net/articleshttps://www.christenseninstitute.org/theory/jobs-to-be-doneDESCRIPTIONJames Lewis interviews Susanne Kaiser about her comprehensive new book "Architecture for Flow: Adaptive Systems with Domain-Driven Design, Wardley Mapping and Team Topologies".Susanne shares how she brought together 3 powerful frameworks over several years of her consulting work, creating a holistic approach to designing socio-technical systems. The discussion covers her journey from startup CTO to independent consultant, the evolution of her thinking around value streams and team organization, and her practical "Architecture for Flow Canvas" that teams can use to assess their current state and envision their future.With 126 hand-drawn illustrations and 599 sticky notes in the book, Kaiser emphasizes the importance of visual communication and starting with the problem space before jumping to solutions.RECOMMENDED BOOKSSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcMatthew Skelton & Manuel Pais • Team Topologies • https://amzn.to/4a2gh0iWoods, Erder & Pureur • Continuous Architecture in Practice • https://amzn.to/2QWAmklSteve Pereira & Andrew Davis • Flow Engineering • https://amzn.to/3GY3u44Stefan Hofer & Henning Schwentner • Domain Storytelling • https://amzn.to/3EroBH7BlueskyInstagramLinkedInFacebookCHANNEL 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!

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubCheck out more here:https://gotopia.tech/episodes/422Fabrice Bernhard - Co-Author of “The Lean Tech Manifesto” & Co-Founder & CTO at TheodoSteve Pereira - C o-Author of “Flow Engineering” & Principal Consultant at Visible Flow ConsultingRESOURCESFabricehttps://bsky.app/profile/fab-ber.bsky.socialhttps://x.com/fabricebhttps://github.com/fabricebhttps://www.linkedin.com/in/fabricebernhardStevehttps://x.com/steveelsewherehttps://github.com/stevepereirahttps://www.linkedin.com/in/devopstohttps://stevepereira.caLinkshttps://hbr.org/1986/01/the-new-new-product-development-gameDESCRIPTIONFabrice Bernhard, co-founder of Theodo and co-author of "The Lean Tech Manifesto", shares his journey from agile practitioner to lean thinking advocate. The discussion explores how lean principles can scale agile practices beyond small teams, the misconceptions around both methodologies, and the emergence of tech-enabled networks of teams as a new organizational model.Fabrice emphasizes that both lean and agile are fundamentally about people, not processes, and shares practical lessons from scaling his consultancy to 700 people while maintaining agility through lean principles.RECOMMENDED BOOKSFabrice Bernhard & Benoît Charles-Lavauzelle • The Lean Tech Manifesto • https://amzn.to/3Z4EbU6Steve Pereira & Andrew Davis • Flow Engineering • https://amzn.to/3GY3u44General Stanley McChrystal, Collins, Silverman & Fussell • Team of Teams • https://amzn.to/4bUzhQYMatthew Skelton & Manuel Pais • Team Topologies • https://amzn.to/4a2gh0iBill Frasure, Bruce Eckel, James Ward • Effect Oriented Programming • https://amzn.to/4sO6wLVSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcBlueskyInstagramLinkedInFacebookCHANNEL 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!

Join us for a sharp, practical conversation with Matthew Skelton on how to build organizations that work when AI starts shipping alongside your teams. We talk cognitive load, fast value flow, leadership without micromanagement, and why safety and trust become the real bottlenecks. This is an episode you do not want to miss.Download the ⁠episode transcript⁠=====AI is changing how value gets built and shipped. But going faster is useless if you are just accelerating confusion. In this episode, Lukas Egger talks with Matthew Skelton about how to stay fast and dependable as AI becomes part of everyday delivery. We start with cognitive load and fast flow of value, and why these ideas are the most practical way to think about team design right now. Many organizations have talented people and solid intentions, yet still struggle to deliver meaningful outcomes. The usual culprits show up fast: teams stretched too thin, feedback that arrives late, systems that feel fragile, and structures that make coordination painfully expensive. Then we get specific about AI. Used well, it can remove busywork and tighten feedback loops. Used carelessly, it creates a new class of risk: content quality issues, product safety failures, and erosion of trust. If automation can push changes at high speed, you need equally serious testing, clear ownership, and real accountability. From there, we shift to leadership and control. Not the old command and control model, but a tighter version of autonomy: clarity on direction, alignment on outcomes, and visibility into how work and value actually move through the org. We close with a surprisingly powerful lever that most teams ignore: procurement. When you look at it through a value-flow lens, procurement can either choke delivery or unlock speed, trigger better conversations, and produce real impact far earlier in the enterprise than anyone expects.=====Guest: ⁠ Matthew Skelton Matthew Skelton is the co-author of Team Topologies, one ofthe most influential approaches in modern organizational design and software delivery. As CEO/CTO of Conflux and leader of the global Team Topologies initiatives, Matthew helps organizations around the world design for fast flow of value, sustainable team health, and organizational resilience in complex, fast-moving environments. His work sits at the intersection of operating models, organizational design, socio-technical systems, cognitive load theory, and platform engineering. Over the past decade, his ideas and approaches have shaped how global companies structure teams, define interactions, and build internal platforms that reduce complexity and accelerate value delivery. Team Topologies has become a reference model for leaders seeking clarity, adaptability, and humane high performance. More recently, Matthew's work explores how AI — particularlyagentic and autonomous systems — changes (and sometimes reinforces) the foundations of team design. His perspective is grounded, practical, and focused on real-world delivery: fast flow, reduced cognitive load, better collaboration, and organizations that don't burn people out. Matthew is a frequent keynote speaker at global conferencesand enterprise events, and advises organizations across industries on organizational effectiveness, operating models, internal platforms, and AI-era team design.If you want to learn more about:Our guest: LinkedIn | Webpage | Mastodon | Bluesky | SpeakerDeckSAP Signavio:https://www.signavio.comEmail us your questions or comments: ⁠processtransformers@sap.com⁠

Software architecture and organizational design are deeply interconnected. Conway's Law captures this relationship, while the Inverse Conway Maneuver uses it to shape architecture through team structures. Team Topologies adds a practical model for designing effective team interactions and boundaries. This talk explores how organizational decisions directly influence architectural outcomes — and why integrating Team Topologies into your architectural strategy is probably critical. You'll learn how purposeful team design can reduce cognitive load, improve system modularity, and create architectures that evolve more sustainably. This episode is supported by Agile meets Architecture.

Join the Mob Mentality Show for a stimulating conversation with Kenny (Baas) Schwegler, co-author of Collaborative Software Design, as we explore the intersection of software architecture, team collaboration, and organizational culture. In this episode, we uncover how collaborative software design and Domain-Driven Design (DDD) transform software delivery from a siloed, top-down process into a shared problem-solving experience that integrates business, engineering, and user perspectives to get all the data on the table. Kenny shares practical strategies for running collaborative modeling sessions, including EventStorming, example mapping, and guerrilla modeling. Learn how to engage stakeholders and developers in the same room, foster shared understanding, and evolve systems iteratively while navigating complex organizational dynamics. Whether you're designing greenfield systems or improving brownfield applications, these techniques empower teams to reduce miscommunication, avoid groupthink, and make better design decisions faster. We also dive into the cultural and systemic challenges that impact software delivery, including implicit hierarchies, patriarchal structures, and unspoken decision-making rules. Discover how amplifying quiet voices, balancing power dynamics, and creating psychologically safe environments directly improve software outcomes. Kenny explains how effective collaboration goes beyond tools and patterns—it's about shaping a culture where diverse expertise is actively leveraged and trade-offs are surfaced transparently. Key takeaways from this episode include: - How collaborative software design bridges business understanding and technical feasibility. - Practical methods to introduce DDD, even in non-collaborative environments. - Techniques to iteratively discover, model, and implement solutions in complex domains. - Strategies to neutralize hierarchy and amplify underrepresented perspectives in decision-making. - Insights on integrating team autonomy, Team Topologies principles, and flow-based development for continuous improvement. This episode is essential for software architects, product leaders, developers, and anyone invested in high-performing, collaborative teams. Gain actionable insights on designing software as a collective endeavor, aligning stakeholders, and creating systems that support innovation, adaptability, and inclusion. Video and Show Notes: https://youtu.be/Mqbm2kwpsHo 

Is your solution architect a gatekeeper or an enabler? Join Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel as they draw from their experiences to debate the reasons these roles - which should be natural partners - often find themselves at odds. It's a no-holds-barred look into the eternal conflict between product managers and solution architects!Watch or listen as we explore:1. Why the role exists and if it's even necessary2. Who owns technical decisions3. How PMs may be part of the problem4. Three conversations that never happen5. Identifying architects: shepherds vs. hoarders6. When and how to escalate (without destroying your career)They provide actionable takeaways including the "documentation test," the "decision autonomy test," and the "vacation test" to evaluate whether your architect is enabling or blocking your teams.Whether you're a product manager frustrated by architectural gatekeeping, a solution architect trying to add value without becoming a bottleneck, or a leader trying to resolve these conflicts, this episode offers you solid, practical takeaways that you can start trying today!#ProductManagement #SolutionArchitect #LeadershipTeam Topologies by Manuel Pais and Matthew Skelton, Empowered by Marty Cagan (2020), Five Dysfunctions of a Team by Patrick Lencioni (2002), Radical Candor by Kim Scott, Release It! by Michael Nygard (2017), The Goal by Eliyahu Goldratt, Arguing Agile Episode 67: Team Topologies, Arguing Agile Episode 235: Changing Your Message - Adaptive vs Manipulative Communication, Arguing Agile Episode 236: Why Product Managers Should Own PricingLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

À 20 ans, Ismail créait sa première entreprise à Alger avec une plateforme SMS.Quelques années plus tard, il se lançait dans une idée qui semblait folle : convaincre les banques européennes d'ouvrir leurs données. Cette vision pionnière de l'open banking l'a mené à négocier avec BNP Paribas, Société Générale ou HSBC pendant 7 ans.En 2021, il rejoint Yassir comme General Manager Product & Technology et fait passer l'équipe tech de 50 à 300+ personnes, dans 25 pays, tout en triplant la base utilisateurs jusqu'à 10 millions. Début 2025, il quitte ce poste pour construire un "portfolio de projets" : CTO fractionné, investisseur en Afrique, refusant désormais le salariat classique. Un parcours qui interroge notre rapport au travail et à l'entrepreneuriat.————— ISMAIL CHAIB ————— Retrouvez Ismail sur LinkedIn : https://www.linkedin.com/in/ichaib/ Sa newsletter Unsettled Threads : https://unsettledthreads.substack.com/————— PARTIE 1/3 : PARCOURS ————— (00:00) Intro + présentation d'Ismail (05:04) Open Bank Project : l'idée folle d'ouvrir les données bancaires(09:10) Les différentes phases du projet et le premier client(13:39) Les 4 premières années avant le product-market fit(21:20) Négocier avec les banques : barrières et politiques internes(28:32) L'effet boule de neige après les premiers deals(36:29) Ne pas pouvoir payer les salaires (38:14) Santé mentale et retraite annuelle dans le désert algérien (41:09) La fin d'Open Bank Project et le départ d'Ismail (42:15) Yassir : la super app africaine(52:17) Les 6 piliers du scaling(59:42) Structure : équipes cross-fonctionnelles (SAUCE framework) (1:23:04) Psychological safety : l'incarner à chaque occasion (1:27:32) Différences entre marché européen et africain(1:30:05) Douter tout le temps : une feature, pas un bug(1:35:21) Ce qui fait un bon leader technique(1:36:57) Embarquer les gens : clarté, cohérence, servant leadership(1:43:19) Construire sa carrière comme un portfolio(1:46:33) Ne plus croire au salariat : pourquoi ?(1:52:27) Décider si on dit oui : l'humain, le secteur, le business————— PARTIE 2/3 : ROLL-BACK —————(1:59:49) Le projet qui a raté : 6 mois de retard et client insatisfait(2:06:40) Leçons : avoir les bonnes personnes, une checklist, de l'humilité————— PARTIE 3/3 : STAND-UP —————(2:08:20) Framework de prise de décision en 5 étapes————— RESSOURCES —————Team Topologies (Manuel Pais & Matthew Skelton) — nouvelle édition avec case study YassirWardley Mapping (Simon Wardley)Architecture for Flow (Susanne Kaiser) — combine Team Topologies, Wardley Maps et DDDEmpire of AI (Karen Hao) — l'histoire d'OpenAI depuis le début————— 5 ÉTOILES —————Si cet épisode vous a plu, pensez à laisser une note et un commentaire - c'est la meilleure façon de faire découvrir le podcast à d'autres personnes !Envoyez-moi une capture de cet avis (LinkedIn ou par mail à dx@donatienleon.com) et je vous enverrai une petite surprise en remerciement.

Lost a $2M deal and nobody discussed why? You're not alone!Your company is running on hope, not learning.Product Manager Brian Orlando and Enterprise Business Agility Consultant Om Patel are discussing the potentially career-limiting topic of asking "why does the organization systematically avoid learning from failures?" Thanks! We'll be sure to shut the door on our way out... but before we do, we'll explore why sales and product teams never debrief lost deals together, why customer churn meetings feel like career suicide, and why executives are never held accountable for their predictions.....as well as:• Why cross-functional lost deal retrospectives rarely happen (and how to run your first one)• The cost of ignoring customer churn and how to conduct no-blame churn reviews• Building prediction accountability systems to track strategic bets against reality• How organizational silos kill learning and prevent teams from improving• Why "move fast and break things" culture prevents meaningful learning• Creating learning backlogs and embedding continuous improvement in fast-moving organizationsToday is all about actionable tips, specific questions to ask in retrospectives, and strategies for navigating the political landmines of organizational learning. Today, we're giving you tools to transform how your organization learns from mistakes!Referenced Episodes:• AA235 - Changing the Message• AA199 - W. Edwards Deming: Profound Knowledge for Transforming Organizations• AA67 - Team Topologies: Organizing Business and Technology Teams for Fast Flow#ProductManagement #AgileCoaching #CustomerChurnTeam Topologies by Matthew Skelton and Manuel Pais, W. Edwards Deming's work on systems thinking and organizational learning, Amazon's six-pager concept, Arguing Agile Episode 235 (Changing the Message), Arguing Agile Episode 199 (W. Edwards Deming), Arguing Agile Episode 67 (Team Topologies), Silicon Valley move fast and break things culture, 996 work cultureLINKSYouTube https://www.youtube.com/@arguingagileSpotify: https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Apple: https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Website: https://arguingagile.com/

Tu imagines un établissement public qui traite l'architecture logicielle comme un produit, avec son propre backlog, ses rituels et ses objectifs mesurables ? C'est pourtant ce qu'a mis en place Célia Carcellaire avec son équipe chez France Travail. Alors qu'on associe parfois les organismes publics à la lourdeur, ils ont choisi de foncer à contre-courant en expérimentant des méthodes agiles pour leur offre de service interne.Dans la pratique, ils courent contre la montre : transformer le système d'info en moins d'un an pour répondre à la loi plein emploi, tout en restant à l'écoute d'équipes qui offrent des services au quotidien aux demandeurs d'emploi. L'architecte n'est plus celui qui plane au-dessus des projets, un dossier de cadrage sous le bras. Il devient l'allié de la fabrication, un facilitateur prêt à dégainer Team Topologies ou DDD dès qu'un blocage apparaît.Le plus marquant, c'est ce virage vers l'« archi en tant que produit » : l'équipe se fixe des objectifs concrets (comme résorber la dette technique), mesure son impact, s'adapte en cycle court. Elle propose une « boîte à outils » pour que chaque équipe s'autoforme et crée ses propres solutions. Le résultat : des équipes engagées, conscientes de leur rôle, et une vraie culture de la collaboration.Est-ce que ça te donne envie de chambouler tes pratiques d'architecture ? Ou simplement de repenser la façon dont ton organisation apprend en continu ? À toi de voir comment tu peux t'en inspirer, et pourquoi pas créer à ton tour ta « boîte à apprendre ».Hébergé par Ausha. Visitez ausha.co/politique-de-confidentialite pour plus d'informations.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/382Alice Bartlett - Tech Director for Customer Products at Financial TimesCharles Humble - Freelance Techie, Podcaster, Editor, Author & ConsultantRESOURCESAlicehttps://x.com/alicebartletthttps://github.com/alicebartletthttps://www.linkedin.com/in/alicebartletthttps://medium.com/@alice.bartletthttps://alicebartlett.co.ukCharleshttps://bsky.app/profile/charleshumble.bsky.socialhttps://linkedin.com/in/charleshumblehttps://mastodon.social/@charleshumblehttps://conissaunce.comLinkshttps://blog.container-solutions.com/wtf-happens-to-psychological-safetyDESCRIPTIONAlice Bartlett, Tech Director at the Financial Times, discusses her journey from principal engineer to leading a 70-person team responsible for https://www.ft.com and mobile apps. She shares insights on managing editorial stakeholders, balancing technical debt with business priorities, leading difficult conversations, and navigating the challenges of AI in software development.The conversation with Charles Humble covers her approach to architectural challenges, communication strategies, and the evolving role of technology leadership in modern media organizations.RECOMMENDED BOOKSSimon Wardley • Wardley Maps • https://amzn.to/45U8UprSimon Wardley • Wardley Mapping, The Knowledge • https://amzn.to/3XQEeDuSun Tzu • The Art of War • https://amzn.to/2BqDehaMark Craddock • Wardley Mapping Doctrine • https://amzn.to/4b3jRYbSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcDInspiring Tech Leaders - The Technology PodcastInterviews with Tech Leaders and insights on the latest emerging technology trends.Listen on: Apple Podcasts SpotifyBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

CTO Series: Toni Sallanmaa on Scaling Engineering Teams and Aligning Tech with Business Goals In this BONUS episode, we explore the journey of scaling technology teams and maintaining alignment between engineering and business objectives with Toni Sallanmaa, CTO at Funidata. Toni shares invaluable insights from leading the development of Sisu, a cutting-edge student information system serving over 100,000 Finnish university users, and discusses practical strategies for growing engineering organizations while preserving company culture. The Genesis of Leadership in Technology "I understood what I was really responsible for. I'm interested in the business we are running—the business adds meaning to the work." Toni's approach to technology leadership was fundamentally shaped by a pivotal moment early in his career when he first gained influence over system development and technology choices. After working with large-scale systems for 20 years, this moment of responsibility revelation transformed his perspective from purely technical to business-focused. He emphasizes that infinite curiosity drives success in tech businesses, and understanding the business context gives meaningful purpose to technical work. Bridging the Gap Between Tech and Product "Don't separate Tech from Product. We established a common language between product and technology people." One of Toni's most significant insights centers on eliminating the traditional divide between technology and product teams. As Funidata grew from a small startup to a 70-person organization, the challenges of maintaining alignment became apparent. Their solution involved several key practices: Teaching developers the language of the product domain  Banning confusing technical terms that create communication barriers Workshopping product language to ensure clarity Keeping entity names deliberately vague until true understanding emerges This approach draws heavily from Domain Driven Design principles, creating a unified vocabulary that enables seamless collaboration. Collaborative Planning and Transparency "We use transparency as a collaboration technique. Every team sees what's being proposed as a goal for the next quarter." Funidata implements a unique "marketplace of goals" approach during their quarterly big room planning sessions. Rather than using scaled agile frameworks, they focus on transparency and collaborative goal-setting. Teams present their high-level quarterly plans to each other, creating visibility across the organization. Product owners are embedded within teams, keeping communication distances short and ensuring alignment between technical execution and business objectives. Future-Forward Roadmapping "We talk about the higher level ideas regularly, but let them bubble up from the community. We hold internal hackathons." Toni's approach to roadmapping balances strategic vision with grassroots innovation. They maintain an internal technology roadmap that addresses emerging trends like AI, while allowing ideas to organically emerge from the engineering community. Internal hackathons serve as catalysts for innovation, providing structured opportunities for teams to explore new technologies and approaches that might inform future roadmap decisions. Scaling Challenges and Cultural Preservation "The biggest challenge is not technology, it was the rapid scaling of technology teams. When you scale up, keep the culture in mind." The most significant challenge Toni faced wasn't technical but organizational—rapidly scaling teams while preserving company culture. Growing from 10 to 50 people required evolving processes, from establishing internal forums for architectural discussions to implementing continuous integration flows. The key was identifying pain points proactively and maintaining open discussions with team members throughout the scaling process. Strengthening company culture became essential to successful growth. AI's Impact on Software Development "Productivity is on the rise. We see opportunities like generating test data, but we have strict requirements for cybersecurity, which puts pressure on code quality." Toni views AI's impact on software development with cautious optimism. While productivity gains are evident, particularly in areas like test data generation, the stringent cybersecurity requirements in their domain mean that AI hasn't yet significantly improved code quality where it matters most. The technology shows promise, but implementation must be carefully considered within the context of security and quality requirements. Measuring Engineering Success "We use DORA and SPACE framework. We measure how much of our work is KTLO (Keep The Lights On) and how much is elective development." Funidata employs both DORA and SPACE frameworks to measure engineering organization success. From SPACE, they particularly focus on measuring software team wellbeing, while also tracking the balance between "Keep The Lights On" (KTLO) work and elective development. Using JIRA connected to a data warehouse, they mine extensive data that serves both leadership decision-making and team improvement efforts, ensuring metrics benefit everyone in the organization. Influential Leadership Resources "The organizational books have been more influential to me than purely technical ones." Toni emphasizes that organizational leadership books have shaped his CTO approach more than technical resources. Two key influences stand out: "Team Topologies" for understanding how to structure and scale engineering teams effectively, and "Radical Candor" for building authentic, productive relationships within the organization. You can find a BONUS episode on Team Topologies with the authors Matthew Skeltton and Manuel Pais. About Toni Sallanmaa Toni leads technology and engineering at Funidata, developing Sisu—a cutting-edge student information system serving over 100,000 Finnish university users. Passionate about agile methodologies, system architecture, and software engineering, Toni specializes in technology management, software lifecycle, OOP, and relational databases to deliver innovative, scalable solutions in higher education tech. You can connect with Toni Sallanmaa on LinkedIn.

Managing technological change in an organization — particularly a large and complex one — has always been challenging. But thanks to the rapid adoption of AI in all kinds of spheres, from knowledge management to software development to content creation, it's becoming more difficult than ever. How do you strike a balance between governance and safety and autonomy and empowerment? How should teams be structured and how should they work together? In this episode of the Technology Podcast, Matthew Skelton and Manuel Pais — authors of the influential Team Topologies book — join hosts Birgitta Böckeler and Ken Mugrage to discuss what AI means for organizational design. They discuss how AI is changing team capabilities, what it means for cognitive load and knowledge sharing and how to ensure there's structure and control without constraining experimentation and creativity.  With the second edition of Team Topologies set to be published in September 2025, Matthew and Manuel used the conversation to explore the evolution of their ideas and what they've learned from working with and listening to the stories of many different organizations around the world. Learn more about Team Topologies: https://teamtopologies.com/  

Widerstände, Unklarheiten und dysfunktionale Zusammenarbeit: Viele Probleme zeigen sich erst, wenn Teamstrukturen aktiv verändert werden. In dieser Fortsetzung zu „Evolution von Teamstrukturen“ sprechen Anja Kammer und Jakob Oswald über typische Herausforderungen bei der Arbeit mit Team Topologies: Enabling Teams, die Vorgaben machen statt zu unterstützen. Plattform-Teams, die den Kontakt zu ihren Nutzer:innen verlieren. Entwicklungsteams, die mit neuer Betriebsverantwortung allein bleiben. Eine Folge über die Praxis hinter dem Modell – und darüber, was hilft, wenn Veränderungen nicht wie gewünscht greifen.

It's reorg season…again. And for many companies, it always is. Every 12 to 18 months, another wave of layoffs, leadership swaps, and org chart redraws rolls through the system. And yet, little changes. Strategy stalls. Trust erodes. Work doesn't get better, just messier. So why do so many organizations keep reaching for the reorg lever first? This week, Rodney and Sam unpack the seductive logic (and systemic failure) of reorgs as a change strategy. They dig into why structure work always feels like the fastest, most visible move a leader can make and why it so rarely delivers. Along the way, they explore the very real fallout of these moves on culture, trust, and performance, and offer smarter starting points for those considering a shake-up. -------------------------------- Let's work together: ⁠⁠⁠⁠https://www.theready.com/working-together⁠⁠⁠⁠ Get our newsletter: ⁠⁠⁠⁠Sign up here⁠⁠⁠⁠⁠⁠. Follow us: ⁠⁠⁠⁠⁠⁠LinkedIn⁠⁠⁠⁠⁠⁠ ⁠⁠⁠⁠⁠⁠Instagram⁠⁠⁠⁠⁠⁠ -------------------------------- Mentioned references: The Ready's OS Canvas "16% of reorgs deliver the expected value" Sunshine, Twilight, and Midnight Zones: The Ready's Depthfinding "layoffs episode": Brave New Work Ep. 152 Team Topologies, 2019 book by Matthew Skelton and Manuel Pais holacracy sociocracy "retention increase if you have a best friend at work" "new job is one of the most stressful life events": Holmes and Rahe stress scale, see combined score of “dismissal from work”, “change to different line of work”, and “Change in responsibilities at work” DAO Miniseries "Jeff Williams departure" "value flow mapping" Haier and micro-enterprises 00:00 Intro + Check-In: What feature is really important in your living space? 03:27 The Pattern: Orgs trapped in a cycle of endless reorgs 05:15 The fastest, most visible sign of change a CEO can show to a board or investors 09:55 Structure work should always come last, but most people do it first 12:22 Reorgs to hit a number come at the expense of workflow, culture, and strategy 19:07 Stop changing the structure without touching the ways of working 22:19 Fundamental components of structure work 25:14 How The Ready approached it's own reorg 26:34 Fallout of bad reorgs on your team and culture 31:17 Companies underestimate the stress of reorgs on individuals 34:40 Hot takes: org structure in the age of AI; legal OS around restructuring 38:15 Idea 1: Use reorgs to recalibrate roles back to defaults 39:42 Idea 2: Value flow map your company before considering a standard reorg 42:53 Idea 3: Test new structure in parts of phases, not everything all at once 44:30 Idea 4: Accept that some centralization is required 47:50 Wrap up: Leave us a review and share the show with your coworkers! Sound engineering and design by Taylor Marvin of ⁠⁠⁠⁠⁠⁠⁠Coupe Studios⁠⁠⁠⁠⁠⁠⁠.

In this special episode of Book Overflow, Carter and Nathan are joined by Manuel Pais, author of Team Topologies! Join them as Manuel reflects on what surprised him the most while writing the book, how the popularity of remote work has changed team organization strategies, and insights from the new second edition!----------------https://bit.ly/tusk-bookoverflow-1-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Team Topologies: Organizing Business and Technology Teams for Fast Flow by Matthew Skelton and Manuel Paishttps://amzn.to/4kgfH3F (paid link)----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereManuel Pais - Co-Author of the Book "Team Topologies"Julian Wood - Serverless Developer Advocate at AWS  RESOURCESManuelhttps://x.com/manupaisablehttps://www.manuelpais.nethttps://www.linkedin.com/in/manuelpaishttps://github.com/manupaisableJulianhttps://bsky.app/profile/julianwood.comhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodLinkshttps://teamtopologies.comhttps://academy.teamtopologies.comhttps://www.teamperature.comhttps://itrevolution.comhttps://matthewskelton.comDESCRIPTIONManuel Pais, co-author of Team Topologies, shares his journey in shaping modern organizational design for fast-flow efficiency with Julian Wood. Reflecting on the widespread impact of the book, Manuel explores how its principles have enabled organizations to redefine team structures, streamline value delivery, and balance cognitive load.The discussion covers communication challenges, the evolution of platform engineering, and strategies for iterative team reorganization. Manuel also addresses the growing influence of AI in software development, emphasizing the need for human oversight, strategic alignment with value streams, and enabling teams to harness AI effectively. With insights from real-world implementations and evolving trends, this episode provides a comprehensive guide to building adaptable, customer-focused, and innovative organizations.RECOMMENDED BOOKSMatthew Skelton & Manuel Pais • Team TopologiesSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team TopologiesHeidi Helfand • Dynamic ReteamingGene Kim, Kevin Behr & George Spafford • The Phoenix ProjectGene Kim, Nicole Forsgren & Jez Humble • AccelerateGene Kim, Jez Humble, Patrick Debois, John Willis & Nicole Forsgren • The DevOps HandbookJonathan Smart • Sooner Safer HappierBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

Bu bölümde ekiplerin ve bireylerin omuzlarındaki “bilişsel yük” kavramını masaya yatırıyoruz. Codefiction ekibi, context-switching'in verimliliği nasıl düşürdüğünü, ölçek büyüdükçe teknoloji setinin çeşitlenmesinin ve sorumlulukların yayılmasının geliştiricinin zihinsel kapasitesini nasıl zorladığını örneklerle anlatıyor. Front-end'den veri tabanına, CI/CD pipeline'larına insan-kaynakları işlemlerine kadar uzanan dağınık görevlerin, doğru kurgulanmamış süreçler ve eksik dokümantasyonla birleşince ne kadar görünmez bir “yavaşlatıcı”ya dönüştüğü açıklanıyor. İkinci kısımda bilişsel yükün hem ekip çıktısını hem de çalışan sağlığını (burn-out riskini) nasıl etkilediği tartışılıyor; Team Topologies, Developer Experience ekipleri, “discovery” time-box'ları, standardize teknoloji seçimleri, net domain sınırları ve iyi yazılmış dokümantasyon gibi çözümler tartışılıyor. Teknik borcun ve sürekli toplantı trafiğinin yaratabileceği gizli maliyetlere değinilirken, yöneticilerin olduğu kadar ekip üyelerinin de yükü ölçme-dile-getirme sorumluluğu vurgulanıyor. Bölüm, “her şeyi yapmaya çalışmak yerine önceliklendirmek, sınırlar koymak ve odaklanmak” çağrısıyla kapanıyor. Katılımcılar;Fırat ÖzbolatDeniz İrginMert SusurDeniz ÖzgenBarış ÖzaydınOnur Aykaç

As startups grow, product teams often find themselves caught between speed and structure. In this episode of The Product Experience, Charlotte King, Lead Product Manager at eBay, shares practical insights from her work leading teams through this transition at companies including Moonpig, Flipdish, and ThoughtWorks. Charlotte unpacks how to define product's role during scaleup, build team structure around strategic value, and use tools like Wardley Mapping and Team Topologies to support organisational change. She also introduces the DHM model (Delightful, Hard to copy, Margin-enhancing) and discusses how to make strategy tangible for cross-functional teams. This conversation is especially useful for product leaders, heads of product, and founders navigating scale.Chapters1:13 – Charlotte's background2:36 – Product's role in startups, scaleups and enterprises4:35 – What product teams need to succeed during scale6:42 – Defining product's role as the company grows9:00 – Using Wardley Mapping to assess team maturity14:30 – Creating and communicating guiding principles20:30 – Using the DHM model to prioritise value25:48 – Structuring teams with Team Topologies29:03 – Multidisciplinary collaboration in practice30:41 – Lessons from leading transformation32:30 – Final reflections and takeawaysFeatured Links: Follow Charlotte on LinkedIn | eBay | Wardley Maps | What we learned at #mtpcon London 2025' feature by Kent McDonald and Louron PrattOur HostsLily Smith enjoys working as a consultant product manager with early-stage and growing startups and as a mentor to other product managers. She's currently Chief Product Officer at BBC Maestro, and has spent 13 years in the tech industry working with startups in the SaaS and mobile space. She's worked on a diverse range of products – leading the product teams through discovery, prototyping, testing and delivery. Lily also founded ProductTank Bristol and runs ProductCamp in Bristol and Bath. Randy Silver is a Leadership & Product Coach and Consultant. He gets teams unstuck, helping you to supercharge your results. Randy's held interim CPO and Leadership roles at scale-ups and SMEs, advised start-ups, and been Head of Product at HSBC and Sainsbury's. He participated in Silicon Valley Product Group's Coaching the Coaches forum, and speaks frequently at conferences and events. You can join one of communities he runs for CPOs (CPO Circles), Product Managers (Product In the {A}ether) and Product Coaches. He's the author of What Do We Do Now? A Product Manager's Guide to Strategy in the Time of COVID-19. A recovering music journalist and editor, Randy also launched Amazon's music stores in the US & UK.

Czym jest podejście Team Topologies? Jakie rozwiązuje problemy i z czego się składa? Jeśli brzmi to interesująco, bo poszukujesz metody by zespoły w Twojej organizacji się dogadywały, a przy tym dostarczały wartość to zapraszam do tego odcinka. W rozmowie z dwoma pozostałymi Team Topologies Advocates - Krzysztofem Hałasą oraz Piotrem Kacałą rozmawiamy nie tylko o częściach składowych, ale i pułapkach związanych ze stosowaniem Team Topologies.

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereSusanne Kaiser - Independent Tech Consultant & Author of "Architecture for Flow"Michaela Greiler - Code Reviews Expert, Trainer & ConsultantAdele Carpenter - Software Engineer at TriforkDaniel Terhorst-North - Originator of Behavior Driven Development (BDD) & Principal at Dan North & AssociatesSimon Wardley - Thought Lord, Mapper, Mostly GoodRESOURCESSusannehttps://mastodon.social/@suksrhttps://susannekaiser.netMichaelahttps://twitter.com/mgreilerhttps://michaelagreiler.comAdelehttps://bsky.app/profile/97adele.bsky.socialDanielhttps://bsky.app/profile/suksr.bsky.socialhttp://dannorth.net/blogSimonhttps://bsky.app/profile/swardley.bsky.socialhttp://blog.gardeviance.orgDESCRIPTIONExplore the rich tapestry of what it truly means to support developers.The conversation took a forward-looking turn as they examined the role of AI, not as a looming replacement, but as a powerful ally that enhances human creativity, much like past innovations that revolutionized workflows. They showcased how intuitive design—exemplified by tools like IntelliJ—can make a developer's experience seamless and enjoyable.RECOMMENDED BOOKSSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team TopologiesSimon Wardley • Wardley MapsSimon Wardley • Wardley Mapping, The KnowledgeMatthew Casperson • DevEx as a ServiceChristian Clausen • Five Lines of CodeDavid Anderson, Marck McCann & Michael O'Reilly • TBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

This week Carter and Nathan discuss the first half of System Design Interview by Alex Xu. Join them as they discuss Alex's excellent newsletter Byte Byte Go, how systems design interviews reflect actual jobs, and what tips and tricks Alex offers to ace your interviews!Byte Byte Go: https://bytebytego.com/-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------System Design Interview – An insider's guide by Alex Xu https://amzn.to/3EXFYUa (paid link)Team Topologies by Matthew Skelton and Manuel Paishttps://amzn.to/4kgfH3F (paid link)----------------00:00 Intro01:33 About the Book03:08 Thoughts on the Book11:57 What is a Systems Design Interview?22:15 Why focus on Systems Design Interview?27:26 Our Experience with System Design Interviews36:09 Strategies, Approach, and Expertise40:20 Importance of Back of the Envelope Calculations45:39 Learning through building57:02 Final Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In this episode of Book Overflow, Carter and Nathan discuss the second half of Team Topologies by Matthew Skelton and Manuel Pais. Join them as they discuss how teams evolve, when you can tell a team might be reaching its breaking point, and what a company needs beyond the team topologies!-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Team Topologies by Matthew Skelton and Manuel Paishttps://amzn.to/4kgfH3F (paid link)----------------00:00 Intro01:26 About the Book03:10 Thoughts on the Book09:20 Team Interaction Modes41:01 Changing Team Structures01:05:04 Final Thoughts----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

In this episode of the Product Thinking Podcast, I am thrilled to welcome Matthew Skelton, co-author of "Team Topologies: Organizing Business and Technology Teams for Fast Flow." We delve into the intricate intersections between team topology principles and product management, exploring how these frameworks can transform the way product teams work together to enhance collaboration and reduce cognitive load.If you're looking to refine your team's approach to delivering outstanding customer outcomes, this episode is a must-listen. Matthew Skelton joins me to discuss the revolutionary concepts within "Team Topologies," highlighting their impact on modern product management and operations. We uncover how organizing teams around flow and customer value can drastically improve product outcomes. Matthew shares practical examples of how these concepts are applied in various industries, providing invaluable insights for anyone involved in managing or organizing product teams.Curious about how team topologies can optimize your product processes? Tune in to hear Matthew Skelton's expert insights and discover practical strategies to enhance your team's workflow. Don't miss this opportunity to learn from a leading voice in the field of organizational design for software delivery.You'll hear us talk about: Product Managers in Regulated Spaces (28:30)We discuss the debate over whether product managers should be domain experts versus having deep product knowledge. Matthew provides insights into how teams can effectively leverage subject-matter experts without them managing the entire product line. Breaking Silos in Teams (14:21)Matthew and I explore how organizations can overcome internal silos, emphasizing the importance of collaboration across product management, development, marketing, and sales for cohesive product delivery. AI and Team Enablement (51:54)We dive into how AI is transforming team topologies and enabling teams, discussing the shift in AI enablement platforms and their potential in redefining team roles and productivity.Episode Resources: Matthew Skelton's Website: https://matthewskelton.com Conflux Website: https://confluxhq.com Team Topologies Information: https://teamtopologies.com Sign up for a free Liveblocks account: ⁠https://liveblocks.io/⁠Timestamps:00:00 Episode Preview00:56 Intro03:00 Dear Melissa08:35 Moving from Projects to Product14:45 Breaking Silos in Teams18:27 Mistakes in Product Models28:14 Product Managers in Regulated Spaces35:51 Product Ops at Scale42:17 SAFE and Big Batch Planning51:37 AI and Team Enablement

In this episode of Book Overflow, Carter and Nathan discuss the first half of Team Topologies by Matthew Skelton and Manuel Pais. Join them as they discuss the four main types of teams, what teams they've worked on in the past, remote work, and more!-- Books Mentioned in this Episode --Note: As an Amazon Associate, we earn from qualifying purchases.----------------------------------------------------------Team Topologies by Matthew Skelton and Manuel Paishttps://amzn.to/4kgfH3F (paid link)----------------Spotify: https://open.spotify.com/show/5kj6DLCEWR5nHShlSYJI5LApple Podcasts: https://podcasts.apple.com/us/podcast/book-overflow/id1745257325X: https://x.com/bookoverflowpodCarter on X: https://x.com/cartermorganNathan's Functionally Imperative: www.functionallyimperative.com----------------Book Overflow is a podcast for software engineers, by software engineers dedicated to improving our craft by reading the best technical books in the world. Join Carter Morgan and Nathan Toups as they read and discuss a new technical book each week!The full book schedule and links to every major podcast player can be found at https://www.bookoverflow.io

This interview was recorded for GOTO Unscripted.https://gotopia.techRead the full transcription of this interview hereBen Ellerby - Founder of aleio & AWS Serverless HeroJulian Wood - Serverless Developer Advocate at AWSRESOURCESBenhttps://twitter.com/EllerbyBenhttps://www.linkedin.com/in/benjaminellerbyhttps://github.com/BenEllerbyhttps://medium.com/@bene_37069Julianhttps://twitter.com/julian_woodhttp://www.wooditwork.comhttps://www.linkedin.com/in/julianrwoodDESCRIPTIONJulian Wood and Ben Ellerby explore the challenges and innovations in event-driven architectures, generative AI, and serverless technologies. They emphasize the importance of well-structured event schemas and the role of platform teams in reducing cognitive load for developers.Ben Ellerby highlights the potential of generative AI in modernizing legacy codebases and discusses the resurgence of event-driven architectures, driven by improved tools and frameworks that promote decoupling and efficiency.The conversation also touches on the future of serverless computing, edge computing, and the significance of data management in global applications, underscoring a transformative shift toward more scalable and flexible cloud solutions.RECOMMENDED BOOKSDavid Anderson, Marck McCann & Michael O'Reilly • The Value Flywheel EffectAdam Bellemare • Building Event-Driven MicroservicesLauren Maffeo • Designing Data Governance from the Ground UpVaughn Vernon & Tomasz Jaskula • Strategic Monoliths & MicroservicesGregor Hohpe • Platform StrategyPeter Sbarski • Serverless Architectures on AWSMichael Stack • Event-Driven Architecture in GolangJames Urquhart • Flow ArchitecturesBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

Organisational effectiveness isn't just about making team members more productive, but [roperly structuring teams and understanding how they work together.Small teams with high trust can make decisions quickly and maintain better context of what they're building, while being mindful of the cognitive load placed on members.Matthew Skelton is the author of Team Topologies. He developed patterns for team organisation and devops that were adopted by companies like Netflix and Accenture. His work focuses on how to structure teams effectively in organisations, particularly looking at concepts like team cognitive load and team interaction modes.Three reasons to listenLearn how small teams can achieve faster results and deliver value more effectively to usersUnderstand the principles behind Amazon's "two pizza team" approach, including how trust enables quick decision-making in small groupsDiscover how organisations often lack self-awareness and how this becomes a major obstacle to their successEpisode highlights[00:11:47] The road to Team Topologies[00:17:18] Why collaboration is not the only answer[00:22:05] Creating flow for small teams[00:23:34] Making work humane[00:28:10] The Uswith example[00:30:45] Alternative schools of thought[00:34:56] Impact on team leaders[00:37:31] Conway's law[00:40:48] Decoupling of teams and architecture[00:46:08] Matthew's media recommendations[00:48:59] Takeaways from Pia and DanLinksTeam Topologies: Organizing Business and Technology Teams for Fast Flow –Matthew's bookThe jazz ensemble: the ultimate team? – We Not MeTeam Topologies' Uswitch case studyConway's lawEmpowered Agile Transformation: Beyond the Framework, by Alexandra StokesArchitecture Modernization, by Nick TuneFrozen II (2019)Leave us a voice note

Wie verändern sich Teamstrukturen, wenn Organisationen wachsen oder neue Anforderungen entstehen? In dieser Folge spricht Anja Kammer mit Jakob Oswald, Senior Consultant bei INNOQ, über die Weiterentwicklung von Teamstrukturen. Jakob erklärt, warum klare Verantwortlichkeiten und die Auswahl passender Kommunikationswege entscheidend sind und wie Visualisierungen möglicher Transformationsmeilensteine helfen, ein gemeinsames Verständnis zu schaffen. Mit einem Fokus auf die Methoden von „Team Topologies“ zeigt die Folge praxisnah, wie Teams den Wandel aktiv gestalten können – ohne dabei ihre Handlungsfähigkeit zu verlieren.

Matthew Skelton joins host Giovanni Asproni to talk about team topologies—an approach to organizing teams for fast flow of value. The episode starts with a description of the underlying principles before exploring the approach in more detail. From there, they discuss when to consider implementing the approach; keys to a successful implementation; and some common mistakes to avoid. Brought to you by IEEE Computer Society and IEEE Software magazine.

This interview was recorded at GOTO Amsterdam for GOTO Unscripted.http://gotopia.techRead the full transcription of this interview here:https://gotopia.tech/articles/326Susanne Kaiser - Independent Tech Consultant & Author of "Architecture for Flow"James Lewis - Software Architect & Director at ThoughtworksRESOURCESSusannehttps://mastodon.social/@suksrhttps://twitter.com/suksrhttps://www.linkedin.com/in/susannekaiser1https://susannekaiser.netJameshttps://twitter.com/boicyhttps://linkedin.com/in/james-lewis-microserviceshttps://github.com/boicyhttps://www.bovon.orgDESCRIPTIONSusanne Kaiser, an expert tech consultant, shares her secrets for integrating Wardley mapping, team topologies and domain-driven design to streamline value delivery and boost team effectiveness. The discussion with James Lewis highlights the power of hands-on collaboration, the value of understanding the purpose behind tools, and practical tips for breaking down silos and overcoming analysis paralysis. Tune in to discover how these cutting-edge techniques can transform your approach to organizational change and team dynamics.RECOMMENDED BOOKSSusanne Kaiser • Adaptive Systems With Domain-Driven Design, Wardley Mapping & Team Topologies • https://amzn.to/3XTmNCcSimon Wardley • Wardley Mapping, The Knowledge • https://amzn.to/3XQEeDuSimon Wardley • Wardley Maps • https://amzn.to/45U8UprMatthew Skelton & Manuel Pais • Team Topologies • http://amzn.to/3sVLyLQHeidi Helfand • Dynamic Reteaming • https://amzn.to/3Fvu5BAEric Evans • Domain-Driven Design • https://amzn.to/3tnGhwmGregor Hohpe • Platform Strategy • https://amzn.to/4cxfYdbBlueskyTwitterInstagramLinkedInFacebookCHANNEL 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!

Success as a platform PM requires both technical depth and exceptional emotional intelligence to navigate complex organizational dynamics...That goes double if you work in banking or finance!In this episode of Arguing Agile, Enterprise Business Agility Coach Om Patel and Product Manager Brian Orlando read and respond to a question from a listener who is a platform product managers at a Bank.Getting into the nitty-gritty of platform how-to's, this episode is perfect for product managers, agile coaches, and technology leaders working in traditional industries looking to modernize their approach to platform management!As industries embrace digital transformation (err... product operating model), platform product managers face unique challenges, including: How to effectively manage cross-functional relationships in siloed environmentsStrategies for prioritizing platform features that deliver organization-wide valueTips for reducing cognitive load across teamsWays to build trust and showcase value as a platform teamCreate value through standardization without weaponizing itBuild effective cross-functional relationships#ProductManagement #TeamTopologies #PlatformTeam #AgileLeadership #Banking #TechLeadership #ProductDevelopment #AgileCoaching= = = = = = = = = = = =Watch it on YouTube= = = = = = = = = = = =Subscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

Find out about cross-functional team members with Daniel Bartholomae, CTO at optilyz (direct mail SaaS). At optilyz, team members wear multiple hats—whatever hats they need to own the product lifecycle. From product management and design to development and customer engagement, this model eliminates silos and drives efficiency. Daniel breaks down how this innovative approach works, the tools and processes that make it possible, and why it's a perfect fit for small B2B SaaS companies. Listen to find out:

In this episode of the E-commerce Toolbox: Expert Perspectives podcast, host Kailin Noivo interviews Dileep Marway, VP of Engineering and Technology at AND Digital. Dileep shares insights from his diverse career journey, beginning with a degree in pharmacy and transitioning to computer science, where he discovered his passion for aligning technology with people. He discusses his experiences at organizations like The Economist and SHL, emphasizing the importance of cultural transformation in tech-driven environments. Dileep also explains how a people-centric approach enhances digital transformation, improves team dynamics, and ultimately drives business success. Tune in as he explores the critical balance between cultural and digital transformation, the role of leadership in fostering innovation, and the challenges businesses face in today's rapidly evolving landscape.

Richard Coplan: The Impact of Product Owner Pressure on Agile Team Morale Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. In this episode, Richard shares his experience working in a toxic team environment at an insurance company. Brought in to replace a beloved Scrum Master, he found himself navigating a strained relationship between the Product Owner (PO) and the team. The PO's aggressive push for deliverables demotivated the team, and management sided with the PO, creating a vicious cycle of disengagement. How can a PO's leadership style make or break a team's performance? Richard explores this anti-pattern of PO-driven disengagement. Featured Book of the Week: Lean Enterprise by Jez Humble, et al. Richard reflects on how the book "Lean Enterprise" helped shape his approach as an Agile Coach, offering a holistic view of organizations. He also discusses "Team Topologies" and the importance of stream-aligned teams with CI/CD pipelines. What role does organizational agility play in the success of Scrum teams? Richard suggests that while many teams practice Scrum, organizations themselves are often not truly Agile.   [IMAGE HERE] Do you wish you had decades of experience? Learn from the Best Scrum Masters In The World, Today! The Tips from the Trenches - Scrum Master edition audiobook includes hours of audio interviews with SM's that have decades of experience: from Mike Cohn to Linda Rising, Christopher Avery, and many more. Super-experienced Scrum Masters share their hard-earned lessons with you. Learn those today, make your teams awesome!     About Richard Coplan Richard joins us from the UK. He has been a software developer for many years and later became data-centric, eventually transitioning into the role of Scrum Master. Over the past decade, Richard has specialized as a Scrum Master and Agile Coach, with a focus on collaboration tools like Miro and helping firms streamline their team structures. You can link with Richard Coplan on LinkedIn.

Estrutura de time não é assunto de pessoas gerentes? Nesse episódio, Edu e Will se juntaram ao Fred e Leandro para discutir como arquitetura de software e decisões técnicas podem ser influenciadas pela estrutura dos times! Vem com a gente aprender mais sobre Team Topologies.

In this episode of the Arguing Agile podcast, Enterprise Agile Coach Om Patel and Product Manager Brian Orlando dive into the often misunderstood concept of platform teams. They discuss:- The definition and purpose of a platform team- How platform teams differ from stream-aligned feature teams - Key behaviors of effective platform teams- Common anti-patterns and mistakes made with platform teams- How platform teams enable greater business agility when implemented wellWhether you're a product manager, agile coach, or tech leader, understanding platform teams is critical for building high-performing organizations. Tune in to learn the do's and don'ts of platform teams.0:00 Podcast Intro0:11 Topic Intro: What is a Platform Team?0:58 What is a Platform?2:26 Stream-Aligned or Durable Teams3:22 What the Platform Team Does6:06 Good Behaviors: Collaboration8:04 Good Behaviors: Fast Feedback Loops9:57 Good Behaviors: Focus on Usability & Reliability12:25 Bottcher's Points: the Source Article16:36 Platform Confusion19:15 Platform Team Product Management21:17 Transferring or Sabotaging Cognitive Load23:49 No Dedicated Platform Team26:18 Customer Focus vs Platform Work30:23 Normal (Platform) Business32:13 Wrap-Upplatform team, platform as a product, stream-aligned teams, team topologies, cognitive load, business agility, product management, devops, enterprise agile= = = = = = = = = = = =Watch it on YouTubeSubscribe to our YouTube Channel:https://www.youtube.com/channel/UC8XUSoJPxGPI8EtuUAHOb6g?sub_confirmation=1Apple Podcasts:https://podcasts.apple.com/us/podcast/agile-podcast/id1568557596Spotify:https://open.spotify.com/show/362QvYORmtZRKAeTAE57v3Amazon Music:https://music.amazon.com/podcasts/ee3506fc-38f2-46d1-a301-79681c55ed82/Agile-Podcast= = = = = = = = = = = =Toronto Is My Beat (Music Sample)By Whitewolf (Source: https://ccmixter.org/files/whitewolf225/60181)CC BY 4.0 DEED (https://creativecommons.org/licenses/by/4.0/deed.en)

In this episode, Frank La Vigne and Andy Leonard dive deep into the world of developer advocacy and data observability with special guest Chris Cooney from CoreLogix. From discussing the evolution of Microsoft Evangelism to the intricacies of data retention and real-time decision-making, this conversation covers a wide range of topics, including the impact of AI technology, the importance of community in software engineering, and the challenges of connecting with engineers at trade shows.Join us as we explore the intersection of technology, advocacy, and data engineering in this insightful episode featuring Chris Cooney on "Data Driven".New Season Means a New Theme SongLet us know what you think! Don't worry, we will use a shortened version for future shows. We were just so excited to get to Season 8!Show Notes03:54 Experienced engineer transitioned into leadership in technology.07:40 Dan delivers insightful speech on tracking activity.12:33 Developers must adapt to new technology continually.13:45 Conference talk success measured by engagement metrics.17:15 Uncertainty about outcome of video creation.20:00 The trend in the field is evolving.25:45 Retain all data, use case-driven storage. Avoid rehydration.27:11 Core principles: smart data science, streaming architecture.32:34 Efficient streaming processes allow for easy scaling.36:16 Instantly triggered alarm blocks malicious IP addresses.37:22 Enormous architecture demonstrates remarkable data management practice.42:13 Struggle with learning Arabic dialect using AI.44:41 Language differences reflect cultural and historical influences.47:55 Regularly listens to audiobooks, recommends "Team Topologies" and "Team of Teams."51:32 Data-driven podcast season 8 debut summary prompt.

Lakshmi Baskaran shares insights on impromptu communication, why it's important, and a framework for successfully navigating these tricky situations! We also cover team topology and why it's so important to have the right composition of product-minded vs. technical-minded engineers within any eng team. Lakshmi shares how prioritizing team topology will impact hiring, influence engineering culture, and aid in eng team reorgs / restructures. She also discusses what the future of AI looks like for executive eng leaders & what to consider when adopting AI practices / technologies. And to bring it all together, we dissect how Lakshmi's Triple-A impromptu communication framework operates in the context of both team topology & AI adoption.ABOUT LAKSHMI BASKARANLakshmi Baskaran is an accomplished business leader, entrepreneur, and an angel investor with over two decades of experience in the tech industry. She has built and managed high-performing engineering teams for startups, scale-ups, and publicly listed companies across North America, Europe, Australia, and Asia.She is currently serving as the VP of Engineering at Metadata, a SaaS company that offers a Marketing Operating System to prominent brands and businesses worldwide.Lakshmi is passionate about coaching and mentoring business leaders and empowering women to pursue careers in technology. With the right support, she firmly believes that any woman can unleash her potential and make a significant impact on the world, rising to the heights of a great leader, entrepreneur, and a board member.Lakshmi shares her insights on leadership and technology through her writing on Medium and Thrive.“Imagine you're presenting it to your executive leadership team or to your board. As an engineering leader, you want to spice up that message with how it is interesting to your customers. The framework that I use in scenarios like this is called 'What If And So That' framework. If you're running an email platform, what if you're able to search through millions of emails in a sub millisecond so that your users can have faster search abilities compared to our competitors? Build a dream scenario and tell them how the technology can help them meet their dream scenario.”- Lakshmi Baskaran   We're less than one week away from GLOW 2024 – Jellyfish's virtual summit for engineering, product, and finance leaders who are looking to deliver greater business impact while building great software and teams. Here's a preview of what's in store:An inspiring guest keynote by TIME Magazine's Kid of the Year, Gitanjali RaoStrategies for engineering excellence from CTOs at Keller Williams, Genius Sports, and FanDuelJellyfish CEO and Co-Founder Andrew Lau's keynote on the future of software engineeringExciting product roadmap updates from JellyfishRegister for this May 15 event today at jellyfish.co/glow!SHOW NOTES:Why the topic of effective impromptu communication is important (2:46)Dissecting frameworks & tools for impromptu conversations (7:16)An example of high-quality impromptu communication with a CEO (11:52)Implement the Triple-A framework (14:03)The impact of this communication method on peers (16:37)Lakshmi's insights on team topologies & essential aspects of different eng teams (18:26)Considerations for eng team composition (20:56)How new hires play into assembling and/or reforming early-stage eng teams (23:44)Aligning with teams about what they're looking for in terms of hiring / composition (26:12)The impact of product & tech-minded eng leaders on engineering culture (29:19)Opportunities to employ impromptu comm skills in the context of team topology (31:42)Lakshmi's observations on AI adoption (33:47)Frameworks for effectively communicating about AI considerations (37:11)How eng leaders should apply these AI areas into their decision-making (40:40)The role of impromptu communication in AI conversations (42:33)Rapid fire questions (45:00)LINKS AND RESOURCESLakshmi's blog post on identifying product-minded and tech-minded engineersThe Engineering Executive's Primer: Impactful Technical Leadership - Will Larson shows you ways to obtain your first executive job and quickly ramp up to meet the challenges you may not have encountered in non-executive measuring engineering for both engineers and the CEO, company-scoped headcount planning, communicating successfully across a growing organization, and figuring out what people actually mean when they keep asking for a "technology strategy.”This episode wouldn't have been possible without the help of our incredible production team:Patrick Gallagher - Producer & Co-HostJerry Li - Co-HostNoah Olberding - Associate Producer, Audio & Video Editor https://www.linkedin.com/in/noah-olberding/Dan Overheim - Audio Engineer, Dan's also an avid 3D printer - https://www.bnd3d.com/Ellie Coggins Angus - Copywriter, Check out her other work at https://elliecoggins.com/about/

Lead a more humane and effective organisation with inspiration from Matthew Skelton, co-author of Team Topologies. Inspired by system design

Johannes Andersen: Ceremony Over Substance, The Scrum Master Trap, And How It Affects Teams And The Product Owner Read the full Show Notes and search through the world's largest audio library on Scrum directly on the Scrum Master Toolbox Podcast website: http://bit.ly/SMTP_ShowNotes. The Great Scrum Master: Beyond the Backlog, How a Great Scrum Master Helps Product Owners From a Product Owner's perspective, Johannes shares what an ideal Scrum Master looks like. This Scrum Master not only introduced him to Scrum but also focused on the underlying purpose beyond mere processes. His patience, clarity, and pragmatic approach in defining priorities and solving conflicts greatly facilitated the PO's understanding of product development challenges. This Scrum Master's ability to foster meaningful conversations significantly helped Johannes in the PO role, highlighting the importance of a Scrum Master's soft skills in guiding and supporting the product vision. The Bad Scrum Master: Ceremony Over Substance, The Scrum Master Trap, And How It Affects Teams And The Product Owner From a Product Owner's perspective, Johannes highlights an anti-pattern where the Scrum Master becomes overly focused on ceremonies and strict adherence to Scrum guidelines, losing sight of the actual outcomes. This approach mistakenly centralizes process ownership with the Scrum Master, rather than distributing it among the entire team. Johannes advises addressing this issue by realigning the Scrum Master's role towards shared goals and understanding, using tools like Team Topologies for discussion. The key is moving beyond the "servant" aspect of "servant leader" to foster a team environment where understanding and self-direction are prioritized.   [IMAGE HERE] Are you having trouble helping the team work well with their Product Owner? We've put together a course to help you work on the collaboration team-product owner. You can find it at bit.ly/coachyourpo. 18 modules, 8+ hours of modules with tools and techniques that you can use to help teams and PO's collaborate.   About Johannes Andersen Johannes comes from a finance and fintech background, and is now an enterprise agility maestro at a leading telco in Copenhagen! He focuses on optimizing the flow from strategy to execution, championing portfolio management with a keen eye on doing the right things, even if imperfectly. Johannes is an international speaker on product development topics. You can link with Johannes Andersen on LinkedIn.