Extreme Programming Refactored: The Case Against XP
Extreme Programming Refactored: The Case Against XP
ISBN: 1590590961
EAN: 2147483647
EAN: 2147483647
Year: 2003
Pages: 156
Pages: 156
Authors: Matt Stephens, Doug Rosenberg
- Table of Contents
- BackCover
- Extreme Programming Refactored - The Case Against XP
- Emperor s New Code (a Story)
- Preface
- Introduction
- How to Read This Book
- Key to Icons
- Satire Stories
- Voice of eXPerience (VoXP) Stories
- Songs of the Extremos
- 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)
- Extreme Programming in Theory
- The Practices
- The Activities
- What Problems Are Being Targeted by XP?
- What Problems That Manifest in Your Typical Software Project Are Being Targeted by XP?
- What Problems with Existing Methodologies Are Being Targeted by XP?
- Extreme Programming in Practice: The Voice of eXPerience
- Knocking It Down . . . and Then Rebuilding It
- The Values
- The Activities
- The Other Stuff
- Summary
- Chapter 2: Where Did XP Come From? (Chrysler Knows It Ain t Easy . . .)
- Overview of C3
- The XP Project Life Cycle (As Illustrated by the Activities at C3)
- Claims That It Wasn t Really Important
- Too Tough for the On-site Customer
- Summary
- Chapter 3: The Case Against XP
- A Self-Referential Safety Net (Circle of Snakes)
- From Symbiosis to Symbolism
- Circle of Life or Circle of Snakes?
- Letting the Snakes Unravel
- Tailoring a Process to Local Conditions: Why XP Stands on Its Head
- Summary
- Part II: Social Aspects of XP (Mama Don t Let Your Coders Grow Up to Be Cowboys)
- Chapter 4: Extremo Culture
- XP Is Not About Mindless Hacking
- XP Goes Mainstream
- XP and the Dot-com Boom
- XP As a People Process
- The XP Manifesto: More Cheesy Puffs, Comrade?
- XP Terminology
- Big Words Like Constantinople and TerminationCanBeSuccess
- Shooting the Messenger
- Fear
- Summary
- Chapter 5: The On-site Customer
- That s the Customer s Problem
- On-site Customer: The Old Testament
- On-site Customer: The New Testament
- No Safety Net
- Summary
- Chapter 6: Pair Programming (Dear Uncle Joe, My Pair Programmer Has Halitosis)
- Pair Programming Basics
- There s a Study That Proves My Point
- Wishing for the Sound of Silence
- It s a Work of Love, Enforced by Coercive Means
- Productivity: numProgrammers2numProgrammers? Right?
- Pair Programming Illuminated
- Watch Out, There s a Snake Under the Desk
- Summary
- Chapter 7: Oral Documentation (Oxymoronic, or Just Plain Moronic?)
- But I Thought You Said . . .
- Requirements Documentation
- Just Plain Moronic
- Summary
- Part III: We Don t Write Permanent Specs and Barely Do Any Upfront Design, So . . .
- Chapter 8: Design After First Testing
- When All You ve Got Is a Hammer
- XP Design Mantra: No BDUF
- Problems with Unit Testing
- Programming Without a Safety Net
- Summary
- Chapter 9: Constant Refactoring After Programming (If It Ain t Broke, Fix It Anyway)
- Refactoring Heaven
- XP Design Mantra: Refactor Mercilessly
- Is Up-Front Design Sufficient to Avoid Large Refactorings Later?
- Refactoring with an Installed User Base
- Summary
- Chapter 10: User Stories and Acceptance Tests
- Tell Me a Story, Daddy
- User Stories vs. Use Cases
- User Stories vs. Requirements
- Documenting Requirements As Acceptance Tests
- Summary
- Part IV: The Perpetual Coding Machine
- Chapter 11: Software Is Never Done (The Schedule Does Not Exist Per Se)
- The Schedule Doesn t Exist Per Se
- Rejecting the Notion of Doneness
- Optional-Scope Contracts
- Summary
- Chapter 12: Emergent Architecture and Design
- XP Design Mantra: YAGNI
- Building an Infrastructure with Emergent Design
- Emergent Architecture vs. Early Prototyping
- Summary
- Chapter 13: Embracing Change (Embrace People, Manage Change)
- The Cost of Change Curve (aka the Cost to Fix Defects Curve)
- Release Early, Release Often
- Release Planning
- Iteration Planning
- The Perpetual Coding Machine (Embracing Change)
- What Is This Change of Which You Speak?
- Use Up-Front Design to Enhance Agility
- Summary
- Part V: The Big Picture
- Chapter 14: Scalability
- Painting Over the Cracks: XP on a 50-Person Project
- Summing Up
- Architectural Scalability
- Scalability Drives the Architecture
- When XP Starts to Fail
- Summary
- Chapter 15: Refactoring XP
- How to Be Agile Without Being Fragile
- Extreme Programming Defanged: Taking the Extreme out of XP
- Case Study: The Server Tools Project (Using a Defanged, Much Less Extreme but Still Very Agile Process)
- Summary
- Chapter 16: Conclusion: Neutralizing the Reality Distortion Field
- Ethereal Wizardry in Action
- Bad Advice by Any Other Name Is Still Bad Advice
- At the End of the Day
- In Closing
- Index
- Index_B
- Index_C
- Index_D
- Index_E
- Index_F
- Index_G
- Index_H
- Index_I
- Index_J
- Index_K
- Index_L
- Index_M
- Index_N
- Index_O
- Index_P
- Index_Q
- Index_R
- Index_S
- Index_T
- Index_U
- Index_V
- Index_W
- Index_X
- Index_Y
- List of Figures
- List of Tables
- List of Sidebars
Extreme Programming Refactored: The Case Against XP
ISBN: 1590590961
EAN: 2147483647
EAN: 2147483647
Year: 2003
Pages: 156
Pages: 156
Authors: Matt Stephens, Doug Rosenberg