scispace - formally typeset
Open AccessJournal ArticleDOI

Towards Effective Technical Debt Decision Making in Software Startups

TLDR
This study aims to understand the relationship between TD decisions and the success or failure of software startups, and explore the best practices related to TD decisions that would better contribute to the startup success.
Abstract
Context: Technical Debt (TD) is a metaphor used to describe outstanding software maintenance tasks or shortcuts made in the software development to achieve short-term benefits (i.e. time to market), but negatively impact the software quality in the long term. TD is quite common in a software startup, which is characterized as a young company with low resources and a small client base, aiming to accelerate time to market. Decisions related to TD can be critical for startup success. Objective: I aim to understand the relationship between TD decisions and the success or failure of software startups, and explore the best practices related to TD decisions that would better contribute to the startup success. Method: I plan to apply multiple retrospective case studies in different software startups that succeed or failed to pass the startup period and become a mature organization. Semi structured interviews will be used to collect data from the team who was involved in the software development in the startup era. Contribution: The outcome of this study will help software founders/entrepreneurs to make effective TD decisions during the startup timeframe; that can better contribute to the startup success and decrease the risk of the startup failure.

read more

Content maybe subject to copyright    Report

Citations
More filters
Journal Article

Voice of Evidence - What Do We Know about Software Development in Startups?

TL;DR: In this paper, the authors characterize their context and identify common software development startup practices, which is a common practice for failure in software development, as well as the reasons why many successful stories fail prematurely.
Journal ArticleDOI

Software Engineering in Small Software Companies: Consolidating and Integrating Empirical Literature Into a Process Tool Adoption Framework

TL;DR: In this paper, the authors conducted a systematic mapping study to determine the state of practice in the empirical literature on software engineering of SSCs by examining and classifying 1096 publications.
Journal ArticleDOI

Detecting Outdated Code Element References in Software Repository Documentation

TL;DR: Huang et al. as mentioned in this paper propose an approach that can automatically detect code element references that survive in the documentation after all source code instances have been deleted, which can prevent documentation becoming out of sync so easily.
References
More filters
Journal ArticleDOI

Critical decision method for eliciting knowledge

TL;DR: A critical decision method is described for modeling tasks in naturalistic environments characterized by high time pressure, high information content, and changing conditions and has been used to elicit domain knowledge from experienced personnel.

Managing Technical Debt in Software Engineering (Dagstuhl Seminar 16162)

TL;DR: This report documents the program and outcomes of Dagstuhl Seminar 16162, “Managing Technical Debt in Software Engineering,” and summarizes the goals and format, results from the breakout groups, and a definition for technical debt.
Book ChapterDOI

Measuring and Monitoring Technical Debt

TL;DR: The objective of the research agenda is to develop and validate a comprehensive technical debt theory that formalizes the relationship between the cost and benefit sides of the concept and propose mechanisms for measuring and managing technical debt in software product maintenance.
Journal ArticleDOI

The role of process in software start-up

Jr. S.M. Sutton
- 01 Jul 2000 - 
TL;DR: An overview of a start-up's relationship with the software process is given and guidelines on how to apply this process to astart-up company are given.
Proceedings ArticleDOI

Why software product startups fail and what to do about it. Evolution of software product development in startup companies

M. Crowne
TL;DR: In this paper, a model for the evolution of product development from startup to maturity is provided, consisting of three phases: startup, stabilization, and growth, and symptoms that can appear in each phase are discussed and the underlying issues analyzed.
Related Papers (5)