Hardware Podcasts

Agile vs. V Model

The Pragmatic Embedded Podcast · 30 Mar 2023 · 45m

What this episode covers

Hosts Jeff Gable and Luca engineer discuss reconciling the V-model with Agile development, particularly for safety-critical industries like medical devices. They argue that the V-model correctly identifies necessary activities but fails when applied as a long-cycle waterfall process. The speakers advocate for treating Agile as a series of mini-Vs, emphasizing rapid iteration, automated documentation, and breaking down silos between engineering and controlling departments to manage risk effectively.

Most relevant to

established companies

Topics

Mentioned

Also
Jeff Gable, Luca, FDA, TIR 45, Cal Vegas, Lean Startup, DevOps

Related episodes from other shows

Other shows on the same ground, closest first.

  • Global Medical Device Podcast · 38m

    Waterfall vs. Agile: Battle of the Product Development Methodologies

    Jon Speer, host of the Global Medical Device Podcast, interviews Devon Campbell, founder and CEO of Prodct, to debunk myths surrounding waterfall and agile methodologies in medical device development. They argue that the FDA's Design Control Guidance is often misinterpreted as mandating a rigid waterfall process, when it merely illustrates one possible approach. Campbell and Speer emphasize that successful product development relies on defined processes, traceability, and hybrid models rather than adherence to a specific named methodology. They advocate for 'documenting early and revising often' to manage the high costs of late-stage changes in electromechanical hardware.

    Validation & product-market fitDesign for manufacturing & NPI
    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 · 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

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

    Scaling productionLeadership, teams & culture
    1 chapters

  • Embedded.fm · 1h 09m

    67: Software for Things That Can Kill People

    Hosts Chris White and Elecia White discuss the rigorous regulatory processes for safety-critical software, drawing on their experiences with the FAA (DO-178B) and FDA (510k, PMA) for medical devices and avionics. They explain how hazard analysis determines certification levels, the necessity of extensive documentation and traceability, and the tension between agile development and waterfall compliance. The conversation highlights the ethical responsibility of engineers to push back against unsafe deadlines, the use of hardware compartmentalization (FPGAs, voting systems) to ensure safety, and the legal liabilities associated with product failures.

    Certification & complianceMechanical engineering
    8 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.