Abstract

Risk identification in the case of technical projects is an issue that has been extensively studied in many previous research efforts; however, a thorough study of the respective literature clearly reveals a methodological and application gap between research and practice, which is further increased by a wide discrepancy of definitions and procedures applied. This paper proposes the consideration of risk sources in the risk identification process as a means to bridge the identified gap and reduce discrepancy. The paper presents the results of the processing and analysis of real projects’ risk data through unstructured interviews with the experts who provided the data, and examines their correlation with a comprehensive risk sources checklist drawn from previous research. The results of this cross-checking clearly highlighted the extensive misconceptions of the related terms and notions in practice (e.g., what is perceived as risk identification is actually risk source identification), as well as the partial implementation of procedures that reflects a similar partial approach to technical project risk analysis in practice (e.g., the risk sources actually identified are fewer than those that could be identified through a holistic approach to technical project risk analysis). These results draw attention to the need for more-focused risk source–related research, because the new paradigm shift in technical project risk analysis highlights the importance of risk sources.

Talk to us

Join us for a 30 min session where you can share your feedback and ask us any queries you have

Schedule a call

Disclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.