Scaling Agile Methods

Authors:
Donald J. Reifer;Frank Maurer;Hakan Erdogmus
Affiliations:
-;-;-
Venue:
IEEE Software
Year:
2003

Citing 0
Cited 7

Is the Software Engineering State of the Practice Getting Closer to the State of the Art?

IEEE Software
Ambidextrous coping strategies in globally distributed software development projects

Communications of the ACM
A survey study of critical success factors in agile software projects

Journal of Systems and Software
A work product pool approach to methodology specification and enactment

Journal of Systems and Software
Inspecting automated test code: a preliminary study

XP'07 Proceedings of the 8th international conference on Agile processes in software engineering and extreme programming
Agility in context

Proceedings of the ACM international conference on Object oriented programming systems languages and applications
Research challenges in large-scale agile software development

ACM SIGSOFT Software Engineering Notes

Quantified Score

Hi-index	0.02

Visualization

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.