Show simple item record

dc.contributor.authorBeecham, S.
dc.contributor.authorHall, T.
dc.contributor.authorRainer, A.
dc.date.accessioned2007-08-11T20:25:42Z
dc.date.available2007-08-11T20:25:42Z
dc.date.issued2003
dc.identifier.citationBeecham , S , Hall , T & Rainer , A 2003 , ' Software process improvement problems in twelve software companies: An empirical analysis ' , Empirical Software Engineering , vol. 8 , no. 1 , pp. 7-42 . https://doi.org/10.1023/A:1021764731148
dc.identifier.issn1382-3256
dc.identifier.otherPURE: 91625
dc.identifier.otherPURE UUID: d79ea520-1368-40aa-9155-9da1d8e91f8e
dc.identifier.otherdspace: 2299/386
dc.identifier.otherScopus: 0037366147
dc.identifier.urihttp://hdl.handle.net/2299/386
dc.description.abstractIn this paper we discuss our study of the problems 12 software companies experienced in software development. In total we present qualitative data collected from 45 focus groups that involved over 200 software staff. We look at how different practitioner groups respond to software process improvement problems. We show our classification and analysis of this data using a graphical data representation method new to software development research. The aim of the work we present is to develop a more holistic understanding of the problems practitioners are experiencing in their attempts to improve their software processes. Our main finding is that there is an association between companies’ maturity and patterns of reported problems. Organisational problems are more associated with high maturity companies than with low maturity companies. Low maturity companies are closely linked to problems relating directly to projects such as quality, timescales, tools and technology. Senior managers cite problems with goals, culture and politics. Project managers are concerned with timescales, change management, budgets and estimates. Developers are experiencing problems with requirements, testing, documentation, communication, tools and technology. These associations are graphically displayed through the use of correspondence analysis mapsen
dc.language.isoeng
dc.relation.ispartofEmpirical Software Engineering
dc.subjectComputer Science
dc.titleSoftware process improvement problems in twelve software companies: An empirical analysisen
dc.contributor.institutionSchool of Computer Science
dc.contributor.institutionScience & Technology Research Institute
dc.contributor.institutionSchool of Physics, Engineering & Computer Science
dc.description.statusPeer reviewed
rioxxterms.versionofrecordhttps://doi.org/10.1023/A:1021764731148
rioxxterms.typeJournal Article/Review
herts.preservation.rarelyaccessedtrue


Files in this item

Thumbnail

This item appears in the following Collection(s)

Show simple item record