Podcasts about team topologies

Eigentlich definiert Architektur “nur” die Struktur der Software. Aber das Gesetz von Conway weißt schon auf den Zusammenhang zwischen Architektur und Organisation hin. Durch das Inverse Conway Maneuvre ist klar geworden, dass die geschickte Aufstellung der Organisation die Architektur maßgeblich beeinflussen kann. Dieser Vortrag zeigt auf, dass Team Topologie auch erhebliche Konsequenzen für die Architektur-Arbeit hat: Team Topologies fungiert nicht nur als Werkzeug für Architektur, sondern muss auch in die architektonische Planung einbezogen werden. Links Folien D.L. Parnas: Information Distribution Aspects of Design Methodology Frederick P. Brooks: The Mythical Man-Month Episode zu Modularisierung Fachliche Architektur - Warum und wie? Episode zu Team Topologies Episode zur DevOps Study Fearless Change - Neue Ideen etablieren Software Architektur - Den menschlichen Faktor verbessern!

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!

Schickt uns euer Feedback zur EpisodeIn Episode 127 fragen wir uns (mal wieder) warum so viele digitale Transformationsprojekte scheitern. Björn Schotte, Mitgründer und Geschäftsführer der Mayflower GmbH, bringt in dieser Folge eine provokante These mit: “Organisation folgt Technologie, nicht umgekehrt.”Während viele Unternehmen zuerst Teams bilden und dann hoffen, dass “geile Software” entsteht, zeigt die Praxis, dass dieser Ansatz oft zum Scheitern verurteilt ist. Stattdessen sollten wir uns zunächst fragen: Welche Geschäftsanforderungen haben wir? Welche Softwarearchitektur brauchen wir dafür? Und erst dann: Wie müssen unsere Teams strukturiert sein, um diese Architektur optimal umzusetzen?Wir erkunden das faszinierende Conway's Law, das besagt, dass die Struktur einer Software die Kommunikationsstrukturen der Organisation widerspiegelt, und diskutieren moderne Ansätze wie Team Topologies. Diese bieten Frameworks, wie Teams in einer zunehmend komplexen Softwarewelt organisiert werden können, um sowohl Autonomie als auch Alignment zu gewährleisten.Doch die eigentliche Herausforderung liegt in der Transformation: Wie können wir in gewachsenen Strukturen mit informellen Netzwerken und mikropolitischen Interessen solche Veränderungen umsetzen? Und welchen Einfluss wird künstliche Intelligenz auf dieses Zusammenspiel haben? Werden Junior-Entwickler überflüssig oder verändert sich nur, wie wir zusammenarbeiten?Eine gedankenprovozierende Folge, die die Grenzen zwischen Technologie und Organisation neu auslotet und praktische Einblicke gibt, wie digitale Transformation wirklich gelingen kann.Shownotes:Manuel Pais und Matthew Skelton, Team Topologies: Organizing Business and Technology Teams for Fast Flow, Buch

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.

This interview was recorded for the GOTO Book Club.http://gotopia.tech/bookclubRead the full transcription of the interview hereNick Tune - Author of "Architecture Modernization" & Staff Engineer at PayFitEduardo da Sliva - Independent Consultant on Socio-technical Systems, Architecture & Leadership ModernizationRESOURCESNickhttps://hachyderm.io/@nick_tunehttps://www.linkedin.com/in/nick-tunehttps://nick-tune.mehttps://medium.com/nick-tune-tech-strategy-blogEduardohttps://x.com/emgsilvahttps://mastodon.social/@eduardodasilvahttps://www.linkedin.com/in/emgsilvahttps://github.com/emgsilvahttps://esilva.nethttps://esilva.net/ametDESCRIPTIONEduardo da Silva interviews Nick Tune about his book "Architecture Modernization." Nick Tune shares his motivations for writing the book, emphasizing the socio-technical alignment of software, strategy, and structure. They discuss the importance of business objectives, the role of Architecture Modernization Enabling Teams (AMET), and practical steps to initiate and sustain modernization efforts. Nick Tune also highlights the continuous nature of modernization and the need for organizations to adapt and learn over time.The conversation provides valuable tips for effectively approaching architecture modernization and ensuring long-term success.RECOMMENDED BOOKSNick Tune & Jean-Georges Perrin • Architecture ModernizationScott Millett & Nick Tune • Patterns, Principles, and Practices of DDDMatthew Skelton & Manuel Pais • Team TopologiesFord, Richards, Sadalage & Dehghani • Software Architecture: The Hard PartsSimon Brown • Software Architecture for Developers Vol. 2Woods, Erder & Pureur • Continuous Architecture in PracticeTwitterInstagramLinkedInFacebookLooking 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!

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)

