Search results

Nowadays, informed decision-making is catching up. Technological advancements and computing ability further fuel and facilitate this tilt toward informed decision-making. In such a scenario, data is cynosure. Therefore, the ability to gather data by a nation (incredibly accurate public data) becomes equally important and relevant, as measured by statistical performance indicators (SPI). This study aims to explore the association of financial inclusion (FI); environmental, social and governance (ESG); poverty; and SPI.

The panel data of 140 nations for nine years are gathered to explore the association of FI, ESG and poverty with the SPI. Panel data estimation is conducted to arrive at the results.

The findings of this study highlight mixed outcomes for FI. ESG is positively associated with SPI, but poverty is not associated with SPI. These findings imply that an increase in FI may reduce the statistical capacity of the nations. An increase in ESG increases the capacity. However, change in poverty does not influence the SPI. The recommendation based on this study’s outcome suggests auditing the FI and poverty vis-à-vis SPI to ensure SPI’s veracity and robustness in the long run.

The way in which the individual social, economic and environmental indicators influence the SPI needs to be tested to establish the veracity and robustness of the SPI, which is barely researched as observed in the literature.

Software process improvement (SPI) is a knowledge activity that is critical to the excellence of information system development. This study observes two knowledge gaps in the quest for SPI success and proposes a research model that integrates existing knowledge antecedents to address these gaps. Based on organizational learning theory and the dynamic capability view, the proposed model consolidates a firm's absorptive capacity (AC), learning ability in terms of exploration and exploitation and knowledge sharing (KS), and it examines the contextual relationships among these knowledge antecedents on the path to SPI success.

A quantitative research design is implemented to examine the model with a sample of 138 SPI-certified organizations in Taiwan and Mainland China. The partial least squares (PLS) technique is used for the data analysis.

The results reveal the following findings. First, AC triggers the effect of exploration/exploitation on SPI success. Second, KS fosters exploitation but has an insignificant influence on exploration. Third, KS can promote AC, and it serves as the sourcing mechanism for all of the knowledge antecedents. Overall, an integrative set of knowledge learning routes is presented in guiding software firms on the way to SPI success.

In addition to identification of the two knowledge gaps, this study advances the authors’ understanding by comprehending the causal associations of the four knowledge antecedents on the way to SPI success.

This paper explores the practical usage of insights on knowledge management (KM) to support innovation in a software organization. The organization has for some time engaged in software process improvement (SPI) initiatives to improve its operation. The paper applies two complementary approaches to KM, the codified and the personalized, to evaluate current KM practices and to improve its SPI practices. Based on the insights from the case we review key principles within SPI and evaluate the applied KM approaches. We conclude that it is advisable for SPI efforts to explicitly address KM issues. Each software organization has to find its own balance between personalized and codified approaches, this balance needs to be dynamically adjusted as the organization matures, and the adopted KM approach should differentiate between different types of SPI services.

While the literature on software process improvement (SPI) offers a number of studies of small software firms, little is known about how such initiatives evolve over time. On this backdrop, this paper aims to investigate how adoption of SPI technology was shaped over a ten year period (1996‐2005) in a small Danish software firm.

The investigation is based on a longitudinal, interpretative case study of improvement efforts over a ten‐year period. To help structure the investigation, we focus on encounters that impacted engineering, management, and improvement practices within the firm. The study contributes to the SPI‐literature and the literature on organizational adoption of technology.

The paper finds the improvement effort fluctuating and shaped between management's attempt to control SPI technology adoption and events that caused the process to drift in unpredictable directions.

The experiences suggest that managers of small software firms remain flexible and constantly negotiate technology adoption practices between control and drift, creating momentum and direction according to firm goals through attempts to control, while at the same time exploring backtalk, options, and innovations from drifting forces inside and outside the firm.

Based on the research, the paper recommends substituting the “from control to drift” perspective on organizational adoption of complex technologies like SPI with a “negotiating control and drift” perspective.

The purpose of this paper is to identify drought conditions in Jordan in the period 1960‐2006 for two major basins – the Yarmouk and the Zarqa. This study aims to look at the long‐term drought conditions (hydrological droughts) and to investigate the possibility of changes in the monthly precipitation pattern for the period of 1997‐2006, as this period has suffered from the average slightly dry conditions for the two basins.

The Standard Precipitation Index (SPI) is used to assess drought conditions in the Yarmouk and Zarqa basins. The SPI is applied on an annual basis to assess the hydrological long‐term droughts. Average monthly precipitation is used as the input to the SPI procedure.

The SPI is applied on an annual basis (12 months) SPI‐12. Results of the SPI‐12 assessment show that the years 1978, 1995, and 1999 represented extremely dry conditions in both basins. The years 1989 and 1993 represented severely dry conditions in the Zarqa basin and extremely dry conditions in the Yarmouk basin. The statistical procedure for precipitation anomalies identifies precipitation anomalies for the years 2000, 2003, and 2006. However, due to the limited number of anomaly years this study does not conclude that there is a change in the pattern of monthly precipitation of the tested period 1997‐ 2006.

Using the SPI method this work can be extended to compare drought conditions in the remaining major basins in the country.

The paper provides important information about drought conditions in Jordan and ways to assess precipitation anomalies and pattern changes. This can be beneficial to the planning of water resources in Jordan and the associated developments (agricultural, industrial, tourism, and residential).

