RDP Technique: Take a Different Look at XP for Adoption
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 descri...
Gespeichert in:
Hauptverfasser: | , , , , |
---|---|
Format: | Tagungsbericht |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 662 |
---|---|
container_issue | |
container_start_page | 656 |
container_title | |
container_volume | |
creator | Mirakhorli, M. Rad, A.K. Aliee, F.S. Mirakhorli, A. Pazoki, M. |
description | 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. |
doi_str_mv | 10.1109/ASWEC.2008.4483259 |
format | Conference Proceeding |
fullrecord | <record><control><sourceid>ieee_6IE</sourceid><recordid>TN_cdi_ieee_primary_4483259</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>4483259</ieee_id><sourcerecordid>4483259</sourcerecordid><originalsourceid>FETCH-LOGICAL-i90t-f5b2c48afb77b52baaf31b9b42abfa153292261bad3918402c1a9abe3f197f5c3</originalsourceid><addsrcrecordid>eNotj0tOwzAUAC0-EqX0ArDxBRKen-3YZhel5SNFooJIsKueU1uYQlKSsOD2INHV7EYzjF0KyIUAd10-v6yqHAFsrpSVqN0Rm6E0JtMK7DFbOGPBFE5LAWBO2ExoCRlYkGfsfBzfARAUFDNmnpZr3oT2rUtf3-GGN7QLnPgyxRiG0E287vsdp4m_rnnsB15u-_2U-u6CnUb6GMPiwDlrbldNdZ_Vj3cPVVlnycGURe2xVZaiN8Zr9ERRCu-8QvKR_prQIRbC01Y6YRVgK8iRDzIKZ6Ju5Zxd_WtTCGGzH9InDT-bw7L8BfA5RvI</addsrcrecordid><sourcetype>Publisher</sourcetype><iscdi>true</iscdi><recordtype>conference_proceeding</recordtype></control><display><type>conference_proceeding</type><title>RDP Technique: Take a Different Look at XP for Adoption</title><source>IEEE Electronic Library (IEL) Conference Proceedings</source><creator>Mirakhorli, M. ; Rad, A.K. ; Aliee, F.S. ; Mirakhorli, A. ; Pazoki, M.</creator><creatorcontrib>Mirakhorli, M. ; Rad, A.K. ; Aliee, F.S. ; Mirakhorli, A. ; Pazoki, M.</creatorcontrib><description>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.</description><identifier>ISSN: 1530-0803</identifier><identifier>ISBN: 9780769531007</identifier><identifier>ISBN: 0769531008</identifier><identifier>EISSN: 2377-5408</identifier><identifier>DOI: 10.1109/ASWEC.2008.4483259</identifier><language>eng</language><publisher>IEEE</publisher><subject>Australia ; Concrete ; Costs ; Customizing ; Extreme Programming ; Feedback ; Large-scale systems ; Mathematics ; Process Tailoring ; Productivity ; Programming ; RDP ; Software engineering ; Software testing</subject><ispartof>19th Australian Conference on Software Engineering (aswec 2008), 2008, p.656-662</ispartof><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/4483259$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>309,310,778,782,787,788,2054,27912,54907</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/4483259$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Mirakhorli, M.</creatorcontrib><creatorcontrib>Rad, A.K.</creatorcontrib><creatorcontrib>Aliee, F.S.</creatorcontrib><creatorcontrib>Mirakhorli, A.</creatorcontrib><creatorcontrib>Pazoki, M.</creatorcontrib><title>RDP Technique: Take a Different Look at XP for Adoption</title><title>19th Australian Conference on Software Engineering (aswec 2008)</title><addtitle>ASWEC</addtitle><description>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.</description><subject>Australia</subject><subject>Concrete</subject><subject>Costs</subject><subject>Customizing</subject><subject>Extreme Programming</subject><subject>Feedback</subject><subject>Large-scale systems</subject><subject>Mathematics</subject><subject>Process Tailoring</subject><subject>Productivity</subject><subject>Programming</subject><subject>RDP</subject><subject>Software engineering</subject><subject>Software testing</subject><issn>1530-0803</issn><issn>2377-5408</issn><isbn>9780769531007</isbn><isbn>0769531008</isbn><fulltext>true</fulltext><rsrctype>conference_proceeding</rsrctype><creationdate>2008</creationdate><recordtype>conference_proceeding</recordtype><sourceid>6IE</sourceid><sourceid>RIE</sourceid><recordid>eNotj0tOwzAUAC0-EqX0ArDxBRKen-3YZhel5SNFooJIsKueU1uYQlKSsOD2INHV7EYzjF0KyIUAd10-v6yqHAFsrpSVqN0Rm6E0JtMK7DFbOGPBFE5LAWBO2ExoCRlYkGfsfBzfARAUFDNmnpZr3oT2rUtf3-GGN7QLnPgyxRiG0E287vsdp4m_rnnsB15u-_2U-u6CnUb6GMPiwDlrbldNdZ_Vj3cPVVlnycGURe2xVZaiN8Zr9ERRCu-8QvKR_prQIRbC01Y6YRVgK8iRDzIKZ6Ju5Zxd_WtTCGGzH9InDT-bw7L8BfA5RvI</recordid><startdate>200803</startdate><enddate>200803</enddate><creator>Mirakhorli, M.</creator><creator>Rad, A.K.</creator><creator>Aliee, F.S.</creator><creator>Mirakhorli, A.</creator><creator>Pazoki, M.</creator><general>IEEE</general><scope>6IE</scope><scope>6IL</scope><scope>CBEJK</scope><scope>RIE</scope><scope>RIL</scope></search><sort><creationdate>200803</creationdate><title>RDP Technique: Take a Different Look at XP for Adoption</title><author>Mirakhorli, M. ; Rad, A.K. ; Aliee, F.S. ; Mirakhorli, A. ; Pazoki, M.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-i90t-f5b2c48afb77b52baaf31b9b42abfa153292261bad3918402c1a9abe3f197f5c3</frbrgroupid><rsrctype>conference_proceedings</rsrctype><prefilter>conference_proceedings</prefilter><language>eng</language><creationdate>2008</creationdate><topic>Australia</topic><topic>Concrete</topic><topic>Costs</topic><topic>Customizing</topic><topic>Extreme Programming</topic><topic>Feedback</topic><topic>Large-scale systems</topic><topic>Mathematics</topic><topic>Process Tailoring</topic><topic>Productivity</topic><topic>Programming</topic><topic>RDP</topic><topic>Software engineering</topic><topic>Software testing</topic><toplevel>online_resources</toplevel><creatorcontrib>Mirakhorli, M.</creatorcontrib><creatorcontrib>Rad, A.K.</creatorcontrib><creatorcontrib>Aliee, F.S.</creatorcontrib><creatorcontrib>Mirakhorli, A.</creatorcontrib><creatorcontrib>Pazoki, M.</creatorcontrib><collection>IEEE Electronic Library (IEL) Conference Proceedings</collection><collection>IEEE Proceedings Order Plan All Online (POP All Online) 1998-present by volume</collection><collection>IEEE Xplore All Conference Proceedings</collection><collection>IEEE Electronic Library (IEL)</collection><collection>IEEE Proceedings Order Plans (POP All) 1998-Present</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Mirakhorli, M.</au><au>Rad, A.K.</au><au>Aliee, F.S.</au><au>Mirakhorli, A.</au><au>Pazoki, M.</au><format>book</format><genre>proceeding</genre><ristype>CONF</ristype><atitle>RDP Technique: Take a Different Look at XP for Adoption</atitle><btitle>19th Australian Conference on Software Engineering (aswec 2008)</btitle><stitle>ASWEC</stitle><date>2008-03</date><risdate>2008</risdate><spage>656</spage><epage>662</epage><pages>656-662</pages><issn>1530-0803</issn><eissn>2377-5408</eissn><isbn>9780769531007</isbn><isbn>0769531008</isbn><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.</abstract><pub>IEEE</pub><doi>10.1109/ASWEC.2008.4483259</doi><tpages>7</tpages></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | ISSN: 1530-0803 |
ispartof | 19th Australian Conference on Software Engineering (aswec 2008), 2008, p.656-662 |
issn | 1530-0803 2377-5408 |
language | eng |
recordid | cdi_ieee_primary_4483259 |
source | IEEE Electronic Library (IEL) Conference Proceedings |
subjects | Australia Concrete Costs Customizing Extreme Programming Feedback Large-scale systems Mathematics Process Tailoring Productivity Programming RDP Software engineering Software testing |
title | RDP Technique: Take a Different Look at XP for Adoption |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-15T19%3A51%3A14IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-ieee_6IE&rft_val_fmt=info:ofi/fmt:kev:mtx:book&rft.genre=proceeding&rft.atitle=RDP%20Technique:%20Take%20a%20Different%20Look%20at%20XP%20for%20Adoption&rft.btitle=19th%20Australian%20Conference%20on%20Software%20Engineering%20(aswec%202008)&rft.au=Mirakhorli,%20M.&rft.date=2008-03&rft.spage=656&rft.epage=662&rft.pages=656-662&rft.issn=1530-0803&rft.eissn=2377-5408&rft.isbn=9780769531007&rft.isbn_list=0769531008&rft_id=info:doi/10.1109/ASWEC.2008.4483259&rft_dat=%3Cieee_6IE%3E4483259%3C/ieee_6IE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rft_ieee_id=4483259&rfr_iscdi=true |