Analysis of Software Process Improvement Activities in SMEs: A Systematic Literature Review

This Software industry is a very significant cog in today’s economic landscape. The majority of these organizations mainly comprise small and medium enterprises (SMEs). These enterprises aim to benefit from Software Process Improvement (SPI) activities in producing high-quality products and services in competitive business environments. For this purpose, SPI models have been developed for specific SME characteristics. In this study, we performed a systematic literature review to analyze the characteristics of these SPI models, the challenges of performing SPI activities in SMEs, and the critical success factors for SPI activities. In this context, 61 articles published from 2007 to 2020 were examined, as a result, 28 SPI models used in SMEs were found out. In addition, ten different situations that make SPI implementations challenging in SMEs and seven factors that affect the success of SPI studies in SMEs were reported

Process Productivity Improvements through Semantic and Linked Data Technologies

Programa de Doctorado en Ciencia y Tecnología Informática por la Universidad Carlos III de MadridPresidente: José María Álvarez Rodríguez.- Secretario: Rafael Valencia García.- Vocal: Alejandro Rodríguez Gonzále

A comparison of project control standards based on network analysis

Project control is a crucial function in project management. Over the years, several best practice standards have been developed to assist project managers in improving project control. The objective of this paper is to compare three prominent best practice models of PMBOK, PRINCE2, and the AACE framework with respect to the core processes of project control. Network analysis is used to achieve this objective. The results show that influential and linkage processes, such as Control quality, Review the stage status, Forecasting, and Change management have the most significant impacts on the complexity of the project control function. This work has the potential to help rethink the project control function by creating a more global view of the most central and critical processes for project control, from which enhancement in the ability to control the project can be drawn

A comparison of project control standards based on network analysis

Project control is a crucial function in project management. Over the years, several best practice standards have been developed to assist project managers in improving project control. The objective of this paper is to compare three prominent best practice models of PMBOK, PRINCE2, and the AACE framework with respect to the core processes of project control. Network analysis is used to achieve this objective. The results show that influential and linkage processes, such as Control quality, Review the stage status, Forecasting, and Change management have the most significant impacts on the complexity of the project control function. This work has the potential to help rethink the project control function by creating a more global view of the most central and critical processes for project control, from which enhancement in the ability to control the project can be drawn

Software prozesuen hobekuntzarako ekimenen biziraupen-analisia eta sailkapen-ikasketa, eta horien ondorioak enpresa txikietan

116 p.Softwareak funtsezko papera dauka negozio gehienetan. Hain zuzen ere, edozein negozioren abantaila lehiakorraren gako nagusietako bat dela esan daiteke. Software hori enpresa handi, ertain edo txikiek sor dezakete. Testuinguru horretan, erakunde mota horiek prozesuak hobetzeko ekimenak martxan jartzeko hautua egiten dute, merkatuan eskaintzen dituzten zerbitzuen edo azken produktuen kalitatea hobetzeko helburuarekin. Hortaz, ohikoa izaten da enpresa handi eta ertainek azken produktuen garapen-prozesuak zehaztea, are eredugarriak diren kalitate-ereduak erabiltzea, industriatik eratorritako jardunbide egokiekin. Izan ere, hobekuntza-ekimen bat aurrera eramaten laguntzeko erreferentziazko eredu eta estandar asko daude. Hortaz, erakundeek hainbat eredutako eskakizunak bete behar izaten dituzte aldi berean. Estandar horien barruan antzekoak diren praktika edo eskakizunak egon ohi dira (bikoiztasunak), edo neurri handiko erakundeentzat pentsatuta daudenak. Erakunde txikien esparruan, bikoiztasun horiek gainkostua eragiten dute ekimen hauetan. Horren ondorioz, erreferentziazko ereduekin loturiko prozesuak zehazteko orduan, burokrazia-lana handitu egiten da. Horrez gain, eredu hauen bikoiztasunak ezabatzera eta bere prozesuak hainbat arau aldi berean aintzat hartuta berraztertzera behartzen ditu. Egoera hori bereziki delikatua da 25 langiletik behera dituzten erakunde txikientzat, Very Small Entities (VSE) izenez ere ezagunak direnak. Erakunde mota hauek ahal duten modurik onenean erabiltzen dituzte haien baliabideak, eta, haien ikuspegitik, erreferentziazko eredu hauek gastu bat dira inbertsio bat baino gehiago. Hortaz, ez dute prozesuak hobetzeko ekimenik martxan jartzen. Ildo horretatik, erakunde horiei VSE-en beharretara egokituko zen eredu bat eskaintzeko sortu zen ISO/IEC 29110.ISO/IEC 29110 arauaren lehen edizioa 2011n sortu zen eta, ordutik, zenbait ikerketa-lan eta industria-esperientzia garatu dira testuinguru horren barruan. Batetik, ez dago VSE-ekin loturik dauden nahikoa industria-esperientzia, eta, beraz, ez da erraza jakitea zein den VSE-en portaera. 2011tik, ISO/IEC29110 arauarekin zerikusia duten hainbat lan argitaratu dira, baina, orain arte, lan horien tipologia oso desberdina izan da. Horrenbestez, ezinbestekoa da lehen esperientzia hauek aztertu eta ezagutzea, egindako lehen lan horiek sailkatu ahal izateko. Bestetik, prozesuak hobetzeko ekimenek ez dute beti arrakastarik izaten, eta mota honetako ekimen baten iraupena zein izango den ere ez da gauza ziurra izaten. Hartara, ekimen hauek testuinguru hauetan daukaten biziraupen maila zein den aztertu behar da, bai eta VSE-etan prozesuak hobetzeko ekimenak garatu eta ezarri bitartean eman daitezkeen lan-ereduak identifikatzea ere. Azkenik, garatzen dituzten produktuen segurtasun-arloarekin kezka berezia izan ohi dute VSEk. Hortaz, segurtasun-alderdi nagusiak kudeatzeko mekanismoak ezarri behar izaten dituzte.Lehenik eta behin, lan honetan, ISO/IEC 29110 arauarekin loturiko artikuluen azterketa metodiko bat egin dugu, eta ikerketa-esparru nagusiak eta egindako lan mota garrantzitsuenak jaso ditugu. Bigarrenik, VSEk prozesuak hobetzeko martxan jarritako mota honetako ekimenen biziraupena aztertzeko marko bat proposatu dugu. Hirugarrenik, haien portaeraren ezaugarriak zehazteko, ekimen hauetan ematen diren ereduak identifikatzeko ikuspegia landu dugu. Laugarrenik, VSEn softwarearen garapenaren bizi-zikloan segurtasun-arloko alderdiak gehitzeko eta zor teknikoa kudeatzeko proposamena egin dugu

