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.

The agile methodology is gaining attention among practitioners and researchers in hardware development. As a new methodology, it is a source of misunderstandings and misinterpretations. This is problematic at the managers' levels as they may hinder its adoption or lead to its impractical implementation and use. This study, therefore, aims to explore the manager's level of understanding of the agile methodology. The study identifies the similarities and differences between the fundamental elements of the agile methodology and the elements mentioned by managers in hardware development. The fundamental elements of the agile methodology are identified based on the elements presented in the Scrum method; the elements mentioned by managers are identified based on ten semi-structured interviews with managers in hardware development. The study shows that the understanding of the agile methodology varies largely among managers. The obtained detailed insights in the managers' level of understanding of the agile methodology could be used to develop appropriate support to facilitate its adoption and implementation.

Multidisciplinary agile teams working in fast paced, delivery-oriented sprint cycles of two weeks can experience moments of stuckness. Typically, these moments can be characterised by the inability to continue, which can be quite detrimental in agile settings, where time is pressured. This paper aims to explore these moments of stuckness, to understand when and why they occur and to understand the different strategies Scrum teams use to overcome them, both on a personal as well as team level. A combination of interviews and observations were conducted with six Scrum team members and two experts to understand their process and experiences while working in an agile set up. We have identified five strategies, which strongly rely on agile values of collaboration, communication, and creativity. These are: looking for expert guidance, open communication, creating spike stories, visual communication and incubation. The findings from this study provide both practice and academia with a deeper understanding into how can creativity be supported in agile settings.

User-centric development is essential to any product development project, especially in order to keep up with today's ever-changing product cycle.

This paper explores the potential of combining specific aspects of Scrum and Design Thinking to maximise user integration as well as implementing short iterations in hardware development projects, in this use case a three-month development project at a German high-end homeware manufacturer. In addition to observations regarding the application of those approaches this paper will then offer a range of newly developed user-centric methods to efficiently integrate the user's perspective in future development projects, as well as feedback from the product developers at the company and comparisons to current methods.

This use case was furthermore able to illustrate how the employment of such methods made short and sprint-like development cycles within hardware development attainable.

These user-centric methods developed within the use case can be applied to future application- and user- oriented projects in order to speed up the product development process and ensure that the product or service matches the users’ needs and desires.