IJCSNS International Journal of Computer Science and Network Security, VOL.17 No.5, May 2017 259 Manuscript received May 5, 2017 Manuscript revised May 20, 2017 A Comparative Analysis of DXPRUM and DSDM Muhammad Fahad 1 , Salman Qadri 1 , Saleem Ullah 2 , Mujtaba Husnain 1 , Rizwan Qaiser 3 , Shehzad Ahmed Qureshi 4 , Waqas Ahmed 5 , Syed Shah Muhammad 4 1 Department of Computer Science & IT, The Islamia University of Bahawalpur, Pakistan. 2 Department of Computer Science & IT, Khwaja Fareed University of Engineering & IT, Abu Dhabi Road, Rahim Yar Khan, Pakistan. 3 Department of Computer Science, National University of Computer & Emerging Sciences, Lahore, Pakistan. 4 Department of Computer Science, Virtual University of Pakistan. 5 Institute of Computing, Bahauddin Zakariya University, Multan, Pakistan. Abstract Agile methodologies are taking over the traditional software development methodologies with the passage of time. These methodologies involve more benefits than traditional software development methodologies and very fewer drawbacks. Due to these benefits, the software development teams are more involved in Agile methodologies. There are a number of Agile methodologies which are famous in software development community. Each of them has its own benefits and drawbacks. Proposing one suitable Agile methodology for a project may benefit the project in one direction but may also cause the project to suffer in some other direction. Due to this fact, the idea of hybrid Agile methodologies evolved. DXPRUM is also one of those hybrid methodologies and is a combination of DSDM, XP, and Scrum. This paper presents a comparative study of DXPRUM and DSDM by applying them to some real time projects and thus comparing their results. Key-words: Agile, Hybrid Methodologies, XP, RUP, Scrum. 1. Introduction ‘Agile’ as the name suggests, are fast ways for developing software with minimum budget and without compromising the quality. Creating high-quality software within low budget and with a minimum amount of time is always a crucial task. Agile methodologies are also better over traditional iterative or incremental methodologies when it comes to large and ambiguous requirements which lead to low-quality software. According to Edeki, breaking the large requirements down into more manageable sub-requirements, the Agile process naturally promotes better estimation [1]. As a result of the overall quality of the software increases. This is the reason why more and more software companies are converting themselves from traditional software development methodologies to Agile. According to a survey conducted by the US and Europe in 2005, it is revealed that 14 percent of companies were using agile methods at that time, and further 49 percent of the companies aware of agile methods were interested in adopting them [2] and these numbers are improving day by day. After having some reading of Agile methodologies, it comes to mind that Agile methods such as XP and Scrum can be viewed as a reaction to traditional and plan based methods, which emphasized an engineering-based and rationalized approach[3]. On the other hand, Agile addresses unpredictability; creeping requirements by focusing much on talented people and their relationship bring to software development [4]. Now with the passage of time, researchers are more focused on combining the advantages of different methodologies in order to get best out of them. This idea is not only limited to combining Agile methodologies, but it also involves traditional software development methodologies like a waterfall or iterative methods. Different researchers proposed hybrid methodologies which are proved to be quite good when it comes to high-quality software. This research work is based on a comparative study of a hybrid Agile methodology DXPRUM with another famous Agile methodology DSDM and to reach a conclusion by comparing their results. 2. Materials and Methods Hybrid Agile methodologies are gaining popularity due to the fact that they involve best rules and practices of the combined methodologies and by leaving their drawbacks. Many researchers in recent past work on different Agile methodologies and proposed hybrid models. Mushtaq and Qureshi (2012) proposed a novel hybrid model by combining two Agile methodologies which are Scrum and XP [5]. Similarly, Bashir and Qureshi (2012) proposed a hybrid software development approach for small to medium scale projects by combining the best practices of RUP, XP, and Scrum [6]. Qureshi (2012) proposed