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

Persuading developers to buy into software process improvement: an exploratory analysis

In order to investigate practitioners' opinions of software process and software process improvement, we have collected information from 13 companies, in a variety of ways i.e. the use of Repertory Grid Technique, survey and focus group discussions. Both the Repertory Grid Technique and the focus group discussions (43 discussions occurred, in total) produced a large volume of qualitative data. At the same time, other researchers have reported--investigations of practitioners, and we are interested in how their reports may relate to our own. Thus, other research publications can also be treated as a form of qualitative data. In this paper, we review advice on a method, content analysis, that is used to analyse qualitative data. Content analysis is a method for identifying and classifying words and phrases used in--ordinary language. We use content analysis to describe and analyse discussions on software--process and software process improvement. We report preliminary findings from an analysis--of both the focus group evidence and some publications. Our main finding is that there is an--apparent contradiction between developers saying that they want evidence for software process improvement, and what developers will accept as evidence. This presents a serious problem for research: even if researchers could demonstrate a strong, reliable relationship between software process improvement and improved organisational performance, there would still be the problem of convincing practitioners that the evidence applies to their particular situation

Persuading developers to buy into software process improvement: a local opinion and empirical evidence

This material is presented to ensure timely dissemination of scholarly and technical work. Copyright and all rights therein are retained by authors or by other copyright holders. All persons copying this information are expected to adhere to the terms and constraints invoked by each author's copyright. In most cases, these works may not be reposted without the explicit permission of the copyright holder.---- Copyright IEEE. Personal use of this material is permitted. However, permission to reprint/republish this material for advertising or promotional purposes or for creating new collective works for resale or redistribution to servers or lists, or to reuse any copyrighted component of this work in other works must be obtained from the IEEE.In order to investigate practitioners’ opinions of software process and software process improvement, we have collected a large volume of qualitative evidence from 13 companies. At the same time, other researchers have reported investigations of practitioners, and we are interested in how their reports may relate to our evidence. Thus, other research publications can also be treated as a form of qualitative data. In this paper, we review advice on a method, content analysis, that is used to analyse qualitative data. We use content analysis to describe and analyse discussions on software process and software process improvement. We report preliminary findings from an analysis of both the focus group evidence and four publications

Implementing software process improvement initiatives: An empirical study

In this paper we present findings from our empirical study of software process improvement (SPI) implementation. We aim to provide SPI practitioners with insight into designing appropriate SPI implementation initiatives in order to achieve better results. Thirty-four interviews were conducted with Australian practitioners. Three SPI implementation issues were investigated: reasons for embarking on SPI initiatives, SPI benefits to the management, and factors that play a positive role in SPI implementation. We have found that most common reasons for embarking on SPI initiatives are to: improve the quality of software developed, reduce software development cost, and increase productivity. Our results show that 71% of the practitioners said that SPI initiatives provided clear benefits to the management. We have also found that most frequently cited SPI implementation factors are: SPI awareness, defined SPI implementation methodology, experienced staff, staff time and resources, senior management commitment and training. Our aim of conducting this study is to provide a SPI implementation framework for the design of effective SPI implementation initiatives. © Springer-Verlag Berlin Heidelberg 2006

Quality management and e-commerce: the role of codes of conduct governing the use of technology

Discussion of the relationship between TQM and information and communications technology (ICT) normally focuses either on technological issues, or on the role of ICT in enabling the achievement of quality goals by means of business process re-engineering. Less attention has been paid to the effects that the increased utilisation of ICT is having on management style, and on the quality of relationships. This paper reports on research undertaken into the development, implementation and enforcement of codes of conduct designed to govern employees' use of ICT. A study of 125 London-based employers found that, although such codes had been introduced in nearly three-quarters of the organisations, the majority failed to address a key issue of concern to customers' privacy of personal data. Furthermore, the codes themselves were seen to have little influence on the behaviour of employees. The reasons for this are discussed within a TQM framework, and suggestions made as to how compliance might be improved in future

Goal-driven agent-oriented software processes

The quality of software processes is acknowledged as a critical factor for delivering quality software systems. Any initiative for improving the quality of software processes requires their explicit representation and management. A current representational metaphor for systems is agent orientation, which has become one of the recently recognized engineering paradigms. In this article, we argue for the convenience of representing the software process using an agent-oriented language to model it and a goal-driven procedure to design it. Particularly we propose using the i* framework which is both an agent- and a goal-oriented modeling language. We review the possibilities of i* as a software process modeling language, and we also show how success factors can be made explicit in i* representations of the software processes. Finally, we illustrate the approach with an example based on the development of a set of ergonomic and safety software tools.Peer ReviewedPostprint (published version

The adoption of software process improvement (SPI) program in the construction industry

Integrating the design process and automating the construction process are called for in the Industrialised Building System (IBS) Roadmap 2003-2010 and the Construction Industry Master Plan (CIMP) 2006-2015. Hence, the industry needs to improve the construction delivery process by having as many processes utilizing advanced IT/ICT technologies. With a goal of producing zero product failure and meeting the users’ requirement satisfaction, this is an initial study into automating the construction tasks by studying a systematic process management commonly used for software implementation. We present a feasibility study on the use of a Software Process Improvement (SPI) Program in an IT organization—assuming that the construction organization will become an implementer of computer-integrated procedures in the future. Based on a case study conducted at a local IT software company, it documents the implementation of a SPI program to improve the internal software process development. The study uses the Capability Maturity Model Integration (CMMI) from Software Engineering Institute as SPI framework and IDEAL model-SPI life cycle model for executing and managing SPI program. Results show that the SPI Program model is successful in terms of the IT organization increasing its work productivity, high end-user product satisfaction and reduction of software defects. The paper concludes with discussions on how we can bridge computer science approach into the construction industry, thereby contributing to the development of future theoretical and application methodologies towards applying IT/ICT initiatives in the local construction industry

Knowledge management in software process improvement: A case study of very small entities

This chapter discusses knowledge management (KM) aspects of how software process and software process improvement (SPI) is practiced within very small entities (VSEs) in the context of Irish software development industry. In particular, this study is concerned with the process of software development knowledge management in supporting the SPI. In order to understand the support process, the authors of this chapter have studied how KM processes are practiced within VSEs which includes communica- tion, learning, sharing, and documentation process. This study also focuses in detail on the issues of the knowledge atrophy problem in VSEs. The findings explain how KM has been practiced and influenced the software development process and process improvement in VSEs. This result indicates that KM processes in VSEs are being undertaken in a very informal manner and also in indirect way. This is due to a small team size, autonomous working and macro-management style and caused VSEs to be more informal in their KM processes specifically and SPI generally. In addition, the results have indicated that the informal environment and culture helped VSEs to easily create and share knowledge between staff members and also assisted VSEs to mitigate the knowledge atrophy problem in their organization