Pragmatic and Opportunistic Reuse in Innovative Start-up Companies

Jansen, Slinger; Brinkkemper, Sjaak; Hunink, Ivo; Demir, Cengiz

doi:10.1109/ms.2008.155

Cited by 45 publications

(38 citation statements)

References 10 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Jansen et al [77] suggest that startups should take advantage of existing components, reducing thereby time-to-market. Leveraging on frameworks and code-reuse of third party components reinforces the architectural structure of the product and the ability to scale with the company size.…”

Section: Design and Architecture Practicesmentioning

confidence: 99%

Software development in startup companies: A systematic mapping study

Paternoster

Giardino

Unterkalmsteiner

et al. 2014

Information and Software Technology

322

356

View full text Add to dashboard Cite

Context: Software startups are newly created companies with no operating history and fast in producing cutting-edge technologies. These companies develop software under highly uncertain conditions, tackling fast-growing markets under severe lack of resources. Therefore, software startups present an unique combination of characteristics which pose several challenges to software development activities. Objective: This study aims to structure and analyze the literature on software development in startup companies, determining thereby the potential for technology transfer and identifying software development work practices reported by practitioners and researchers. Method: We conducted a systematic mapping study, developing a classification schema, ranking the selected primary studies according their rigor and relevance, and analyzing reported software development work practices in startups. Results: A total of 43 primary studies were identified and mapped, synthesizing the available evidence on software development in startups. Only 16 studies are entirely dedicated to software development in startups, of which 10 result in a weak contribution (advice and implications (6); lesson learned (3); tool (1)). Nineteen studies focus on managerial and organizational factors. Moreover, only 9 studies exhibit high scientific rigor and relevance. From the reviewed primary studies, 213 software engineering work practices were extracted, categorized and analyzed. Conclusion: This mapping study provides the first systematic exploration of the state-of-art on software startup research. The existing body of knowledge is limited to a few high quality studies. Furthermore, 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.

show abstract

Section: Design and Architecture Practicesmentioning

confidence: 99%

Software development in startup companies: A systematic mapping study

Paternoster

Giardino

Unterkalmsteiner

et al. 2014

Information and Software Technology

322

356

View full text Add to dashboard Cite

show abstract

“…In the work on pragmatic reuse [4,5] in start-up companies, we observed eight different pragmatic extension patterns. The pragmatism is found, for instance, in the fact that these start-ups would sometimes simply hack the database of another product and read and write to it directly to extend it.…”

Section: Analysis Discussion and Related Workmentioning

confidence: 99%

Opening the Ecosystem Flood Gates: Architecture Challenges of Opening Interfaces Within a Product Portfolio

Jansen

2015

Software Architecture

Self Cite

View full text Add to dashboard Cite

Abstract. Technology firms are increasingly opening up their products to develop an active ecosystem of developing partners around it. Both opening up products and organizing a developer ecosystem around an organization are non-trivial. In this paper we provide a case study of a leading communications technology firm that opened up and platformized 11 product lines. First, we identify and describe four architecture patterns that are applied multiple times across these product lines. Also, the software ecosystems initiative is centralized in one central department, which has created a central knowledge hub for the creation of a software ecosystem. We highlight the guidelines collected by the central department, to assist technology firms in the platformization process and support them in their own software ecosystem creation efforts.

show abstract

“…Semi-structured individual interviews were used to collect data, since they enable the focus on pre-defined research topics and flexible structures to discover unforeseen information [28]. Methodological triangulation in data collection is also implemented by using evidence from documents and observations (in S01-S05, S09).…”

Section: Data Collection and Analysismentioning

confidence: 99%

What Influences the Speed of Prototyping? An Empirical Investigation of Twenty Software Startups

Nguyen-Duc¹,

Wang

Abrahamsson³

2017

Lecture Notes in Business Information Processing

View full text Add to dashboard Cite

Abstract. It is essential for startups to quickly experiment business ideas by building tangible prototypes and collecting user feedback on them. As prototyping is an inevitable part of learning for early stage software startups, how fast startups can learn depends on how fast they can prototype. Despite of the importance, there is a lack of research about prototyping in software startups. In this study, we aimed at understanding what are factors influencing different types of prototyping activities. We conducted a multiple case study on twenty European software startups. The results are two folds; firstly we propose a prototype-centric learning model in early stage software startups. Secondly, we identify factors occur as barriers but also facilitators for prototyping in early stage software startups. The factors are grouped into (1) artifacts, (2) team competence, (3) collaboration, (4) customer and (5) process dimensions. To speed up a startup's progress at the early stage, it is important to incorporate the learning objective into a well-defined collaborative approach of prototyping.

show abstract

Pragmatic and Opportunistic Reuse in Innovative Start-up Companies

Cited by 45 publications

References 10 publications

Software development in startup companies: A systematic mapping study

Software development in startup companies: A systematic mapping study

Opening the Ecosystem Flood Gates: Architecture Challenges of Opening Interfaces Within a Product Portfolio

What Influences the Speed of Prototyping? An Empirical Investigation of Twenty Software Startups

Contact Info

Product

Resources

About