Extreme Programming (XP) is a new lightweight software developing methodology. XP is the most popular of the “agile” development methodologies. Agile development is an integral part of technology movements in the software development world. XP has quickly gained in popularity over the last few years and is now becoming recognized by development shops from large consulting firms through small software houses. Some of the companies that are using XP include DaimlerChrysler, First Union National Bank, and Ford Motor Company.

Sams Teach Yourself Extreme Programming in 24 Hours includes coverage on Extreme Programming, agile development, automated test frameworks (Junit, etc.), Automated Build (Ant), and Refactoring in a step-by-step approach.

Extreme Programming (XP) has been established as a significant departure from traditional software development methods. The success of the XP 2001 and XP Universe 2001 conferences is no surprise; some of the brightest minds in software engineering gathered at these venues to discuss the discipline that is XP. These conferences showcase the continuously changing face of XP. Common programming practices will never be the same, and developers and business people alike need to bear this fact in mind as they plan for the future.Inspired by the techniques and challenges explored at these conferences, Extreme Programming Perspectives presents 47 articles that represent the insights and practical wisdom of the leaders of the XP community. Encompassing a wide variety of key topics on XP and other agile methodologies, this book offers experience-based techniques for implementing XP effectively and provides successful transitioning strategies. Articles are grouped into six main sections: an overview of XP and agile methodologies; XP development practices; issues involved in transitioning to XP and agile methodologies; real-life experiences of working with XP; tools for facilitating XP development; and finally, ideas for expanding and extending XP.

Extreme Programming Refactored: The Case Against XP (featuring Songs of the Extremos) takes a satirical look at the increasingly hyped Extreme Programming methodology. It explores some quite astonishing Extremo quotes that have typified the XP approach quotes such as, XPers are not afraid of oral documentation, Schedule is the customers problem, Dependencies between requirements are more a matter of fear than reality and Concentration is the Enemy.

In between the chuckles, though, there is a serious analysis of XPs many flaws. The authors also examine C3, the first XP project, whose team (most of whom went on to get XP book deals shortly before C3s cancellation) described themselves as “the best team on the face of the Earth”. (In a later chapter, the authors also note that one problem which can affect pair programmers is overconfidence or is that “eXcessive courage”). The authors examine whether the problems that led to C3s inexplicable cancellation could also afflict present-day XP projects.

In the final chapter (Refactoring XP) Matt and Doug suggest some ways of achieving the agile goals of XP using some XP practices (used in moderation) combined with other, less risk-laden methods.

Developing complex software requires more than just churning out lines of code. As a software architect or developer involved in an industrial project, you must understand and be able to leverage critical software subdisciplines such as architecture, analysis and design techniques, development processes, visual modeling, and the underlying technology to be successful. This book brings all these diverse elements together from the Java 2 Platform, Enterprise Edition (J2EE) development perspective to provide a holistic approach for the reader. Specifically, this book tries to answer the following key questions: What is the Unified Modeling Language (UML), and how is it relevant to J2EE development? How do Java and UML relate to each other? What are the key concepts in software architecture? How does a software development process fit into the J2EE software development equation? How can analysis and design help you to arrive at a better J2EE application design? What are the key J2EE technologies, and how do they fit together? How can you leverage the UML for J2EE development? Rather than reinvent the wheel, the approach taken in this book is that of bringing together known works, such as Jim Conallen’s Web Modeling Profile and the Sun Java Specification Request-26 for UML/EJB Mapping Specification. To provide a practical illustration of the topics discussed, this book guides you through a sample J2EE application development project using the Rational Unified Process (RUP) and the UML. A working implementation is provided. Suggestions for further enhancements are also listed to assist you in continuing your exploration of the UML and J2EE technologies. Intended Audience This book is suitable for anyone interested in learning about the UML and how it can be applied to J2EE development. Current J2EE application developers will learn how to apply the UML to J2EE application development. UML practitioners will benefit from learning about the J2EE in the context of the UML. And software professionals interested in learning both the UML and J2EE will be able to get to a productive state faster facilitated by the intertwined contextual discussion.

You know what XP is, how to get it up and running, and how to plan projects using it. Now it’s time to expand your use of Extreme Programming and learn the best practices of this popular discipline.

In Extreme Programming Explored, you can read about best practices as learned from the concrete experience of successful XP developers. Author and programmer Bill Wake provides answers to practical questions about XP implementation. Using hands-on examples–including code samples written in the Java programming language–this book demonstrates the day-to-day mechanics of working on an XP team and shows well-defined methods for carrying out a successful XP project.

The book is divided into three parts:

• Part 1, Programming–programming incrementally, test-first, and refactoring.
• Part 2, Team Practices–code ownership, integration, overtime, and pair programming; how XP approaches system architecture; and how a system metaphor shapes a common vision, a shared vocabulary, and the architecture.
• Part 3, Processes–how to write stories to plan a release; how to plan iterations; and the activities in a typical day for the customer, the programmer, and the manager of an XP project.

To demonstrate how an XP team uses frequent testing, you’ll learn how to develop the core of a library search system by unit testing in small increments. To show how to make code ready for major design changes, the author teaches you how to refactor a Java program that generates a Web page. To see how a system metaphor influences the shape of a system, you’ll learn about the effects of different metaphors on customer service and word processing applications. To show how customers and programmers participate in release planning, the book demonstrates writing and estimating stories, and shows how the customer plans a release.