in 99 words

Any big change is a challenge. When adopting XP, expect the first few months to be chaotic, and a little painful, as everyone gets up to speed. Give yourself four to nine months to feel truly comfortable with your new process.

If you can, adopt XP all at once. This works best when you have a brand-new codebase. It's the easiest way to learn.

When applying XP to an existing project, take an incremental approach. Start by introducing the structural practices. Follow up with the technical practices, paying down technical debt and chipping away at your bug backlog.

as haiku

freshly turned soil--
fertile, waiting, it smells like
possibility

Commentary

Marick's Missing Manifesto

Inside the Book

• Go!
• Sidebar: Extreme Shopping
• The Challenge of Change
• Final Preparation
• Sidebar: Second Adopter Syndrome
• Applying XP o a Brand-New Project (Recommended)
• Applying XP to an Existing Project
  • The big decision
  • Bring order to chaos
  • Pay down technical debt
  • Organize your backlog
  • Fix important bugs
  • Move testers forward
  • Emerge from the darkness
• Applying XP in Phase-Based Organizations
  • Mandatory planning phase
  • Mandatory analysis phase
  • Mandatory design phase
  • Mandatory coding phase
  • Mandatory testing phase
  • Mandatory deployment phase
• Extremities: Applying Bits and Pieces of XP
  • Iterations
  • Retrospectives
  • Ten-minute build
  • Continuous integration
  • Test-driven development
  • Other practices