This paper discuss experiences and lessons learned in doing offshore agile development.

In today’s work environments, research proves that distributed Scrum teams can achieve the same quality results as collocated teams, but relationships, communication and culture play important roles in the latter.

The goal of this article is to share experiences and the model for organizing and operating distributed Agile teams that evolved from these efforts, but the main message is much simpler: Agile is the best way with distributed teams.

This article presents experience and provides guidance for working with teams in less-than-ideal distributed and virtual environments.

The author recounts experiences of applying XP to a large projects and how analysts participate in the XP team. This paper outlines a project which had multiple development teams using mulitple software development processes. The paper discusses how an XP team can be integrated with team using more formal methods using techniques such as Integration Pairs, Interface Story Cards and Interface Task Cards.

Is “distributed agile” an oxymoron? This article explains how to deal with the costs of going distributed.

The generally accepted ideal of XP has an expert customer representative on the site with the programming. This paper presents strategies for working in less-than-ideal situations with either a remote customer or multiple customers.

Nowadays the products are increasingly developed globally in collaboration between subcontractors, third party suppliers and in-house developers. However, management of a distributed product development project is proven to be more challenging and complicated than traditional one-site development. From the viewpoint of project management, the measurements and metrics are important activities for successful product development. This paper is focused on describing a set of metrics that is successfully used in industrial practice in distributed product development. Based on the experiences, the reasoning for selecting these metrics was similar: they are easy to capture and can be quickly calculated and analysed on a regular interval. One of the most important reasons for choosing these metrics was that they were aimed especially to provide early warning signals, i.e., means to proactively react to potential issues in the project. This is especially important in distributed projects, where specific means to track project status are needed.

This fairly detailed case study of an outsourced XP project describes the approach taken by the team and the modifications they made to standard XP.

Many software development projects struggle with creating and communicating a testing culture that is appropriate for the project’s needs. This may degrade software quality by leaving defects undiscovered. Previous research suggests that social coding sites such as GitHub provide a collaborative environment with a high degree of social transparency. This makes developers’ actions and interactions more visible and trackable.
We conducted interviews with 33 active users of GitHub to investigate how the increased transparency found on GitHub influences developers’ testing behaviors. Subsequently, we validated our findings with an online questionnaire that was answered by 569 members of GitHub. We found several strategies that software developers and managers can use to positively influence the testing behavior in their projects. However, project owners on GitHub may not be aware of them. We report on the challenges and risks this creates and suggest guidelines for promoting a sustainable testing culture in software development projects.