Extreme Programming Kent Beck, Ward Cunningham

Software Development History During the 1970s, it was discovered that most large software development projects failed. During the 1980s, many of the reasons for those failures began to be recognized. In the 1990s, experiments and measurements were used to validate individual methods to prevent failure. The current decade is characterized by complete processes to improve success.

Schedule Failure One of the primary causes of project failure was the extended period of time it took to develop a system. Costs escalated and requirements changed. Agile methods were developed to develop systems more quickly with limited time spent on analysis and design.

What are the Agile Methodologies? –FDD –dX (agile RUP) –Open Source –Agile Modeling –Pragmatic Programming eXtreme Programming has received the most attention, but here is a list: –XP –SCRUM –DSDM –The Crystal Family –ASD Since Larman is based on RUP, dX might be interesting.

What is Extreme about XP? A rheostat is a common electrical control. Most volume controls on audio devices are rheostats. It you want silence, turn the knob all the way to one side. For maximum volume, turn the knob all the way to the other side. XP treats good practices in programming as if they had rheostats, and turns all of them all the way up. See examples on next page?

Some eXtreme Practices Are code inspections good? Then code in pairs—all code is inspected all the time! Is testing good? Then write the unit test before the code, automate testing, and run all tests all the time. Is customer contact good? Then locate a customer representative in the team, so that you have access to them all the time.

Extreme Programming Explained

Four principles of XP Communication Simplicity Feedback Courage

Key Ideas in XP Code in Pairs Stay in Contact with the Customer Create Tests before Coding then Test Heavily Short Iterations Keep it Simple Don’t Anticipate: Code for Current Needs Collective Ownership

Update (Fall 2008) At this time, it seems that very few organizations are using eXtreme Programming as a methodology. However, the ideas within it, including test first and pair programming, short iterations, customer contact, no anticipation, and collective ownership have gone mainstream, and are widely practiced by many organizations.

Most "software development" books focus on one of two things: "Big Design Up Front" (BDUF) or "Nitty Gritty Details of Programming" (Hacking). This book does neither. It challenges the idea that disciplined software development implies lots of drawings and a CASE tool. Review by Ken Auer

It challenges the idea that "design" is a waste of time and you just need a good code hacker which you slide pizza to under the crack in the door. It speaks for the quietly successful minority of software developers who believe software that is worth anything is built by teams who communicate, and constantly pay attention to all the details necessary to make sure software development is successful in the eyes of both the customer and the software developer.

It speaks to those who know "there's got to be a better way" than the way typical software is developed, whether BDUF or hacking. And, oh, how it does it. Kent Beck masterfully makes the developer understand the concerns of the sponsor. He also masterfully makes the sponsor aware of what is necessary to get quality software that meets their changing needs.

If you think software is already done right, and refuse to allow this notion to be challenged, ignore this book... you'll hate it. Everyone else having anything to do with software, read it NOW. It will change the way you look at everything you do.

Description by Kent Beck 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.

Description by Kent Beck This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.

Fundamentals of XP Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders. Writing unit tests before programming and keeping all of the tests running at all times. Integrating and testing the whole system- several times a day.

Fundamentals of XP Producing all software in pairs, two programmers at one screen. Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity. Putting a minimal system into production quickly and growing it in whatever directions prove most valuable.

Why is XP so controversial? Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators-every XP programmer participates in all of these critical activities every day. Don't conduct complete up-front analysis and design-an XP project starts with a quick analysis of the entire system, and XP programmers continue to make analysis and design decisions throughout development.

Why is XP so controversial? Develop infrastructure and frameworks as you develop your application, not up-front-delivering business value is the heartbeat that drives XP projects. Don't write and maintain implementation documentation- communication in XP projects occurs face-to-face, or through efficient tests and carefully written code.

Quotes from Book Jacket 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. 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 dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.

Extreme Programming Installed

Doing Extreme Programming While Kent Beck’s Extreme Programming Explained is a good resource for explaining Extreme Programming, it is not very helpful in actually trying to use the practices. Extreme Programming Installed, by Ron Jeffries, Ann Anderson, and Chet Hendrikson is a very good tool for teams that want to start using Extreme Programming.

Web Resources This Web Site has excellent materials on Extreme Programming: Students are required to understand XP. I have used material from this site on exams, so I suggest that every class member review it.