I continue my conversation with Manuel Pais, co-author of the seminal Team Topologies book about team topologies suitable for reliability teams.In this second part, we will talk about platform teams. A quick refresher on what platform teams doIn the team topologies context:Platform teams provide a curated set of self-service capabilities to enable stream-aligned teams (product or feature teams) to deliver work with greater speed and reduced complexity.They achieve this directive by abstracting away common infrastructure and operational concerns. By doing this, they aim to allow stream-aligned teams to focus on delivering business value.Here are the key takeaways from our conversation For those who don't have time to listen to this episode (but you're missing out on a great conversation):* Focus on User-Centric Design: Prioritize the user experience in platform development. Regularly collaborate with internal teams to ensure the platform meets their needs and reduces their pain points.* Build and Maintain Trust: Establish and nurture trust with your platform's users. Trust is crucial for platform adoption and can prevent resistance thus assuring sustained use.* Justify Platform Value: Continuously demonstrate the value of your platform to management and stakeholders, especially during economic downturns. Highlight its contributions to avoid cuts and maintain support.* Understand Adoption Lifecycle: Recognize that platforms go through different stages of adoption. Identify and support early adopters, and gradually bring in late adopters by showcasing successful use cases.* Enhance Collaboration: Foster open communication between platform teams and other teams. Avoid rigid roadmaps and be adaptable to changing needs to prevent barriers and build stronger internal relationships.* Manage Cognitive Load: Be mindful of the cognitive load on your teams. Simplify processes and reduce unnecessary complexities to enhance productivity and efficiency.* Use Tools to Measure Cognitive Load: Implement tools like Teamperature to assess the cognitive load on your teams regularly. Use the insights to identify and mitigate factors contributing to cognitive overload.* Leverage Experienced Product Managers: Ensure experienced product managers are part of your platform team. They can balance long-term goals with the flexibility needed to adapt to the evolving needs of internal users.I think the uncommon takeaway here is #9 in that platform teams should treat their platform as a product. Product Managers like and Marty Cagan are doing great work in laying out the roadmap for product management. Did you end up checking out the reliability workstreams map I published last week?It's free and can help you stay focused on the right priorities at work.Check it out via this link This is a public episode. If you would like to discuss this with other subscribers or get access to bonus episodes, visit read.srepath.com

I got the inside word from Manuel Pais, co-author of the seminal Team Topologies book, to explain in a 2-part series about 2 of the most relevant team topologies for reliability work. In this first part, we will talk about enabling teams.A quick refresher on what enabling teams doIn the team topologies context:Enabling teams help stream-aligned teams (product or feature teams) to overcome obstacles and improve their capabilities in specific areas.This kind of team is available to provide expertise, guidance, and support to other teams working to adopt new technologies, practices, or skills.In other news…This podcast has a new nameWhat more a fitting moment to announce renaming the SREpath podcast to “The Reliability Enablers” podcast?This name change reinforces our quest to demystify and enable reliability efforts so that more organizations successfully implement SRE principles and beyond. Before we get to the 8 takeawaysHere's something relevant to enabling reliability work — a reliability workflows map I've had in my private notes for years, now going public.What is a workstream?

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/

