• Corpus ID: 46768313

Extreme programming explained - embrace change

@inproceedings{Beck1990ExtremePE,
  title={Extreme programming explained - embrace change},
  author={Kent L. Beck},
  year={1990}
}
Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises… 

Figures from this paper

Development Lifecycle for Extreme Programming
TLDR
The proposed framework makes XP be useful for small teams of specialists, who are able to communicate well with the end-users and who are smart designers and implementers thus providing productivity and maintenance practices for developing quality products which could facilitate to comprehend the international standards.
Fast development Extreme Programming (XP)
TLDR
This paper summarizes the emergence of agile methodologies, their values, principles and some comparisons with traditional methodologies and eXtreme Programming, the most popular agile methodology today, is described almost in cellular form.
Extreme programming and its development practices
  • R. Juric
  • Computer Science
    ITI 2000. Proceedings of the 22nd International Conference on Information Technology Interfaces (Cat. No.00EX411)
  • 2000
TLDR
The paper gives an overview of XP practices and raises some serious concerns regarding their role in conceptual modelling and code generation; which directly affects software architecture solutions.
Extreme programming modified: embrace requirements engineering practices
TLDR
This paper assesses XP from two points of view: the capability maturity model and the Sommerville-Sawyer model (1997) and proposes how to introduce documented requirements to XP, how to modify the planning game to allow many customer representatives and how to get a wider perspective of a system to be built at the beginning of the project lifecycle.
Improving requirements management in extreme programming with tool support - an improvement attempt that failed
TLDR
The principal results show that the Storymanager tool was found to be too difficult to use and that it failed to provide as powerful a visual view as the paper-pen board method.
eXtreme Software Development (XSoft)
TLDR
XSoft is a new methodology to manage software development successfully has been evolved and it is derived from Extreme Programming and COSMIC-Full Function Point and named as EXtreme Software Development (XSoft).
Formal Extreme (and Extremely Formal) Programming
TLDR
The thesis is that most of XP practices are technology independent and therefore can be used in FM based developments, and other essential pieces like test first, incremental development and refactoring can be improved by using FM.
Evolving to a "lighter" software process: a case study
  • R. Moore
  • Computer Science
    Proceedings 26th Annual NASA Goddard Software Engineering Workshop
  • 2001
TLDR
This paper describes the experiences of a development effort within an organization of the United States government as it tried to evolve to a lighter process.
Using extreme programming to manage high-risk projects successfully
Today, software development and its process management is a demanding task. The development company must reach the project goals on time and in budget. On the other hand, requirements change daily,
Maximum Commonality Problems: Applications and Analysis
TLDR
This work introduces the problem of assigning pairs of developers to modules so as to maximize the commonality---a measure of the extent to which common developers work on related modules---subject to a load-balancing constraint that is motivated by the need to control the completion time of the project.
...
...