| dc.contributor.author | Coleman, Gerry | |
| dc.date.accessioned | 2011-07-21T12:01:28Z | |
| dc.date.available | 2011-07-21T12:01:28Z | |
| dc.date.issued | 2004 | |
| dc.identifier.uri | http://hdl.handle.net/10344/1161 | |
| dc.description | peer-reviewed | en_US |
| dc.description.abstract | Within the body of literature, much emphasis has been placed on the use of process models to support software development [1, 2, 3]. Despite this, there is significant variation in the software processes used by software companies. Analysis shows that many companies are deploying proprietary, tailored “good enough” or “minimum” process in their software development activity. But what is “minimum” process? What factors influence the composition of minimum process in software companies and why are these companies choosing to reject standard process models in favour of a tailored minimum? | en_US |
| dc.language.iso | eng | en_US |
| dc.publisher | IEEE Computer Society | en_US |
| dc.relation.ispartofseries | Proceedings of the 28th Annual International Computer Software and Applications Conference; | |
| dc.rights | ©2004 IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE. | en_US |
| dc.subject | software process | en_US |
| dc.subject | programming | en_US |
| dc.title | EXtreme Programming (XP) as a ‘minimum’ software process : a grounded theory | en_US |
| dc.type | Conference item | en_US |
| dc.type.supercollection | all_ul_research | en_US |
| dc.type.supercollection | ul_published_reviewed | en_US |
| dc.type.restriction | none | en |
| dc.contributor.sponsor | SFI |