Presenting and Evaluating Scaled Extreme Programming Process Model

Abstract

Extreme programming (XP) is one of the widely used software process model for the development of small scale projects from agile family. XP is widely accepted by software industry due to various features it provides such as: handling frequent changing requirements, customer satisfaction, rapid feedback, iterative structure, team collaboration, and small releases. On the other hand, XP also holds some drawbacks, including: less documentation, less focus on design, and poor architecture. Due to all of these limitations, XP is only suitable for small scale projects and doesn't work well for medium and large scale projects. To resolve this issue many researchers have proposed its customized versions, particularly for medium and large scale projects. The real issue arises when XP is selected for the development of small scale and low risk project but gradually due to requirement change, the scope of the project changes from small scale to medium or large scale project. At that stage its structure and practices which works well for small project cannot handle the extended scope. To resolve this issue, this paper contributes by proposing a scaled version of XP process model called SXP. The proposed model can effectively handle such situation and can be used for small as well as for medium and large scale project with same efficiency. Furthermore, this paper also evaluates the proposed model empirically in order to reflect its effectiveness and efficiency. A small scale client oriented project is developed by using proposed SXP and empirical results are collected. For an effective evaluation, the collected results are compared with a published case study of XP process model. It is reflected by detailed empirical analysis that the proposed SXP performed well as compared to traditional XP.

Development of Reading Literacy Application System using Extreme Programming Method

“…Menurut [4], dalam manajemen proyek klasik yang mengikuti proses perencanaan dan eksekusi "waterfall", hasil yang diharapkan dikomunikasikan dengan baik dan jelas oleh klien pada awal proyek, sehingga proyek dikerjakan secara terarah dan terencana, perencanaan dilakukan dengan holistik, mulai dari awal hingga selesai, dengan tanggung jawab dan batas waktu yang telah ditetapkan. Sedangkan extreme programming menurut [5], bahwa XP dirancang untuk tim kecil dalam mengembangkan proyek skala kecil dengan cakupan terbatas. Dalam XP, pengumpulan engineering yang baik serta langkah-langkah SDLC yang sederhana membantu menghasilkan produk perangkat lunak berkualitas tinggi dalam waktu yang telah dijadwalkan, namun dengan ruang lingkup yang terbatas.…”

Developing a Decision Support System for Supply Chain Component

“…The diagram design focuses on the application of user stories defined at the planning stage by developing specifications regarding program architecture, interfaces, and supporting elements. The design begins with creating the CRC card and a prototype solution (Ibrahim et al, 2020). In addition, system modelling is carried out using case diagrams that aim to show business processes and actor interactions with the system.…”

Extreme Programming vs Scrum: A Comparison of Agile Models

“…A great interest has been observed as well in customizing XP as it is simple and flexible [23]. An example of such customization is Scaled Extreme Programming [24] XP also assists the developers to consistently recognize and get work done on the software artifacts with higher priorities [15]. Scrum is an iterative project management model which gives a straightforward 'inspect and adapt' system [25].…”