View in EDS PDF Full Text

RDP Technique: a Practice to Customize XP.

Saved in:
Bibliographic Details
Title: RDP Technique: a Practice to Customize XP.
Authors: Mirakhorli, Mehdi1 m•mirakhorli@sbu.ac.ir, Rad, Abdorrahman Khanipour2 ab•khanipoor@comp.iust.ac.ir, Aliee, Fereidoon Shams1 f•shams@sbu.ac.ir, Pazoki, Maryam3 m•pazoki@sina.icntu.ac.ir, Mirakhorli, Abbas4 abbas.mira@gmail.com
Source: ICSE: International Conference on Software Engineering. 2008, p23-32. 10p. 3 Diagrams, 7 Charts.
Subjects: Extreme programming, Software engineering, Computer programming, Case studies, Computer software
Abstract: Although software projects can benefit from XP practices, but all projects can not directly adopt it. Characteristics of some projects make it difficult to use XP thoroughly; therefore, we need to tailor XP to the local conditions, contexts and the size of these projects. In this article we will describe why defining XP by its practices has problem and argue why it should be defined by its rules. Then we precisely redefine rules of XP. With the belief that XP's practices do not define XP and XP is defined by its rules, we propose RDP practice which is a practical technique for tailoring XP. Finally we conducted an industrial case study. Our goal was to understand the practical feasibility of proposed practice. [ABSTRACT FROM AUTHOR]
Copyright of ICSE: International Conference on Software Engineering is the property of Association for Computing Machinery and its content may not be copied or emailed to multiple sites without the copyright holder's express written permission. Additionally, content may not be used with any artificial intelligence tools or machine learning technologies. However, users may print, download, or email articles for individual use. This abstract may be abridged. No warranty is given about the accuracy of the copy. Users should refer to the original published version of the material for the full abstract. (Copyright applies to all Abstracts.)
Database: Engineering Source
Description
Abstract:Although software projects can benefit from XP practices, but all projects can not directly adopt it. Characteristics of some projects make it difficult to use XP thoroughly; therefore, we need to tailor XP to the local conditions, contexts and the size of these projects. In this article we will describe why defining XP by its practices has problem and argue why it should be defined by its rules. Then we precisely redefine rules of XP. With the belief that XP's practices do not define XP and XP is defined by its rules, we propose RDP practice which is a practical technique for tailoring XP. Finally we conducted an industrial case study. Our goal was to understand the practical feasibility of proposed practice. [ABSTRACT FROM AUTHOR]