1999
DOI: 10.1145/383371.383376
|View full text |Cite
|
Sign up to set email alerts
|

Situated assessment of problems in software development

Abstract: This paper reports on action research undertaken to understand and to improve the problems with software processes of a medium-sized Danish company. It is argued that, in order to understand what the specific problems are, we may, on the one hand, rely on normative process models like CMM or Bootstrap. On the other hand, we may also see the specific and unique features of software processes in a company through what we call "problem diagnosis." Problem diagnosis deals with ellciting problems perceived by softw… Show more

Help me understand this report

Search citation statements

Order By: Relevance

Paper Sections

Select...
2
1

Citation Types

0
38
0
4

Year Published

2009
2009
2019
2019

Publication Types

Select...
6
1
1

Relationship

3
5

Authors

Journals

citations
Cited by 86 publications
(42 citation statements)
references
References 23 publications
0
38
0
4
Order By: Relevance
“…In a much narrower definition, maturity models are regarded as synonyms for assessment artifacts like, e.g., the Capability Maturity Model Integration (CMMI) proposed by the Software Engineering Institute at Carnegie Mellon University (Paulk et al 1993). Maturity models apply different stages of development or maturity as a measure to evaluate the capabilities of an organization in regards to a certain discipline, and thus provide a framework for prioritizing improvement actions that are meaningful to the organization Iversen et al 1999). The objective is hence to assess the as-is situation, to incrementally build skills and capabilities, and to outline the stages of maturation paths in order to diagnose and eliminate deficient capabilities (Rummler and Brache 1990).…”
Section: Stages Of Development and Maturitymentioning
confidence: 99%
“…In a much narrower definition, maturity models are regarded as synonyms for assessment artifacts like, e.g., the Capability Maturity Model Integration (CMMI) proposed by the Software Engineering Institute at Carnegie Mellon University (Paulk et al 1993). Maturity models apply different stages of development or maturity as a measure to evaluate the capabilities of an organization in regards to a certain discipline, and thus provide a framework for prioritizing improvement actions that are meaningful to the organization Iversen et al 1999). The objective is hence to assess the as-is situation, to incrementally build skills and capabilities, and to outline the stages of maturation paths in order to diagnose and eliminate deficient capabilities (Rummler and Brache 1990).…”
Section: Stages Of Development and Maturitymentioning
confidence: 99%
“… Not adequacy to the specific needs: other criticisms refer to the multitude of almost identical maturity models and to the not thoughtful adoption of the CMM main plan ( [17], [18], [19]). The carelessness of the specific needs can hinder the achievement of the objectives of the maturity model.…”
Section: Introductionmentioning
confidence: 99%
“…The success of SPI in these companies is attributed to four factors (Kautz 2000): a tailored approach; an experience network between companies; external assistance; and partial external funding. In another study a medium-sized company's problems with current software processes were assessed with a technique for problem diagnosis, which was not on the basis of a maturity model and many of the identified problems could later be alleviated (Iversen et al 1999;Nielsen et al 2002). In this study the success of the improvement effort was attributed to the particular way experience and knowledge were shared during the problem diagnosis.…”
Section: Introductionmentioning
confidence: 99%