Properties that influence business process management maturity and its effect on organizational performance

Abstract BPM maturity is a measure to evaluate how professionally an organization manages its business processes. Previous research provides evidence that higher BPM maturity leads to better performance of processes and of the organization as a whole. It also claims that different organizations should strive for different levels of maturity, depending on their properties. This paper presents an empirical investigation of these claims, based on a sample of 120 organizations and looking at a selection of organizational properties. Our results reveal that higher BPM maturity contributes to better performance, but only up to a point. Interestingly, it contradicts the popular belief that higher innovativeness is associated with lower BPM maturity, rather showing that higher innovativeness is associated with higher BPM maturity. In addition, the paper shows that companies in different regions have a different level of BPM maturity. These findings can be used as a benchmark and a motivation for organizations to increase their BPM maturity

Towards a model for managing success factors in software process improvement

Existing software engineering and management literature argue for\u3cbr/\u3emany different ways of looking at success factors that influence Software\u3cbr/\u3eProcess Improvement (SPI). This study investigates success factors identified in a number of research projects and proposes a model for managing these factors in a structured way during different phases of an SPI program. It also aspires to describe a model that reflects the cyclical influences of factors in a continuously progressing SPI progra

Informatiesystemen, bestuurlijk en administratief

No abstract

A framework for characterizing usability requirements elicitation and analysis methodologies (UREAM)

Dedicated methodologies for the elicitation and analysis of usability requirements have been proposed in literature, usually developed by usability experts. The usability of these approaches by non-expert software engineers is not obvious. In this paper, the objective is to support developers and managers in a software development project in deciding on which methodology to select, taking into account local strengths and weaknesses. We define a framework based on a set of criteria that allow for the comparison of methodologies