We are concluding our conversation with Jurgen Appelo on Versatile Organization Design using the unFIX Model, a pattern library that he authored. The unFIX Model is a simple toolbox that helps you with versatile organization design. It facilitates gradual change, dynamic teams, and an important role to play for managers. The pattern library is inspired by innovative companies, including Haier and Tesla, various agile scaling frameworks, and books such as Team Topologies, Dynamic Reteaming, and Organization Design.Jurgen is the founder of the Agile Management Company and the author of several best-selling books, including Management 3.0 and Startup, Scaleup, Screwup. With a background in computer science and management, he has been instrumental in transforming countless businesses worldwide.NOTE: The book that Jurgen Appelo refers to in the podcast is Networked, Scaled, and Agile: A Design Strategy for Complex Organizations by Amy Kates, Greg Kesler, et al. Visit us at https://www.ouragiletales.com/about

We are continuing our conversation with Jurgen Appelo on Versatile Organization Design using the unFIX Model, a pattern library that he authored. The unFIX Model is a simple toolbox that helps you with versatile organization design. It facilitates gradual change, dynamic teams, and an important role to play for managers. The pattern library is inspired by innovative companies, including Haier and Tesla, various agile scaling frameworks, and books such as Team Topologies, Dynamic Reteaming, and Organization Design.Jurgen is the founder of the Agile Management Company and the author of several best-selling books, including Management 3.0 and Startup, Scaleup, Screwup. With a background in computer science and management, he has been instrumental in transforming countless businesses worldwide.NOTE: The book that Jurgen Appelo refers to in the podcast is Networked, Scaled, and Agile: A Design Strategy for Complex Organizations by Amy Kates, Greg Kesler, et al. Visit us at https://www.ouragiletales.com/about

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

We are continuing our conversation with Jurgen Appelo on Versatile Organization Design using the unFIX Model, a pattern library that he authored. The unFIX Model is a simple toolbox that helps you with versatile organization design. It facilitates gradual change, dynamic teams, and an important role to play for managers. The pattern library is inspired by innovative companies, including Haier and Tesla, various agile scaling frameworks, and books such as Team Topologies, Dynamic Reteaming, and Organization Design.Jurgen is the founder of the Agile Management Company and the author of several best-selling books, including Management 3.0 and Startup, Scaleup, Screwup. With a background in computer science and management, he has been instrumental in transforming countless businesses worldwide.NOTE: The book that Jurgen Appelo refers to in the podcast is Networked, Scaled, and Agile: A Design Strategy for Complex Organizations by Amy Kates, Greg Kesler, et al. Visit us at https://www.ouragiletales.com/about

Este conteúdo é um corte do nosso episódio: “#200 - "Team Topologies": criando estruturas e times de alta confiança”. Nele, os crafters da dti digital Gabriel Naves, Arquiteto de Software e Angela Duarte, Tech Manager, explicam o conceito de “Topologia de Times” apresentado no livro “Team Topologies”, de Matthew Skelton e Manuel Pais. Essa, inclusive, é uma técnica bem utilizada que pode virar a chave de um negócio que não está caminhando bem com seus resultados. Ficou curioso? Então, dá o play! Quer conversar com Os Agilistas? É só mandar sua dúvida/sugestão na nossa página do Linkedin ou pelo e-mail osagilistas@dtidigital.com.br que nós responderemos em um de nossos conteúdos! Nos acompanhe pelas redes sociais e assine a nossa newsletter que chega todo mês com os assuntos quentes do agilismo através do site.See omnystudio.com/listener for privacy information.

