Introducing Agile at John Deere with Joe Schneider

The Pragmatic Embedded Podcast · 27 Apr 2021 · 58m

What this episode covers

Joe Schneider, founder of Dojo 5, recounts his experience modernizing firmware development at John Deere, where he led a grassroots technical transformation from a legacy Star Team environment to Git, Cruise Control, and eventually Agile methodologies. He details how overcoming specific engineering pain points, such as 45-minute build times and inefficient GPS simulators, built the credibility needed to advocate for organizational changes like cross-functional teams and external coaching. Schneider now runs Dojo 5, which helps other embedded companies bridge the gap between web/mobile practices and firmware development through their EmbedOps platform and services.

Mentioned

Companies
Dojo 5, John Deere
Products
EmbedOps
Tools
Star Team, Cruise Control, Git, LabVIEW
Also
SAFe

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.fm · 1h 17m

    395: I Can No Longer Play Ping Pong

    Tyler Hoffman, co-founder of Memfault, explains how his team at Pebble and later Fitbit transformed firmware development by standardizing developer environments, optimizing build systems, and automating debugging. He details the shift from slow, sequential IAR builds to parallel GCC builds using Make and Conda, which reduced build times from 18 minutes to 2 minutes. Hoffman also describes building web applications and GDB Python scripts to enable remote debugging of field crashes without physical debuggers. The discussion highlights the importance of dedicated developer productivity roles and the evolution of tools from one-off scripts to robust, company-wide platforms.

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

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