Enterprise Architecture Approach for Project Management and Project-Based Organizations: A Review

Project-based organizations (PBOs) derive income from conducting projects for their clients. Maintaining the most effective and efficient project governance style is an ongoing process for these organizations as the context continuously changes. Enterprise architecture (EA) is a systemic approach that supports organizations in modeling and describing themselves in different layers, such as strategy, business, application, and technology. This literature review describes the current state of EA usage in improving and quickly revising project management governance in PBOs to benefit practitioners and researchers for an integrated view of EA, PM, and PBO, and identification of future research gaps. This review used an EA model composed of layers as an analytical framework. The extracted bibliometric and content data from selected articles were processed using the VOSviewer tool for identifying and understanding the relationships between main concepts through network mapping. The selected articles are oriented to internal organization projects, mainly in information technology (IT). The need to align projects with business is highlighted, with EA positioned as a governance tool. It was found that application of EA in PBOs is rare. A trend toward using popular PM and EA frameworks, such as PMBOK and ArchiMate, was observed

Distinguishing coefficient driven sensitivity analysis of GRA model for intelligent decisions: application in project management

The Distinguishing Coefficient (ξ) is an important parameter of Grey Relational Analysis (GRA), a flagship multi-criteria decision making (MCDM) model of Grey System Theory, an intelligent and multifaceted field developed by Chinese scientists in 1980s. However, the scholars widely assume ξ = 0.5. The current study questions this practice. Also, some scholars have argued that the variation in ξ doesn’t influence the ranking of the factors through GRA. On contrary, the study demonstrates, the variation in ξ can influence the ranking. This has been shown through a case involving primary data concerning the perceived relative importance of Project Management Knowledge Areas (PMKAs). This study is significant for the analysts of uncertain systems, represented by grey or fuzzy systems, who intend to use GRA for intelligent multi-criteria decision making. It encourages ξ – driven sensitivity analysis of GRA model before interpreting the results. The study reveals, by tailoring the value of ξ a point can be achieved where the ranking obtained through GRA can be made most comparable to the other MCDM methods. For comparative analysis of the GRA based results the study deployed three other MCDM techniques; Analytic Hierarchy Process, Best Worst Method and Simple Additive Weighting

Systematic mapping of software engineering management with an agile approach

