A hierarchy of SPI activities for software SMEs: results from ISO/IEC 12207-based SPI assessments

In an assessment of software process improvement (SPI) in 15 software small- and –medium-sized enterprises (software SMEs), we applied the broad spectrum of software specific and system context processes in ISO/IEC 12207 to the task of examining SPI in practice. Using the data collected in the study, we developed a four-tiered pyramidal hierarchy of SPI for software SMEs, with processes in the higher tiers undergoing SPI in more companies than processes on lower level tiers. The development of the hierarchy of SPI activities for software SMEs can facilitate future evolutions of process maturity reference frameworks, such as ISO/IEC 15504, in better supporting software development in software SMEs. Furthermore, the findings extend our body of knowledge concerning the practice of SPI in software SMEs, a large and vital sector of the software development community that has largely avoided the implementation of established process maturity and software quality management standards

An evaluation of the RAPID assessment-based process improvement method for small firms

[Abstract]: With increasing interest by the software development community in software process improvement (SPI), it is vital that SPI programs are evaluated and the reports of lessons learned disseminated. This paper presents an evaluation of a program in which low-rigour, one-day SPI assessments were offered at no cost to 22 small Australian software development firms. The assessment model was based on ISO/IEC 15504 (SPICE). About twelve months after the assessment, the firms were contacted to arrange a follow-up meeting to determine the extent to which they had implemented the recommendations from the assessment. Comparison of the process capability levels at the time of assessment and the follow-up meetings revealed that the process improvement program was effective in improving the process capability of many of these small software development firms. Analysis of the assessment and follow-up reports explored important issues relating to SPI: elapsed time from assessment to follow-up meeting, the need for mentoring, the readiness of firms for SPI, the role of the owner/manager, the advice provided by the assessors, and the need to record costs and benefits. Based on a meta-analysis of the program and its outcomes, advice and recommendations are provided to small firms and assessors. As well as providing validation of the assessment model and method, the outcomes from this research have the potential to better equip practitioners and consultants to undertake software process improvement, hence increasing the success of small software development firms in domestic and global markets

Process capability assessments in small development firms

[Abstract}: Assessment-based Software Process Improvement (SPI) programs such as the Capability Maturity Model (CMM), Bootstrap, and SPICE (ISO/IEC 15504) are based on formal frameworks and promote the use of systematic processes and management practices for software development. These approaches identify best practices for the management of software development and when applied, enable organizations to understand, control and improve development processes. The purpose of a SPI assessment is to compare the current processes used in an organization with a list of recommended or ‘best’ practices. This research investigates the adoption of SPI initiatives by four small software development firms. These four firms participated in a process improvement program which was sponsored by Software Engineering Australia (SEA) (Queensland). The assessment method was based on SPICE (ISO/IEC 15504) and included an initial assessment, recommendations, and a follow-up meeting. For each firm, before and after snapshots are provided of the capability as assessed on eight processes. The discussion which follows summarizes the improvements realized and considers the critical success factors relating to SPI adoption for small firms

Naming the Pain in Requirements Engineering: A Design for a Global Family of Surveys and First Results from Germany

For many years, we have observed industry struggling in defining a high quality requirements engineering (RE) and researchers trying to understand industrial expectations and problems. Although we are investigating the discipline with a plethora of empirical studies, they still do not allow for empirical generalisations. To lay an empirical and externally valid foundation about the state of the practice in RE, we aim at a series of open and reproducible surveys that allow us to steer future research in a problem-driven manner. We designed a globally distributed family of surveys in joint collaborations with different researchers and completed the first run in Germany. The instrument is based on a theory in the form of a set of hypotheses inferred from our experiences and available studies. We test each hypothesis in our theory and identify further candidates to extend the theory by correlation and Grounded Theory analysis. In this article, we report on the design of the family of surveys, its underlying theory, and the full results obtained from Germany with participants from 58 companies. The results reveal, for example, a tendency to improve RE via internally defined qualitative methods rather than relying on normative approaches like CMMI. We also discovered various RE problems that are statistically significant in practice. For instance, we could corroborate communication flaws or moving targets as problems in practice. Our results are not yet fully representative but already give first insights into current practices and problems in RE, and they allow us to draw lessons learnt for future replications. Our results obtained from this first run in Germany make us confident that the survey design and instrument are well-suited to be replicated and, thereby, to create a generalisable empirical basis of RE in practice

