Agile in embedded usually gets dismissed early: you cannot iterate, the argument goes, when the hardware arrives in week twelve. That is true of textbook Scrum and false of agile applied with the constraints in mind. The goal was never two-week sprints for their own sake; it is shortening the distance between a decision and the feedback that tells you it was wrong — even when part of the system is still silicon on order.
These courses come out of real embedded transformations, the same ground our trainers cover on the Agile Embedded podcast. They run from kickstarting a team that has never worked this way, through Scrum Master and requirements engineering for hardware-software products, to the product-owner and leadership roles that keep a transformation from sliding back the moment a deadline tightens.