Subscribe

Extreme Programming Explained

Diposting oleh Information and Technology on Sabtu, 02 Mei 2009

Addison Wesley

This is a book about Extreme Programming (XP). XP is a lightweight methodology for small-to-
medium-sized teams developing software in the face of vague or rapidly changing requirements.
This book is intended to help you decide if XP is for you. To some folks, XP seems like just good common sense. So why the "extreme" in the name? XP takes commonsense principles and practices to extreme levels.
  1. If code reviews are good, we'll review code all the time (pair programming).
  2. If testing is good, everybody will test all the time (unit testing), even the customers (functional testing).
  3. If design is good, we'll make it part of everybody's daily business (refactoring).
  4. If simplicity is good, we'll always leave the system with the simplest design that supports its current functionality (the simplest thing that could possibly work).
  5. If architecture is important, everybody will work defining and refining the architecture all the time (metaphor).
  6. If integration testing is important, then we'll integrate and test several times a day (continuous integration).
  7. If short iterations are good, we'll make the iterations really, really short—seconds and minutes and hours, not weeks and months and years (the Planning Game).

When I first articulated XP, I had the mental image of knobs on a control board. Each knob was a
practice that from experience I knew worked well. I would turn all the knobs up to 10 and see what happened. I was a little surprised to find that the whole package of practices was stable,
predictable, and flexible.
For more information Download This book..

File type : pdf
Size : 552.81 KB
Download Now

Label:

0 komentar:

Posting Komentar
Langganan: Posting Komentar (Atom)