Why Cross-Functional Product Teams Rule

The Pragmatic Embedded Podcast · 19 Jan 2021 · 33m

What this episode covers

Jeff Gable and Luca discuss why cross-functional product teams are superior to traditional siloed departments for developing embedded systems. They argue that functional silos create communication barriers, conflicting goals, and slow feedback loops, whereas small, interdisciplinary teams enable faster iteration and better problem-solving. The hosts share anecdotes from their careers in aerospace, automotive, and medical device industries to illustrate the pitfalls of large corporate structures and the benefits of agile, product-centric organization.

Most relevant to

established companies

Topics

Mentioned

Companies
Boeing, Agile Embedded Academy
Also
Pragmatic Embedded Slack

Other shows on the same ground, closest first.

  • The Hardware Entrepreneur · 12m

    #064 - To transform or not to transform your hardware company to an all agile one next year, with Balint Horvath, Switzerland

    Host Balint Horvath discusses the necessity of agile transformation in hardware companies, citing examples like Tesla, Bosch, and Mercedes-Benz to illustrate the risks of rigid waterfall development. He details a Swiss high-tech company's shift from functional silos to cross-functional teams to improve synchronization and accountability. Horvath highlights specific Scrum tactics for hardware, such as modular design with defined interfaces and T-shaped skill development, while referencing Paulo Samicelli's book 'Scrum for Hardware'.

  • Product Startup · 15m

    225: Communication Silos for Product Design Stakeholders

    John Conafay, founder of Integrate, explains how compartmentalized communication tools solve the 'source of truth' problem in hardware development. Drawing from his background with aerospace startups and the US Air Force, he argues that siloing information protects intellectual property and reduces administrative overhead compared to disjointed toolchains like spreadsheets and email. He details how object-level permissions allow startups to scale from garage prototypes to enterprise manufacturing without losing data integrity or security.

  • The Amp Hour · 1h 26m

    Is This A Show?

    Chris Gammell and Dave Jones host Chris White and Alicia White of Embedded.fm to discuss the 256th episode milestone, the challenges of producing technical podcasts without visual aids, and the state of hardware conferences like Solid Con. The group debates the user experience of smartwatches, specifically the Pebble Time, focusing on the lack of out-of-the-box functionality and the industry trend of shipping incomplete firmware. They also touch on the importance of product management in ensuring quality and the frustrations engineers face when their technical concerns are ignored by management.

  • Embedded.fm · 1h 13m

    290: Rule of Thumbs (Repeat)

    Phillip Johnston, founder of Embedded Artistry, discusses his embedded systems consulting firm and his educational website, highlighting his focus on firmware engineering, code reviews, and robust software design. He explains how his company helps early-stage startups and medium-sized companies transition from prototypes to production, often by addressing firmware bottlenecks and implementing better testing and abstraction strategies. The conversation covers specific technical challenges, including the limitations of standard C++ threading libraries on embedded RTOSs like FreeRTOS and ThreadX, and the importance of risk analysis in complex systems, using the Boeing 737 MAX crashes as a case study for systemic failure.

  • Embedded.fm · 1h 23m

    440: Condemned to Being Perfect

    Elecia White and Chris White host a crossover episode with Jeff Gable and Luca Ingianni of the Agile Embedded podcast to debate the application of Agile principles to embedded systems. The group discusses redefining Agile as 'risk management through feedback loops' rather than rigid Scrum, and explores the challenges of scaling these practices in large enterprises versus small teams. They also tackle specific technical debates, including the role of unit testing, the definition of Minimum Viable Products (MVPs) for hardware, and the necessity of documentation in regulated industries like medical devices.

The summary, chapters and topics are generated from the episode’s audio by this directory, not written by The Pragmatic Embedded Podcast. The episode itself belongs to its publisher.