Sep 2026· Reviews of Management Sciences· 0 citations· 129 references
Entrepreneurship Studies and Influences
Abstract
Social network analysis (SNA) offers an analytical toolkit for researching the relational structures that shape entrepreneurial processes. However, it remains comparatively underutilized in entrepreneurship research, and where it is applied, the methodological choices do not always match the demands of the field’s own theoretical foundations. To address these shortcomings, this paper systematically reviews how SNA has been methodologically applied in entrepreneurship research and to what extent current practices align with the requirements of structural embeddedness, social capital, and processual perspectives on entrepreneurial networking. The review is based on 53 articles published between 2005 and 2025 in journals ranked in the first two quartiles (Q1 and Q2) of the Journal Citation Reports and indexed in the Web of Science Core Collection. The findings are organized across four dimensions: study overview, network configurations, data collection and preparation, and data analysis. The review reveals that the field relies heavily on cross-sectional designs, single data sources, and a narrow set of conventional metrics, primarily density and degree centrality. This creates a systematic mismatch between the dynamic, relationally complex nature of entrepreneurial networks as described by theory and the static, structurally focused methods used to study them. Nearly half of the reviewed studies drew on only one data source, limiting the ability to capture the relational depth that social capital theory emphasizes. Longitudinal designs, which are essential for testing processual accounts of network evolution, remain scarce. Based on these findings, the paper develops a methodologically grounded framework with recommendations for data collection, metric selection, and software use that are tied to the specific gaps identified in the review.
This publication proposes a definition and a classification of agile software development approaches and analyses ten software development methods that can be characterized as being "agile" against the defined criterion.
P. Abrahamsson, O. Salo, Jussi Ronkainen et al.· arXiv.org· 727 citations· ⚡54
The study shows that agile practices improve both informal and formal communication, but indicates that, in larger development situations involving multiple external stakeholders, a mismatch of adequate communication mechanisms can sometimes even hinder the communication.
M. Pikkarainen, Jukka Haikara, O. Salo et al.· Empirical Software Engineeri...· 401 citations· ⚡48
The results indicate that software engineering work practices are chosen opportunistically, adapted and configured to provide value under the constrains imposed by the startup context.
Nicolò Paternoster, Carmine Giardino, M. Unterkalmsteiner et al.· Information and Software Tec...· 394 citations· ⚡54
The results show that the embedded industry has been able to apply agile methods in its development processes and that the appreciation of the agile methods and their individual practices appears to increase once adopted and applied in practice.
O. Salo, P. Abrahamsson· IET Software· 238 citations· ⚡9
Consequences of happiness and unhappiness that are beneficial and detrimental for developers' mental well-being, the software development process, and the produced artifacts are found.
D. Graziotin, Fabian Fagerholm, Xiaofeng Wang et al.· Journal of Systems and Softw...· 236 citations· ⚡13
The Mobile-D approach is briefly outlined here and the experiences gained from four case studies are discussed, which helped develop an agile development approach for mobile application development.
P. Abrahamsson, Antti Hanhineva, H. Hulkko et al.· Conference on Object-Oriente...· 225 citations· ⚡18
Related blog posts
MIT News · Artificial Intelligence· news.mit.eduOct 6, 2026
Writing as a participant and researcher, PhD student JS Tan SM ’22 has co-authored a new book about the rise of tech worker protests and the employer backlash that followed.
Requirements in large systems rarely exist in isolation. Their meaning depends on the wider project context - other requirements, policies, decisions, tests, and implementation details. That becomes especially important when AI is used for review, because spotting a possible conflict or gap is only the beginning. ReqSpace explores how AI, visualisation, and connected project context can help reviewers understand those findings, trace the relationships behind them, and focus on the questions that…
AI is making software generation faster, but speed does not remove the need for expertise. As more work is delegated to AI, tacit knowledge may become one of the most important human advantages in software engineering. The post Beyond Prompt Engineering: The Role of Tacit Knowledge in Software Engineering appeared first on GPT-Lab.
We use cookies to run the site and, with your consent, for analytics and to show ads.
See our Cookie Policy.