Extreme Programming in Action: A Longitudinal Case Study

Tingling, Peter; Saeed, Akbar

doi:10.1007/978-3-540-73105-4_27

Cited by 26 publications

(22 citation statements)

References 4 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…During these sessions, developers also made use of coding standards to help cross-team code readability and reduce the risks related to the high-rate of developer turnover. In a different study, Tingling [80] attested an initial high resistance to the introduction of coding standards and pair-programming. These practices were then adopted only in later stages, when the complexity of the project required them.…”

Section: Discussionmentioning

confidence: 99%

“…The software team studied by Zettel et al [82] had a bugfix process centered around their issue-tracking tool and relied on a release system. Several authors reported on advantages of constant code refactoring: ensuring readability and understandability of the code [82], improving modularity [80] and providing discipline to developers [93]. On the other hand, introducing refactoring may cause problems since developers had no or little experience [63] and they didn't see immediate value in introducing high level abstractions [67].…”

Section: Discussionmentioning

confidence: 99%

“…In this context, fast releases with an iterative and incremental approach shorten the lead time from idea conception to production with fast deployment [93]. The benefits of having weekly releases and frequent build cycles, addressing the uncertainty of the market, has been further reported by Blank [29], Tingling [80], Ambler [91] and Silva [67].…”

Section: Process Management Practicesmentioning

confidence: 99%

“…In any case, flexible in nature, startups' processes don't strictly follow any specific methodology, but opportunistically select practices (e.g. pair-programming [63], backlog [80]). In fact, processes are tailored to the specific features that characterize each development context [92,72,11].…”

Section: Process Management Practicesmentioning

confidence: 99%

“…Development in startups is usually guided by simple principles, trying to avoid architectural constraints that are difficult to overcome as the product and user-base grows. Tinglings [80] results suggest that a not well analyzed architecture causes problems in the long run. However, a good-enough architecture analysis should at least identify the decisions that might cause problems before obtaining product revenue, and which can be fixed at a later point in time, accounting for increased resources after revenue cash starts to flow [92].…”

Section: Design and Architecture Practicesmentioning

confidence: 99%

See 4 more Smart Citations

Software development in startup companies: A systematic mapping study

Paternoster

Giardino

Unterkalmsteiner

et al. 2014

Information and Software Technology

331

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: Discussionmentioning

confidence: 99%