Abstract
One saying is that, if you have a hundred people on a development team, get rid of at least eighty of them and keep the top twenty (or less). As a result the chances for project success will raise significantly. But maybe you don’t have even twenty top ones and/or the company just have these hundred people sitting around. It seems like the only places where large projects with huge teams seem to really work are projects where everything is formalized, the requirements are fixed and, most importantly, they don’t change over time. A detailed plan can be set up and every successive action will stupidly follow the plan. Example are defense projects or projects with a similar structure, such as in airlines or nuclear power plants.
We as software-engineers tend to question software engineering in the large not only because most of the agile processes claim to work only for small teams, also because most of the failed projects are really large ones. (Well, maybe nobody talks about failed small projects.) However, there are more than enough projects that are large in some sense. So, the question arises, how to use aspects of agile software development in large projects.
We don’t want to focus on every aspect of agile processes, but on those who we encountered to be mainly different in large projects. The differences might be that some things have to be implemented differently, because at a specific size of the project things don’t work out the normal way anymore. Other differences are based on problems, which pop up especially in large teams, or rather which won’t be problems at all in small teams.
This tutorial is based on our experience coordinating — so far successfully — a large (currently 160 people) project. Although we are still in the process of learning we would like to share our experiences about how agile processes can serve large projects. And besides — chances are high, that at the time XP Agile Universe 2002 is held, we have made even more valuable experiences.
Access this chapter
Tax calculation will be finalised at checkout
Purchases are for personal use only
Editor information
Editors and Affiliations
Rights and permissions
Copyright information
© 2002 Springer-Verlag Berlin Heidelberg
About this paper
Cite this paper
Eckstein, J. (2002). Scaling Agile Processes: Agile Software Development in Large Projects. In: Wells, D., Williams, L. (eds) Extreme Programming and Agile Methods — XP/Agile Universe 2002. XP/Agile Universe 2002. Lecture Notes in Computer Science, vol 2418. Springer, Berlin, Heidelberg. https://doi.org/10.1007/3-540-45672-4_44
Download citation
DOI: https://doi.org/10.1007/3-540-45672-4_44
Published:
Publisher Name: Springer, Berlin, Heidelberg
Print ISBN: 978-3-540-44024-6
Online ISBN: 978-3-540-45672-8
eBook Packages: Springer Book Archive