We are continuing our conversation with Jurgen Appelo on Versatile Organization Design using the unFIX Model, a pattern library that he authored. The unFIX Model is a simple toolbox that helps you with versatile organization design. It facilitates gradual change, dynamic teams, and an important role to play for managers. The pattern library is inspired by innovative companies, including Haier and Tesla, various agile scaling frameworks, and books such as Team Topologies, Dynamic Reteaming, and Organization Design.Jurgen is the founder of the Agile Management Company and the author of several best-selling books, including Management 3.0 and Startup, Scaleup, Screwup. With a background in computer science and management, he has been instrumental in transforming countless businesses worldwide. NOTE: The book that Jurgen Appelo refers to in the podcast is Networked, Scaled, and Agile: A Design Strategy for Complex Organizations by Amy Kates, Greg Kesler, et al. Visit us at https://www.ouragiletales.com/about

Join our slack channel!https://agileembeddedslack.slack.com/   You can find Jeff at https://jeffgable.com.You can find Luca at https://luca.engineer.

We are kicking off our new season with Jurgen Appelo. Our conversation with Jurgen centers around Versatile Organization Design using the unFIX Model, a pattern library that he authored. The unFIX Model is a simple toolbox that helps you with versatile organization design. It facilitates gradual change, dynamic teams, and an important role to play for managers. The pattern library is inspired by innovative companies, including Haier and Tesla, various agile scaling frameworks, and books such as Team Topologies, Dynamic Reteaming, and Organization Design.Jurgen is the founder of the Agile Management Company and the author of several best-selling books, including Management 3.0 and Startup, Scaleup, Screwup. With a background in computer science and management, he has been instrumental in transforming countless businesses worldwide. NOTE: The book that Jurgen Appelo refers to in the podcast is Networked, Scaled, and Agile: A Design Strategy for Complex Organizations by Amy Kates, Greg Kesler, et al. Visit us at https://www.ouragiletales.com/about

In today's episode, we are joined by João Rosa and Trond Hjorteland, two organizational consultants with a unique point of view, who take us through the depth of Open Systems Theory, and what it means to be socio-technical practitioners, passionate about transitioning democratic organizations to fast-flowing operational models.  With many years of experience in large and complex contexts, they delve into what it means to create a collaborative and democratic organization, and how to balance mission, business outcomes, and cognitive load. Join us on this episode, as we debate the role of “purpose”, entrepreneurship, and autonomy and learn how to avoid the creation of agile bureaucracies. Tune in, and get inspired. In the conversation with Rosa and Hjorteland we started from an original question that Simone threw out at a small conference recently: how do we avoid building Agile Bureaucracies?  What does it mean to develop a business that achieves agility without having to exert total control on flows and processes? With increasingly complex and dynamic environments, it becomes pivotal for organizations to recognize and adapt to change, if not stay ahead of it and rigidities are more than dangerous - even the cultural ones. Emphasizing learnings from different methodologies like Open Systems Theory, Domain Driven Design, and Team Topologies; our guests advocate a team-centered, and democratic approach over industrial and hierarchical practices.  A unique episode to look out for.  Tune in.   Key Highlights

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.

An independent tech consultant with over 20 years, Susanne Kaiser joins the podcast and shares her insights on what makes a robust socio-technical system. Integrating takeaways from different approaches like Wardley Mapping, Domain Driven Design, and Team topologies, she helps the listeners understand how to mold systems into ones that are adaptable to change, how to invest in the right things, and how to avoid wasting resources on things that do not make a competitive advantage.  We further touch upon topics like building in bounded contexts and unbundling the right way. This episode has an ocean of information, which can help listeners achieve better strategic awareness of their company, products, and initiatives. Grab a coffee cup and a notebook and listen.  In this episode, Susanne takes us through what it means to operate a business with a strategic perspective.  An organization's evolutionary journey goes through high levels of change and uncertainty. With insights on bounded contexts and evolution, Susanne takes us through how you can enforce modularity and cohesion among the different parts of the system, to deal with such a journey. With significant experience working as a consultant in the software development world, Susanne shares real-world examples of how organizations can create architecture and team structures that are dynamic and play to an organization's competitive advantage.   Key Highlights

