Context: Previous research found that the performance of a team not only depends on the team personality composition, but also on the interactive effects of team climate. Although investigationon p ...

Investigating the relationship between personalities and agile team climate of software professionals in a telecom company

The five-factors of personality are examined.The composite of code quality, project quality and programmer quality is examined.Conscientiousness affects depth-first; Openness to Experience affects breadth-first.Depth-first and large-revisions affect performance in programming.Programming styles help to explain the influence of personality in programming. There are repetitive patterns in strategies of manipulating source code. For example, modifying source code before acquiring knowledge of how a code works is a depth-first style and reading and understanding before modifying source code is a breadth-first style. To the extent we know there is no study on the influence of personality on them. The objective of this study is to understand the influence of personality on programming styles. We did a correlational study with 65 programmers at the University of Stuttgart. Academic achievement, programming experience, attitude towards programming and five personality factors were measured via self-assessed survey. The programming styles were asked in the survey or mined from the software repositories. Performance in programming was composed of bug-proneness of programmers which was mined from software repositories, the grades they got in a software project course and their estimate of their own programming ability. We did statistical analysis and found that Openness to Experience has a positive association with breadth-first style and Conscientiousness has a positive association with depth-first style. We also found that in addition to having more programming experience and better academic achievement, the styles of working depth-first and saving coarse-grained revisions improve performance in programming.

Links between the personalities, styles and performance in computer programming.

Non‐functional requirements define qualities of the software system that ensure effectiveness while embedding any constraints and restrictions on the design. A challenge rises with agile implementation in handling non‐function requirements in regulated environments. Thus, a practitioner's perceptions of agile method tailoring are described in
relation to inter‐team boundaries and non‐functional requirements. The research comprises 18 practitioner interviews from two multinational agile software development companies. Interviews were recorded, transcribed, and analysed using an approach informed by grounded theory and information flow models were used to compare and
contrast interactions of processes. It was discovered that one of the case study companies managed non‐functional requirements as artefacts in their agile methodology, while the other company reverts to conventional plan‐based software development practices of documentation, timeline estimations, and safety critical requirements. This research creates a detailed comparison of these contrasting approaches. The main contribution of this study is a set of proposed recommendations to deal with non‐functional requirements in
a regulated environment using agile techniques. The introduction of two new artefacts, Documentation Work Item and Safety Critical Work Item, is recommended and it is accompanied with an illustrative example, to transform the handling of documentation and safety critical requirements in a more agile way.

Managing non‐functional requirements in agile software development

The COVID-19 pandemic has set new challenges for the HoReCa industry. Lockdowns have coincided with and strongly impacted the industrial transformation processes that have been taking place for a decade. Among the most important HoReCa transition processes are those related to the rapid growth of the delivery-food market and ordering meals via internet platforms. The new delivery-food market requires not only the development of specific distribution channels, but also the introduction of appropriate, very specific food packaging. Food packaging and its functionality are defined by the administrative requirements and standards applicable to materials that have contact with food and principally through the prism of the ecological disaster caused by enormous amounts of plastic waste, mainly attributed to the food packaging. To meet environmental and administrative requirements, new technologies to produce food packaging materials are emerging, ensuring product functionality, low environmental impact, biodegradability, and potential for composting of the final product. However, predominantly, the obtained product should keep the nutritional value of food and protect it against changes in color or shape. Current social transformation has a significant impact on the food packaging sector, on one hand creating a new lifestyle for society all over the world, and on the other, a growing awareness of the negative impact of humans on the environment and increasing responsibility for the planet. The COVID-19 pandemic has highlighted the need to develop a circular economy based on the paradigm of shortening distribution channels, using local raw materials, limiting the consumption of raw materials, energy, water, and above all, minimizing waste production throughout the life cycle of products, all of which are in line with the idea of low-carbon development.

New Circular Challenges in the Development of Take-Away Food Packaging in the COVID-19 Period

