查看文章

Extreme Programming (XP) is a renowned agile model, commonly used for small scale projects. It uses an iterative approach for software development, assisted with agile practices used in extreme manner. Although XP provides the opportunity to handle shortcomings of traditional software development models however it is not exempt from limitations. Lack of proper design, no documentation and poor architectural structure are some of its drawbacks. Furthermore, some of its practices like on-site customer and pair programming are not beneficial in every situation and may cause an extra burden on development process. Simplified Extreme Programming (SXP) process model was proposed to cover these problems without affecting the agility of development process. This paper compares classical XP and proposed SXP with the help of empirical case studies.