This book is about extreme programming. Extreme Programming, often abbreviated "XP", is a simplified production methodology for small to medium-sized development teams developing a software product under conditions of unclear or rapidly changing requirements. This book is designed to help you determine whether XP is justified in your situation...

This part of the book sets the stage on which Extreme Programming is to come. It describes the various aspects of the problem that will be solved by forming a new discipline of software engineering.

This part discusses the basic assumptions that we must take into account when selecting software development techniques - the metaphor of driving a car, four meanings, the principles formed on the basis of these values, as well as the activities that need to be structured within the new discipline of software development.

We can consider that we have set the stage on which the discipline we are developing is to appear. We got acquainted with the problem that we have to solve. We realized that to formulate a solution to this problem, we needed to define how coding, testing, listening, and design—the four basic activities that any software project must do—should be done. We have a set of guiding values and principles that will help us choose strategies for each of these activities. Finally, we know that the cost curve should be flat, not exponential, so that we can work efficiently on a software project within XP.

In this part of the book, we will discuss the practical application of the strategies described in the previous one. parts. Once you have chosen a simplified set of strategies, you have significantly more flexibility with which you can use them. You can use this flexibility for many purposes, but first of all, you should know that this flexibility exists and what opportunities it opens up for you.