TABLE OF CONTENTS In this chapter, we will consider what experiences teams developing with XP and Agile Modelling methods have had. It considers what issues have been found and how they have been overcome. It does reach some contentious conclusions about some aspects of XP and also considers what happens when XP is applied to larger software projects.
The remainder of this chapter is structured in the following manner. Section 8.2 reviews the twelve XP practices given the current experiences. Section 8.3 considers other factors such as scalability and the use of daily meetings. Section 8.4 addresses the issue of the need for a core software architecture around which to build the software. Section 8.5 addresses the uses of XP on larger projects, while Section 8.6 considers where XP tends to be applied most successfully.
One of the biggest benefits of the planning game is that it requires a great deal of interaction between the developers and the customers. It thus helps to breakdown barriers and open the two sides of the project up to each other. Post-planning game, people know each other by name, can put a face to that name and are able to work together more effectively.
It is also typically important to capture performance and quality expectations at this stage as well as user stories. Not all requirements can easily be expressed (or at least are best expressed) as user stories.
The definition of a...
