Overview
Extreme Programming (XP) is a recent methodology for software development that has become something of a movement. Some dismiss XP as a frivolous or even dangerous fad, while others pursue it with religious zeal. XP is not just a collection of programming techniques, but a philosophy of project management. At its heart, XP is about managing risk and change, two of the most significant factors in the failure of software projects.
This session will explain the core practices of Extreme Programming:
the planning game
pair programming
testing
on-site customer
collective ownership
small releases
metaphor
simple design
refactoring
continuous integration
40-hour week
coding standards
Attention will be paid to the more radical-seeming practices like pair programming, of which one might ask, “Does that actually work?” We will also see how XP makes a clear distinction between business and technical responsibilities, defining which decisions are made by the Customer and which ones belong to the Developer. There is even a “Bill of Rights” for both the Customer and Developer. While XP is still in its infancy, some case studies of XP in action will be discussed, as well as the presenter’s own experience in Flash projects.
Who should attend:
“Seat of Your Pants” developers will learn how the disciplines and structure of Extreme Programming can bring method to their madness, saving them time and frustration but remaining flexible and fun.
“Big Plan Up Front” developers will see a different perspective on software development that addresses some limitations of the traditional approach to software engineering, and how XP practices could be implemented gradually in existing projects.
Project managers and business decision-makers will learn how Extreme Programming can improve the quality and timely delivery of software while giving them more freedom to change priorities and requirements during development without penalty.
