scholarly journals A Statistical Model to Compute the Effect of Agile Teams’ Productivity

2020 ◽  
Author(s):  
Amir Mashmool ◽  
Samiyeh Khosravi ◽  
Javad Hassannataj Joloudari ◽  
Irum Inayat ◽  
Zulkefli Mansor ◽  
...  
Keyword(s):  
Software Development ◽  
Team Effectiveness ◽  
Agile Software Development ◽  
Accurate Estimation ◽  
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 model that has spread through the world of software development over the past decade. Software 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 more accurate 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 evaluate the productivity of the software in an up-to-date view of software development and to present a model for computing software team productivity. A survey was conducted with forty software development organizations located in Iran 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 an impact on productivity. Moreover, the results also state that inter-team relations affect the most on software teams’ productivity. Finally, using the model fit test, it found that 80% of productivity changes based on team effectiveness factors.

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 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’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’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’ productivity. Finally, the model fit test showed that 80% of productivity depends on team effectiveness factors.

scholarly journals Collocation Impact on Team Effectiveness

2010 ◽  
Vol 46 ◽  
Author(s):  
M Eccles ◽  
J Smith ◽  
M Tanner ◽  
JP Van Belle ◽  
S Van der Watt
Keyword(s):  
Software Development ◽  
Team Effectiveness ◽  
Negative Impact ◽  
Positive Impact ◽  
Agile Software Development ◽  
Development Teams ◽  
Effectiveness Factors ◽  
Software Development Teams ◽  
Agile Software ◽  
The Impact

The collocation of software development teams is common, specially in agile software development environments. However little is known about the impact of collocation on the team’s effectiveness. This paper explores the impact of collocating agile software development teams on a number of team effectiveness factors. The study focused on South African software development teams and gathered data through the use of questionnaires and interviews. The key finding was that collocation has a positive impact on a number of team effectiveness factors which can be categorised under team composition, team support, team management and structure and team communication. Some of the negative impact collocation had on team effectiveness relate to the fact that team members perceived that less emphasis was placed on roles, that morale of the group was influenced by individuals, and that collocation was invasive, reduced level of privacy and increased frequency of interruptions. Overall through it is proposed that companies should consider collocating their agile software development teams, as collocation might leverage overall team effectiveness.

scholarly journals Reconciling agility and architecture: a theory of agile architecture

2021 ◽  
Author(s):  
◽  
Michael Grant Waterman
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Architecture Design ◽  
Development Team ◽  
Grounded Theory Research ◽  
Responding To Change ◽  
Agile Software ◽  
Theory Research ◽  
Time Planning ◽  
Agile Teams

<p>The purpose of agile software development is to enable the software development team to respond to change and learn from change so that it can better deliver value to its customer. If an agile software development team spends too much time planning and designing architecture up-front then the delivery of value to the customer is delayed or otherwise compromised, and responding to change can become extremely difficult. Not doing enough architecture design increases exposure to risk and increases the chance of failure. The balance between architecture and agility is not well understood by agile practitioners or researchers.  This thesis is based on grounded theory research involving 44 participants from 36 organisations, all working in agile software development and who are either experienced in architecture design or are closely involved with architecture. The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility.  The theory describes six forces that affect the agility of the architecture and up-front design, and five strategies that teams use in response to those forces to determine how much effort they put into up-front design. Understanding these forces and strategies helps agile teams to determine how much up-front design is appropriate in their contexts.</p>

scholarly journals Expertise Coordination for Agile Software Development Projects

2021 ◽  
Author(s):  
◽  
Mawarny Md. Rejab
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Development Projects ◽  
Structured Interviews ◽  
Team Members ◽  
Coordination Strategies ◽  
Management Roles ◽  
Agile Software ◽  
Agile Teams ◽  
Insight Into

<p>Agile software development projects rely on the diversity of team members’ expertise. This expertise, however, is not adequate on its own: it is important to leverage available expertise through expertise coordination. Expertise coordination requires team members to rely on each other for recognizing who has particular expertise, when and where they are needed, and how to access the expertise effectively. Agile teams also need to rely on outside expertise such as user experience designers, architects, and database administrators. This thesis presents a theory of expertise coordination in Agile Software Development projects. We employed semi-structured interviews, observations, and document analysis in a Grounded Theory study involving 48 Agile practitioners and external specialists. This study discovered three main categories of expertise coordination: processes of expertise coordination, strategies of managing external expertise, and management roles in supporting expertise coordination. The theory provides a new insight into how Agile teams coordinate internal and external expertise, how they utilize external specialists and outsourcers’ expertise, and how management can support expertise coordination.</p>

scholarly journals Reconciling agility and architecture: a theory of agile architecture

2021 ◽  
Author(s):  
◽  
Michael Grant Waterman
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Architecture Design ◽  
Development Team ◽  
Grounded Theory Research ◽  
Responding To Change ◽  
Agile Software ◽  
Theory Research ◽  
Time Planning ◽  
Agile Teams

