Predicting fault inflow in iterative software development processes: an industrial evaluation

This paper addresses the need for accurate predictions on the fault inflow, i.e. the number of faults found in the consecutive project weeks, in highly iterative processes. In such processes, in contrast to waterfall-like processes, fault repair and development of new features run almost in parallel. Given accurate predictions on fault inflow, managers could dynamically re-allocate resources between these different tasks in a more adequate way. Furthermore, managers could react with process improvements when the expected fault inflow is higher than desired. This study suggests software reliability growth models (SRGMs) for predicting fault inflow. Originally developed for traditional processes, the performance of these models in highly iterative processes is investigated. Additionally, a simple linear model is developed and compared to the SRGMs. The paper provides results from applying these models on fault data from three different industrial projects. One of the key findings of this study is that some SRGMs are applicable for predicting fault inflow in highly iterative processes. Moreover, the results show that the simple linear model represents a valid alternative to the SRGMs, as it provides reasonably accurate predictions and performs better in many cases.

The agile governance of business IT projects

Organisations typically define and execute their selected strategy by developing and managing a portfolio of projects. The governance of this portfolio has proved to be a major challenge, particularly for large organisations. Executives and managers face even greater pressures when the nature of the strategic landscape is uncertain. This paper explores approaches for dealing with different levels of certainty in business IT projects and provides a contingent governance framework. Historically business IT projects have relied on a structured sequential approach, also referred to as a waterfall method. There is a distinction between the development stages of a solution and the management stages of a project that delivers the solution although these are often integrated in a business IT systems project. Prior research has demonstrated that the level of certainty varies between development projects. There can be uncertainty on what needs to be developed and also on how this solution should be developed. The move to agile development and management reflects a greater level of uncertainty often on both dimensions and this has led the adoption of more iterative approaches. What has been less well researched is the impact of uncertainty on the governance of the change portfolio and the corresponding implications for business executives. This paper poses this research question and proposes a govemance framework to address these aspects. The governance framework has been reviewed in the context of a major anonymous organisation, FinOrg. Findings are reported in this paper with a focus on the need to apply different approaches. In particular, the governance of uncertain business change is contrasted with the management approach for defined IT projects. Practical outputs from the paper include a consideration of some innovative approaches that can be used by executives. It also investigates the role of the business change portfolio group in evaluating and executing the appropriate level of governance. These results lead to recommendations for executives and also proposed further research.

Goal sketching: towards agile requirements engineering

This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number of real-world development projects, one of which is described here.

Goal sketching: an agile approach to clarifying requirements

This paper describes a technique that can be used as part of a simple and practical agile method for requirements engineering. It is based on disciplined goal-responsibility modelling but eschews formality in favour of a set of practicality objectives. The technique can be used together with Agile Programming to develop software in internet time. We illustrate the technique and introduce lazy refinement, responsibility composition and context sketching. Goal sketching has been used in a number of real-world development.

British pharmacy professionals’ beliefs and participation in continuing professional development: a review of the literature.

Objectives Continuing professional development (CPD) has potential to be useful in pharmacy revalidation but past uptake and attitudes to CPD in Great Britain (GB) need to be mapped. This review examines published literature to chart the participation and beliefs of pharmacy professionals towards CPD in GB in a decade that had seen a formal transition from continuing education to CPD. Methods A comprehensive review of the published literature was conducted to identify studies of the uptake of, or attitudes towards, CPD cross different sectors of pharmacy in GB from 2000 to 2010. Key findings Twenty-two studies were included and analysed, including 13 research papers, six conference papers, two news items reporting survey outcomes and one commissioned study. Eight barriers to CPD were identified as: time, financial costs and resource issues, understanding of CPD, facilitation and support for CPD, motivation and interest in CPD, attitudes towards compulsory CPD, system constraints, and technical problems. Pharmacy professionals on the whole agreed with the principle of engaging with CPD but there was little evidence to suggest widespread and wholehearted acceptance and uptake of CPD, essential for revalidation. Conclusions If CPD is to succeed, people's beliefs and attitudes must be addressed by recognising and modifying perceived barriers through a combination of regulatory, professional, work-related and personal channels. A number of recommendations are made. Direct experience of effective CPD in the absence of perceived barriers could impact on personal development, career development and patient benefit thus strengthening personal beliefs in the value of CPD in an iterative manner.

British pharmacy professionals' beliefs and participation in continuing professional development: a review of the literature

Objectives:  Continuing professional development (CPD) has potential to be useful in pharmacy revalidation but past uptake and attitudes to CPD in Great Britain (GB) need to be mapped. This review examines published literature to chart the participation and beliefs of pharmacy professionals towards CPD in GB in a decade that had seen a formal transition from continuing education to CPD. Methods:  A comprehensive review of the published literature was conducted to identify studies of the uptake of, or attitudes towards, CPD cross different sectors of pharmacy in GB from 2000 to 2010. Key findings:  Twenty-two studies were included and analysed, including 13 research papers, six conference papers, two news items reporting survey outcomes and one commissioned study. Eight barriers to CPD were identified as: time, financial costs and resource issues, understanding of CPD, facilitation and support for CPD, motivation and interest in CPD, attitudes towards compulsory CPD, system constraints, and technical problems. Pharmacy professionals on the whole agreed with the principle of engaging with CPD but there was little evidence to suggest widespread and wholehearted acceptance and uptake of CPD, essential for revalidation. Conclusions:  If CPD is to succeed, people's beliefs and attitudes must be addressed by recognising and modifying perceived barriers through a combination of regulatory, professional, work-related and personal channels. A number of recommendations are made. Direct experience of effective CPD in the absence of perceived barriers could impact on personal development, career development and patient benefit thus strengthening personal beliefs in the value of CPD in an iterative manner.