86 research outputs found

    Agile, Web Engineering and Capability Maturity ModelI ntegration : A systematic literature review

    Get PDF
    Context Agile approaches are an alternative for organizations developing software, particularly for those who develop Web applications. Besides, CMMI (Capability Maturity Model Integration) models are well-established approaches focused on assessing the maturity of an organization that develops software. Web Engineering is the field of Software Engineering responsible for analyzing and studying the specific characteristics of the Web. The suitability of an Agile approach to help organizations reach a certain CMMI maturity level in Web environments will be very interesting, as they will be able to keep the ability to quickly react and adapt to changes as long as their development processes get mature. Objective This paper responds to whether it is feasible or not, for an organization developing Web systems, to achieve a certain maturity level of the CMMI-DEV model using Agile methods. Method The proposal is analyzed by means of a systematic literature review of the relevant approaches in the field, defining a characterization schema in order to compare them to introduce the current state-of-the-art. Results The results achieved after the systematic literature review are presented, analyzed and compared against the defined schema, extracting relevant conclusions for the different dimensions of the problem: compatibility, compliance, experience, maturity and Web. Conclusion It is concluded that although the definition of an Agile approach to meet the different CMMI maturity levels goals could be possible for an organization developing Web systems, there is still a lack of detailed studies and analysis on the field

    Mapping Agile Practices to CMMI-DEV Level 3 in Web Development Environments

    Get PDF
    Agile approaches formally appeared ten years ago and nowadays they are a valid alternative for organizations developing software. Agile methodologies are especially interesting to those developing Web environments applications, as they can fit properly the special characteristics of this type of developments. In addition, maturity models like CMMI-DEV (Capability Maturity Model Integration for Development) focus on assessing the maturity level of organizations developing or acquiring software. These models are well established and can increment quality of development process to enhance costumers’ satisfaction. CMMI-DEV level 3 provides a good compromise on maturity gained and effort needed. The feasibility of reaching it through a combination of Agile methods can be very useful to organizations developing systems in Web environments, as they can keep the adaptability of Agile together with a more mature development process. This paper proposes a set of Agile methods so as to reach all CMMI-DEV maturity level 3 generic and specific goals. Based on this analysis, the paper proposes further research lines

    NDT-Agile: An Agile, CMMI-Compatible Framework for Web Engineering

    Get PDF
    Agile and Web Engineering show important synergies, making Agile a common approach for Web development. Besides, several initiatives emerged to support CMMI-DEV within Agile, where CMMI-DEV aims to improve organizations’ software development process. An approach integrating Agile, Web and CMMI-DEV might be of great value, since they might allow Web development teams to use Agile, as well as progress through CMMI-DEV maturity levels. For this purpose, we developed NDT-Agile, an NDT-based Agile framework to achieve the goals of CMMI-DEV in the context of Web Engineering. It was developed by mapping Agile practices to the goals of CMMI-DEV so as to identify existing gaps. Next, we searched for suitable Agile practices to cover the gaps and integrated them into a framework called NDTAgile, which was validated using an expert-judgment technique: the Delphi method. This paper describes how we integrated Agile and CMMI-DEV into a Web Engineering framework. Besides, it also analyzes its initial evaluation, together with a first tool developed to support it.Ministerio de Economía y Competitividad TIN2013-46928-C3-3-RMinisterio de Economía y Competitividad TIN2016-76956-C3-2-RMinisterio de Economía y Competitividad TIN2015-71938-RED

    On the Role of Agile Software Development Practices in Software Process Improvement

    Get PDF
    Tarkvaraarendus on endiselt võrdlemisi uus ja arenev valdkond. Tarkvaraettevõtted on otsinud tarkvara arendusprotsessi parendamist (ingl SPI) aastaid, kuid tegu on mitmekülgse valdkonnaga. Antud magistritöö eesmärk on pakkuda suurt pilti väleda tarkvaraarenduse meetoditest ja tavadest tarkvara arendusprotsessi parendamise kontekstis. Lisaks eelmainitule on antud töö eesmärgiks minna rohkem süvitsi väledate tarkvaraarenduse meetodite alamhulgaga laiahaardelisema kaardistamistöö raames, mis uurib SPI hetkeseisu kirjanduses. Leidmaks vastuseid töös püstitatud uuritavatele küsimustele, viidi antud töö raames läbi süstemaatiline kirjanduse ülevaade. Kirjanduse ülevaate tulemused valideeriti erinevates Eesti tarkvaraettevõtetes viies läbi küsitlusi. Avaldatud teoste, mis hõlmavad tarkvaraarenduse meetodite kasutamist SPI kontekstis aastane avaldamishulk on vaikselt kasvanud aastate jooksul. Kirjandusülevaate tulemused viitavad, et väledate meetodite kasutamine SPI jaoks pole ainult idee. Avaldatud teoste hulgas on võrdlemisi võrdselt teoseid, mis analüüsivad antud teemat idee tasandil ning neid, mis kirjeldavad väledate tarkvaraarenduse meetodite kasutamist ka professionaalses töös. Lisaks sellele viitavad tulemused, et professionaalide jaoks potentsiaalselt kasulikke teoseid on kirjanduses suur kogus. Enimuuritud väleda tarkvaraarenduse meetodid SPI kontekstis on Scrum ning Extreme Programming. Kõige enam mainitakse kirjanduses tavasid nagu pidev integratsioon, kõigepealt testi ning igapäevaste koosolekute pidamine. Kogu uuritud kirjanduses on piisvalt tõendeid tööstusest väledate meetodite kasutamisest SPI tarbeks, mida kinnistavad ka Eestis opereerivates tarkvaraettevõtetes läbiviidud küsitluse tulemused.Software development in general is still a fairly new and evolving field. Software development companies have been looking for software process improvement (SPI) for years, but the field of SPI is a diverse one. The goal of the Master’s thesis at hand is to provide the big picture of the use of agile methodologies along with its practices in the context of SPI within the current literature. Furthermore, the paper at hand aims to provide more insight into the subset of agile practices of a bigger, more general systematic mapping study on the current state of the art of software process improvement. To find answers to the research questions stated in the thesis, systematic literature review was conducted. The results of the literature review were validated by conducting surveys amongst professionals in several Estonian software development companies with varying sizes. The publication rate of papers concerning agile practices in the context of SPI shows a steady rise over the years. Results of the literature review show that the field of agile practices in SPI is fairly evenly balanced regarding being a concept or being adapted and evaluated in the industry. Furthermore, the results indicate that the there are many papers published that are of high relevance to industry professionals. By far the most discussed agile methods in the literature regarding SPI are Scrum and Extreme Programming while the most addressed practices include integrating often, testing first and conducting daily meetings. Within the analysed papers there are plenty of evidence from the industry of using agile methods in SPI. The survey conducted amongst several Estonian companies confirms that the use of agile practices in SPI is a relevant topic and that Scrum being the most popular topic in the literature is not a coincidence

    Mastering Agile Practice Adoption through a Model-Driven Approach for the Combination of Development Methods

    Get PDF
    Many software companies are adapting their traditional development processes to incorporate agile practices. In this context, it is necessary to count on expert knowledge to evaluate different agile practices and configure them according to project needs. However, this expert knowledge is scarce, difficult to validate, and time-consuming, since it is applied manually. As a solution, the paper presents a model-driven approach, called SIAM, which automatically generates guidelines for the adoption of agile practices through the combination of different development methods. SIAM is supported by a meta-model architecture to implement a knowledge repository that characterizes method configuration decisions, which can be reused in different development projects. SIAM has been implemented in a tool suite that facilitates the specification of models and the identification of issues during the definition of the development processes. The approach has been successfully applied to reconfigure an industrial development process with agile methods, showing that the effort required for tailoring agile practices according to organizational standards is considerably reduced

    What are Hybrid Development Methods Made Of? An Evidence-Based Characterization

    Get PDF
    Among the multitude of software development processes available, hardly any is used by the book. Regardless of company size or industry sector, a majority of project teams and companies use customized processes that combine different development methods— so-called hybrid development methods. Even though such hybrid development methods are highly individualized, a common understanding of how to systematically construct synergetic practices is missing. In this paper, we make a first step towards devising such guidelines. Grounded in 1,467 data points from a large-scale online survey among practitioners, we study the current state of practice in process use to answer the question: What are hybrid development methods made of? Our findings reveal that only eight methods and few practices build the core of modern software development. This small set allows for statistically constructing hybrid development methods. Using an 85% agreement level in the participants’ selections, we provide two examples illustrating how hybrid development methods are characterized by the practices they are made of. Our evidence-based analysis approach lays the foundation for devising hybrid development methods

    Metrics Model to Complement the Evaluation of DevOps in Software Companies

    Get PDF
    This article presents a model to complement the evaluation of DevOps in software companies. It was designed by harmonizing the elements of the DevOps process identified through a systematic mapping of the literature and aimed to know the state of the art of methodological solutions and tools to evaluate DevOps in the industry. The process elements were identified, compared, and integrated into a common process structure that was used to establish a total of 11 metrics using the Goal-Question-Metric approach. The model was evaluated by a focus group of expert DevOps professionals. They determined that the model is clear, easy to apply, and provides valuable information to companies to improve their DevOps practices

    Risk Management in Scrum Projects: A Bibliometric Study

    Get PDF
    This article presents a bibliometric study of Risk Management in Scrum Projects. It was carried out an analysis involving the ISI Web of Knowledge and Scopus databases, identifying the main authors, countries and periodicals. It also identified the most cited authors by the analyzed articles, in addition to the keywords most frequently cited. These analyzes were performed using the reference maps, which were generated by CiteSpace® software, which offers a set of features to support bibliometrics. The objective was to identify the current scenario research of Risk Management applied in Scrum Projects in order to offer a consistent basis of information to researchers. The research verified that, despite the importance of the research topic, few scientific studies have been identified, which brings the need for new researches on the subject

    Reengineering the Industrial CMMI

    Get PDF
    Abstract of Re-engineering of Industrial CMMI Through this research, I have established a general strategy to appraise an organization against a scale of five process maturity levels whilst maintaining a strong mechanics of CMMI. Reengineering of industrial CMMI proposes a novel method for Industrial Competence ranking of those organizations/companies which are targeting various CMMI levels. This approach uses SCAMPI assessment techniques to rank different organizations that fall below certain level of CMMI model. Furthermore, it adds the credulous factors, i.e., Score, Reliance and Confidence level for an organization’s capability and maturity evaluation. The benefit of proposed model is, that an organization can set its objectives to achieve target level of CMMI model, and it could be differentiated from less mature organizations at same level. This technique not only reclassifies the CMMI levels but also exposes various confidence factors.Index Terms— CMMI, Industrial Process Optimization, Process Engineering, Capability and Maturity Ranking, Product Quality Assurance
    corecore