Enabling Teams bilden einen der vier grundlegenden Teamtypen innerhalb des Frameworks von 'Team Topologies'. Über diesen Teamtyp sprechen Anja und Sven mit Michael, der kürzlich das dazugehörige Buch von Matthew Skelton und Manuel Pais ins Deutsche übersetzt hat. Es geht darum, was Enabling Teams auszeichnet, welche spezifischen Aufgaben sie innerhalb von Organisationen erfüllen können und auf welche Schlüsselkompetenzen es bei den Enablern besonders ankommt, um andere Teams im Erlernen und der Anwendung neuer Fähigkeiten zu unterstützen.

Matthew Skelton is co-author of "Team Topologies: organizing business and technology teams for fast flow". He is Head of Consulting at Conflux and specialises in Continuous Delivery, operability, and organisation dynamics for modern software systems. In this conversation with Dave, he talks about the ecosystem necessary to build and nurture software, and the wide range of topics that impact on the effectiveness, and performance of development teams. The approach that his book "Team Topologies" describes is to use team structure as a tool, guided by the idea of managing the cognitive load of the team. This talk ranges from how to deal with the complex adaptive system that we inhabit when undertaking software development, to the structure of software development being more like an ant colony than an organised, predictable hierarchy.xx⭐ PATREON: Join the Continuous Delivery community and access extra perks & content!

Let's put Team Topologies to use. What can it tell us about why some team structures work out, why some struggle, and when we should switch our organisations to be more effective? Mon-Chaio and Andy scrutinise a software project through the lens of the interaction modes, sensing, and triggers for change that the book introduces. They find that it provides a rich vocabulary to talk about the ills and strengths of your tech organisation. References Team Topologies: https://teamtopologies.com/book TTL Podcast BART episode: https://spotifyanchor-web.app.link/e/MY0ihq1VlGb --- Send in a voice message: https://podcasters.spotify.com/pod/show/tactics-tech-leadership/message

In the most recent episode of The Remotely One Podcast, hosts Rick Haney and Kaleem Clarkson invite Manuel Pais, co-author of the book "Team Topologies," for a lively conversation that transcends the technical realm! This delightful discussion spans from Manuel's affection for cheesy 80s music to his intriguing background, originating from Lisbon, Portugal, and presently residing in Madrid, Spain.With a master's degree in computer science from Carnegie Mellon and a noteworthy stint as the former editor for InfoQ, Manuel's extensive career provides the backdrop for an insightful discussion. The exchange leads to a profound reflection on Manuel's experience, sharing valuable lessons learned as an editor and underscoring the significance of connecting with influential figures in the tech industry.A pivotal question arises regarding Manuel's transition from his established career to focusing on his co-authored book, "Team Topologies." Manuel's motivation behind the book addresses critical issues related to team dynamics, interactions, and leadership in a technical environment. Our guest emphasizes the importance of recognizing and resolving non-technical problems within teams for enhanced motivation and engagement.The conversation delves deep into the challenges faced by remote teams, particularly during the COVID-19 pandemic. Manuel discusses how the shift to remote work brought existing issues to the forefront, with teams grappling to collaborate effectively. He underscores the importance of intentionally addressing problems related to team interactions, dependencies, and communication in a remote environment.The animated trio also touches on the evolving attitudes toward remote work, workplace flexibility, and goal setting. Manuel reflects on the current trend of remote work and suggests rethinking the purpose of in-person meetings, focusing on goal alignment during face-to-face interactions, opening a space to discuss the broader landscape of remote work, touching on transparency, intentional communication, and knowledge sharing among teams.Venturing into more personal territory, Manuel shares insights into his journey as an author, highlighting the unexpected growth in his communication skills influenced by his work at InfoQ and participation in conference talks. Before concluding, Manuel introduces his latest project, a workbook on remote team interactions based on concepts from "Team Topologies." He elucidates the specific challenges of remote work and provides practical techniques and templates to help teams navigate these challenges.A comprehensive exploration encompassing Manuel Pais's background, his experiences at InfoQ, insights from "Team Topologies," and perspectives on the challenges and solutions for remote team collaboration. The engaging and informative discussion positions it as a valuable resource for professionals navigating the complexities of the remote work environment. Don't miss out and get ready to take notes, Manuel is spilling golden nuggets in this installment!Learn more about Manuel:LinkedIn: https://www.linkedin.com/in/manuelpais/TeamTopologies Webpage: https://teamtopologies.com/Get the Workbook: https://teamtopologies.com/workbook