<p>The purpose of agile software development is to enable the software development team to respond to change and learn from change so that it can better deliver value to its customer. If an agile software development team spends too much time planning and designing architecture up-front then the delivery of value to the customer is delayed or otherwise compromised, and responding to change can become extremely difficult. Not doing enough architecture design increases exposure to risk and increases the chance of failure. The balance between architecture and agility is not well understood by agile practitioners or researchers.  This thesis is based on grounded theory research involving 44 participants from 36 organisations, all working in agile software development and who are either experienced in architecture design or are closely involved with architecture. The thesis presents a theory that describes how agile software teams design an agile architecture with reduced up-front design and which is able to respond to change, helping teams find a balance between architecture and agility.  The theory describes six forces that affect the agility of the architecture and up-front design, and five strategies that teams use in response to those forces to determine how much effort they put into up-front design. Understanding these forces and strategies helps agile teams to determine how much up-front design is appropriate in their contexts.</p>

scholarly journals Principles of reforming an agile-compliant performance appraisal

2019 ◽  
Vol 16 (2) ◽  
pp. 1009
Author(s):  
Mawarny Md. Rejab ◽  
Mazni Omar ◽  
Mazida Ahmad ◽  
Syahida Hassan
Keyword(s):  
Software Development ◽  
Performance Appraisal ◽  
Agile Software Development ◽  
Structured Interviews ◽  
Development Environment ◽  
Team Members ◽  
Consistent Manner ◽  
Software Engineers ◽  
Agile Software ◽  
Agile Teams

This paper presents principles of reforming an Agile-compliant performance appraisal. In this study, several semi-structured interviews have been carried out and discovered eight principles for reforming an Agile-compliant performance appraisal for Agile teams. Performance appraisal for software engineers in an Agile software development environment is complex and different from the traditional software development.  Performance appraisal should be aligned to Agile values, principles, and practices, which advocate interactions, collaborations, teamwork, and knowledge transfer among Agile team members. Therefore, a transition to Agile Software Development requires the implementation of Agile-compliant performance appraisal. These principles embark the proper practices and guidance to support management and Agile teams in deriving and implementing an Agile-compliant performance appraisal. Therefore, the emerged principles can be a baseline in generating an Agile-compliant performance appraisal to assess Agile team members in a fair and consistent manner. This indirectly increases motivation amongst team members and tends to produce capable workforce to perform at a higher level.

The Role of Neural Networks and Metaheuristics in Agile Software Development Effort Estimation

2020 ◽  
Vol 11 (2) ◽  
pp. 50-71 ◽  
Author(s):  
Anupama Kaushik ◽  
Devendra Kumar Tayal ◽  
Kalpana Yadav
Keyword(s):  
Neural Network ◽  
Neural Networks ◽  
Artificial Neural Networks ◽  
Software Development ◽  
Agile Software Development ◽  
Accurate Estimation ◽  
Effort Estimation ◽  
Whale Optimization ◽  
Artificial Neural ◽  
Agile Software

In any software development, accurate estimation of resources is one of the crucial tasks that leads to a successful project development. A lot of work has been done in estimation of effort in traditional software development. But, work on estimation of effort for agile software development is very scant. This paper provides an effort estimation technique for agile software development using artificial neural networks (ANN) and a metaheuristic technique. The artificial neural networks used are radial basis function neural network (RBFN) and functional link artificial neural network (FLANN). The metaheuristic technique used is whale optimization algorithm (WOA), which is a nature-inspired metaheuristic technique. The proposed techniques FLANN-WOA and RBFN-WOA are evaluated on three agile datasets, and it is found that these neural network models performed extremely well with the metaheuristic technique used. This is further empirically validated using non-parametric statistical tests.

scholarly journals Collaborative security risk estimation in agile software development

2019 ◽  
Vol 27 (4) ◽  
pp. 508-535 ◽  
Author(s):  
Inger Anne Tøndel ◽  
Martin Gilje Jaatun ◽  
Daniela Soares Cruzes ◽  
Laurie Williams
Keyword(s):  
Software Development ◽  
Software Security ◽  
Risk Estimation ◽  
Agile Software Development ◽  
Easy Access ◽  
Agile Development ◽  
Security Risk ◽  
Content Type ◽  
Agile Software ◽  
Agile Teams

PurposeToday, agile software development teams in general do not adopt security risk-assessment practices in an ongoing manner to prioritize security work. Protection Poker is a collaborative and lightweight software security risk-estimation technique that is particularly suited for agile teams. Motivated by a desire to understand why security risk assessments have not yet gained widespread adoption in agile development, this study aims to assess to what extent the Protection Poker game would be accepted by agile teams and how it can be successfully integrated into the agile practices.Design/methodology/approachProtection Poker was studied in capstone projects, in teams doing a graduate software security course and in sessions with industry representatives. Data were collected via questionnaires, observations and group interviews.FindingsResults show that Protection Poker has the potential to be adopted by agile teams. Key benefits include good discussions on security and the development project, along with increased knowledge and awareness. Challenges include ensuring efficient use of time and gaining impact on the end product.Research limitations/implicationsUsing students allowed easy access to subjects and an ability to collect rich data over time, but at the cost of generalizability to professional settings. Results from interactions with professionals supplement the data from students, showing similarities and differences in their opinions on Protection Poker.Originality/valueThe paper proposes ways to tackle the main obstacles to the adoption of the Protection Poker technique, as identified in this study.

Sign in / Sign up

Export Citation Format

Share Document