El enfoque ágil ha generado una amplia variedad de estrategias para administrar con éxito diversos proyectos de software en todo el mundo. Además, podemos asegurar que los proyectos de software se han beneficiado de los métodos ágiles ya conocidos. En este sentido, este artículo busca demostrar cómo se aplica el enfoque ágil en las áreas de la gestión en la ingeniería del Software. Para ello, este estudio realiza un mapeo sistemático para identificar las principales tendencias en la gestión de la ingeniería de software con un enfoque ágil. Se han identificado un total de 1137 artículos, de los cuales 165 son relevantes para los fines de este estudio, estos indican que la entrega temprana de valor, un principio clave de la agilidad, sigue siendo la principal tendencia para el uso de métodos ágiles. Sin embargo, también existen fuertes tendencias enfocadas en puntos clave de la gestión en ingeniería de software, como optimizar la gestión de calidad, optimizar la especificación de requisitos, optimizar la gestión de riesgos y mejorar la comunicación y coordinación del equipo, estos resultados permitirán generar nuevas líneas de investigación para cada punto clave de la gestión en la ingeniería del software impactado por el enfoque ágil.The agile approach has generated a wide variety of strategies to successfully manage various software projects worldwide. In addition, we can ensure that software projects have benefited from the already known agile methods. In this sense, this article seeks to demonstrate how the agile approach is applied in Software engineering management areas. To do this, this study performs a systematic mapping to identify the main trends in software engineering management with an agile approach. A total of 1137 articles have identified, of which 165 are relevant for the purposes of this study, these indicate that early value delivery, a key principle of agility, continues to be the main trend for the use of agile methods. However, there are also strong trends focused on key points of management in software engineering, such as optimize quality management, optimize requirements specification, optimize risk management, and improve team communication and coordination, these results will allow generating new lines of research for each key point of management in software engineering impacted by the agile approach

Systematic mapping of software engineering management with an agile approach

El enfoque ágil ha generado una amplia variedad de estrategias para administrar con éxito diversos proyectos de software en todo el mundo. Además, podemos asegurar que los proyectos de software se han beneficiado de los métodos ágiles ya conocidos. En este sentido, este artículo busca demostrar cómo se aplica el enfoque ágil en las áreas de la gestión en la ingeniería del Software. Para ello, este estudio realiza un mapeo sistemático para identificar las principales tendencias en la gestión de la ingeniería de software con un enfoque ágil. Se han identificado un total de 1137 artículos, de los cuales 165 son relevantes para los fines de este estudio, estos indican que la entrega temprana de valor, un principio clave de la agilidad, sigue siendo la principal tendencia para el uso de métodos ágiles. Sin embargo, también existen fuertes tendencias enfocadas en puntos clave de la gestión en ingeniería de software, como optimizar la gestión de calidad, optimizar la especificación de requisitos, optimizar la gestión de riesgos y mejorar la comunicación y coordinación del equipo, estos resultados permitirán generar nuevas líneas de investigación para cada punto clave de la gestión en la ingeniería del software impactado por el enfoque ágil.The agile approach has generated a wide variety of strategies to successfully manage various software projects worldwide. In addition, we can ensure that software projects have benefited from the already known agile methods. In this sense, this article seeks to demonstrate how the agile approach is applied in Software engineering management areas. To do this, this study performs a systematic mapping to identify the main trends in software engineering management with an agile approach. A total of 1137 articles have identified, of which 165 are relevant for the purposes of this study, these indicate that early value delivery, a key principle of agility, continues to be the main trend for the use of agile methods. However, there are also strong trends focused on key points of management in software engineering, such as optimize quality management, optimize requirements specification, optimize risk management, and improve team communication and coordination, these results will allow generating new lines of research for each key point of management in software engineering impacted by the agile approach

Systematic mapping of software engineering management with an agile approach

El enfoque ágil ha generado una amplia variedad de estrategias para administrar con éxito diversos proyectos de software en todo el mundo. Además, podemos asegurar que los proyectos de software se han beneficiado de los métodos ágiles ya conocidos. En este sentido, este artículo busca demostrar cómo se aplica el enfoque ágil en las áreas de la gestión en la ingeniería del Software. Para ello, este estudio realiza un mapeo sistemático para identificar las principales tendencias en la gestión de la ingeniería de software con un enfoque ágil. Se han identificado un total de 1137 artículos, de los cuales 165 son relevantes para los fines de este estudio, estos indican que la entrega temprana de valor, un principio clave de la agilidad, sigue siendo la principal tendencia para el uso de métodos ágiles. Sin embargo, también existen fuertes tendencias enfocadas en puntos clave de la gestión en ingeniería de software, como optimizar la gestión de calidad, optimizar la especificación de requisitos, optimizar la gestión de riesgos y mejorar la comunicación y coordinación del equipo, estos resultados permitirán generar nuevas líneas de investigación para cada punto clave de la gestión en la ingeniería del software impactado por el enfoque ágil.The agile approach has generated a wide variety of strategies to successfully manage various software projects worldwide. In addition, we can ensure that software projects have benefited from the already known agile methods. In this sense, this article seeks to demonstrate how the agile approach is applied in Software engineering management areas. To do this, this study performs a systematic mapping to identify the main trends in software engineering management with an agile approach. A total of 1137 articles have identified, of which 165 are relevant for the purposes of this study, these indicate that early value delivery, a key principle of agility, continues to be the main trend for the use of agile methods. However, there are also strong trends focused on key points of management in software engineering, such as optimize quality management, optimize requirements specification, optimize risk management, and improve team communication and coordination, these results will allow generating new lines of research for each key point of management in software engineering impacted by the agile approach