In this episode of Cloud Unplugged, Jon and author Matthew Skelton discuss the book Team Topologies and the complexities of team management in the modern workplace. Matthew Linkedin: https://www.linkedin.com/in/matthewskelton/

This week we welcome to the show Manuel Pais who is the co-author of "Team Topologies: Organizing business and technology teams for fast flow". Manuel will walk us through some of the concepts that enable companies to deliver value more frequently and effectively to their customers by organizing their teams in an optimized way.

BONUS: The Surprising Costs Of Outsourcing Software Development, And Effective Outsourcing Strategies with Douglas Squirrel 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. Squirrel delves into the misconception that outsourcing engineers overseas automatically leads to cost reduction in software organizations. He explains that while the salary expenses might be lower for offshore teams, other costs come into play.  He illustrates the situation with an example involving two tech teams, one located onshore in California, USA, and the other in India. The Indian team had one quarter the salary of the onshore team, prompting the question of why the more expensive US engineers are retained. The discussion highlights the importance of evaluating the genuine costs of offshoring beyond just salaries. Additionally, Squirrel raises the question of which team is more productive and points out the time zone difference as a significant factor impacting communication and coordination.  Surprisingly, when the overall costs are tallied, they often don't exhibit a substantial difference due to various expenses that often get ignored. The aspect of speed of delivery is also examined, and the suggestion is made to have a local representative support the outsourced team to facilitate smoother communication. Beyond the operational costs, we also talk about how difficult it is to maintain effective communication between teams, and the cost of frequent international travel.  Squirrel emphasizes the necessity of having experienced individuals in the offshore team, highlighting that it's even more important to hire very senior people in offshore teams. We also discuss how hard it is to find accommodation for senior engineers that move to the offshore locations. Effective Offshoring Patterns Squirrel delves into the patterns that can enhance the effectiveness of offshoring. The concept of near shoring is introduced, especially when there are significant challenges in finding talent close to the headquarters.  The discussion then pivots to the importance of team organization for offshoring success. The idea of cross-functional teams or feature teams is introduced as an effective approach. Squirrel references FeatureTeams.org, emphasizing that these teams possess the flexibility to work on any feature, thereby minimizing communication dependencies.  A strategy to integrate feature teams across regions is presented through the "ambassador pattern," which involves designated individuals who bridge the communication gaps between teams in different locations. Optimizing Communication and Resources for Remote Teams We also discuss how to optimize communication and resources for remote teams. Squirrel introduces the notion that outsourcing and offshoring may be a possible solution to solve the talent problem by tapping into global talent pools. He offers practical tips, such as conducting all meetings online and making it a rule to always include offshore team members. Creating opportunities for "osmotic communication" – the exchange of information through casual interactions – is suggested as a means to foster team cohesion across distances. Recommended Resources The episode concludes with a list of recommended resources for further exploration. These include Stack Overflow's own experience about fully remote work, Squirrel's own website (DouglasSquirrel.com), Team Topologies (a topic which has been presented on the podcast by its authors Matthew Skelton and Manuel Pais), the FeatureTeams.org website, and the virtual office platform Sococo. Throughout the conversation, Squirrel provides insights into the complexities of offshoring, shedding light on the multifaceted considerations that impact its success. From cost evaluation to effective team organization and communication strategies, the episode offers a comprehensive overview of the nuances surrounding offshore software development teams. About Douglas Squirrel Squirrel has been coding for more than forty years and has led software teams for twenty. He uses the power of conversations to create dramatic productivity gains in technology organisations of all sizes. Squirrel's experience includes growing software teams as a CTO in startups from fintech to biotech to music, and everything in between. He lives in Frogholt, England, in a timber-framed cottage built in the year 1450. You can link with Douglas Squirrel on LinkedIn and connect with Douglas Squirrel on his website. 

