A Documentation-Centred Approach to Software Design, Development and Deployment

Changes in Indian workforce and globalisation have resulted in an increase in heterogeneous information technology (IT) teams. Team heterogeneity has been shown to impact various team outcomes. This paper examines the impact of demographic, knowledge and underlying diversity in IT teams on various team outcomes. Data were collected from 62 software development (SD) teams and analysed using multiple regressions. The result suggests that more than other forms of heterogeneity, underlying heterogeneity in SD teams has been consistently a significant predictor of the various team outcomes and thus impacts the team effectiveness.

Shared understandings are important for software development as they guide effective individual contributions and coordination of the software development process. However, it is not clear if such understandings can be developed in highly distributed groups that do not regularly meet face-to-face. In this paper, we present the results of a preliminary analysis of shared mental models within a Free/Libre Open Source Software (FLOSS) development team. We analyzed mental models using cognitive mapping and process analysis and compared the models of four developers from the Apache Lucene Java project. Our analysis suggests that there is a high level of sharing among core developers but the sharing is not complete, with some differences related to tenure and role in the project. Finally, we suggest directions for further research on shared mental models in FLOSS teams.

Managers recognize that software development project teams need to be developed and guided.Although technical skills are necessary, non-technical (NT) skills are equally, if not more, necessary for project success.Currently, there are no proven tools to measure the NT skills of software developers or software development teams.Behavioral markers (observable behaviors that have positive or negative impacts on individual or team performance) are beginning to be successfully used by airline and medical industries to measure NT skill performance.The purpose of this research is to develop and validate the behavior marker system tool that can be used by different managers or coaches to measure the NT skills of software development individuals and teams.This paper presents an empirical study conducted at the Software Factory where users of the behavior marker tool rated video clips of software development teams.The initial results show that the behavior marker tool can be reliably used with minimal training.

Context: It is known that men practitioners are predominant in software development teams over women. In recent years, researchers have investigated gender inequality from different perspectives, such as gender bias and suggestions to increase diversity in development teams. However, while most of the existing literature investigates the perception of women practitioners, the vast majority of the software development workforce – men – has received less attention. Goal: This work investigates men’s perceptions of gender inequality in software development teams and their experiences compared in software development to women. Method: Our study conducted a survey with 217 male practitioners, using a questionnaire consisting of 27 questions. The collected data was analyzed using a combination of quantitative and qualitative techniques, including graphical representations, percentages, and the grounded theory methodology. Results: Our findings reveal that most men do not perceive any sexist behavior among their team members and they are satisfied with the performance of their functions. In addition, their main suggestions to increase their participation in software development projects are offering training courses and improving the interaction among team members. Conclusions: The barriers and challenges that men practitioners face in software development teams are not the same as those faced by women. In addition, they consider that women do not work in software development due to a lack of affinity and knowledge about coding.

Software development teams that work together well, particularly those that can operate virtually, are an enormous competitive advantage for organizations (Cohen & Gibson, 2003). One challenge for software development or new product development teams in a global marketplace is managing and developing individuals from different disciplines who are remotely located. Such teams often encounter communication, environmental and philosophical barriers related to completing design tasks that threaten the success of projects (Warkenton, Sayeed & Hightower, 1997). For students at the university level, virtual cross-disciplinary learning experiences are key to their success in the competitive marketplace. The authors are currently in the second phase of an ongoing project designed to explore pedagogical, communications and logistical issues related to development of a sense of community between graduate students in the United Kingdom (UK) and United States (U.S.) (Schaffer et.al., 2005). One of the main goals of the current phase is to learn more about how virtual cross-disciplinary teams communicate and learn the concepts, models and discipline-specific language used by one another, as well as to identify key barriers and supports to such learning. Request access from your librarian to read this chapter's full text.

Communities of identity, communities of practice: Understanding Santa Fe black-on-white pottery in the Española Basin of new Mexico

