How extreme does extreme programming have to be? Adapting XP practices to large-scale projects
Published 1 January 2004
Lan Cao, K. Mohan, Peng Xu, Balasubramaniam Ramesh
Citations109
Generate an AI Snapshot to get a quick, structured summary of this paper.
Study Snapshot
ObjectiveStudy objective
MethodsResearch methodology
PopulationPopulation studied
Sample sizeSample sizes
OutcomesStudy outcomes here
ResultsStudy results comes here
LimitationsResearch study limitations comes here
A concise AI-generated summary of the paper will appear here once you click Generate AI Snapshot.
TL;DR
The key differences between agile principles proposed in prior literature and the agile practices that are suitable for large-scale, complex software development are highlighted and general guidelines on tailoring agile development methodologies are proposed.
Abstract
The need to develop software at Internet speed and accommodate changes during the entire software development life cycle has made lightweight or agile development methodologies like extreme programming popular. However, such methodologies have been considered to be beneficial for small and medium sized projects, with small teams. In this paper, based on a case study in an organization that develops large-scale, complex software using a modified form of extreme programming, we highlight the key differences between agile principles proposed in prior literature and the agile practices that are suitable for large-scale, complex software development. Based on these differences, we propose general guidelines on tailoring agile development methodologies to make them suitable for the development of large, complex software systems.
Keywords
Computer Science
Design Patterns: Elements of Reusable Object-Oriented Software
21,864 Citations1994Erich Gamma, Richard F. Helm +2 more
The book is an introduction to the idea of design patterns in software engineering, and a catalog of twenty-three common patterns, which most experienced OOP designers will find out they've known about patterns all along.
Extreme programming explained embrace change
5,875 Citations2008Kent Beck
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Communications of the ACMA field study of the software design process for large systems
2,093 Citations1988Bill Curtis, Herb Krasner +1 more
A layered behavioral model is used to analyze how three of these problems—the thin spread of application domain knowledge, fluctuating and conflicting requirements, and communication bottlenecks and breakdowns—affected software productivity and quality through their impact on cognitive, social, and organizational processes.
Agile Software Development
1,803 Citations2001Alistair Cockburn
ComputerAgile software development: the business of innovation
1,198 Citations2001James A. Highsmith, Alistair Cockburn
The rise and fall of the dotcom-driven Internet economy shouldn't distract us from seeing that the business environment continues to change at a dramatically increasing pace, and Agile software development approaches view change from a perspective that mirrors today's turbulent business and technology environment.
ComputerAgile software development, the people factor
1,095 Citations2001Alistair Cockburn, James A. Highsmith
ComputerGet ready for agile methods, with care
902 Citations2002Barry Boehm
Although many of their advocates consider the agile and plan-driven software development methods polar opposites, synthesizing the two can provide developers with a comprehensive spectrum of tools and options, and a combined approach is feasible and preferable in some circumstances.
CERN Document Server (European Organization for Nuclear Research)Planning Extreme Programming
491 Citations2000Kent Beck, Martin Fowler
Planning Extreme Programming presents the approaches, methods, and advice you need to plan and track a successful Extreme Programming project, and alerts you to the red flags that signal serious problems.
IEEE SoftwareExtreme programming from a CMM perspective
303 Citations2001N.C. Paulk
The author reviews XP from the perspective of the capability maturity model for software, gives overviews of both approaches, and critiques XP from a SW-CMM perspective, concluding that lightweight methodologies such as XP advocate many good engineering practices.
IEEE SoftwareIs internet-speed software development different?
116 Citations2003Richard Baskerville, Balasubramaniam Ramesh +3 more
Agile principles are better suited than traditional software development principles to provide a flexible development environment that can cope with fast-changing requirements and an increasingly demanding market.
arXiv (Cornell University)Quantitative Survey on Extreme Programming Projects
96 Citations2014Bernhard Rumpe⋆, Astrid Schröder
The results of 45 evaluated questionnaires that have been received during the Summer 2001 survey on XP are presented.
IEEE SoftwareIntroducing xp into greenfield projects: lessons learned
81 Citations2003Jonathan Rasmusson
This article illustrates not only how XP helped make the project a success, but also gives other lessons learned regarding the introduction of XP at client sites.
IEEE SoftwareAssessing xp at a european internet company
62 Citations2003O. Murru, R. Deias +1 more
The article describes the company's experiences with XP, explores its implementation practice by practice, and discusses XPs pros and cons in three key areas; customer relationships, project management, and ISO 9001 quality assurance.
IEEE SoftwareXP and the CMM
32 Citations2003D.J. Reifer
Putting XP to work in an SW-CMM environment is often difficult, because guidance on how to take advantage of existing best practices is not available while transitioning to XP.
IEEE SoftwareeXtreme Programming development through dialog
29 Citations2000Robert Martin
EXtreme Programming is a software development method that views people, rather than paper, as a project's most potent element and facilitates this by identifying the parties in the conversation and arming them with the clear knowledge of what they are responsible for communicating to others.
XP On A Large Project – A Developer’s View
12 Citations2001Amr Elssamadisy
This paper is written from a developer's point of view, the experiences and the techniques that were tried and either became habit because they were useful, or never quite caught on, and a recommendation of what changes must be made to the XP process to be able to utilize this methodology and still produce quality code at a fast pace for a large project.
Up-Front Design Versus Evolutionary Design in Denali's Persistence Layer
4 Citations2001Jim Little
This experience report describes the evolution of a persistence architecture developed as part of a common code base for internally developed web applications using Extreme Programming and a team of six programmers.