scholarly journals From Collaboration to Solitude and Back: Remote Pair Programming During COVID-19

2021 ◽  
pp. 3-18
Author(s):  
Darja Smite ◽  
Marius Mikalsen ◽  
Nils Brede Moe ◽  
Viktoria Stray ◽  
Eriks Klotins
Keyword(s):  
Social Practice ◽  
Pair Programming ◽  
Software Projects ◽  
Collaborative Practices ◽  
Face To Face ◽  
Software Teams ◽  
Software Companies ◽  
Work From Home ◽  
The Usa ◽  
Agile Software

AbstractAlong with the increasing popularity of agile software development, software work has become much more social than ever. Contemporary software teams rely on a variety of collaborative practices, such as pair programming, the topic of our study. Many agilists advocated the importance of collocation, face-to-face interaction, and physical artefacts incorporated in the shared workspace, which the COVID-19 pandemic made unavailable; most software companies around the world were forced to send their engineers to work from home. As software projects and teams overnight turned into distributed collaborations, we question what happened to the pair programming practice in the work-from-home mode. This paper reports on a longitudinal study of remote pair programming in two companies. We conducted 38 interviews with 30 engineers from Norway, Sweden, and the USA, and used the results of a survey in one of the case companies. Our study is unique as we collected the data longitudinally in April/May 2020, Sep/Oct 2020, and Jan/Feb 2021. We found that pair programming has decreased and some interviewees report not pairing at all for almost a full year. The experiences of those who paired vary from actively co-editing the code by using special tools to more passively co-reading and discussing the code and solutions by sharing the screen. Finally, we found that the interest in and the use of PP over time, since the first months of the forced work from home to early 2021, has admittedly increased, also as a social practice.

scholarly journals A Statistical Model to Assess the Team's Productivity in Agile Software Teams

2021 ◽  
Author(s):  
Amir Mashmool ◽  
Samiyeh Khosravi ◽  
Javad Hassannataj Joloudari ◽  
Irum Inayat ◽  
Taghi Javdani Gandomani ◽  
...  
Keyword(s):  
Software Development ◽  
Statistical Model ◽  
Software Teams ◽  
Software Companies ◽  
Software Productivity ◽  
Effectiveness Factors ◽  
Team Productivity ◽  
Agile Software ◽  
Agile Teams ◽  
Software Team

Agile methods promise to achieve high productivity and provide high-quality software. Agile software development is the most important approach that has spread through the world of software development over the past decade. Software team productivity measurement is essential in agile teams to increase the performance of software development. Due to the prevalence of agile methodologies and increasing competition of software development companies, software team productivity has become one of the crucial challenges for agile software companies and teams. Awareness of the level of team productivity can help them to achieve better estimation results on the time and cost of the projects. However, to measure software productivity, there is no definitive solution or approach whether in traditional and agile software development teams that lead to the occurrence of many problems in achieving a reliable definition of software productivity. Hence, this study aims to propose a statistical model to assess the team’s productivity in agile teams. A survey was conducted with forty software companies and measured the impact of six factors of the team on productivity in these companies. The results show that team effectiveness factors including inter-team relationship, quality conformance by the team, team vision, team leader, and requirements handled by the team had a significant impact on the team’s productivity. Moreover, the results also state that inter-team relations affect the most on software teams’ productivity. Finally, the model fit test showed that 80% of productivity depends on team effectiveness factors.

scholarly journals The Theory of One Team: Agile Software Development with Distributed Teams

2021 ◽  
Author(s):  
◽  
Siva Dorairaj
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Impact Factors ◽  
Distributed Teams ◽  
Agile Methods ◽  
Team Members ◽  
Software Companies ◽  
Distributed Team ◽  
The Usa ◽  
Agile Software

