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

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

An approach to reconcile the agile and CMMI contexts in product line development

Software product line approaches produce reusable platforms and architectures for products set developed by specific companies. These approaches are strategic in nature requiring coordination, discipline, commonality and communication. The Capability Maturity Model (CMM) contains important guidelines for process improvement, and specifies "what" we must have into account to achieve the disciplined processes (among others things). On the other hand, the agile context is playing an increasingly important role in current software engineering practices, specifying "how" the software practices must be addressed to obtain agile processes. In this paper, we carry out a preliminary analysis for reconciling agility and maturity models in software product line domain, taking advantage of both.Postprint (published version

A DISCUSSION ON ASSURING SOFTWARE QUALITY IN SMALL AND MEDIUM SOFTWARE ENTERPRISES: AN EMPIRICAL INVESTIGATION

Under the studies of general core activities including software inspection, review and testing to achieve quality objectives in small-medium size enterprises (SMEs), the paper presents a contemporary view of such companies against quality measures. The results from a local empirical investigation of quality standards in the Turkish software industry are reported.Around 150 software companies have been approached from which 17 detailed feedback inform that in order to ensure software quality, standards including internationally recognized International Standards Organization (ISO) and Capability Maturity Model Integration (CMMI) are given credit. However the substantial workload and resources required to obtain them are also reported as serious; downscaled frameworks of such large models proposed in the literature are not well known by the SMEs either. The paper also discusses "work around" that bypasses such standards to ease delivery of products while keeping certificates as labels just to acquire new jobs for the business

Cultivating knowledge sharing through the relationship management maturity model

Purpose - The purpose of this paper is to present the development of the relationship management maturity model (RMMM), the output of an initiative aimed at bridging the gap between business units and the IT organisation. It does this through improving and assessing knowledge sharing between business and IT staff in Finco, a large financial services organisation. Design/methodology/approach - The objectives were achieved by undertaking ethnographic research with the relationship managers (RMs) as they carried out their activities, and developing the RMMM by visualizing the development of a community of practice (CoP) between business and IT. Findings - The RMMM demonstrates a learning mechanism to bridge the business/IT gap through an interpretive approach to knowledge sharing by defining knowledge sharing processes between business and IT and defining the tasks of the relationship managers as facilitators of knowledge sharing. Research limitations/implications - More research is necessary to determine whether the RMMM is a useful tool on which Finco can base the development of RM over the next few years. Practical implications - The RMMM acts as a practical knowledge management tool, and will act as a future reference for the RMs as they attempt to further develop the business/IT relationship. Originality/value - The findings provide an initial endorsement of the knowledge sharing perspective to understand the business/IT relationship. Also, the RMMM can be used to identify problematic issues and develop processes to address them

Software process measuring model

U ovom radu opisan je Model mjerenja softverskog procesa (MMSP). MMSP je metoda procjene softverskih procesa, kvantitativnog mjerenja i unapređenja procesa za organizacije koje se bave razvojem softvera (SPO). Metoda je razvijena dijelom na temelju poboljšanja metoda CMM/CMMI, Bootstrap i SPICE, i na standardima ESA PSS05 i ISO 90003. U žarištu MMSP-a je proces razvoja softvera u softverskim poduzećima. Članak objašnjava glavni koncept dobavljanja podataka o softverskim inženjerskim organizacijama i njihovim projektima pomoću temeljito izgrađenog upitnika. MMSP se može interpretirati kao metoda za opisivanje kakav je položaj organizacije i koje se promjene predlažu u slijedećim koracima. Osnovna ideja MMSP-a je utvrditi profil zrelosti procesa SPO-a. Ciljevi MMSP procjene su: a) izmjeriti i razviti profil zrelosti kvalitete procesa prikazom jakih i slabih strana procijenjenog SPŠO-a, b) derivirati korake za unapređenja iz prikazanog profila kvalitete procesa. Prikazan je rezultat procjene obavljene u jedan dan u organizaciji koja se bavi proizvodnjom softvera (SPO X) i Projekta X unutar SPO-a X koji je održan početkom listopada 2010. Rezultati procjene prikazuju ukupne organizacijske i metodološke razine za Projekt X. Organizacija je na razini zrelosti od 2,83. Metodologija je na razini zrelosti od 2,48. Ukupna razina zrelosti za organizaciju SPO X je na razini zrelosti od 2,42, dok je metodologija na razini zrelosti od 2,57. Organizacija članka je sljedeća: nakon uvoda u poglavlju jedan, poglavlje dva objašnjava razloge razvoja sustava MMSP. Poglavlje tri opisuje razvoj MMSP-a. Algoritam razina zrelosti je prikazan u slijedećem poglavlju. Poglavlje pet objašnjava evaluaciju SPO-a, rezultati procjene prikazani su u poglavlju šest. Poglavlje sedam sadrži zaključak, popis literature je u poglavlju osam.In this paper the Software Process Measuring Model (SPMM) is described. SPMM is a method for software process assessment, quantitative measurement and improvement for software producing organizations (SPOs). It has been developed partly based on a renovation of the CMM/CMMI, Bootstrap and SPICE methods, standards ESA PSS 05, and ISO 90003. SPMM focuses on the software development process in software production enterprises. The article explains the central concept of gaining data about software engineering organizations with a thoroughly constructed questionnaire. It gives a ground to measure the quality maturity level of organization and its projects. The SPMM can be interpreted as a method for describing where an organization stands and what changes are to be recommended in the next steps. The main idea of the SPMM is to determine the process maturity profile of an SPO. The goals of a SPMM self-assessment are: a) to measure and develop an SPO maturity quality profile showing strengths and weaknesses of the SPO assessed, b) to derive the steps for improvement from the shown quality profile. The result of one day assessment in software production organization X (SPO X), and Project X within the SPO X which was held at the beginning of October 2010 is presented. The result of the assessment showed the total organization and methodology maturity levels of the Project X. The organization is on maturity level 2,83. The methodology is on maturity level of 2,48. The total maturity level of the organization of SPO X is on maturity level of 2,42, and the methodology is on maturity level of 2,57. The organization of the paper is as follows: after the introduction in section one, section two explains the reasons of the SPMM development. Section three depicts the SPMM development. The maturity level algorithm is explicated in the next section. Section five explains the evaluation of the SPO, the assessment results are in section six. The conclusion is given in section seven, and the list of literature in section eight

