but then, what is Agile?
If you are a SW dev you would know it.
If you are a HW dev then an analogy is that most HW engineers work according to the V mode. Lets say you have to make a flashlight. You think of the architecture, design, thermo , physical layout, board layout, chips, implement, test, system test , deliver.
And you deliver one big bang product. And guess whst you're customer does not like it, he wanted more light. So you have to start from scratch.
If you would do this Agile (if possible) then you would first build for instance the led driver and led, test if this is good enough deliver to your customer or other stakeholder , get his feedback if stakeholder happy vontinue, if not adjust and deliver again till stakeholder is happy, now do thermal design, then battery charge circuit etc etc. So you deliver many small parts of the total product and combine it over time to the end product.
Ofcourse this is a flawed example but in theory instead of doing the entire v-model waterfall style in one big bang you do it in a lot of small v-models, that way your customer/stakeholder is continuously informed and gets part of the evaluation that is your feedback.
And yes in software esp. apps and gui like software this works great because you can adapt quickly to the wants of your dtakeholder and if time or money runs out the stakeholder de ides what features to drop or implement later then the first official release.