I had the pleasure of speaking again with Jurgen Appelo in regards to his work on the Unfix model.  He and his team have taken the work on Team Topologies and extended it with a number of organizational patterns.  As he says they are like organizational lego blocks that allow you to visualize and experiment with different organizational structures when you are designing an new operating model for your teams.  He has integrated a lot of tools from his Management 3.0 work as well and the community resources are a treasure trove of goodies. I hope you enjoy the talk as much as I did. https://unfix.com/

Takunda Noha: How to Convince the Organization for Cross-Functional Collaboration to overcome Missing Deadlines and Integration Problems 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, the focus is on the challenges faced in a delivery factory where multiple teams are required to collaborate in order to deliver a feature. However, these teams were siloed and lacked collaboration, leading to missed deadlines and integration problems. The first step was to gather facts and data to identify the causes of delays. The next challenge was to create a vision for a cross-functional team, but faced resistance from other teams. Persistence was key in convincing the organization to adopt a cross-functional approach. Although the team faced initial failures, the advice is to have a thick skin, learn from failures, and try again. To help understand and navigate this type of challenges, Takunda recommends the book is Team Topologies by Skelton and Pais, who have been previous guests on the podcast.    As Scrum Master we work with change continuously! Do you have your own change framework that provides the guidance, and queues you need when working with change? The Lean Change Management framework is a fully defined, lean-startup inspired change framework that can be used as the backbone of any change process! You can buy Lean Change Management the book at Amazon. Also available in French, Spanish, German and Portuguese.   About Takunda Noha Takunda is a seasoned change agent. He specializes in turning dysfunctional teams into high performing teams. You can link with Takunda Noha on LinkedIn.

BONUS: From Scrum Master to Engineering Lead, how to prepare the transition with Tim Bourguignon We start this episode, reflecting on Tim's journey of realizing the importance of working collaboratively and embracing agile methodologies. Tim noticed early on that he drifted to teaching and providing assistance to others rather than actively developing software. After a while, he moved to consulting in Agile, and in that role, he noticed recurring patterns and struggled with unclogging processes that seemed to be missing something crucial. Over time, frustration set in. He felt like he was fighting an uphill battle and highlighted the disruptive nature of Agile, which aimed to uncover and solve problems but often revealed bigger and deeper underlying issues. The big problem with Agile adoption, and what we can do to prepare for it With time and experience, Tim realized that leadership was a crucial factor in the team's success. He observed a recurring pattern where leadership was either blocking progress or not fulfilling their role effectively. This realization led him to recognize the significance of leadership's involvement and the impact it had on the overall performance of the team.  From developer, to coach, and finally to leader: learning to help teams at all levels of the organization Tim shares his journey at WeMaintain and discusses the challenges of scaling while maintaining agility. Before joining, and during the interview process, Tim already sought to identify the problems he could help solve but couldn't pinpoint a specific issue. His boss expressed concerns about managing fast growth while staying agile. Initially, WeMaintain had two teams working efficiently from a backlog, releasing frequently, and measuring their progress. But, they wanted to grow the company without resorting to a traditional approach of multiple teams working on the same problem, which often led to communication issues. Instead, they advocated for compartmentalized teams with strong ownership and defined success metrics for each team based on specific business streams. Each team had the necessary skills and accountability to achieve their success metrics, ensuring a shared responsibility for success. From coach to leader, and the critical lessons learned on the way Tim reflects on the differences between his current approach and what he observed in the past, when he was the coach trying to help teams and organizations. He emphasizes the importance of taking personal responsibility as a leader when facing problems within a team. Previously, their clients would assume that the leaders were right and focused only on changing the teams, and he wanted to avoid that anti-pattern at all costs. Tim shares the tip of starting with leadership and establishing a clear vision, emphasizing the impact of lacking a clear vision and passionate individuals on the organization. When it comes to reflecting on our performance, Tim recommends evaluating oneself against the 12 principles of the Agile Manifesto and highlights the necessity of enabling developers to communicate directly with customers to foster agility. Scaling with Agility: Building Compartmentalized Teams and other strategies for growing companies, and staying Agile Tim's current focus is on stream-aligned teams and metrics. Tim recommends the book "Team Topologies", whose authors have been guests on the podcast. Tim also shares the tip of asking teams to create a portfolio of metrics that demonstrate they are working on the right things. Various teams have found interesting metrics to track their progress. The PDCA cycle and DORA (DevOps Readiness Assessment) metrics are mentioned. The guest highlights a positive sign of organizational health, with a rate of 1.5 deployments per day across the entire product group. They suggest having frequent discussions with people throughout the organization and implementing practices like showcasing Monday morning deliveries and sharing post-release messages on Slack as early documentation for stakeholders. The book "Accelerate" is also recommended for further insights into metrics. In this final segment, we also refer to Extreme Programming.

