Critical sucess factors in software process improvement

The aim of the thesis project was to identify Software Process Improvement (SPI) success factors through a deeply literature review. Objectives: • Identify the models of SPI • To identify SPI success factors through literature review. • To identify the most important SPI success factors based on the frequency of occurrence in published research. • To identify the variety of definitions or explanations of the most important SPI success factors in published research

Critical sucess factors in software process improvement

The aim of the thesis project was to identify Software Process Improvement (SPI) success factors through a deeply literature review. Objectives: • Identify the models of SPI • To identify SPI success factors through literature review. • To identify the most important SPI success factors based on the frequency of occurrence in published research. • To identify the variety of definitions or explanations of the most important SPI success factors in published research

IT-enabled Process Innovation: A Literature Review

The importance of Information Technology (IT) is growing, and in a hypercompetitive market IT must be used as a strategic asset for companies to succeed. In order to gain strategic benefits from IT, companies need to be innovative when deploying IT. This can be achieved by reengineering business processes to take advantage of the possibilities IT provides. In 1993 Thomas H. Davenport presented a framework describing the role of IT in process innovation . Based on this framework, the purpose of this paper is to conduct a literature review to answer the following research question: What kind of opportunities does IT provide for process innovation? . Davenport\u27s framework is used as an analytical lens to review articles from the top 20 IS and management journals. The paper provides an overview and an in-depth analysis of the literature on IT-enabled process innovation and suggests avenues for future research as well as recommendations for practitioners. Our analyses reveal five distinct themes related to opportunities for IT-enabled process innovation, all of which offer guidance to practitioners and highlight gaps in our current knowledge about how to leverage IT for innovation purposes

Improving Practices in a Small Software Firm: An Ambidextrous Perspective

Despite documented best practices and specialized tools, software organizations struggle to deliver quality software that is on time, within budget, and meets customer requirements. Managers seeking improved software project outcomes face two dominant software paradigms which differ in their emphasis on upfront planning, customer collaboration, and product documentation: plan-driven and agile. Rather than promoting one approach over the other, this research advocates improving software management practices by developing the organization’s ambidextrous capability. Ambidextrous organizations have the ability to simultaneously succeed at two seemingly contradictory capabilities (e.g. discipline and agility) which leads to enhanced organizational performance. Overall, this study asks the question: How can an ambidextrous perspective facilitate improvement in software practices? Driven by this question, and based on a two year action research study at a small software firm, TelSoft, the objectives of this research are to: 1. Identify dualities involved in improving software practices 2. Design interventions based on these dualities to improve software practices 3. Explore the process of becoming an ambidextrous software organization The resulting dissertation consists of a summary and four papers that each identify and address particular dualities encountered during software process improvement. The first paper asserts that both process-driven and perception-driven inquiry should be used during assessment of software practices, presents a model that shows how this combination can occur, and demonstrates the use of this model at TelSoft. The second paper explicates two theories for understanding and resolving issues in requirements engineering practice – repeat-ability and response-ability – and argues for the need to negotiate between the two. The third paper identifies a tension between managing legacy and current processes and proposes a model for software process reengineering, a systematic process for leveraging legacy processes created during prior SPI efforts. Finally, the fourth paper applies the theoretical lens of ambidexterity to understand the overall change initiative in terms of the tension between alignment and adaptability. The study used a variety of data sources to diagnose software practices, including semi-structured interviews, software process documents, meeting interactions, and workshop discussions. Subsequently, we established, facilitated, and tracked focused improvement teams in the areas of customer relations, requirements management, quality assurance, project portfolio management, and process management. Furthermore, we created and trained two management teams with responsibility for ongoing management of SPI and project portfolio management respectively. We argue that these activities improved software practices at TelSoft and provided a stronger foundation for continuous improvement. Keywords: Ambidexterity, software process improvement (SPI), action research, requirements engineering assessment, action planning, software process reengineering, software management

Software Process Modeling with Eclipse Process Framework

