Hardware Podcasts

Agile is Old-Fashioned Engineering

The Pragmatic Embedded Podcast · 30 Mar 2021 · 27m

What this episode covers

Jeff Gable and Luca argue that Agile is not a new software fad but rather 'old-fashioned engineering' principles like rapid prototyping and feedback loops that have always existed in fields like aeronautics. They cite Lockheed Skunk Works and the Apollo program as historical examples of iterative development, contrasting them with the 'waterfall' illusion often forced onto embedded systems. The hosts discuss how embedded teams can apply these principles by decoupling software and hardware iteration cycles through hardware abstraction layers and simulators to reduce friction.

Most relevant to

early-stage companies and companies scaling up

Topics

Mentioned

Companies
Lockheed Skunk Works
Products
SR 71, F 117
Also
Agile Manifesto, FDA, Apollo Space Program

Related episodes from other shows

Other shows on the same ground, closest first.

  • Embedded.fm · 53m

    16: Democracy Is the Worst Form of Government

    Curtis Cole, a veteran embedded systems engineer and former VP of Engineering at Leapfrog, argues that Agile methodologies like Scrum and Test-Driven Development (TDD) are effective for embedded software when adapted to hardware constraints. He explains how user stories, sprints, and story points allow teams to manage unknown requirements and deliver incremental, usable prototypes without compromising the final product's stability. Cole emphasizes that Agile is merely a process tool; success depends on hiring skilled engineers who prioritize quality, testing, and modular design over mere speed.

    Embedded firmwareLeadership, teams & culture
    8 chapters

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

    Embedded firmwareLeadership, teams & culture
    6 chapters

  • Embedded.fm · 1h 05m

    53: Being a Grownup Engineer (Repeat)

    Jack Ganssle, author of 'The Art of Designing Embedded Systems' and 'The Embedded Systems Dictionary', argues that embedded software development has failed to adopt true engineering discipline, relying on 'heroics' rather than process. He cites the Toyota unintended acceleration case, where Michael Barr identified 11,000 global variables, as evidence of the catastrophic costs of poor software practices. Ganssle advocates for rigorous requirements gathering, static analysis tools like LDRA and Spark, and metrics-driven benchmarking to reduce debugging time and improve code quality. He contrasts this disciplined approach with the 'hacker' and 'maker' cultures, emphasizing that safety-critical systems require proven processes rather than ad-hoc coding.

    Embedded firmwareDebugging & failure analysis
    10 chapters

  • Embedded.fm · 1h 03m

    53: Being a Grownup Engineer

    Jack Ganssle, author of 'The Art of Designing Embedded Systems' and long-time embedded industry expert, argues that firmware engineers must adopt disciplined engineering practices rather than relying on 'heroic' hacking. He discusses the necessity of requirements gathering, design reviews, code inspections, and rigorous testing to ensure safety and reliability, citing the Toyota unintended acceleration case as a failure of process. Ganssle advocates for measuring metrics like bug rates and lines of code to benchmark performance, and critiques the misuse of Linux in deeply embedded systems and the confusion between the maker movement and professional engineering.

    Embedded firmwareCareers & education
    10 chapters

  • The Hardware Entrepreneur · 50m

    #010 - How to think like Elon Musk - Scrum for Hardware, with Joe Justice of WIKISPEED and Scrum Inc, USA

    Joe Justice, CEO of Team WIKISPEED and President of Scrum @ Hardware at Scrum Inc, explains how the Scrum framework accelerates hardware innovation by replacing rigid waterfall planning with short, adaptive sprints. He contrasts the traditional phase-gate model with agile practices, citing Tesla’s adoption of Scrum and Team WIKISPEED’s own global, open-source CAD collaboration as examples of scaling agile in physical product development. Justice identifies outdated perceptions of tooling costs and restrictive corporate policies as the primary barriers to wider Scrum adoption in hardware.

    Scaling productionLeadership, teams & culture
    9 chapters

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.