Examining decision characteristics &amp; challenges for agile software development

Drury‐Grogan, Meghann L.; Conboy, Kieran; Acton, T.B.

doi:10.1016/j.jss.2017.06.003

Cited by 42 publications

(24 citation statements)

References 34 publications

Supporting

Mentioning

Contrasting

Unclassified

Order By: Relevance

“…Basándose en el artículo, Examinando decisiones características y desafíos para el desarrollo ágil de software Meghann L. Drury-Grogan la investigación que estudia los aspectos estrechos de la toma de decisiones en diferentes entornos pretende conocer cuáles son las características de decisiones relacionadas con los valores ágiles y los desafíos que presentan entre otros, se pude evidenciar e identificar las fallas en la toma de decisiones en un entorno ágil, aun más cuando se tiene en cuenta la calidad de gestión, el proceso de decisión y demás [24], sin embargo, es pertinente también conocer los factores que influyen en el éxito de los proyectos de desarrollo de software ágil para esto Carlos Tam proponer en su artículo los factores considerados como influyentes, pues relaciona el éxito en términos de costos, tiempo y satisfacción del cliente convirtiéndolos en un triángulo de enfoque de métodos mixto [25].…”

Section: Estado Del Arteunclassified

Estimation of effort in agile software development: Study of the current state in Bogotá

Bustamante

2020

ITECKNE

View full text Add to dashboard Cite

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.

show abstract

Section: Estado Del Arteunclassified

Estimation of effort in agile software development: Study of the current state in Bogotá

Bustamante

2020

ITECKNE

View full text Add to dashboard Cite

show abstract

“…• ASD is linked to improved decision-making, and the existing theories concentrate on the precise strategies of decision-making in such environments. The clarity regarding the establishment and evaluation of the myriad of decisions from software feature inception to product delivery and refinement is lacking [5]. • The standard or common method of risk management process and tool are not available in software development situations [12].…”

Section: Challengesmentioning

confidence: 99%

“…There are a large number of unique characteristics in ASD that have an impact on the decision-making process such as fast-paced incremental and iterative nature, and one relies on selfmotivation and management [4]. Moreover, to differentiate the features for effective decision-making, ASD gains remarkable significance [5]. The basic assumptions made in the agile development pose a massive challenge while applying it practically in large-scale projects.…”

Section: Introductionmentioning

confidence: 99%

Distributed cat modeling based agile framework for software development

Prakash

Viswanathan

2019

Sādhanā

View full text Add to dashboard Cite

Software development is a challenging process that requires in-depth understanding and an effective model such that the developed software inherits good quality and reliability, and attains customer satisfaction towards achieving the goals successfully. The effectiveness of the software is enabled by modifying the operating modules of the software through a model, like agility. In this paper, the catastrophic and distributed computing models are integrated into the software development process. The proposed model is termed as a distributed cat model that is developed with the aim to handle the risk factors engaged in various developing stages of the agile model. The risk factors that affect the communication, planning, release, design, coding and testing modules of the agile modules are deeply learned and executed such that the risk factors are tackled by various modules present in the proposed distributed cat model. The effectiveness of the proposed model is analysed based on the performance metrics such as Index of Integration (IoI) and Usability Goals Achievement Metric (UGAM), for which five products, including the hotel management system, Customer Relationship Management system (CRM), rainfall prediction system, temperature monitoring system and meta-search system, are employed. The analysis is performed using the parameters like mean difference, variance, standard deviation and correlation coefficient. The result proves that the proposed model offers a great positive deviation contributing to high degree of performance in software development.

show abstract

“…The authors explored challenges focusing on internal and external communication. Since the groups are becoming self-organised in their research context, the communication among team members and between team members and customer, management, support group, enterprise staff show increasing challenges, such as a lack of coordination [23] and a non-deterministic decision-making process [24].…”

Section: Communication Channels In Modern Organisation Managementmentioning

confidence: 99%

Communication channels in safety analysis: An industrial exploratory case study

Wang

Graziotin

Kriso

et al. 2019

Journal of Systems and Software

View full text Add to dashboard Cite

Context: Safety analysis is a predominant activity in developing safety-critical systems. It is a highly cooperative task among multiple functional departments due to increasingly sophisticated safety-critical systems and close-knit development processes. Communication occurs pervasively. Motivation: Effective communication channels among multiple functional departments influence safety analysis quality as well as a safe product delivery. However, the use of communication channels during safety analysis is sometimes arbitrary and poses challenges. Objective: In this article, we aim to investigate the existing communication channels, their usage frequencies, their purposes and challenges during safety analysis in industry. Method:We conducted a multiple case study by surveying 39 experts and interviewing 21 experts in safety-critical companies including software developers, quality engineers and functional safety managers. Direct observations and documentation review were also conducted. Results: Popular communication channels during safety analysis include formal meetings, project coordination tools, documentation and telephone. Email, personal discussion, training, internal communication software and boards are also in use. Training involving safety analysis happens 1-4 times per year, while other aforementioned communication channels happen ranging from 1-4 times per day to 1-4 times per month. We summarise 28 purposes of using these aforementioned communication channels. Communication happens mostly for the purpose of clarifying safety requirements, fixing temporary problems, conflicts and obstacles and sharing safety knowledge. The top 10 challenges are: (1) sensitiveness and confidentiality of safety analysis information; (2) fragmented safety analysis information;(3) inconsistent safety analysis information; (4) asynchronous channels; (5) a lack of tool support; (6) misunderstanding between developers and safety analysts; (7) language, geographic and culture limitations; (8) unwillingness to communicate (groupthink); (9) storage, authority, regulation and monitoring of safety analysis information; (10) a lack of documentation concerning safety analysis to support communication. Conclusion: During safety analysis, to use communication channels effectively and avoid challenges, a clear purpose of communication during safety analysis should be established at the beginning. We have limitations primarily on the research context namely the scope of domains, participants and countries. To derive countermeasures of fixing the top 10 challenges are potential next steps. OutlineThe article is organised as follows. In Section 2, we describe the background of communication channels and the related work regarding our study. We define a theoretical lens of communication channels during safety analysis in Section 3. Section 4 presents the case study design including context, research questions, data collection and analysis procedures. In Section 5, we report our study results. We discuss our implications and limitations i...

show abstract

Examining decision characteristics & challenges for agile software development

Cited by 42 publications

References 34 publications

Estimation of effort in agile software development: Study of the current state in Bogotá

Estimation of effort in agile software development: Study of the current state in Bogotá

Distributed cat modeling based agile framework for software development

Communication channels in safety analysis: An industrial exploratory case study

Contact Info

Product

Resources

About