Automotive OEM introduced Product-Service Systems in the past 20 years, challenging their traditional business model. A qualitative study was developed to characterise the decision-making process across 6 case studies, and similar patterns across different enabled the identification of lessons learned and possible future implications. All PSS initiatives were introduced following an Agile/Lean experimental approach, but the opportunistic nature of trials casts doubts in future validity. New testing methods that generate more robust conclusions need to be developed.

Empirical studies show that adaptations of existing agile methods are necessary for developing physical products creating obstacles and challenges. This paper aggregates the gathered findings from several cross-sectional industry surveys and establishes a relationship between the extent of utilization of individual agile elements based on Scrum and the need to adapt these elements in applying agile procedural models. The emphasis of examination resides in the purpose perspective of agile elements with the aim of facilitating context-specific adaptations more effectively.

As the complexity of products and their development processes increases, a trend emerged where companies try to manage the complexity through implementing agile practices on all or on some levels of the development process. It is not yet clear if an agile approach is the solution or under which circumstances it can be most effective in the development of physical products. This paper aims to compile the information from existing empirical and meta-studies to give an overview of the strengths and weaknesses of conventional, agile and hybrid paradigms.

Agile has its roots in software, improving the pace and quality of development projects. The application of Agile to hardware is less mature, and anecdotal evidence suggests there are specific challenges in this space. Based upon qualitative interviews with organizations working simultaneously across hardware and software applications, this paper presents three key challenges we identified. We also document several useful adjustments to Agile practice which provide a toolset that teams can use to more successfully apply Agile to hardware projects.