Introducing XP—When Shouldn’t You Use XP?

Microsoft .NET Framework, ASP.NET, Visual C# (CSharp, C Sharp, C-Sharp) Developer Training, Visual Studio

When Shouldn’t You Use XP?

Are there times when XP is not the right choice? Certainly there are. As you’ve learned, communication is a key value of XP. The larger the number of individuals directly involved in a project, the more difficult it gets to manage face-to-face communication. Therefore, it would seem that XP is not well suited for projects with extremely large teams. But note that our experience has indicated that large project teams are rarely, if ever, a good idea.

Another instance where XP might not be the best choice is for a project with requirements that will never change. This phenomenon is rare indeed, and we have not seen such a project in all our years of experience. Industry sectors such as space or military may fall into the solid requirements category.

Finally, remember that XP requires a significant amount of customer involvement. If your customer is not willing to invest the necessary amount of project time, you will be hard-pressed to successfully execute XP.