2009
DOI: 10.1109/tem.2009.2013829
|View full text |Cite
|
Sign up to set email alerts
|

Managing Cultural Variation in Software Process Improvement: A Comparison of Methods for Subculture Assessment

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
1
1
1
1

Citation Types

1
16
0
3

Year Published

2013
2013
2020
2020

Publication Types

Select...
4
3
2

Relationship

1
8

Authors

Journals

citations
Cited by 27 publications
(20 citation statements)
references
References 56 publications
1
16
0
3
Order By: Relevance
“…Quality management standards and process models are cultural artifacts embodying certain organizational values and management ideals. They espouse ideal practices and desirable value orientations as the end goal of process improvement (Müller, Kraemmergaard, & Mathiassen, 2009;Müller & Nielsen, 2013;Ngwenyama & Nielsen, 2003). Previous research has shown that cultural incongruence, i.e.…”
Section: Introductionmentioning
confidence: 99%
“…Quality management standards and process models are cultural artifacts embodying certain organizational values and management ideals. They espouse ideal practices and desirable value orientations as the end goal of process improvement (Müller, Kraemmergaard, & Mathiassen, 2009;Müller & Nielsen, 2013;Ngwenyama & Nielsen, 2003). Previous research has shown that cultural incongruence, i.e.…”
Section: Introductionmentioning
confidence: 99%
“…Some papers describe cases of agile development, either for a system as a whole [11] or by individual teams within the organisation [20]. When described, most case architectures focus on enabling product quality attributes, usually domainspecific such as safety, cost and variability in the automotive domain [13], security in defence [21], and dependability in space [22]. Some organisations utilise a product line architecture to enable tailoring of the system to a particular customer [23], [24].…”
Section: Study Results and Limitationsmentioning
confidence: 99%
“…This can be considered the standard practice at which MPES software is developed, with six cases clearly falling into this category (described in papers [6], [13], [15]- [17], [19], [21], [27], [28]). An additional twelve cases (in papers [22], [23], [25], [29]- [31]) fall either into this category or category D.…”
Section: A Approach E: Rorqual Organisationsmentioning
confidence: 99%
“…Studies have also shown that culture have an impact on the implementation of SPI models [14]. Thus, models developed using a particular culture as context, may not be applicable in other cultures or region with different culture.…”
Section: Discussionmentioning
confidence: 99%