463 research outputs found

    A Scrum-based approach to CMMI maturity level 2 in Web Development environments

    Get PDF
    Scrum has become one of the most popular agile methodologies, either alone or combined with other agile practices. Besides, CMMI (Capability Maturity Model Integration) is accepted as a suitable model to measure the maturity of the organizations when developing or acquiring software. Although these two approaches are often considered antagonist, the use of an agile approach to reach certain CMMI maturity levels may result beneficial to organizations that develop Web systems, since they would take the advantages of both approaches. In Web community, this union may be very interesting, because agile approaches fits with the special needs of Web development, and they could be a useful tool for companies getting a certain grade of maturity. This work analyzes the goals of CMMI maturity level 2 and the feasibility of achieving them using the practices proposed by Scrum, trying to assess whether the use of this methodology is suitable for meeting the CMMI generic and specific goals or not. Finally, and based on this analysis, this paper raises a possible extension of Scrum, based on agile techniques, to accommodate the CMMI maturity level 2.Ministerio de Educación y Ciencia TIN2010-20057-C03-02Junta de Andalucía TIC-578

    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

    An Agile approach to CMMI-DEV levels 4 and 5 in Web development

    Get PDF
    CMMI (Capability Maturity Model-Integration) model proposes a set of process areas, including suggested practices, with the aim of helping organizations to improve the quality of their products and processes. It is commonly accepted that as an organization progresses through the different levels of CMMI, the quality of its development might improve as well as the overhead of the development process, impeding it to quickly adapt to customers or partners changing needs. Besides, Agile practices allow quick adaptation and early delivery of business value. The specificity of Web environments makes them suitable for Agile approaches. However, as quality requirements for Web systems increase, a combination of Agile practices allowing organizations to achieve higher levels of CMMI-DEV with a limited process overhead can be very interesting to organizations that aim to keep adaptability. This way, they might strengthen their development processes in order to produce high quality results. This paper presents a gap analysis between the most used Agile practices (Scrum and XP) as well as a mapping proposal, including ad-hoc modifications and other Agile practices, to achieve all CMMI-DEV level 4 and 5 specific goals. To conclude, it drafts relevant conclusions and proposes future lines of researc

    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

    Metrics for Performance Improvement in Organisations Using Scrum, ITIL and CMMI

    Get PDF
    It is very important to understand the metrics that are applied within IT processes in today's industry, why they are important, and in what types of companies they are used. This article presents the results of a systematic literature review of some of the most widely used metrics exposed in the literature, referring to Scrum, ITIL and CMMi practices. The objective is to determine the scientific progress in this field and to identify the candidate metrics that can be used later in a metrics integration model, designed to help monitor IT services to improving the performance of organisations that use Scrum, CMMi and ITIL. The exploratory search found 1,196 articles, of which 198 were reviewed, from which 31 were finally chosen. From these, a total of 297 metrics were identified, of which 112 (38%) are for Scrum, 98 metrics (33%) are for ITIL, and 87 (29%) are for CMMi. Most of these metrics are used in European companies

    Capability Maturity Model Integration (Cmmi) for Small Organizations

    Get PDF
    Software Process Improvement (SPI) is a large area of expertise that deals with software development standard processes and is a progression of proven methods of process improvement from many different methodologies. Personal Software Process (PSP) and Team Software Process (TSP) complement the implementation of Capability Maturity Model Implementation (CMMI) and can be applied gradually from the individual, to the team, and then to the organization. These solutions from Carnegie Melon\u27s Software Engineering Institute (SEI) are leading edge for the field of process improvement. Solutions like this consume many resources, are very complex, require years to implement, and can be costly. The SEI solutions offer an industry standard for SPI. Three case studies were analyzed to provide insight into the benefits of CMMI for small organizations. Decisions that steer these solutions generally involve scheduling, quality, and cost. Depending on the individual needs of an organization, the CMMI technology can fulfill what is required. The example case studies were examined and concluded that given favorable conditions, implementing CMMI is feasible for small organizations
    corecore