Challenges of using software size in agile software development: A systematic literature review

Academic Papers at IWSM Mensura, IWSM-Mensura 2018; Beijing; China; 19 September 2018 through 20 September 2018Software size is a fundamental measure for software management. Size is used for a variety of purposes, such as benchmarking, normalization, and portfolio measurement, and it is frequently considered as the sole input of estimation. Estimations can be produced for various reasons; e.g., to predict effort, cost and duration of software development projects. There are different types of software size measures. Particularly in projects where agile methodologies are adopted, measurement becomes a significant challenge as it is perceived as a non-value-added task and records of tasks such as requirements identification are not always consistent. The difficulties of applying traditional size measurement techniques in agile contexts, however, do not diminish the need, and new methods and techniques are introduced to improve the manageability of the agile projects. In this paper, we discuss estimation and measurement approaches in relation with ―software size in agile contexts. Based on this review, we present the perceptions of software size and related challenges, such as misinterpretation of size, difficulties in implementation, and acceptability of the measurement processes. We anticipate that providing a baseline for the state of software size measures in agile contexts and presenting related challenges, particularly in terms of its acceptability by practitioners can shed light on the development of new techniques

Estimación de esfuerzo en desarrollo de software ágil: Estudio del estado actual en Bogotá

Context: Over the years, numerous studies have been developed related to estimating effort in agile software development, which allow us to understand the advances that have been made and the need for their use in companies. Objective: To know the perspective of entrepreneurs from different organizations in Bogotá that work in the sector or are related to the development of agile software and those who have had projects related to the subject. Method: For the elaboration of the article, a bibliographic research is carried out. Results: The data obtained are from 314 respondents in the city of Bogotá, the main findings are: 1) For companies it is extremely important with (34%) the adoption of an effort estimation methodology. 2) The most used estimation technique is the use case point with (43.31%). 3) The most used effort predictor is the Code Line (38.85%) and followed by this STORY POINT with (33.76%). 4) The agile methodology adopted in companies is SCRUM with (43.95%). 5) As the most determining factor to estimate the effort, the team experience with (53.50%) is considered. 6) In the percentage of error between estimate of projected effort and real effort (26.75%) of the respondents determine that this 5% -25% is underestimated. 7) Finally, as a difficulty in your company to estimate the effort of projects through agile software development, the respondents recognize (26.11%) that the resources are the greatest. Conclusions: The estimation of effort is relatively variable, for many companies this depends on the needs of each one, on the other hand, the use of agile methodology and estimation techniques varies in its use depending on the cross between them and how they are used. complement each other.Contexto: A lo largo de los años se han desarrollado numerosos estudios relacionados con la estimación de esfuerzo en el desarrollo de software ágil los cuales permiten comprender los avances que han tenido y la necesidad de su uso en las empresas. Objetivo: Conocer la perspectiva de empresarios de distintas organizaciones de Bogotá que trabajan en el sector o estén relacionados con el desarrollo de software ágil y aquellos que han tenido proyectos relacionados con el tema. Método: Para la elaboración del artículo se realizar una investigación a nivel bibliográfico. Resultados: Los datos obtenidos son de 314 encuestados en la cuidad de Bogotá, los principales hallazgos son: 1) Para las compañías es sumamente importante con (34%) la adopción de una metodología de estimación de esfuerzo. 2) La técnica de estimación mas usada es el punto de caso de uso con (43,31%). 3) El predictor de esfuerzo mas utilizado es la Línea de código (38,85%) y seguida de este STORY POINT con (33,76%). 4) Como metodología ágil adoptada en las empresas se encuentra SCRUM con (43,95%). 5) Como factor mas determinante para estimar el esfuerzo es considerado la experiencia de equipo con (53,50%). 6) En el porcentaje de error entre estimación de esfuerzo proyectada y esfuerzo real el (26,75%) de los encuestados hacen determina que esta 5%-25% subestimada. 7) Finalmente, como dificultad en su empresa para estimar el esfuerzo de proyectos mediante desarrollo de software ágil los encuestados reconocer con (26,11%) que los recursos como el mayor. Conclusiones: La estimación de esfuerzo es relativamente variable, para muchas compañías esto depende también de las necesidades de cada una, por otro lado, el uso de metodología ágil y técnicas de estimación varia en su uso dependiendo del cruce que se de entre ellas y como se complementan entre sí

