RDP Technique: Take a Different Look at XP for Adoption
Authors:
- Mehdi MirakhorliMMMehdi Mirakhorli
- Abdorrahman Khanipour RadARAbdorrahman Khanipour Rad
- Fereidoon Shams AlieeFAFereidoon Shams Aliee
- Abbas MirakhorliAMAbbas Mirakhorli
- Maryam PazokiMPMaryam Pazoki
- 1 March 2008
- conference paper
- Published by Institute of Electrical and Electronics Engineers (IEEE)
- No. 15300803,p. 656-662
Abstract
Although software projects can benefit from XP practices, all projects can't directly adopt it. Characteristics of some projects make it difficult to use XP directly, 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 problems and with the belief that XP's values make it agile, XP's practices do not define XP and XP is defined by its rules, we introduce a practical technique for tailoring XP. Proposed technique benefits from RDP (rule-description-practice) cards for identifying a set of suitable practices for a specific project: organizing "YourXP" software development process.Keywords
This publication has 10 references indexed in Scilit:
- A simple model of agile software processes -- or -- extreme programming annealed2005
- Piloting XP on four mission-critical projectsIEEE Software, 2004
- Introducing xp into greenfield projects: lessons learnedIEEE Software, 2003
- Assessing xp at a european internet companyIEEE Software, 2003
- The Rules of the GameLecture Notes in Computer Science, 2003
- How to Get the Most out of Extreme Programming/Agile MethodsLecture Notes in Computer Science, 2002
- Get ready for agile methods, with careComputer, 2002
- Agile software development: the business of innovationComputer, 2001
- Launching extreme programming at a process-intensive companyIEEE Software, 2001
- Embracing change with extreme programmingComputer, 1999