This book contains the refereed proceedings of the 11th International Conference on Agile Software Development, XP 2010, held in Trondheim, Norway, in June 2010. In order to better evaluate the submitted papers and to highlight the applicational aspects of agile software practices, there were two different program committees, one for research papers and one for experience reports. Regarding the research papers, 11 out of 39 submissions were accepted as full papers; and as far as the experience reports were concerned, the respective number was 15 out of 50 submissions. In addition to these papers, this volume also includes the short research papers, the abstracts of the posters, the position papers of the PhD symposium, and the abstracts of the panel on Collaboration in an Agile World.

Agile Processes in Software Engineering and Extreme Programming: 11th International Conference, XP 2010, Trondheim, Norway, June 1-4, 2010, Proceedings ... Notes in Business Information Processing)

Agile systems development (SD) is described as a cooperative game of invention and communication, in which teams are characterized by relying heavily on informal communication mechanisms such as face-to-face conversations. Our current state of knowledge about the actual communication process in agile SD projects is fragmented because of the lack of an integrative lens across different studies. On the basis of the Unified Model of SD Success, we provide an integrated view on the role of communication in agile SD by conducting a structured, systematic literature review. Our data collection process resulted in 333 relevant papers on agile SD and communication. We find that despite its acknowledged importance, our knowledge on communication and agile SD is limited and research is scattered, inconclusive, as well as contradictory. In consequence, we present several research gaps that deserve future research attention. Specifically, we call for research that opens up the communication process and empirically validates the implications for communication frequency and quality triggered by agile SD.

/pdf/the-role-of-communication-in-agile-systems-development-4x4h0qirq7.pdf

The Role of Communication in Agile Systems Development

http://www.cs.rug.nl/~paris/papers/JSS16a.pdf

A systematic mapping study on the combination of software architecture and agile development

In the last decade, there has been increasing interest in pair programming (PP). However, despite the existing work, there is still a lack of substantial evidence of the effects of PP in industrial environments. To address this issue, we have analyzed the work of a team of 17 industrial developers for 14 months. The team is part of the IT department of a large Italian manufacturing company; it adopts a customized version of extreme programming (XP). We have investigated the effects of PP on software quality in five different scenarios. The results show that PP appears to provide a perceivable but small effect on the reduction of defects in these settings.

Pair Programming and Software Defects--A Large, Industrial Case Study

A software engineering perspective on engineering machine learning systems: State of the art and challenges

In 1990, Anthony Hall identified and challenged seven common myths about formal methods in the IEEE Software article "Seven Myths of Formal Methods." This update re-examines those myths, reflecting both on the authors' experience with formal methods in practice and on their persistent mythic status

/pdf/software-mythbusters-explore-formal-methods-18f2dtguo2.pdf

Software Mythbusters Explore Formal Methods

Over its 10-year history, the annual Software Engineering Institute (SEI) Architecture Technology User Network (SATURN) conference has become a barometer for the ever-evolving software architecture climate. This article summarizes some software architecture trends that emerged during SATURN 2014 and gives a glimpse of the future based on the current SATURN 2015 technical program.

Lightweight and Flexible: Emerging Trends in Software Architecture from the SATURN Conferences

An architecture haiku aims to capture software system architecture's most important details on a single piece of paper. An architecture haiku helps development teams focus on the most essential information relevant to the architecture, provides clear guidance for construction, and encourages collaboration.

Architecture Haiku: A Case Study in Lean Documentation [The Pragmatic Architect]

The system metaphor was proposed in Extreme Programming as a lightweight alternative to more rigorous architecture practices, but many teams have trouble using metaphors effectively to improve team communication or evaluate a system's architecture. This is no surprise as few agile teams have had training in architecture practices let alone in how to create metaphors. In our experience this does not invalidate the metaphor, but rather shows that more guidance is needed in the proper use of metaphors. This paper outlines one team's positive experience using system metaphors in the development of a medium-sized, service-oriented, enterprise system. Specific guidelines for creating effective metaphors are presented along with concrete examples.

Michael Keeling

Papers

Software Mythbusters Explore Formal Methods

Lightweight and Flexible: Emerging Trends in Software Architecture from the SATURN Conferences

Architecture Haiku: A Case Study in Lean Documentation [The Pragmatic Architect]

Making Metaphors that Matter

Architecture Haiku: A Case Study in Lean Documentation