A: Most Agile practitioners apply Agile to pure software or software-centric development. You will find that most training and consulting firms as well as the majority of the Agile community shares this software-centric background,  hence focuses on Agile Software Development. We do not. We focus on Agile Product Development.

We apply the Agile phylosophy, principles, and practices to complex Systems and Product Development which includes all Engineering and non-Engineering domains necessary to create such systems. This includes Hardware, Software, Mechanical, Electrical, Scientific, Systems on the Engineering side, supply-chain and logistics on the Operational side, and the mapping of Agile and Stage-Gate processes at the Governance side. In other words, we apply and adopt Agile to complex Agile Product Development.

Agile Product Development addresses therefore a broader range of issues typically found in complex Systems and Product Development. For example, Agile Software Development suggests to produce a "potentially shippable increment" at each iteration. For Hardware Development, this does not make any sense (in most cases). A deliverable at the end of an Agile Product Development iteration could be a prototype, a simulation, or some other tangible result which provides continuous feedback and thus enables empirical control in addition to the usual define approach of managing the development process.