Preventing Incomplete/Hidden Requirements: Reflections on Survey Data from Austria and Brazil

Many software projects fail due to problems in requirements engineering (RE). The goal of this paper is analyzing a specific and relevant RE problem in detail: incomplete/hidden requirements. We replicated a global family of RE surveys with representatives of software organizations in Austria and Brazil. We used the data to (a) characterize the criticality of the selected RE problem, and to (b) analyze the reported main causes and mitigation actions. Based on the analysis, we discuss how to prevent the problem. The survey includes 14 different organizations in Austria and 74 in Brazil, including small, medium and large sized companies, conducting both, plan-driven and agile development processes. Respondents from both countries cited the incomplete/hidden requirements problem as one of the most critical RE problems. We identified and graphically represented the main causes and documented solution options to address these causes. Further, we compiled a list of reported mitigation actions. From a practical point of view, this paper provides further insights into common causes of incomplete/hidden requirements and on how to prevent this problem.Comment: in Proceedings of the Software Quality Days, 201

Commercialisation of eHealth Innovations in the Market of UK Healthcare Sector: A Framework for Sustainable Business Model.

This is the peer reviewed version of the following article: Festus Oluseyi Oderanti, and Feng Li, ‘Commercialization of eHealth innovations in the market of the UK healthcare sector: A framework for a sustainable business model’, Psychology & Marketing, Vol. 35 (2): 120-137, February 2018, which has been published in final form at https://doi.org/10.1002/mar.21074. Under embargo until 10 January 2020. This article may be used for non-commercial purposes in accordance with Wiley Terms and Conditions for Self-Archiving.Demographic trends with extended life expectancy are placing increasing pressures on the UK state-funded healthcare budgets. eHealth innovations are expected to facilitate new avenues for cost-effective and safe methods of care, for enabling elderly people to live independently at their own homes and for assisting governments to cope with the demographic challenges. However, despite heavy investment in these innovations, large-scale deployment of eHealth continues to face significant obstacles, and lack of sustainable business models (BMs) is widely regarded as part of the greatest barriers. Through various empirical methods that include facilitated workshops, case studies of relevant organizations, and user groups, this paper investigates the reasons the private market of eHealth innovations has proved difficult to establish, and therefore it develops a framework for sustainable BMs that could elimiesnate barriers of eHealth innovation commercialization. Results of the study suggest that to achieve sustainable commercialization, BM frameworks and innovation diffusion characteristics should be considered complements but not substitutes.Peer reviewe

Risk across design domains

Design processes involve risk: to life and limb if the product is unsafe, to the financial health of the company if the product is late, unsuccessful or simply the wrong product, as well as to the emotions and careers of the designers. Many of the risks are shared universally by all designers, but each different industry and each different project faces its own spectrum of serious and minor risks. Different industries have put their methodological effort into finding ways to mitigate the risks they recognise as important. As part of the Across Design project exploring similarities and differences between design processes in different industries, this paper examines how risks are perceived and handled in different types of design process, and proposes that designers and managers can usefully look to other industries for ways to handle risks that are more central for those other industries

Investing In Results: How Business Roundtable Is Supporting Proven Education Reforms

The CEO effort to expand on what's working started in 2013 when Business Roundtable launched its Education Philanthropy Initiative. Two years later, this report examines how the five programs selected for their outstanding work in K-12 education reform have reached more students and improved educational outcomes as a result of the more than $15 million contributed to the Initiative by Roundtable CEOs

Using process mapping software to redesign a management system

Management Systems are becoming de rigueur for Organisations, but many with existing Management Systems are finding that they are creaking at the seams. Changes to Standards, Regulations, Business Practices, Organisation structures and Products mean that Organisations have be flexible and their Management Systems also. With Management Systems based on those written in the 1990s, companies are realising that they need to make a step change in order to maintain their competitive advantage. This Management Summary will discuss why Process Mapping should be considered as a method for this improvement, what to consider when choosing a Process Mapping tool and how the change should be planned. It uses experience from several companies with which the author has been involved