Extreme Programming Installed
Summary
The book is about a software development methodology called Extreme Programming, and it particularly focuses on what makes an XP project work. The first chapter explains the concept of XP and discusses the different players in an XP project. The principle of XP can apply to any moderately sized projects that need to deliver quality software rapidly and flexibly. Let’s take a look at who is needed in the process: customers, programmers and managers. Customers express what must be done in terms of stories. Programmers build the system and keep it integrated at all times so there is always a good version to look at. Finally, managers’ cause, coordinate, report, reward, and remove obstacles for the team. The first chapter goes into more detail about the responsibilities and rights of these three players. Chapter two discusses the circle of life: define, estimate, choose, and build. It boils down to the need for the customers and programmers to understand that they depend on each other and that dependency could be responsible for the success of the project. The third chapter focuses on communication and its importance in the XP methodology. The customer and programmers need to work in concert and as physically close as possible. Written communications take much more time and effort than face-to-face conversations. However, if the customer cannot be physically present all the time it is important to get someone to represent the customer locally and be constantly in contact with the real customer.
Discussion
The information provided by the first chapters of this book was very informative and useful. I believe it discusses many things that you would think are obvious after you read them but you haven’t really thought about it before. Even for projects that might not be suited for XP, the book may be extremely useful as it has general information applicable to any software development project.
No comments:
Post a Comment