Towards an Understanding of Software Development Process Knowledge in Very Small Companies

Basri, Shuib; O’Connor, Rory V.

doi:10.1007/978-3-642-25462-8_6

Cited by 12 publications

(6 citation statements)

References 16 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…Grounded Theory has been applied by other researchers in similar contexts to attest relationships among conceptualizations of an examined phenomenon (see [34], [117], [17]). Those relationships should be verified in such a way that emerging findings remain consistent as further data is collected.…”

Section: Conclusion Validitymentioning

confidence: 99%

Software Development in Startup Companies: The Greenfield Startup Model

Giardino

Paternoster

Unterkalmsteiner

et al. 2016

IIEEE Trans. Software Eng.

142

126

View full text Add to dashboard Cite

PostprintThis is the accepted version of a paper published in IEEE Transactions on Software Engineering. This paper has been peer-reviewed but does not include the final publisher proof-corrections or journal pagination.Citation for the original published paper (version of record):Giardino, C., Paternoster, N., Unterkalmsteiner, M., Gorschek, T., Abrahamsson, P. The Greenfield Startup Model Carmine Giardino, Nicolò Paternoster, Michael Unterkalmsteiner, Member, IEEE, Tony Gorschek, Member, IEEE, and Pekka Abrahamsson, Member, IEEE Abstract-Software startups are newly created companies with no operating history and oriented towards producing cutting-edge products. However, despite the increasing importance of startups in the economy, few scientific studies attempt to address software engineering issues, especially for early-stage startups. If anything, startups need engineering practices of the same level or better than those of larger companies, as their time and resources are more scarce, and one failed project can put them out of business. In this study we aim to improve understanding of the software development strategies employed by startups. We performed this stateof-practice investigation using a grounded theory approach. We packaged the results in the Greenfield Startup Model (GSM), which explains the priority of startups to release the product as quickly as possible. This strategy allows startups to verify product and market fit, and to adjust the product trajectory according to early collected user feedback. The need to shorten time-to-market, by speeding up the development through low-precision engineering activities, is counterbalanced by the need to restructure the product before targeting further growth. The resulting implications of the GSM outline challenges and gaps, pointing out opportunities for future research to develop and validate engineering practices in the startup context.

show abstract

Section: Conclusion Validitymentioning

confidence: 99%

Software Development in Startup Companies: The Greenfield Startup Model

Giardino

Paternoster

Unterkalmsteiner

et al. 2016

IIEEE Trans. Software Eng.

142

126

View full text Add to dashboard Cite

show abstract

“…This paper focuses on team processes, also called team dynamics [8]. Our goal is to define the main elements of these processes that could be applied independently of the various perspectives.…”

Section: Structure Of This Papermentioning

confidence: 99%

Software team processes: A taxonomy

Robillard¹,

Lavallee²

2012

2012 International Conference on Software and System Process (ICSSP)

View full text Add to dashboard Cite

A software development team must integrate many process perspectives imposed by the client, the organization, team management, and team dynamics. All these perspectives intermingle at the team process level. We propose a taxonomy to define the various episodes observed at this level and a useful vocabulary for reporting the observations made. Our taxonomy is based on a previous literature review performed in the business management field and adapted in this paper for the software engineering field. It was applied on existing data obtained from a real project carried out with an industrial partner. The vocabulary defined can accurately present team interactions, and may help diagnose communication breakdowns leading to project failures. The benefit of this approach is that it enables team process activities to be measured without reference to specific concepts related to perspectives other than that of the team process.

show abstract

“…Software VSEs are subject to a number of distinctive and intrinsic characteristics that make them different from their larger counterparts, therefore affecting the content, the nature and the extent of the activities. We partition our discussion of VSE characteristics below based on four main categories: financial constraints, typical customer profile, the focus of internal business processes and the constraints on learning and growth (Basri & O'Connor, 2011).…”

Section: Very Small Entitiesmentioning

confidence: 99%

The Evolution of the ISO/IEC 29110 Set of Standards and Guides

O’Connor

Laporte

2017

International Journal of Information Technologies and Systems Approach

View full text Add to dashboard Cite

While the quality of products is a competitive advantage for very small software development organizations, the usage of Software and Systems Engineering standards amongst such very small organizations is extremely low. A key factor in the literature explaining this lack of quality standards adoption is the perception by small and very small organizations that such standards have been developed for large multi-national companies and not with small and very small organizations in mind. The ISO/IEC 29110 standard is unique amongst software and systems engineering standards, in that the working group (ISO/IEC JTC1/SC7 WG 24) mandated to develop a new standard approached industry to conduct a needs assessment and gather actual requirements for a new standard as part of the standards development process. This paper presents a historical perspective behind the development of the ISO/IEC 29110 systems and software engineering standard and its constituent components, including the rationale behind its development and the innovative design of implementation guides to assist very small companies in adopting the standards. Further this paper will present an overview of the various parts of the ISO/IEC 29110 family and briefly present the plans for the future evolution of this series of standards.

show abstract

Towards an Understanding of Software Development Process Knowledge in Very Small Companies

Cited by 12 publications

References 16 publications

Software Development in Startup Companies: The Greenfield Startup Model

Software Development in Startup Companies: The Greenfield Startup Model

Software team processes: A taxonomy

The Evolution of the ISO/IEC 29110 Set of Standards and Guides

Contact Info

Product

Resources

About