Agile Manifesto Part 2

The Pragmatic Embedded Podcast · 23 Mar 2022 · 41m

What this episode covers

Jeff Gable and Luca Engineer discuss the Agile Manifesto's principles of customer collaboration and responding to change, arguing that frequent working demos build trust more effectively than rigid contracts. They highlight the 'iron triangle' of project management, noting that fixing time and resources while allowing scope to flex is essential for success in both software and hardware development. The hosts emphasize that organizations must cultivate a culture that values learning from failures, citing examples from medical devices, aerospace, and chaos engineering to illustrate how shortening iteration cycles improves product quality.

Other shows on the same ground, closest first.

  • Oxide and Friends · 1h 11m

    Agile + 20

    Bryan Cantrill, Adam Leventhal, and a panel of software veterans including Tom Killalea, Tom Lyon, and Dan Cross discuss the 20-year legacy of the Agile Manifesto, arguing that while its core principles regarding customer focus are sound, the methodology has been corrupted by prescriptive 'cargo cult' rituals like rigid 2-week sprints and excessive estimation. They contrast these failures with successful implementations, such as the development of AWS S3, which utilized Agile pragmatically to provide engineers with uninterrupted focus and accountability through demos and retrospectives. The group concludes that Agile is not a silver bullet but a flexible framework that works best in high-trust environments where teams can adapt processes to their specific context rather than following dogma.

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

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

  • The Hardware Entrepreneur · 51m

    #048 - RERUN - How to think like Elon Musk - scrum for hardware, with Joe Justice of WIKISPEED and Scrum Inc, USA

    Joe Justice, President of Scrum @ Hardware at Scrum Inc. and CEO of WikiSpeed, explains how the Scrum framework accelerates hardware development by replacing rigid waterfall planning with short, iterative feedback loops. He contrasts the traditional phase-gate model with Scrum’s ability to adapt to market changes, citing Tesla’s adoption of agile as a key factor in its rapid scaling and success. Justice details how WikiSpeed scaled from a garage prototype to a global collaborative effort and discusses the specific obstacles to Scrum adoption in hardware, such as perceived tooling costs and outdated corporate policies.

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.