Hitting the Bullseye: The Influence of Technical Debt on the Accuracy of Effort Estimation in Agile Projects

As firms rapidly develop solutions in order to increase revenue and market share, software development decisions considered to be temporary shortcuts and/or compromises may be implemented. These shortcuts represent “technical debt,” a metaphor which succinctly describes a software solution that should be “paid in full” or remediated in the future. Software architects and developers intend to resolve the “debt” in future product releases, but practitioners recognize that the challenge of always innovating may indefinitely postpone this remediation effort. Further, the accumulation of technical debt may have long term impact on the product’s maintainability by the software development teams and, consequently, impact the effort estimate delivered to management for forecasting product delivery timelines and product revenue expectations. While there are multiple publications that have studied effort estimation in traditional and agile software development strategies, there is limited research which considers technical debt during the estimation effort. As a result, the purpose of this dissertation is to design and propose a research model intended to determine whether or not the consideration of technical debt during the effort estimation process will improve the accuracy of the effort estimate in an agile project

Caracterização de um ambiente visual para apoiar as cerimónias do SCRUM

Dissertação de mestrado integrado em Engenharia Eletrónica Industrial e ComputadoresMetodologias ágeis de desenvolvimento de software, como o Scrum, ganharam enorme popularidade e foram bem-sucedidos em oferecer grandes benefícios para os seus utilizadores, como a aceleração de processos e recursos para lidar com a instabilidade de ambientes tecnológicos. O feedback rápido do cliente e o suporte para requisitos voláteis resultam num valor de produto mais alto, no entanto, a modelação de requisitos iniciais usando técnicas de modelação, não são comumente usados em processos ágeis como o Scrum para preparar melhor a fase de implementação do projeto de software. Esta dissertação, irá propor um ambiente visual adequado para apoiar o sprint e product backlog. Para tal, será modelada uma solução/abordagem técnica utilizando uma linguagem de modelação, como por exemplo a Unified Modeling Language (UML) para apoiar a priorização de requisitos, melhorar a qualidade da solução e facilitar a manutenção de software. Este procedimento seguirá a organização e gestão padrão de Scrum, e fornecerá uma implementação detalhada baseada no processo de modelação UML ou noutra linguagem de modelação de software. O ambiente visual a ser proposto será validado com estudo de caso e painel de especialistas tornando assim a solução uma alternativa para resolver ou reduzir os problemas relacionados com a complexidade e qualidade de software produzidos pelas organizações. Serão estudadas as técnicas informais e formais de modelação de software no sentido de se encontrar o método adequado ao problema, menos complexa e que envolva menor custo para o desenvolvimento de um produto. A metodologia que será utilizada para o desenvolvimento desta dissertação, é a Design Science Research. Esta metodologia consiste na revisão de literatura ajustada nos conceitos mais importantes para o problema em estudo, seguido de uma proposta de um artefacto que contribua com um novo conhecimento para a ciência, sendo avaliado posteriormente num contexto real.Agile software development methodologies, such as Scrum, have gained tremendous popularity and have been successful in delivering great benefits to their users, such as accelerating processes and resources to deal with the instability of technological environments. Rapid customer feedback and support for volatile requirements result in a higher product value; however, modeling of initial requirements using modeling techniques is not commonly used in agile processes such as Scrum to better prepare the implementation phase of the project. software project. This dissertation will propose a suitable visual environment to support the sprint and product backlog. For this, a technical solution / approach will be modeled using a modeling language such as the Unified Modeling Language (UML) to support the prioritization of requirements, improve the quality of the solution and facilitate the maintenance of software. This will follow the standard Scrum organization and management and will provide a detailed implementation based on the UML modeling process or other software modeling language. The visual environment to be proposed will be validated with a case study and expert panel thus making the solution an alternative to solve or reduce the problems related to the complexity and quality of software produced by the organizations. The informal and formal techniques of software modeling will be studied in order to find the appropriate method to the problem, less complex and involving less cost for the development of a product. The methodology that will be used to develop this dissertation is Design Science Research. This methodology consists of a literature review adjusted to the most important concepts for the problem under study, followed by a proposal for an artifact that contributes to a new knowledge for science and is evaluated later in a real context

Volume II Acquisition Research Creating Synergy for Informed Change, Thursday 19th Annual Acquisition Research Proceedings

ProceedingsApproved for public release; distribution is unlimited