Oguz Ozyurt: Helping Scrum Teams by Establishing Trust and Shared Understanding with Product Owners 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 segment, guest Oz emphasizes that we all work in a complex environment and are change agents. Oz shares a story about a team that faced problems with its product owner, who would add stories to the sprint backlog without refinement and interrupt the team even on the last day of the iteration. As a result, the team lost trust in the PO. To address this challenge, Oz recommends making sure the team has an agreement on how to bring new stories into an ongoing sprint and discussing the team agreement with the PO. Oz also suggests bringing up the topic in the retrospective when the PO introduces a surprise story. Oz acknowledges that these conversations can be difficult, especially when the PO is a good friend of the team's manager, but emphasizes the importance of building trust and ensuring shared understanding. Featured Book of the Week: Leading Change by John Kotter In this segment, Oz recommends "Leading Change" by John Kotter, which outlines eight steps for organizational transformation and is useful for anyone looking to apply these steps to a change process. Oz also suggests "Start with Why" by Simon Sinek for its insights on inspiring others and finding the purpose behind the work. Finally, Oz recommends "Team Topologies" which provides guidance on building and managing modern teams, a key responsibility for Scrum Masters. The authors of Team Topologies, Matthew Skelton and Manuel Pais, have been previous guests on the podcast.   About Oguz Ozyurt Oz came from a technical background, and has worked across multiple industries, applying agile practices toward the technical and non-technical areas. He is passionate about agile, he has leveraged his passion for delivery value and agile practices by coaching, teaching, mentoring many teams to transform from traditional software development life cycle to Agile principles and practices. You can link with Oguz Ozyurt on LinkedIn.

Effective software teams are essential for any organization to deliver value continuously and sustainably. But how do you build the best team organization for your specific goals, culture, and needs?That's the question posed by authors Matthew Skelton and Manuel Pais in their highly-acclaimed book, Team Topologies: Organizing Business and Technology Teams for Fast Flow.On this week's episode of Dev Interrupted, we revisit Dan's 2021 conversation with Matthew and Manuel. Since first airing, their book has received broad recognition for its step-by-step advice, approach to team patterns and interactions, and compelling analysis of the communication pathways that lead to organizational success. We think this episode is as relevant today as it was when it was released - and we hope you agree!Show Notes:Learn more at teamtopologies.comCheck out the Team Topologies Academy: https://academy.teamtopologies.comRegister for the Dev Interrupted Live Stream on April 4th and 5th. Support the show: Subscribe to our Substack Follow us on YouTube Review us on Apple Podcasts or Spotify Follow us on Twitter or LinkedIn Offers: Learn about Continuous Merge with gitStream Want to try LinearB? Book a Demo & use discount code "Dev Interrupted Podcast"