Within a perspective that views groups as communities of practice and sites of construction of knowledge, learning, and identity, this article aims to explore the contribution that participation in different groups over the course of one’s life provides to the development of the professional practices of psychotherapist trainees enrolled in the C.O.I.R.A.G. school, an Italian graduate program in group psychotherapy. Through qualitative analyses of 10 semi-structured interviews, our study empirically shows that by participating in groups, the trainees not only learn the practices of that group but also develop a sort of meta-learning which takes place across groups. The results highlight that: (1) Transversality, duration, and informality are found to be the group properties with the highest formative value; and (2) Learning practices across different groups have common characteristics: are organized around complex topics of group life (e.g., how to manage conflicts, how to join and leave groups, etc.), began in early group experiences, are in continuous evolution, are associated with a critical event, and a negative affect. At the same time, it seems that these critical events are exactly what triggered and sustained the learning practices. Data from the interviews also showed how professional identities are constructed as the outcome of learning in different communities of practice. The study outlines how the experience made in different groups is elaborated in and through meaningful self-narratives, highlighting them as a fundamentally collective and culturally shaped sense-making process. Overall, these results contribute to a better understanding of learning processes as situated and jointly constructed through multiple group participations over time. Furthermore, they contribute to highlighting the role of self-narratives as a primary way through which trainees shape their identity as self-reflexive professionals who are competent in reading group dynamics. Directions for future research and suggestions for psychotherapist training paths are outlined in the conclusions.

The NA-42 TI program initiated an effort in FY2010 to standardize its software development efforts with the long term goal of migrating toward a software management approach that will allow for the sharing and reuse of code developed within the TI program, improve integration, ensure a level of software documentation, and reduce development costs. The Pacific Northwest National Laboratory (PNNL) has been tasked with two activities that support this mission. PNNL has been tasked with the identification, selection, and implementation of a Shared Software Component Library. The intent of the library is to provide a common repository that is accessible by all authorized NA-42 software development teams. The repository facilitates software reuse through a searchable and easy to use web based interface. As software is submitted to the repository, the component registration process captures meta-data and provides version control for compiled libraries, documentation, and source code. This meta-data is then available for retrieval and review as part of library search results. In FY2010, PNNL and staff from the Remote Sensing Laboratory (RSL) teamed up to develop a software application with the goal of replacing the aging Aerial Measuring System (AMS). The application under development includes an Advanced Visualization and Integration of Data (AVID) framework and associated AMS modules. Throughout development, PNNL and RSL have utilized a common AMS code repository for collaborative code development. The AMS repository is hosted by PNNL, is restricted to the project development team, is accessed via two different geographic locations and continues to be used. The knowledge gained from the collaboration and hosting of this repository in conjunction with PNNL software development and systems engineering capabilities were used in the selection of a package to be used in the implementation of the software component library on behalf of NA-42 TI. The second task managed by PNNL is the development and continued maintenance of the NA-42 TI Software Development Questionnaire. This questionnaire is intended to help software development teams working under NA-42 TI in documenting their development activities. When sufficiently completed, the questionnaire illustrates that the software development activities recorded incorporate significant aspects of the software engineering lifecycle. The questionnaire template is updated as comments are received from NA-42 and/or its development teams and revised versions distributed to those using the questionnaire. PNNL also maintains a list of questionnaire recipients. The blank questionnaire template, the AVID and AMS software being developed, and the completed AVID AMS specific questionnaire are being used as the initial content to be established in the TI Component Library. This report summarizes the approach taken to identify requirements, search for and evaluate technologies, and the approach taken for installation of the software needed to host the component library. Additionally, it defines the process by which users request access for the contribution and retrieval of library content.

Background: Software organizations increasingly need developers with high skills for social interactions. Managers, leaders, and academics need to know the human factors influencing the individuals, the development team, and the software project activities. Despite the increasing number of secondary studies about human factors in Software Engineering (SE) and in Agile Software Development (ASD), there is no study synthesizing which human factors influence software development without a specific perspective from SE or human factor thematic. Objective: We aim to summarise human factors and their influence on SE development teams and ASD teams. Method: We executed a tertiary study. We used thematic analysis to examine the resulting data. Results: We found 29 systematic literature reviews and systematic mapping studies addressing the human perspective in SE teams. We identified 101 human factors and 79 influences grouped in 4 categories (Team member, Team, Project, and Organization). Also, we identified 71 human factors and 60 influences on ASD. The most investigated human factors are Communication, Collaboration, Knowledge, and Motivation. Conclusions: The identified human factors and their influences can be considered most significant by software organizations, researchers, and academics in SE practices. Based on our results, practitioners might propose activities that enhance human capital behaviors that influence individual motivation, agile mindset, team climate, software quality, or agile transition in traditional organizations.

