📖 Overview
Planning Extreme Programming provides guidance on integrating XP planning practices into software development teams. The book outlines specific techniques for estimating, prioritizing, and scheduling work within the XP methodology.
The text walks through the key roles involved in XP planning, including customers, developers, trackers, and managers. It covers essential planning activities like writing user stories, breaking down tasks, and conducting iteration planning meetings.
Beck presents concrete examples and addresses common challenges teams face when implementing XP planning approaches. The material includes worksheets, templates, and practical tips that teams can apply immediately.
The book's focus on sustainable pace and continuous delivery reflects broader themes about maintaining development momentum while responding to change. Its approach emphasizes technical excellence balanced with business value.
👀 Reviews
Readers found this book more practical and actionable than many other XP texts. The step-by-step planning processes and real-world examples helped teams implement XP methods.
Likes:
- Clear explanations of story cards, iterations, and estimating
- Useful templates and worksheets
- Focus on practical planning over theory
- Short length makes it accessible
Dislikes:
- Content feels dated compared to modern agile practices
- Some examples are overly simplistic
- Limited coverage of scaling XP to larger teams
- Too basic for experienced practitioners
One reader noted: "The concrete examples helped our team start using XP immediately, though we had to adapt some practices for our larger organization."
Ratings:
Goodreads: 3.8/5 (249 ratings)
Amazon: 3.9/5 (32 ratings)
Several reviewers recommended reading this alongside "Extreme Programming Explained" to get both practical and theoretical XP foundations. Multiple readers called out the book's age (published 2000) but said the core planning concepts remain relevant.
📚 Similar books
Extreme Programming Explained by Kent Beck
This guide establishes the core principles and practices of Extreme Programming methodology.
The Pragmatic Programmer by Dave Thomas The text presents practical techniques and tools for software development through real-world examples and case studies.
Test-Driven Development by Kent Beck The book demonstrates the practice of writing tests before code to create robust software solutions.
Agile Software Development Principles, Patterns, and Practices by Robert C. Martin The work integrates agile methodologies with software design principles through pattern implementations and coding examples.
User Stories Applied by Mike Cohn This reference details the creation and use of user stories in agile development through practical implementation steps.
The Pragmatic Programmer by Dave Thomas The text presents practical techniques and tools for software development through real-world examples and case studies.
Test-Driven Development by Kent Beck The book demonstrates the practice of writing tests before code to create robust software solutions.
Agile Software Development Principles, Patterns, and Practices by Robert C. Martin The work integrates agile methodologies with software design principles through pattern implementations and coding examples.
User Stories Applied by Mike Cohn This reference details the creation and use of user stories in agile development through practical implementation steps.
🤔 Interesting facts
🔸 Kent Beck not only wrote about XP (Extreme Programming) but is considered its founder, developing the methodology while working on the Chrysler Comprehensive Compensation System project in 1996.
🔸 Planning Extreme Programming was co-authored with Martin Fowler, another influential software development expert who wrote the bestselling "Refactoring: Improving the Design of Existing Code."
🔸 The book introduced the concept of "Planning Game," a collaborative approach where business and technical teams work together to estimate and prioritize features, which has influenced modern agile estimation techniques.
🔸 While published in 2000, many of the book's core principles about iterative planning and customer collaboration became foundation elements of the Agile Manifesto, which was created just one year later in 2001.
🔸 The planning techniques described in the book were revolutionary for their time, as they rejected the traditional long-term detailed planning approach in favor of short cycles and frequent adjustments - now a standard practice in software development.