Hardware Podcasts

Project Management Dysfunctions - Part 1

The Pragmatic Embedded Podcast · 21 Jun 2022 · 43m

What this episode covers

Jeff Gable and Luca discuss common project management dysfunctions in embedded systems, focusing on the anti-pattern of sticking to inefficient processes because teams feel they are 'close to done.' They advocate for small, continuous improvements like unit testing and hardware abstraction layers to reduce friction between hardware and software teams. The hosts also address the danger of promising fixed dates without credible estimation, explaining the project management triangle and the importance of managing uncertainty by tackling high-risk items first.

Most relevant to

early-stage companies and companies scaling up

Topics

Mentioned

Also
Agile Embedded Podcast, Jeff Gable, Luca, The Phoenix Project, Part Unlimited, Luca.engineer, Agile Embedded Academy, Embedded AI Podcast

Related episodes from other shows

Other shows on the same ground, closest first.

  • Embedded.fm · 1h 27m

    402: We Are a Lazy Species

    Chris Svec of iRobot and Phillip Johnston of Embedded Artistry join hosts Elecia and Christopher White to debate the value and methods of estimating software schedules. They discuss why estimation is difficult, the necessity of feedback loops for improvement, and how to handle fixed-bid projects with clients. The conversation covers the role of trust in engineering teams, the use of Gantt charts for dependency management, and the analogy of estimating travel time to justify software estimates.

    Careers & educationLeadership, teams & culture
    7 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 Amp Hour · 1h 05m

    Occam's Engineering Razor

    Dave Jones and Chris Gammell discuss the pitfalls of over-complicating troubleshooting, illustrated by Dave's solar panel saga where a tiny coax cable shadow caused a 20% power drop. They explore the psychology of engineering resilience, referencing Ben Krasnow's persistence, and debate the efficacy of project management methodologies like Gantt charts versus agile demos in hardware development. The conversation also covers the semiconductor industry, analyzing Intel's foundry ambitions and the challenges of automotive chip sourcing.

    Debugging & failure analysisChips, FPGAs & semiconductors
    6 chapters

  • Embedded.fm · 1h 08m

    183: Robots Having Nervous Breakdowns

    Professor Philip Koopman of Carnegie Mellon University and co-founder of Edge Case Research discusses the critical importance of formal peer reviews in embedded software development. He argues that while informal reviews are insufficient, structured Fagan-style inspections find the majority of bugs for a fraction of the total project cost, effectively making high quality 'free' by preventing expensive late-stage fixes. Koopman explains that cultural resistance often stems from a misunderstanding of progress, where managers equate 'code complete' with actual completion, leading to dangerous shortcuts in safety-critical and mission-critical systems.

    Embedded firmwareQuality & yield
    8 chapters

  • Embedded.fm · 1h 01m

    38: Blame the Monkey

    Elecia White and producer Chris White discuss strategies for debugging 'insurmountable' problems in embedded systems, ranging from race conditions and stack overflows to non-reproducible hardware issues. They advocate for methodical approaches such as drawing system diagrams, writing detailed emails to clarify thoughts, and using the scientific method to isolate variables. The conversation also covers the importance of logging, reverting to known good code, and knowing when to walk away or accept a bug as a feature.

    Debugging & failure analysisEmbedded firmware
    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.