Data literacy is a multidimensional concept that attracts the attention of a variety of communities of practice, from different angles. The authors grouped these communities of practice in three categories: education, fields and professions, and citizenship. The meaning of data literacy varies depending on who uses it, and its concept is often conveyed in terms other than data literacy. This paper addresses the problematization of data literacy as a term by examining academic literature around it. To this end, a desk study was carried out to gather sources where the term is used. After an extensive search in the main academic databases and a subsequent PRISMA selection process, automated content analysis was applied to the gathered sources. The findings suggest that the concept of data literacy has a different treatment in different communities of practice. For example, librarians and citizen scientists have a different understanding of the concept of data literacy.

The history of English language education is punctuated with teaching and learning theories and approaches advocated by different communities of practice. One of such recent trend is the support for the integration of intercultural communicative competence (ICC) in the English language classroom. To date, minimal studies have examined this extension of the English language classroom. Hence, to determine the teaching practice of ICC this study looked at the identity-in-practice and -in-discourse, as well as sources of pedagogical knowledge of four English teachers teaching at private institutions in Bangkok. This study employed a discourse analysis approach to first identify the participants' emergent trajectories and funds of knowledge, and subsequently compared the findings with the fundamental principles of intercultural education, or the community of practice that support ICC. The findings indicated that while some participants' trajectories paralleled the tenets of ICC, there were also divergent ones. This reflected the contextualization of intercultural education, as well as the teachers' (lack of) knowledge regarding ICC. More than this, the findings also indicated the viability of a community of practice, especially for intercultural education, in a disparate educational sector.

Communities, boundary practices and incentives for knowledge sharing?

Previous studies of communities of practice had often emphasized the ease with which members are able to participate in the collective learning process through joint practices within a particular community. However, nothing much has been done to reveal the difficulties and problems of learning between different communities due to different and sometimes conflicting identities and power inequalities. This article reports a failed experience of a tertiary institution to outsource its information technology (IT) department. By highlighting the social conflicts experienced by the in-house IT technicians in coordinating with the outsourcing staff, we argue that the received unitary, managerialist viewpoints of communities of practice somehow neglect the broader social context and micro-political factors of learning. This neglect underestimates the critical challenges of resolving the social tensions caused by multiple identities and embedded power differentials across different communities of practice.

Homeland security operations would greatly benefit from bi-directional information sharing between military and civilian systems. Military-civilian information sharing, however, presents a myriad of unique technical and nontechnical challenges. Technical challenges include interoperability issues among disparate, stove-piped systems; heterogeneity of data formats; security (particularly in cross-domain sense); entitlement to data; and lack of a uniform lexicon. Non-technical challenges include the disparate operating protocols and communication styles of different communities of practice; legal, privacy, and regulatory issues surrounding the sharing of various types of data; ambiguity in authority and jurisdictional relationships amongst the different organizations in an information-sharing network; and lack of a common framework for command and control. These difficulties can be exacerbated in ad-hoc coalitions, for instance large-scale disaster response. We describe our ongoing effort to create a field-deployable platform to enable bi-directional automated information sharing among military and civilian systems. This platform uses ontologies designed by multiple subject matter experts to drive a peer-to-peer information exchange network in the syndromic bio-surveillance domain. In addition to technical issues, our research also addresses secure data sharing in the context of compliance and privacy regulations, particularly context-dependent entitlement. In addition to our findings, we will also discuss gaps that were identified as the result of this research and our vision of areas for future research

Technical debt are those convenience tasks that developers perform to obtain short-term benefits but that in the future can produce activities that are difficult to perform or more costly. The impact of technical debt is perceived in all project resources, becoming a present and future problem in software development, affecting the quality of the software. This study uses a qualitative analysis, through interviews with a software development team, explores the knowledge and perception of technical debt, the practices used to manage it, the factors that influence its appearance and accumulation, the impact that development suffers, as well as the team and the maintainability of the software, as a result, ideas and solutions are proposed to address it effectively. The study was carried out with a qualitative investigative approach, which was based on the study of a single case with which the experiences and practices in the perception and management of technical debt are investigated. The data obtained reveal that technical debt affects the normal development of the development team and that it is present in the activities carried out by the team. Although the development team has a perception of the debt, it does not address it directly, and it is necessary to implement good practices to identify it and integrate it into the software development process. Addressing technical debt with the implementation of a formal process to manage it will ensure that scheduled time is controlled and resources are optimized, which will result in a culture of good practices that will ensure product quality, improving team performance and guaranteeing software maintainability