Towards an Anatomy of Software Craftsmanship

Context: The concept of software craftsmanship has early roots in computing, and in 2009, the Manifesto for Software Craftsmanship was formulated as a reaction to how the Agile methods were practiced and taught. But software craftsmanship has seldom been studied from a software engineering perspective. Objective: The objective of this article is to systematize an anatomy of software craftsmanship through literature studies and a longitudinal case study. Method: We performed a snowballing literature review based on an initial set of nine papers, resulting in 18 papers and 11 books. We also performed a case study following seven years of software development of a product for the financial market, eliciting qualitative, and quantitative results. We used thematic coding to synthesize the results into categories. Results: The resulting anatomy is centered around four themes, containing 17 principles and 47 hierarchical practices connected to the principles. We present the identified practices based on the experiences gathered from the case study, triangulating with the literature results. Conclusion: We provide our systematically derived anatomy of software craftsmanship with the goal of inspiring more research into the principles and practices of software craftsmanship and how these relate to other principles within software engineering in general.

Security Assurance in Agile Software Development Methods

Agile software development was introduced in the beginning of the 2000s to increase the visibility and efficiency software projects. Since then it has become as an industry standard. However, fitting sequential security engineering development models into iterative and incremental development practices in agile methods has caused difficulties in defining, implementing, and verifying the security properties of software. In addition, agile methods have also been criticized for decreased quality of documentation, resulting in decreased security assurance necessary for regulative purposes and security measurement. As a consequence, lack of security assurance can complicate security incident management, thus increasing the software's potential lifetime cost. This chapter clarifies the requirements for software security assurance by using an evaluation framework to analyze the compatibility of established agile security development methods: XP, Scrum, and Kanban. The results show that the agile methods are not inherently incompatible with security engineering requirements.

Enhancing Hybrid OSS Development Through Agile Methods and High Media Synchronicity

Open source software (OSS) is increasingly being developed by hybrid teams that consist of a mix of company employees and volunteer developers. While hybrid OSS teams are becoming more prevalent, they also face unique challenges due to the involvement of different constituents. To address those challenges, this paper develops and validates a new organizing model. Specifically, the paper draws on media synchronicity theory (MST) to theorize that hybrid OSS teams would benefit from adopting an organizing model that involves practicing agile methods and using communication tools with multiple symbols sets and high transmission velocity. The paper also extends MST by conceptualizing the theory's key concept of communication convergence as consisting of two distinct dimensions: affective and cognitive convergence. Using primary survey data from hybrid OSS teams, the paper presents empirical evidence that such an organizing model can enhance those teams' affective convergence and cognitive convergence and, in turn, their development productivity and the quality of the software. In addition, the results show that affective convergence has a stronger impact on hybrid OSS teams' performance than cognitive convergence.

Are we ready? Identifying the gap between academia and software industry in the context of agile methodologies

Nowadays, there is an exponential increase in the technology industry. However, there is not enough movement to promote changes in the Computer Science curricula. This study aims to analyze the alignment between Brazilian northeast academia and the global industry regarding developing skills in the context of agile methods. This research conducted an exploratory and quantitative survey with 161 participants represented by 65 students, 85 professionals from 10 countries, and 16 university professors. The preliminary results illustrate that academics believe that they are moderately aligned with the market. However, from the practitioner's viewpoint, it is unsatisfactory. This article reports relevant findings that can help the Brazilian academy align its practices with the needs of the global software industry.

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

<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>

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

<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>