Search results

This study explores the significance and implementation priorities for Digital Product Passports (DPP) in the context of building renovation projects. It aims to reveal bottlenecks and how a data-driven workflow bridges the DPP understanding/implementation gap, facilitating the transition towards practices aligned with the EU Green Deal goals.

A mixed-methods embedded design was employed for a real-case study exploration. Desk research and field observations ground the two-level analysis combining project documentation, namely the Bill of Quantities (BoQ), with different criteria in digitalisation and sustainability, such as economic ratio, 3D modelling, waste management, hazards, energy performance and facility management. All results were interpreted from the DPP lens.

The analysis revealed a system for identifying building products representing a significant part of the renovation budget. About 11 priority DPPs were found. Some are crucial for both the deconstruction and construction phases, highlighting the need for an incremental and strategic approach to DPP implementation.

The study is limited to a single case study. Constraints are minimised given the sample's archetype representativeness. The outcomes introduce the need for strategic thinking for incremental DPP implementation. Future research will explore additional criteria and cases.

The research has resulted in a classification framework for DPPs' significance and priority, which is provided with case results. The outcome of the framework provides views on concept alignment to make the implementation in construction more straightforward. Its practical use can be replicated in other projects, emphasizing the importance of data structure and management for the circular economy.

Agile principles have been widely used in software development team practice since the creation of the Agile Manifesto. Studies have examined variables related to agile principles without systematically considering the relationships among key team, agile methodology, and process variables underlying the agile principles and how these variables jointly influence the achievement of software development agility. In this study, the authors tested a team/methodology–process–agility model that links team variables (team autonomy and team competence) and methodological variable (iterative development) to process variables (communication and collaborative decision-making), which are in turn linked to software development agility (ability to sense, respond and learn).

Survey data from one hundred and sixty software development professionals were analyzed using structural equation modeling methods.

The results support the team/methodology–process–agility model. Process variables (communication and collaborative decision-making) mediated the effects of team (autonomy and competence) and methodological (iterative development) variables on software development agility. In addition, team, methodology and process variables had different effects on the three dimensions of software development agility.

The results contribute to the literature on organizational IT management by establishing a team/methodology–process–agility model that can serve as a basis for developing a core theoretical foundation underlying agile principles and practices. The results also have practical implications for organizations in understanding and managing holistically the different roles that agile methodological, team and process factors play in achieving software development agility.