Agile + 20

Oxide and Friends · 27 Jul 2021 · 1h 11m · Episode 9

What this episode covers

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.

Mentioned

Companies
AWS, Delphix, Sun Microsystems
Products
S3, Solaris
Also
Agile Manifesto, Extreme Programming, Scrum

Other shows on the same ground, closest first.

  • The Pragmatic Embedded Podcast · 41m

    Agile Manifesto Part 2

    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.

  • The Pragmatic Embedded Podcast · 39m

    Agile in Small Teams

    Hosts Jeff Gable and Luca Gable discuss whether agile methodologies are suitable for small teams and solo developers in embedded systems. They argue that while specific ceremonies like daily stand-ups may be unnecessary, core principles such as short feedback loops and automation remain critical. The conversation highlights the challenges of working in contract development firms with rigid, spec-driven contracts and emphasizes that trust between developers and customers is the foundation of successful agile adoption.

  • 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 Pragmatic Embedded Podcast · 37m

    Agile Manifesto Pt. 1

    Hosts Jeff Gable and Luca Engineer discuss the first two principles of the Agile Manifesto, specifically 'Individuals and interactions over processes and tools' and 'Working software over comprehensive documentation,' with a focus on safety-critical industries like medical devices. They argue that while processes and documentation are necessary for regulatory compliance (FDA, MDR) and safety, they must be useful and not become 'cargo cult' rituals that hinder development. The conversation highlights the danger of overly granular specifications and emphasizes that code, infrastructure, and user interfaces can serve as valuable forms of documentation if they are clear and maintained.

  • The Pragmatic Embedded Podcast · 44m

    Project Management Dysfunctions - Part 2

    Jeff Gable and Luca discuss project management dysfunctions in embedded product development, focusing on treating estimates as truths, introducing 'capital A Agile' without actual agility, and forgetting to iterate on processes. They highlight the danger of 'accidental agility' in large enterprises, where cross-functional task forces are disbanded after solving a crisis, and praise a client achieving 2-week hardware iteration cycles. The hosts argue that teams should prioritize high-value or high-risk items first and use mechanisms like story points or flow-based approaches to manage work effectively without rigid cargo-cult practices.

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