<p>Team co-location is a hallmark of Agile software development that advocates face-to-face interaction and close collaboration among team members. Distributed teams, however, use Agile methods despite the separation of team members through space, time and culture. Little is known about how distributed teams use Agile methods for software development. A Grounded Theory research study that involved 55 participants from 38 different software companies in the USA, India, and Australia was carried out to investigate the key concern of distributed teams in Agile software development. This thesis proposes “The Theory of One Team” which explains how a distributed team in Agile software development adopts explicit strategies for bridging spatial, temporal, and socio-cultural distances, while facing critical impact factors, in order to become one team. This thesis primarily describes how a distributed team resolves the key concern of becoming one team. This thesis also provides the members of a distributed team with techniques for building trust with one another. In addition, this thesis serves to inform senior managers about the importance of supporting distributed teams in Agile software development.</p>

scholarly journals How agile teams make self-assignment work: a grounded theory study

2020 ◽  
Vol 25 (6) ◽  
pp. 4962-5005
Author(s):  
Zainab Masood ◽  
Rashina Hoda ◽  
Kelly Blincoe
Keyword(s):  
Grounded Theory ◽  
Task Allocation ◽  
Theory Analysis ◽  
Grounded Theory Study ◽  
Software Teams ◽  
Software Companies ◽  
Agile Practices ◽  
Facilitating Conditions ◽  
Agile Software ◽  
Agile Teams

Abstract Self-assignment, a self-directed method of task allocation in which teams and individuals assign and choose work for themselves, is considered one of the hallmark practices of empowered, self-organizing agile teams. Despite all the benefits it promises, agile software teams do not practice it as regularly as other agile practices such as iteration planning and daily stand-ups, indicating that it is likely not an easy and straighforward practice. There has been very little empirical research on self-assignment. This Grounded Theory study explores how self-assignment works in agile projects. We collected data through interviews with 42 participants representing 28 agile teams from 23 software companies and supplemented these interviews with observations. Based on rigorous application of Grounded Theory analysis procedures such as open, axial, and selective coding, we present a comprehensive grounded theory of making self-assignment work that explains the (a) context and (b) causal conditions that give rise to the need for self-assignment, (c) a set of facilitating conditions that mediate how self-assignment may be enabled, (d) a set of constraining conditions that mediate how self-assignment may be constrained and which are overcome by a set of (e) strategies applied by agile teams, which in turn result in (f) a set of consequences, all in an attempt to make the central phenomenon, self-assignment, work. The findings of this study will help agile practitioners and companies understand different aspects of self-assignment and practice it with confidence regularly as a valuable practice. Additionally, it will help teams already practicing self-assignment to apply strategies to overcome the challenges they face on an everyday basis.

scholarly journals The Theory of One Team: Agile Software Development with Distributed Teams

2021 ◽  
Author(s):  
◽  
Siva Dorairaj
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Impact Factors ◽  
Distributed Teams ◽  
Agile Methods ◽  
Team Members ◽  
Software Companies ◽  
Distributed Team ◽  
The Usa ◽  
Agile Software

<p>Team co-location is a hallmark of Agile software development that advocates face-to-face interaction and close collaboration among team members. Distributed teams, however, use Agile methods despite the separation of team members through space, time and culture. Little is known about how distributed teams use Agile methods for software development. A Grounded Theory research study that involved 55 participants from 38 different software companies in the USA, India, and Australia was carried out to investigate the key concern of distributed teams in Agile software development. This thesis proposes “The Theory of One Team” which explains how a distributed team in Agile software development adopts explicit strategies for bridging spatial, temporal, and socio-cultural distances, while facing critical impact factors, in order to become one team. This thesis primarily describes how a distributed team resolves the key concern of becoming one team. This thesis also provides the members of a distributed team with techniques for building trust with one another. In addition, this thesis serves to inform senior managers about the importance of supporting distributed teams in Agile software development.</p>

scholarly journals Intelligent System for Forecasting Failure of Agile Projects

2021 ◽  
pp. 08-19
Author(s):  
Ahmed Abdelaziz ◽  
Alia N Mahmoud ◽  
◽  
Keyword(s):  
Neural Network ◽  
Fuzzy Logic ◽  
Intelligent System ◽  
Support Vector ◽  
Multiple Linear Regressions ◽  
Software Projects ◽  
Software Companies ◽  
Area Of Interest ◽  
Agile Software ◽  
Linear Regressions