The software development industry is constantly evolving. The rise of the agile methodologies in the late 1990s, and new development tools and technologies require growing attention for everybody working within this industry. The organizations have, however, had a mixture of various processes and different process languages since a standard software development process language has not been available. A promising process meta-model called Software & Systems Process Engineering Meta- Model (SPEM) 2.0 has been released recently. This is applied by tools such as Eclipse Process Framework Composer, which is designed for implementing and maintaining processes and method content. Its aim is to support a broad variety of project types and development styles. This thesis presents the concepts of software processes, models, traditional and agile approaches, method engineering, and software process improvement. Some of the most well-known methodologies (RUP, OpenUP, OpenMethod, XP and Scrum) are also introduced with a comparison provided between them. The main focus is on the Eclipse Process Framework and SPEM 2.0, their capabilities, usage and modeling. As a proof of concept, I present a case study of modeling OpenMethod with EPF Composer and SPEM 2.0. The results show that the new meta-model and tool have made it possible to easily manage method content, publish versions with customized content, and connect project tools (such as MS Project) with the process content. The software process modeling also acts as a process improvement activity.Ohjelmistoprosessin mallinnus Eclipse Process Frameworkilla ja SPEM 2.0 metamallilla Ohjelmistot ja ohjelmistoteollisuus kehittyvät jatkuvasti. Ketterien menetelmien tulo 1990-luvun loppupuolella, uudet kehitystyökalut ja teknologiat vaativat yhä enemmän huomiota alalla työskenteleviltä ihmisiltä. Organisaatioilla on kuitenkin ollut sekalainen kirjo prosesseja ja erilaisia prosessikuvauskieliä, koska standardia kuvauskieltä ei ole ollut saatavilla. Prosessimetamalli SPEM 2.0 julkaistiin hiljattain. Tätä mallia hyödyntää mm. Eclipse Process Framework Composer (EPFC) –työkalu, joka on suunniteltu prosessien ja menetelmäsisällön kehittämiseen ja ylläpitoon. Työkalun tavoitteena on tukea useita erilaisia projektityyppejä ja kehitystyylejä. Tässä työssä esitellään seuraavat aiheet ja käsitteet: ohjelmistoprosessit, mallit, perinteiset ja ketterät lähestymistavat, metoditekniikkaa sekä prosessien kehittäminen. Lisäksi tutustutaan muutamiin tunnetuimmista metodologioista (RUP, OpenUP, OpenMethod, XP ja Scrum) ja vertaillaan näitä. Työssä tutkitaan tarkemmin Eclipse Process Framework Composer –työkalua, SPEM 2.0 metamallia, näiden ominaisuuksia, käyttöä sekä mallintamista. Esitän tutkimustulokset ja tutkimuksenkulun OpenMethodin mallintamisesta EPFC –työkalulla sekä SPEM 2.0 -metamallilla. Tulokset osoittavat, että uusi metamalli ja työkalu helpottavat prosessin ja menetelmäsisällön hallintaa, mahdollistavat räätälöityjen julkaisujen teon sisällöstä, sekä yhdistävät prosessin projektityökaluihin kuten MS Projectiin. Mallinnus voidaan lisäksi ymmärtää osana prosessin kehittämistä.Siirretty Doriast

A requirements-based software process maturity model

The requirements phase of software development is an on-going problem for the software engineering community. The many disparate recommendations and best practices found in the literature make it difficult for software organisations to recognise which practices apply to their individual needs. The aim of this thesis is to pull together key solutions into a framework that allows practitioners to assess where their requirements process needs strengthening and to provide a means in which improvements can be achieved. In this thesis I show how I design, develop and validate a model of requirements engineering processes. This requirements capability maturity model (R-CMM) adheres to the characteristics of the Software Engineering Institute's Software Capability Maturity Model (SW-CMM) and is designed to take practitioners from an immature process capability through to an advanced capability. I contribute to the body of knowledge in both software process improvement and requirements engineering (RE) by providing rigorous detail of how a process maturity framework is developed to support RE practices. The model is generic and should apply to many software development organisations. The R-CMM guides users towards a view of RE that is based on goals and is problem driven. The SW-CMM framework is transformed into a simplified model that relates goals and problems to individual RE practises

Software knowledge management using wikis : a needs and features analysis

Estágio realizado na StrongstepDocumento confidencial. Não pode ser disponibilizado para consultaTese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 201

Cmmi Implementation Framework

Tez (Yüksek Lisans) -- İstanbul Teknik Üniversitesi, Fen Bilimleri Enstitüsü, 2007Thesis (M.Sc.) -- İstanbul Technical University, Institute of Science and Technology, 2007Bu çalısmada, sistematik ve en iyi pratiklere dayanan bir süreç yönetimi yazılımı gelistirilmektir. Tasarlanan proses altyapısı ve gelistirilen yazılım, yazılım mühendisliginin proje yönetimi, gereksinim yönetimi, analiz ve tasarm, uygulama gelistirme, test, degisiklik yönetimi ve aktarım süreçlerinde gerekli olan spesifik tecrübeleri bir bütün içinde, yönetilebilir bir sekilde tutulmasını hedeflemektedir. CMMI modelinde yer alan temel özellik olan izlenebilirligin süreç altyapısına uygulanması ve uygulamada maksimum faydanın alınması amaçlanmaktadır. Orta ve küçük ölçekli firmaların süreç yönetimi konularına adaptasyonunu en hızlı ve en dogru yapabilecekleri bir ortam gelistirilmistir.This thesis studies the development of a systematic software solution to provide software engineering process management based on best practices. The said software solution which has been designed and developed for this study aims to provide specific practices for integrated management of project management, requirements management, analysis & design, implementation, testing, change management, and deployment. Accordingly, this thesis aims to establish an environment that provides fast and applicable adaptation to such software engineering processes for small and medium scale companies. The solution provided within this thesis study is based on one of the more popular models developed by Carnegie Mellon University (U.S.) Software Engineering Institute, the Capability Maturity Model Integration (CMMI) model.Yüksek LisansM.Sc