Process Deployment: A Taxonomy of Critical Success Factors

Various methods, models and standards for software process improvement have been adopted by organizations to improve their software processes. However, despite these efforts they still encounter difficulties in their process deployment throughout the organization. This is because the vast majority of these efforts focus more on the technical aspects, bypassing the human aspects. There is a set of factors that influence the successful deployment of new or modified processes. This paper presents a taxonomy of critical success factors in software process deployment to achieve the processes institutionalization. The development of a taxonomy related to these critical success factors is based on a systematic review of existing literature on specialized databases and industrial experiences that have deployed or implemented processes

The impact of enterprise application integration on information system lifecycles

Information systems (IS) have become the organisational fabric for intra-and inter-organisational collaboration in business. As a result, there is mounting pressure from customers and suppliers for a direct move away from disparate systems operating in parallel towards a more common shared architecture. In part, this has been achieved through the emergence of new technology that is being packaged into a portfolio of technologies known as enterprise application integration (EAI). Its emergence however, is presenting investment decision-makers charged with the evaluation of IS with an interesting challenge. The integration of IS in-line with the needs of the business is extending their identity and lifecycle, making it difficult to evaluate the full impact of the system as it has no definitive start and/or end. Indeed, the argument presented in this paper is that traditional life cycle models are changing as a result of technologies that support their integration with other systems. In this paper, the need for a better understanding of EAI and its impact on IS lifecycles are discussed and a classification framework proposed.Engineering and Physical Sciences Research Council (EPSRC) Grant Ref: (GR/R08025) and Australian Research Council (DP0344682)

AOSD Ontology 1.0 - Public Ontology of Aspect-Orientation

This report presents a Common Foundation for Aspect-Oriented Software Development. A Common Foundation is required to enable effective communication and to enable integration of activities within the Network of Excellence. This Common Foundation is realized by developing an ontology, i.e. the shared meaning of terms and concepts in the domain of AOSD. In the first part of this report, we describe the definitions of an initial set of common AOSD terms. There is general agreement on these definitions. In the second part, we describe the Common Foundation task in detail

Identifying how automation can lose its intended benefit along the development process : a research plan

Doctoral Consortium Presentation © The Authors 2009Automation is usually considered to improve performance in virtually any domain. However it can fail to deliver the target benefit as intended by those managers and designers advocating the introduction of the tool. In safety critical domains this problem is of significance not only because the unexpected effects of automation might prevent its widespread usage but also because they might turn out to be a contributor to incident and accidents. Research on failures of automation to deliver the intended benefit has focused mainly on human automation interaction. This paper presents a PhD research plan that aims at characterizing decisions for those involved in development process of automation for safety critical domains, taken under productive pressure, to identify where and when the initial intention the automation is supposed to deliver can be lost along the development process. We tentatively call such decisions as drift and the final objective is to develop principles that will allow to identify and compensate for possible sources of drift in the development of new automation. The research is based on case studies and is currently entering Year 2

Challenges and influential factors in ERP adoption and implementation

The adoption and implementation of Enterprise Resource Planning (ERP) systems is a challenging and expensive task that not only requires rigorous efforts but also demands to have a detailed analysis of such factors that are critical to the adoption or implementation of ERP systems. Many efforts have been made to identify such influential factors for ERP; however, they are not filtered comprehensively in terms of the different perspectives. This paper focuses on the ERP critical success factors from five different perspectives such as: stakeholders; process; technology; organisation; and project. Results from the literature review are presented and 19 such factors are identified that are imperative for a successful ERP implementation, which are listed in order of their importance. Considering these factors can realize several benefits such as reducing costs and saving time or extra effort

An Exploratory Study into Open Source Platform Adoption

Research on open source software has focused mainly on the motivations of open source programmers and the organization of open source projects [17] [19]. Some researchers portray open source as an extension of the earlier open systems movement [36]. While there has been some research on open-systems software adoption by corporate MIS organizations [4] the issue of open source adoption has received little attention. We use a series of interviews with MIS managers to develop a grounded theory of open source platform adoption. We contrast this to prior academic and popular reports about the adoption of open source

Benchmarking performance management systems

The Balanced Scorecard and associated performance management approaches, has become a widely practiced and popular management reporting method in recent times. Moreover, enabling technology, which assists in the delivery and personalisation of corporate performance information, is having a deeper and more rapid impact than ever before. This paper presents a brief comparative benchmarking study of leading enterprise performance management systems. Also, the author discusses the merits of bespoke internet technology development and out-of-the-box portal functionalities. An analysis of key business drivers and implementation risks of such approaches is highlighted via a case study example, and concludes the paper

Transforming failure into success through organisational learning: An analysis of a manufacturing information system

This paper describes the idiosyncracies of a case study company, through highlighting issues and problems experienced during their attempts to evaluate, implement and realise the holistic implications of a manufacturing information system. Although the Information System (IS) was operational for a period of time, it was eventually deemed a failure. The reason for this was that a range of human and organisational factors prevented the organisation from embracing the full impact of the system. The eventual success of their information system was realised through a bespoke implementation, based upon a traditional systems development lifecycle that indirectly addressed learning issues following the earlier failed deployment. The paper highlights key issues relating to business success and failure, and then contrasts them alongside the presented case study. In doing so, the authors conclude by proposing methods through which manufacturing information systems can be transformed for business success. This is described achievable through both a realisation in the positioning of the organisation relative to technology management, and the related mapping of human and technological constructs that support information systems related succes

Influential factors of aligning Spotify squads in mission-critical and offshore projects – a longitudinal embedded case study

Changing the development process of an organization is one of the toughest and riskiest decisions. This is particularly true if the known experiences and practices of the new considered ways of working are relative and subject to contextual assumptions. Spotify engineering culture is deemed as a new agile software development method which increasingly attracts large-scale organizations. The method relies on several small cross-functional self-organized teams (i.e., squads). The squad autonomy is a key driver in Spotify method, where a squad decides what to do and how to do it. To enable effective squad autonomy, each squad shall be aligned with a mission, strategy, short-term goals and other squads. Since a little known about Spotify method, there is a need to answer the question of: How can organizations work out and maintain the alignment to enable loosely coupled and tightly aligned squads? In this paper, we identify factors to support the alignment that is actually performed in practice but have never been discussed before in terms of Spotify method. We also present Spotify Tailoring by highlighting the modified and newly introduced processes to the method. Our work is based on a longitudinal embedded case study which was conducted in a real-world large-scale offshore software intensive organization that maintains mission-critical systems. According to the confidentiality agreement by the organization in question, we are not allowed to reveal a detailed description of the features of the explored project