Revealing the failure of agile software projects is a great challenge faced by software companies. This paper focuses on the using of intelligent techniques such as fuzzy logic, multiple linear regressions, support vector machine, neural network to address this challenge. This paper also presents a review of some works related to this area of interest. In this paper, the researchers propose an approach for revealing the failure of agile software projects based on two intelligent techniques: fuzzy logic and multiple linear regressions (MLR). MLR is used to determine crucial failure factors of agile software projects. Fuzzy logic is used for revealing failure of agile software projects.

scholarly journals A Statistical Model to Assess the Team's Productivity in Agile Software Teams

2020 ◽  
Author(s):  
Amir Mashmool ◽  
Samiyeh Khosravi ◽  
Javad Hassannataj Joloudari ◽  
Irum Inayat ◽  
Taghi Javdani Gandomani ◽  
...  
Keyword(s):  
Software Development ◽  
Statistical Model ◽  
Software Teams ◽  
Software Companies ◽  
Software Productivity ◽  
Effectiveness Factors ◽  
Team Productivity ◽  
Agile Software ◽  
Agile Teams ◽  
Software Team

Agile methods promise to achieve high productivity and provide high-quality software. Agile software development is the most important approach that has spread through the world of software development over the past decade. The software team&rsquo;s productivity measurement is essential in agile teams to increase the performance of Software development. Due to the increasing competition of software development companies, software team productivity has become one of the crucial challenges for software companies and teams. Awareness of the level of team productivity can help them to achieve better estimation results on the time and cost of the projects. However, to measure software productivity, there is no definitive solution or approach whether in traditional and agile software development teams that lead to the occurrence of many problems in achieving a reliable definition of software productivity. Hence, this study aims to propose a statistical model to assess the team&rsquo;s productivity in agile teams. A survey was conducted with forty software companies and measured the impact of six factors of the team on productivity in these companies. The results show that team effectiveness factors including inter-team relationship, quality conformance by the team, team vision, team leader, and requirements handled by the team had a significant impact on team productivity. Moreover, the results also state that inter-team relations affect the most on software teams&rsquo; productivity. Finally, the model fit test showed that 80% of productivity depends on team effectiveness factors.

scholarly journals Measurement and structural model of agile software development critical success factors

2018 ◽  
Vol 7 (3) ◽  
pp. 1236
Author(s):  
Vinay Kukreja ◽  
Sachin Ahuja ◽  
Amitoj Singh
Keyword(s):  
Software Development ◽  
Structural Equation ◽  
Success Factors ◽  
Structural Model ◽  
Measurement Model ◽  
Agile Software Development ◽  
Equation Modeling ◽  
Software Projects ◽  
Software Companies ◽  
Agile Software

Purpose: Agile methodologies have emerged as an innovative and successful business changing way for software development companies since the success rate for completing the software projects on time and budget is better than conventional methodologies. This study proposes a theoretical framework of success factors for agile software development and validates the proposed framework using structural equation modeling.Design Methodology: A survey based random sampling was performed for data collection from 201 respondents identified from the pool of agile practitioners in software companies. Structural Equation Modeling performed on the collected data to validate measurement model as well as the structural model.Findings: The theoretical model was confirmed with modifications and the results showed that required level of fitness indexes have been achieved for the measurement model and structural model. The validation of the factors has also been done.Originality/Value: This study will guide the agile practitioners, academicians and project managers to focus more on the particular success factors which have high weight towards project success.

Process conflict management among Indian software employees

2015 ◽  
Vol 7 (2) ◽  
pp. 140-160
Author(s):  
Swati Alok ◽  
Jayasree Raveendran ◽  
Anil Kumar Jha
Keyword(s):  
Structural Equation ◽  
Role Model ◽  
Software Projects ◽  
Content Type ◽  
Software Companies ◽  
Conflict Situations ◽  
Tpb Model ◽  
Structural Assurance ◽  
Conflict Handling ◽  
Process Conflict

