Conference Paper

Distributing a Lean Organization: Maintaining Communication While Staying Agile

DOI: 10.1007/978-3-642-16416-3_14 Conference: Lean Enterprise Software and Systems - First International Conference, LESS 2010, Helsinki, Finland, October 17-20, 2010. Proceedings
Source: DBLP


Distributed software development teams are common-place today. One good reason for distribution is the need to combine special
skills or competencies from different locations. However, integrating skills flexibly is both a technical and a communication
challenge. Lean and agile projects depend on direct communication. In this contribution, we investigate how agile teams can
be distributed by adding a “remote partner” - and still maintain agile advantages. We analyze communication using the goal-question-metric
paradigm (GQM) and apply it to a programming project, part of which was distributed. We discuss our insights on the minimal
set of additions (technical and organizational) that are required to turn distributed while staying agile.

Download full-text


Available from: Eric Knauss, Oct 14, 2015
29 Reads
  • 18th Australian Software Engineering Conference (ASWEC 2007), April 10-13, 2007, Melbourne, Australia; 01/2007
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: Several empirical studies have been carried out with college students as subjects in the last few years. Researchers often use these studies to pilot experiments before they are carried out in industrial environments. Reports on these studies usually focus on the results obtained and issues such as their external validity. However, the effects and value of empirical studies with students may go beyond the contribution to scientific literature. For instance, the pedagogical challenges and value of these studies is hardly ever stressed. We identify four primary actors that are involved in these empirical studies, i.e., researchers, students, instructors, and industry. We discuss the costs and benefits of empirical studies with students for these actors, which are different because of the actors' different goals, expectations, and constraints, which must be recognized to fully exploit empirical studies with students. We also provide some advice on how to carry out empirical studies with students based on our experiences.
    Software Metrics Symposium, 2003. Proceedings. Ninth International; 10/2003
  • Source
    [Show abstract] [Hide abstract]
    ABSTRACT: ABSTRACT Teaching (and therefore learning) eXtreme Programming,(XP) in auniversity setting is difficult because of course,time limitations and the soft nature of XP that requires ,first-hand experience in order to see and really learn the methods. For example, iterations are either shorter or fewer ,than appropriate. In this paper we present the ,properties to tune ,when ,designing ,an eXtreme Programming,course. These are the properties we gathered ,by conducting,three XP labs ,as part of ,our software ,engineering teaching. Within this paper we describe,our set-up as well,as the important properties. Lecturers and teachers can use this property
    ICSE '08: Proceedings of the 30th international conference on Software engineering; 01/2008