Influence of team organisation and forum support for software development team members' interactions

Author(s):  
Heng Li Yang ◽  
Cheng Hwa Lee
2011 ◽  
Vol 19 (3) ◽  
pp. 1-29
Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.


Author(s):  
Mirna Muñoz ◽  
Adriana Peña ◽  
Jezreel Mejia ◽  
Gloria Piedad Gasca-Hurtado ◽  
Maria Clara Gómez-Álvarez ◽  
...  

Author(s):  
Suranjan Chakraborty ◽  
Saonee Sarker ◽  
Sudhanshu Rai ◽  
Suprateek Sarker ◽  
Ranganadhan Nadadhur

This research uses configuration theory and data collected from a major IT vendor organization to examine primary configurations of distributed teams in a global off-shoring context. The study indicates that off-shoring vendor organizations typically deploy three different types of configurations, which the authors term as thin-at-client, thick-at-client, and hybrid. These configurations differ in terms of the size of the sub-teams in the different distributed locations and the nature of the ISD-related tasks performed by the distributed team members. In addition, the different configurations were compared on their inherent process-related and resource-related flexibilities. The thick-at-client configuration emerged as the one that offers superior flexibility (in all dimensions).However, additional analysis also revealed contingencies apart from flexibility that may influence the appropriateness of the distributed ISD team configuration, including the volatility of the client organization’s environment and the extent to which the ISD tasks can be effortlessly moved to the vendor’s home location.


2021 ◽  
Vol 27 (2) ◽  
pp. 111-134
Author(s):  
Liliana Machuca-Villegas ◽  
Gloria Piedad Gasca-Hurtado ◽  
Solbey Morillo Puente ◽  
Luz Marcela Restrepo Tamayo

In terms of productivity in software development, there is specific interest in identifying its influencing factors. For this purpose, several classification approaches have been previously used, which have already recognized technical factors, organizational factors, product factors, project factors, and personal factors. However, these approaches often focus on technical factors over social and human factors (SHFs). Nevertheless, in addition to the obvious technical aspects, the software development process involves problem-solving skills and cognitive aspects and social interaction. In this sense, determining SHFs can lead to software organizations designing strategies for improving team productivity. In this study, we first conducted a preliminary classification of the SHFs identified in the literature. Because this study seeks to assess the factors from the standpoint of software development professionals, we developed and validated an instrument to measure the perception of software development team members about SHFs that may be affecting their productivity. For this purpose, the first four stages of survey-based research were followed: objective definition, survey design, instrument construction, instrument validity, and reliability assessment. The instrument included 79 items assessing 13 different SHFs. After assessing both their validity and reliability, the results demonstrated that the instrument is a valid and reliable tool for measuring SHFs perception among software development team members.


Author(s):  
Beata Krawczyk-Bryłka ◽  
Henryk Krawczyk

Software development team collaboration requires various decisions regarding essential aspects of a project’s progress. General and particular decision-making models are considered, and their main aspects such as team types, problem solving categories, and decision-making ways are analysed. The research concerns representative groups of IT specialists and their preferences in decision-making are investigated. Four possible cases were tested: hierarchical choice (by leader) team members' choice (team consensus or voting) and external expert impact. It allows one to show some differences in behaviors of traditional and virtual teams.


Author(s):  
Rajani Dixit ◽  
Brij Bhushan

In a traditional software development process such as the Waterfall Model, works best in a stable environment. But, it is not flexible when it comes to change. There is a gap in the interaction between the users and the development team which leads to incomplete and misunderstood specification. Because of this, the end product is sometimes a surprise to users and this gap accelerates incorrect development of the software product. Once requirements are frozen there is no scope of accepting changes. There is a need for a framework which holds the solution for all these situations. With this premise, the agile development methodology came into existence. Scrum, an agile approach supports continuous collaboration among the customer, team members, and other stakeholders. Its time-boxed approach and continuous feedback from the product owner ensures the development of working product with essential features at all the time. This paper explains the agile software development approach, its proclamation and different frameworks of agile approach. Further illustrate most widely used framework: Scrum. This research paper covers the implementation and application of Scrum. It focuses on why Scrum is preferred over the Waterfall Model with the help of some survey results and later a discussion on some Scrum Metrics which will be helpful and accounting for the best Scrum Practices in achieving goals set by the software development team, the product owner and the customers. The outcome of this study shows that Scrum Metrics is critical and highly valuable for successful product development. The quantitative insight that these metrics provide for the Scrum Team, Product Owner and Stakeholders is necessary for achieving strong project dynamics and optimal results.


Sign in / Sign up

Export Citation Format

Share Document