Purpose – The purpose of this paper is to test the possible influence of the Ajzen’s theory of planned behaviour (TPB) in predicting conflict-handling intentions during process conflict episodes. Conflict situations are often to be managed with limited time in software projects. With this cue, the study is conducted in the context of software companies in India. Design/methodology/approach – Five variables of the TPB comprising attitude, injunctive subjective norms, descriptive subjective norm, conflict efficacy (CE) and structural assurance (SA) have been studied in relation to the two standard conflict-handling intentions: integrating and dominating approach. By developing vignettes on process conflict, salient beliefs towards process conflicts were elicited among software employees in India. A questionnaire using Ajzen’s guidelines was administered. Structural equation modelling for 150 responses is used for testing path suitability and significance. Findings – Employees with positive attitude towards conflict, high CE and high SA intend to integrate during process conflict. Employees with low efficacy and who are influenced by the action of their role model intend to dominate during process conflict. Research limitations/implications – The study is contextualized to Indian software employees. Findings should not be generalized until replicated in samples from other settings. Practical implications – This study will help practitioners in understanding the various elements that play role in a process conflict and also help in developing appropriate interventions in managing conflicts. This can be done by identifying and resolving issues related to unfavourable attitude and behavioural norms towards process conflicts. Originality/value – This study is the first to examine the efficacy of the TPB model in predicting multiple conflict-handling intentions among Indian software companies.

scholarly journals “Blood pressure monitoring should be a habit”: adaptation of the Check. Change. Control. program for Asian American older adults, from group-based in-person to one-on-one telephone delivery

2021 ◽  
Author(s):  
Sou Hyun Jang ◽  
Emily V R Brown ◽  
Eun Jeong Lee ◽  
Linda K Ko
Keyword(s):  
Blood Pressure ◽  
Older Adults ◽  
Asian American ◽  
Limited English Proficiency ◽  
Blood Pressure Monitoring ◽  
Control Program ◽  
Hypertension Control ◽  
Group Setting ◽  
Face To Face ◽  
The Usa

Abstract Asian Americans have the lowest rate of awareness about hypertension, including controlled hypertension, among all racial/ethnic groups in the USA. A high proportion of Asian American older adults have limited English proficiency (LEP) and hypertension. This study adapted the Check. Change. Control. (CCC) program, a community-based intervention for hypertension control delivered in a face-to-face group setting, to phone-based delivery and evaluated the acceptability of the program among Asian American older adults with LEP. Thirteen participants received phone-based educational sessions on hypertension control over 4 months. After 4 months of interventions, we interviewed the 13 Asian American older adults and 4 counselors to examine the acceptability of the adapted CCC program. Both Asian American older adults and counselors found the phone-based delivery of the CCC program to be acceptable, and some participants recommended holding an in-person meeting before telephone delivery to review the program content and clarify information. Future study needs to explore the effectiveness of the phone-based delivery of the program on blood pressure management among larger groups of Asian American older adults.

Insights on Cost Estimation Methods and its Uses in Software Project Design

2020 ◽  
pp. 166-169
Author(s):  
Aravindhan K
Keyword(s):  
Project Management ◽  
Cost Estimation ◽  
Estimation Methods ◽  
Software Project ◽  
Estimation Model ◽  
Software Projects ◽  
Software Applications ◽  
Software Companies ◽  
Cost Estimation Model ◽  
The Cost

Cost estimation of software projects is risky task in project management field. It is a process of predicting the cost and effort required to develop a software applications. Several cost estimation models have been proposed over the last thirty to forty years. Many software companies track and analyse the current project by measuring the planed cost and estimate the accuracy. If the estimation is not proper then it leads to the failure of the project. One of the challenging tasks in project management is how to evaluate the different cost estimation and selecting the proper model for the current project. This paper summarizes the different cost estimation model and its techniques. It also provides the proper model selection for the different types of the projects.

Sign in / Sign up

Export Citation Format

Share Document