The purpose of this paper is to identify the relationships among absorptive capacity (AC), organisational culture (OC), and software process improvement (SPI) implementation success based on capability maturity model integration (CMMI). Specifically, the aim of this study is to understand the roles of potential and realised AC in SPI success.

This study proposes a research model and examines the relations among firm AC, SPI success, and OC. The authors surveyed 56 Taiwanese firms that adopted the CMMI-based SPI programme and received official certification.

The findings indicate that potential and realised AC have significantly positive effects on SPI success. In particular, realized (AC) partially mediates the effects of potential AC on SPI success. Furthermore, the effects of potential and realised AC on SPI success are significantly moderated by the adhocracy and hierarchy OCs, respectively.

Given that the scope of this empirical study was limited to Taiwan, the findings might lack generalisability; however, this provides an opportunity for future research.

This is the first empirical study investigating the influence of AC on CMMI-based SPI success. The proposed research model also examines the moderating relationships of two types of OCs, namely adhocracy and hierarchy, on AC (potential and realized) and SPI success.

The purpose of the article is to investigate the impact of organizational culture on software process improvement (SPI). Is cultural congruence between an organization and an adopted process model required? How can the level of congruence between an organizational culture and the values and assumptions underlying an adopted process model be assessed?

The competing values framework and its associated assessment instrument are used in a case study to establish an organizational culture profile of a software development business unit within the case company. The instrument is supplemented with a technique to produce culture profiles of texts such as process models like the Capability Maturity Model Integration (CMMI) and the case company's quality management system. The different profiles are subsequently analyzed and compared.

The culture profile of the CMMI confirms previous research and depicts a result‐oriented, formalized, and structured organization. A comparison with the company's quality management system shows congruent culture profiles suggesting that the case company has succeeded in capturing underlying assumptions of the CMMI when updating the quality management system. The analysis also reveals the organizational culture profile of the business unit to be incongruent with the quality management system's profile. This disconfirms previous research claiming that congruence is a prerequisite. Further analysis reveals that actions were taken by managers in the case company to address the cultural challenges and successfully implement new processes. It is, therefore, concluded that cultural incongruence is not an insurmountable barrier to SPI. By comparing cultural profiles, some SPI implementation challenges become evident and that in turn allows for effective SPI management action.

The research is based on a single case study and that is sufficient to disconfirm existing research. Additional research is, however, needed to validate both the proposed text analysis technique as well as the proposed process for assessing and managing cultural challenges confronting SPI projects.

SPI managers are provided with a more complex view of organizational culture in which congruence is not a necessity. SPI managers can choose to compare culture profiles and decide how to address incongruences. To that end the text analysis technique is offered as a web service that allows for analysis of all text‐based process models and standards, and of internal process documentation.

The proposed culture management process, including the text analysis technique, is a cost‐efficient approach to analyzing and providing the basis for managing cultural challenges during SPI in a specific company. The process provides understanding and guidance in dealing with the specific challenges faced by software companies during SPI.

The paper seeks to explore the impact of events in Software Process Improvement (SPI) environments based on a longitudinal study of a requirements management initiative at Ericsson.

The paper presents the initiative from three perspectives – the improvement initiative, the targeted software practices, and the environment.

SPI initiatives easily get interrupted, are side‐tracked, and progress slowly due to changing environments. While most practitioners are painfully aware of this, the SPI literature has so far only touched on the issue. Agility principles would have helped Ericsson respond more effectively to events that impacted the initiative. Development of agile SPI practices requires coordination and alignment with other initiatives to develop agile software organizations.

SPI has been adopted by many organizations to help them to deliver quality software. However, its success is a matter of debate and this paper deals with the issues involved.

Reports from a systems development research tradition in which emphasis is put on relating research activities to practice and on establishing fruitful collaboration between groups of researchers and practitioners. Describes and evaluates a specific research project in which a large group of researchers and practitioners worked together to understand, support, and improve systems development practices in four organisations over a period of three years. Uses the case to reflect on the research goals, approaches, and results involved in this tradition for researching systems development practice. Proposes collaborative practice research as a way to organise and conduct research into systems development practice based on close collaboration between researchers and practitioners. Exemplifies the use of pluralist research methodology by combining action research with experiments and conventional practice studies. Argues that collaborative practice research offers one practical way to strike a useful balance between relevance and rigour. Concludes with a discussion of the implications for the relation between research and practice within the systems development discipline and with lessons on how to design research efforts as collaborations between researchers and practitioners.

Quality improvement is critical to the success of software development organizations. Automated tools can greatly assist in the implementation of quality improvement. The purpose of this paper is to investigate the state of tool support of software process improvement.

The authors first review three quality improvement models that can be used for improving the quality of software products, and then identify the required activities of the quality improvement effort based on those models. These activities identified then serve as a reference list to determine the support provided by commercial tools. The paper then conducts two surveys of software quality improvement tools and presents the results.

The results from two surveys indicate that: there is no tool that supports problem identification; most tools can provide several software process improvement functions to help software organizations to improve their process capability and the quality of their products; and there is no set of tools that can provide a complete coverage of all improvement activities.

Although the authors have conducted a detailed search on the internet to identify SPI tools, such a survey will miss those tools which have no presence on the internet. However, the authors are confident that their results can reflect what is available in the marketplace.

Process practitioners will learn about the state of support available in the marketplace and what they may need to develop on their own to provide complete support for their improvement efforts.

The paper proposes a classification of software process improvement functions and present a first survey of software quality improvement tools. The results will be beneficial to process practitioners.