| | ||||||||||
| Extreme Programming Refactored: The Case Against XP | |
| by Matt Stephens and Doug Rosenberg | ISBN:1590590961 |
| Apress © 2003 | |
| This text provides a thorough and systematic analysis of XP practices, proposing better ways of achieving XP's agile goals that are applicable to a much wider range of projects. | |
| Table of Contents | |||
| | Extreme Programming Refactored”The Case Against XP | ||
| | Emperor™s New Code (a Story) | ||
| | Preface | ||
| | Introduction | ||
| Part I - Another Fine Mess You™ve Gotten Me Into (Laurel and Hardy Take Up Programming) | |||
| | Chapter 1 | - | XP in a Nuthouse (Oops, We Mean Nutshell) |
| | Chapter 2 | - | Where Did XP Come From? (Chrysler Knows It Ain™t Easy . . .) |
| | Chapter 3 | - | The Case Against XP |
| Part II - Social Aspects of XP (Mama Don™t Let Your Coders Grow Up to Be Cowboys) | |||
| | Chapter 4 | - | Extremo Culture |
| | Chapter 5 | - | The On-site Customer |
| | Chapter 6 | - | Pair Programming (Dear Uncle Joe, My Pair Programmer Has Halitosis) |
| | Chapter 7 | - | Oral Documentation (Oxymoronic, or Just Plain Moronic?) |
| Part III - We Don™t Write Permanent Specs and Barely Do Any Upfront Design, So . . . | |||
| | Chapter 8 | - | Design After First Testing |
| | Chapter 9 | - | Constant Refactoring After Programming (If It Ain™t Broke, Fix It Anyway) |
| | Chapter 10 | - | User Stories and Acceptance Tests |
| Part IV - The Perpetual Coding Machine | |||
| | Chapter 11 | - | Software Is Never Done (The Schedule Does Not Exist Per Se) |
| | Chapter 12 | - | Emergent Architecture and Design |
| | Chapter 13 | - | Embracing Change (Embrace People, Manage Change) |
| Part V - The Big Picture | |||
| | Chapter 14 | - | Scalability |
| | Chapter 15 | - | Refactoring XP |
| | Chapter 16 | - | Conclusion: Neutralizing the Reality Distortion Field |
| | Index | ||
| | List of Figures | ||
| | List of Tables | ||
| | List of Sidebars | ||