Exploring the Relations Between Net Benefits of IT Projects and CIOs’ Perception of Quality of Software Development Disciplines

Abstract

Software development enterprises are under consistent pressure to improve their management techniques and development processes. These are comprised of several disciplines like requirements acquisition, design, coding, testing, etc. that must be continuously improved and individually tailored to suit specific software development project. This paper presents an evaluation approach that enables the enterprises to increase development process net benefits by improving disciplines' quality and increasing developers' satisfaction. Our approach builds on Kano's model of quality. Based on an empirical study of top 1000 enterprises from Slovenia we find that application of software development methodologies in individual development disciplines significantly relates to net benefits of IT projects. The results show that different types of Kano quality are present in individual disciplines. Enterprises should be cautious when altering must-be quality disciplines like testing or deployment as they can significantly disrupt the established routines, cause great dissatisfaction between developers and significantly reduce benefits. On the other hand, changing the attractive quality disciplines like requirements acquisition can notably increase developers' satisfaction and benefits but is less likely to disrupt the established routines.

Identifying Key Characteristics of Business Rules That Affect Software Project Success

“…The response rate was 11.2% (n = 112). Such response rates are typical for mail surveys conducted in enterprises (not only in Slovenia) [40]. Existing research demonstrated that even with response rates of around 10%, we can treat such a sample as a random sample [41,42].…”

Improving the efficiency of remote conference tool use for distance learning in higher education: A kano based approach

“…1 shows different Kano categories where y -axis measures the level of satisfaction and x -axis measures the level of requirement implementation. The original Kano model differentiates between four main types of quality categories: must-be (M), one-dimensional (O), attractive (A), and indifferent (I) ( Nayebi and Ruhe, 2019 , Vavpotič, Robnik-Šikonja, & Hovelja, 2020 ; Xu et al, 2019 ; S.; Zhao et al, 2020 ). The requirements that users expect software to have are classified as must-be .…”

Software Process Evaluation from User Perceptions and Log Data

“…Adopting a specific methodology can determine to what extent performance goals such as cost, quality, and timeliness are achieved. 1 Existing studies show [2][3][4] that the adoption of SDMs is critical for success of development teams, but not easy to apply in practice. More specifically, it is often the case that a specific methodology is either applied partially or incorrectly, is not suitable for the enterprise due to incompatible technical characteristics, or has unsatisfactory impact on software quality, cost, and development time.…”

“…Software development methodologies (SDMs) highly influence the management of software projects. Adopting a specific methodology can determine to what extent performance goals such as cost, quality, and timeliness are achieved 1 . Existing studies show 2–4 that the adoption of SDMs is critical for success of development teams, but not easy to apply in practice.…”