Agile Method Tailoring in a CMMI Level 5 Organization

We investigate the use and tailoring of agile methods in a highly disciplined CMMI Level 5 organization. We explore gaps between traditional agile practices and those required for enhanced levels of governance required by CMMI appraisal. We conducted a case study with recorded interviews from practitioners at NIIT Technology Ltd. The interviews were iteratively analysed and coded. Our findings show that agile methods must be supplemented with pre-sprint planning, evidence recording, project metrics, team self-organization, process standardization, and process base-lining to support the CMMI appraisal. There are challenges around Agile compliance with CMMI Level 4 processes and misconceptions about agile methods precluding documentation of the rationale for design decisions. This research contributes data to the tailoring of agile methods in a high-maturity CMMI context and will be useful for agile teams conducting level 5 appraisal

An Initial Maturity Model for Information Governance

This report details the maturity model for information governance which will be used to assess the E-ARK Project use cases. The method that guides the application of this maturity model will then be detailed in deliverable 7.5, A Maturity Model consists of a number of entities, including “maturity levels” (often six) which are, from the lowest to the highest, (0) Non Existent, (1) Initial, (2) Basic, (3) Intermediate, (4) Advanced and (5) Optimizing. Each process can have its own Maturity Model, which expresses quantitatively the maturity level of an organization regarding a certain process. A Maturity Model provides also a way for organizations to see clearly what they must accomplish in order to pass to the next maturity level. The use of maturity models is wide spread and accepted, both in industry and academia. There are numerous maturity models, at least one for each of the most trending topics in such areas as Information Technology or Information Systems. Maturity Models are widely used and accepted because of their simplicity and effectiveness. They can easily help understanding the current level of maturity of a certain aspect in a meaningful way, so that stakeholders can clearly identify strengths and weaknesses requiring improvement, and thus prioritise what must be done in order to reach a higher level. This can be used to show the outcomes that will result from that effort, enabling stakeholders to decide if the outcomes justify the effort