Software development projects can be fun, productive, and even daring. Yet they can consistently deliver value to a business and remain under control.
Extreme Programming (XP) was conceived and developed to address the specific needs of software development conducted by small teams in the face of vague and changing requirements. This new lightweight methodology challenges many conventional tenets, including the long-held assumption that the cost of changing a piece of software necessarily rises dramatically over the course of time. XP recognizes that projects have to work to achieve this reduction in cost and exploit the savings once they have been earned.
Fundamentals of XP include:
Distinguishing between the decisions to be made by business interests and those to be made by project stakeholders.
Writing unit tests before programming and keeping all of the tests running at all times.
Integrating and testing the whole system--several times a day.
Producing all software in pairs, two programmers at one screen.
Starting projects with a simple design that constantly evolves to add needed flexibility and remove unneeded complexity.
Putting a minimal system into production quickly and growing it in whatever directions prove most valuable.
Why is XP so controversial? Some sacred cows don't make the cut in XP:
Don't force team members to specialize and become analysts, architects, programmers, testers, and integrators--every XP programmer participates in all of these critical activities every day.
Don't conduct complete up-front analysis and design--an XP project starts with a quick analysis of the entire system, and XP programmers continue to make analysis and design decisions throughout development.
Develop infrastructure and frameworks as you develop your application, not up-front--delivering business value is the heartbeat that drives XP projects.
Don't write and maintain implementation documentation--communication in XP projects occurs face-to-face, or through efficient tests and carefully written code.
You may love XP, or you may hate it, but Extreme Programming Explained will force you to take a fresh look at how you develop software.
Table of contents
1. The Problem
- 1. Risk: The Basic Problem
- 2. A Development Episode
- 3. Economics of Software Development
- 4. Four Variables
- 5. Cost of Change
- 6. Learning to Drive
- 7. Four Values
- 8. Basic Principles
- 9. Back to Basics
2. The Solution
- 10. A Quick Overview
- 11. How Could This Work?
- 12. Management Strategy
- 13. Facilities Strategy
- 14. Splitting Business and Technical Responsibility
- 15. Planning Strategy
- 16. Development Strategy
- 17. Design Strategy
- 18. Testing Strategy
3. Implementing XP
- 19. Adopting XP
- 20. Retrofitting XP
- 21. Lifecycle of an Ideal XP Project
- 22. Roles for People
- 23. 20–80 Rule
- 24. What Makes XP Hard
- 25. When You Shouldn't Try XP
- 26. XP at Work
- 27. Conclusion
- A. Annotated Bibliography
- Title: Extreme Programming Explained
- Release date: October 1999
- Publisher(s): Addison-Wesley Professional
- ISBN: 9780201616415
You might also like
40 Algorithms Every Programmer Should Know
Learn algorithms for solving classic computer science problems with this concise guide covering everything from fundamental …
Lean Software Development: An Agile Toolkit
Lean Software Development: An Agile Toolkit Adapting agile practices to your development organization Uncovering and eradicating …
Unit Testing Principles, Practices, and Patterns
Unit Testing Principles, Patterns and Practices teaches you to design and write tests that target the …
Software Engineering at Google
Today, software engineers need to know not only how to program effectively but also how to …