Feb 2021· International Conference on Product Focused Software Process Improvement· pp. 402-418· 5 citations· 27 references
Computer ScienceEngineering
TL;DR
This paper study software development in startups from the point of view of practices to better understand how startups develop software, and devise a list of practices which are categorized using the Essence Theory of Software Engineering (Essence).
Abstract
. Software startups continue to be important drivers of economy globally. As the initial investment required to found a new software company becomes smaller and smaller resulting from technological advances such as cloud technology, increasing numbers of new software startups are born. Startups are considered to differ from other types of software organizations in various ways, including software development. In this paper, we study software development in startups from the point of view of practices to better understand how startups develop software. Using extant literature and case study data, we devise a list of practices which we categorize using the Essence Theory of Software Engineering (Essence). Based on the data, we propose a list of common practices utilized by software startups. Additionally, we propose potential changes to Essence to make it better suited for the software startup context.
Agile and DevOps are currently the most popular software development techniques. Software methodologies started with the application of the Waterfall model and other models of Software development. It provides a general overview of the approaches and their integration throughout the Software Development Life Cycle (SDLC). SDLC phases are described and different SDLC methodologies are discussed with respect to their impact on motivation, productivity and quality. A comparison of the traditional Waterfall and newer iterative/incremental/agile is identified, as are the reasons behind this change, such as customer participation, timely feedback, and quality improvement. The following issues are common to all methodologies: architecture limitations, scalability and organizational restrictions. It was identified that the industry tends to follow a hybrid Agile-DevOps practice with more emphasis on automation, continuous integration and collaboration to achieve quick and competitive software environments.
Mr. Raman Kumar · Journal of Global Research i...· 0 citations
Seven major CSFs that drive success in globally distributed projects are revealed, highlighting a major paradigm shift within the software industry: socio-technical skills and reliable technology now carry significantly more weight than strict, traditional processes.
Chellal Mostafa, Mohammed Saber, M. Belkasmi· EPJ Web of Conferences· 0 citations
Software companies have streamlined their engineering processes, and continuous development has been key to achieving flexible, market‐driven software solutions. Continuous software engineering (CSE) emerged as an approach to iteratively develop and maintain software, integrating business strategy, development, and operations aligned with agile principles. CSE activities also lead to technical debt (TD) buildup, negatively impacting software quality over time, so technical debt management (TDM) in CSE is crucial. However, TD in CSE is still poorly understood, as well as its causes and consequences, and how to better manage it. In addition, to the best of our knowledge, no study has investigated TDM in CSE. This paper then presents the state of the art of TDM in CSE, focusing on TD causes and consequences and how to manage them continuously. For this, we carefully examined the literature and selected 56 relevant studies from an initial set of 1299. Our main findings indicate that the field is relatively young and has considerable industry involvement. While most studies reported an experience with TD in continuous and agile contexts or the use of systematic approaches for TDM (e.g., frameworks and processes), none investigated TD explicitly in CSE or tried to understand its causes and consequences in those contexts. Some CSE activities addressed TD, particularly those associated with development, such as continuous architecting, coding, verification/testing, and documentation. Other important activities at the business and operation levels were left aside. These findings supported us in defining a research agenda with important research opportunities that could contribute to maturing the field.
L. Carvalho, J. P. Biazotto, Daniel Feitosa et al.· Journal of Software: Evoluti...· 0 citations
The objective of this research is to obtain feedback from industry experts to understand the challenges related to the employability of future-ready software engineering undergraduate students and employs a qualitative study to gather the views of the experts.
Nor Azliana Akmal Jamaludin, Najjah Salwa Abd Razak, Ummul Fahri Abdul Rauf et al.· JOIV: International Journal...· 0 citations
Related blog posts
Microsoft Research Blog· microsoft.comJul 30, 2026
Computer-use AI agents struggle with multi-step workflows like email and customer support. Echoverse trains agents in realistic environments rather than simply providing more training tasks, helping them improve as the tasks, tests, and environments evolve. The post Echoverse: Deep, evolving environments for computer-use agents appeared first on Microsoft Research.