Scaling agile methods

descriptionPublicationkeyboard_double_arrow_right Article 01 Jul 2003 Canada English Publisher:Institute of Electrical and Electronics Engineers (IEEE)Journal:IEEE Software, volume 20, pages 12-14 (issn: 0740-7459,

Copyright policy )

Authors: Donald J. Reifer; Frank Maurer; M. Hakan Erdogmus;

doi: 10.1109/ms.2003.1207448

Scaling agile methods

- Summary
- Metrics

Abstract

Using agile methods to develop large systems presents a thorny set of issues. If large teams are to produce lots of software functionality quickly, the agile methods involved must scale to meet the task. After all, a small team could create the software if the functionality to be delivered was small and, conversely, could be delivered given we had the time. Scaling agile teams thus becomes an issue if the only option for meeting a system delivery deadline is to have many developers working concurrently.

Country

Canada

Related Organizations

University of Southern California
United States
University of California System
United States
National Academies of Sciences, Engineering, and Medicine
United States
National Research Council Canada
Canada
University of Calgary
Canada

Impact byBIP!

	selected citations These citations are derived from selected sources. This is an alternative to the "Influence" indicator, which also reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).	56
	popularity This indicator reflects the "current" impact/attention (the "hype") of an article in the research community at large, based on the underlying citation network.	Top 10%
	influence This indicator reflects the overall/total impact of an article in the research community at large, based on the underlying citation network (diachronically).	Top 1%
	impulse This indicator reflects the initial momentum of an article directly after its publication, based on the underlying citation network.	Average