Extreme Programming Refactored: The Case Against XP
Before we get started, we want to draw attention to some of this book’s very unique elements. This isn’t your normal, run-of-the-mill computer science book! The subject matter is, we feel, worthy of a satirical treatment, so that’s what we’ve set out to give it. In addition to the satire, there’s al...
Đã lưu trong:
| Những tác giả chính: | , |
|---|---|
| Định dạng: | Sách |
| Ngôn ngữ: | English |
| Được phát hành: |
Apress
2012
|
| Những chủ đề: | |
| Truy cập trực tuyến: | http://scholar.dlu.edu.vn/thuvienso/handle/DLU123456789/31357 |
| Các nhãn: |
Thêm thẻ
Không có thẻ, Là người đầu tiên thẻ bản ghi này!
|
| Thư viện lưu trữ: | Thư viện Trường Đại học Đà Lạt |
|---|
| Tóm tắt: | Before we get started, we want to draw attention to some of this book’s very unique elements. This isn’t your normal, run-of-the-mill computer science book! The subject matter is, we feel, worthy of a satirical treatment, so that’s what we’ve set out to give it. In addition to the satire, there’s also lots of dry humor. We do occasionally get serious and give a systematic breakdown of the flaws and dangers inherent in Extreme Programming (XP).
Having said that, this book isn’t an outright “slam” piece. As we point out later, not all of XP is bad. So we do aim to provide a balanced critique and to signpost the parts of XP that we feel can be salvaged or refactored into something that achieves the same agile goals in a more robust kind of way.
XP has received more than its fair share of hype, and new XP books continue to appear at an incredible rate. The industry is being affected by the inflated claims surrounding XP in all sorts of ways (some of them positive, as we explore, but many of them negative). With this in mind, we feel a book that swims against the tide and rejects XP is important.
Here’s one small example of how XP is affecting the industry. Matt (intrepid coauthor of this book) received an e-mail from a consultant who had just recently lost an important contract because he refused to launch into a project without doing some detailed requirements analysis and up-front design first. The customer had read about XP and told the consultant that “if XP says it’s okay to run a project like that, then we’ll find someone who will skip requirements and up-front design!” |
|---|