Several studies have shown that both individual and team capability can affect software development performance and project success; a deeper understating of such phenomena is crucial within the context of Agile Software Development (ASD), given that its workforce is a key source of agility. This paper contributes towards such understanding by means of a case study that uses data from 14 interviews carried out at a large telecommunications company, within the context of a mobile money transfer system developed in Sweden and India, to identify individual and team capability measures used to form productive teams. Our results identified 10 individual and five team capability measures, of which, respectively, five and four have not been previously characterised by a systematic literature review (SLR) on this same topic. Such review aggregated evidence for a total of 133 individual and 28 team capability measures. Further work entails extending our findings via interviewing other software/software-intensive industries practicing ASD.

Realising Individual and Team Capability in Agile Software Development: A Qualitative Investigation

Background: Previous studies investigated key characteristics of software engineers and factors influencing the performance of individuals, productivity of teams and project success within agile software development (ASD). They aided in the active investigation of human aspects in ASD. However, capability measurement and prediction with respect to agile workforce, owing to its importance, is an area that needs spotlight. Objective: The objective of this paper is to present the state of the art relating to capability measurement of software engineers and teams working in ASD projects. Method: We carried out a systematic literature review (SLR) focused on identifying attributes used for measuring and predicting the capabilities of individual software engineers and teams. Results: Evidence from 16 studies showed attributes that can measure capabilities of engineers and teams, and also attributes that can be used as capability predictors. Further, different instruments used to measure those attributes were presented. Conclusions: The SLR presented a wide list of attributes that were grouped into various categories. This information can be used by project managers as, for example, a checklist to consider when allocating software engineers to teams and in turn teams to a project. Further, this study indicated the necessity for an investigation into capability prediction models.

An Insight into the Capabilities of Professionals and Teams in Agile Software Development: A Systematic Literature Review

A significant number of studies reported models for competence profiling, measuring capabilities of professionals and recommendation systems for roles within agile software development (ASD). These models coordinated in human resource management within ASD. However, in the light of swift, incremental and iterative nature of ASD practices, designing solutions that easily integrate capability measurements with ongoing project management routines, is an important area for investigation. With the support of interviews, grounded theory procedure and workshops, we identified the aspects valued by our industrial collaborator while allocating professionals to tasks. This information was further utilized towards devising a framework for capability-centric Web tool. This tool provides a one-stop solution for project managers to create projects, keep track of capabilities and execute allocation routines.

Designing a capability-centric web tool to support agile team composition and task allocation: a work in progress

Context: In the light of the swift and iterative nature of Agile Software Development (ASD) practices, establishing deeper insights into capability measurement within the context of team formation is crucial, as the capability of individuals and teams can affect team performance and productivity. Although a former Systematic Literature Review (SLR) synthesized the state of the art in relation to capability measurement in ASD with a focus on selecting individuals to agile teams, and capabilities related to team performance and success, determining to what degree the SLR's results apply to practice can provide progressive insights to both research and practice. 
Objective: Our study investigates how agile practitioners perceive the relevance of individual and team level measures for characterizing the capability of an agile team and its members. Furthermore, to scrutinize variations in practitioners' perceptions, our study further analyzes perceptions across stratified demographic groups. 
Method: We undertook a Web-based survey using a questionnaire built based on the capability measures identified from a previously conducted SLR. 
Results: Our survey responses (60) indicate that 127 individual and 28 team capability measures were considered as relevant by the majority of practitioners. We also identified seven individual and one team capability measure that have not been previously characterized by our SLR. The surveyed practitioners suggested that an agile team member's responsibility and questioning skills significantly represent the member's capability. 
Conclusion: Results from our survey align with our SLR's findings. Measures associated with social aspects were observed to be dominant compared to technical and innovative aspects. Our results can support agile practitioners in their team composition decisions.

Sai Datta Vishnubhotla

Papers

Investigating the relationship between personalities and agile team climate of software professionals in a telecom company

An Insight into the Capabilities of Professionals and Teams in Agile Software Development: A Systematic Literature Review

Designing a capability-centric web tool to support agile team composition and task allocation: a work in progress

Realising Individual and Team Capability in Agile Software Development: A Qualitative Investigation

Understanding the Perceived Relevance of Capability Measures: A Survey of Agile Software Development Practitioners