To see the other types of publications on this topic, follow the link: Agile Software Model.
Dissertations / Theses on the topic 'Agile Software Model'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the top 50 dissertations / theses for your research on the topic 'Agile Software Model.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Browse dissertations / theses on a wide variety of disciplines and organise your bibliography correctly.
1
Bodicherla, Saikumar, and Divyani Pamulapati. "Knowledge Management Maturity Model for Agile Software Development." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17659.
Full textAbstract:
Context: Knowledge is the major aspect of an organization which enables the enterprise to be more productive and to deliver the high complexity services. Knowledge management plays a key role in agile software development because it supports cultural infrastructure esteems like collaboration, communication, and knowledge transfer. This research aims to explore how organizations that adopts Agile Software Development (ASD) implement knowledge management utilizing practices that supports the key process areas. Several knowledge management maturity models have been proposed over a decade ago but not all of the models that is specially stated knowledge Management Maturity Model (KMMM) for Agile software development. To fulfil this research gap, we introduce the maturity model which emphasize knowledge management in ASD among the practitioners. This maturity model helps to assess their knowledge management in organization and provides a road map to the organizations for any further improvement required in their processes. Objectives: In this thesis, we investigate the key process areas of knowledge management maturity models that could support agile software development. Through investigation about the key process areas, we found that the organizations should emphasis on key process areas and its practices in order to improve the software process. The objectives of this research include: Explore the key process areas and practices of knowledge management in the knowledge management maturity models. Identify the views of practitioners on knowledge management practices and key process areas for Agile software development. To propose the maturity model for Knowledge management in Agile software development among the practitioner’s opinions. Methods: In this research, we conducted two methods: Systematic mapping and Survey to fulfil our aim and objectives. We conducted Systematic mapping study through the snowballing process to investigate empirical literature about Knowledge management maturity models. To triangulate the systematic mapping results, we conducted a survey. From the survey results, we obtained the responses and were analyzed statistically using descriptive statistics. Results: From Systematic mapping, we identified 18 articles and analyzed 24 practices of Knowledge management maturity models. These practices are indicated in key process areas such as process, people, technology. Through the systematic mapping results, 9 KM practices that were found from KMMM literature were listed in the survey questionnaire and answered by software engineering practitioners. Moreover, 5 other new practices for agile have suggested in the survey that was not found in KMMM literature. To address the systematic mapping and survey results, we propose the maturity model which emphasize knowledge management practices in ASD among the practitioners. Conclusions: This thesis lists the main elements of practices that are utilized by the organization and also show the usage of maturity levels at each practice in detail. Furthermore, this thesis helps the organization's to assess the current levels of maturity that exist to each practice in a real process. Hence, the researchers can utilize the model from this thesis and further they can improve their Km in organizations.
2
Deekonda, Rahul, and Prithvi Raj Sirigudi. "Assessment of Agile Maturity Models : A Survey." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13230.
Full textAbstract:
Context. In recent years Agile has gained lots of importance in the fieldof software development. Many organization and software practitioners hasalready adopted agile practice due to its flexibility in nature. Hence, agiledevelopment methodologies have been replaced to traditional developmentmethods. Agile is a family of several methodologies namely Scrum. eXtremeprogramming (XP) and several others. These several methods areembedded with different set of agile practices for the organizations to adoptand implement for their development process. But there is still a need forempirical research to understand the benefits of implementing the Agilepractices which contributes to the overall success of accomplishment of thesoftware project. Several agile maturity models have been published over adecade but not all of the models have been empirically validated. Hence,additional research in the context of agile maturity is essential and needed. Objectives. This study focus on providing a comprehensive knowledgeon the Agile Maturity Models which help in guiding the organizations regardingthe implementation of Agile practices. There are several maturitymodels published with different set of Agile practices that are recommendedto the industries. The primary aim is to compare the agile maturity maturitymodels and to investigate how the agile practices are implemented inthe industry Later the benefits and limitations faced by the software practitionersdue to implementation of agile practices are identified. Methods. For this particular research an industrial survey was conductedto identify the agile practices that are implemented in the industry. Inaddition, this survey aims at identifying the benefits and limitations of implementingthe agile practices. A literature review is conducted to identifythe order of agile practices recommended from the literature in agile MaturityModels. Results. From the available literature nine Maturity Models have beenextracted with their set of recommended agile practices. Then the resultsfrom the survey and literature are compared and analyzed to see if thereexist any commonalities or differences regarding the implementation of agilepractices in a certain order. From the results of the survey the benefitsand limitations of implementing the Agile practices in a particular order areidentified and reported. Conclusions. The findings from the literature review and the survey resultsin evaluating the agile maturity models regarding the implementationof agile practices.
3
Tkachuk, M. V., and T. F. Abbasov. "An operating model for dynamic requirements management in agile software development." Thesis, NTU "KhPI", 2018. http://repository.kpi.kharkov.ua/handle/KhPI-Press/38080.
Full text
4
D'Angelo, Laura. "Evaluation of code generation in agile software development of embedded systems." Thesis, Uppsala universitet, Avdelningen för datorteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-353798.
Full textAbstract:
Generating code from software models is considered to be a new generation leap within software development methods. The objective of this M.Sc. project is to evaluate how different approaches to modelling and code generation affect embedded systems software development and propose recommendations on how to improve software development. Two product areas at Saab Surveillance EW Systems in Järfälla, Stockholm, are used as study objects. A research overview is made to highlight themes regarding modelling, code generation and software development in general. Based on these, interviews are held with system engineers and software developers at each product area, where they use different modelling and code generation approaches. The two development processes are described thoroughly. Challenges and advantages related to each area’s approach are investigated. Software development within product area A is affected by the product complexity and the larger scale of the development, including projects running over a longer time with more teams involved. Recommendations include enabling code generation by aligning it with other investments on process improvement and limiting the approach to generating some system components. Software developers within product area B can use full code generation, enabled by the limited product complexity. The product area is affected by software standards and external requirements on the process. Recommendations include extending the modelling approach to make it easier to trace functionality from system to software level. Conclusions are that both product areas can apply modelling and code generation to more software development activities to improve their respective development processes.
5
Laanti, M. (Maarit). "Agile Methods in large-scale software development organizations:applicability and model for adoption." Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526200347.
Full textAbstract:
Abstract Agile methods have proven to be beneficial in small organizations, and there has also been growing interest in using these methods in large organizations. This dissertation analyzes what agility and agile development are and creates a framework for using those methods in large organizations. The work starts with a Concept Analysis of Agile Software Development and agile-in-large. The theoretical part also reflects the necessary background of Complex Adaptive Systems, Lean Thinking, and Learning Organizations. Then a model of an Agile Enterprise is defined and a Framework for Organizational Development and putting Agile Methods into use in large software development organizations is presented. Large development organizations consist of many levels. It is not enough to use Agile Methods on a certain level only, e.g., on the lowest level, but all levels need to change and adapt to the new way of working. Failure to do so leads to several unwanted consequences, which are described. One possible large-scale Agile Framework is described and analyzed. The usage of Agile Methods on a large scale is validated by quantitative studies. The level of success of using an Agile Framework on a large scale is dictated by how much the same framework for operation is shared within the organization, as partial transformation leads to confusion. But smaller successes can lead into organizational learning. The framework that is proposed can be used to further enhance agility. In this way large-scale agility can be seen as a never-ending series of systematic improvements of the enterprises’ Agile Aspects<br>Tiivistelmä Tämä väitöskirja tarkastelee suurten organisaatioiden tarpeisiin sopivien ketterien prosessimallien mallinnusta ja käyttöä. Ketterät menetelmät on todettu hyödyllisiksi pienissä ohjelmistoyrityksissä, joten myös isoissa yrityksissä on herännyt kiinnostus ketteriä menetelmiä kohtaan. Työ alkaa ketterien menetelmien käsiteanalyysillä, ja jatkuu määrittelemällä mitä ketteryys laajassa mittakaavassa on. Teoriaosuus käsittelee taustatiedot kompleksisista sopeutuvista järjestelmistä, lean-ajattelusta ja oppivista organisaatioista tarvittavin osin. Tämän jälkeen määritellään ketterän yrityksen käsite ja esitetään malli laajamittaiselle ketteryydelle. Suurissa kehitysorganisaatioissa on monta tasoa. Ei riitä, että ketteriä menetelmiä käytetään vain jollakin (yleensä alimmalla) tasolla, vaan kaikkien organisaation tasojen täytyy sopeutua uuteen toimintatapaan. Mikäli näin ei tapahdu, saattaa tuloksena olla joukko ei-toivottavia seurauksia, jotka on myös kuvattu tässä työssä. Työssä on esitetty ja analysoitu mahdollinen malli suuren yrityksen ketteryyden toteuttamiseksi. Ketterien menetelmien käyttö isossa yrityksessä on validoitu kvantitatiivisin menetelmin. Isoissa yrityksissä ketteristä menetelmistä saatu hyöty on sidottu siihen miten hyvin koko organisaatio pystyy noudattamaan samaa ketterää toiminnan mallia – osittainen toimintatavan muutos johtaa toimintatapojen konflikteihin. Kuitenkin myös osittaiset onnistumiset voivat johtaa organisaation oppimiseen. Esitettyä mallia voidaan käyttää kehitettäessä toimintatapaa entisestään ketterämpään suuntaan. Tällä tavalla suuren organisaation ketteryys voidaan nähdä jatkuvana sarjana systemaattisia toimintatavan parannuksia, joista jokainen johtaa entistä ketterämpään toimintatapaan
6
Cassirer, Albin, and Erik Hane. "Model-Pipe-Hardware: Method for Test Driven Agile Development in Embedded Software." Thesis, KTH, Maskinkonstruktion (Inst.), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-182670.
Full textAbstract:
In this thesis, we present development and evaluation of a new test driven design method for embedded systems software development. The problem of development speed is one of major obstacles for transferring Test Driven Development (TDD) methodologies into the domain of embedded software development. More specically, the TDD cycle is disrupted by time delays due to code uploads and transfer of data between the development "host" system and the "target" embedded platform. Furthermore, the use of "mock objects" (that abstract away hardware dependencies and enable host system testing techniques) is problematic since it creates overhead in terms of development time. The proposed model, Model-Pipe-Hardware (MPH), addresses this problem by introducinga strict set of design rules that enable testing on the "host" without the need of the "mock objects". MPH is based on a layer principle, "trigger-event-loop" and supporting "target" architecture. The layer principle provides isolation between hardware dependent/independent code. The trigger-event-loop is simply a proxy between the layers. Finally, the developed testing fixture enables testing of hardware dependent functions and is independent of the target architecture. The MPH model is presented and qualitatively evaluated through an interview study and an industry seminar at the consulting company Sigma Technology in Stockholm. Furthermore, we implement tools required for MPH and apply the model in a small scale industry development project. We construct a system capable of monitoring and visualisation of status in software development projects. The combined results (from interviews and implementation) suggest that the MPH method has a great potential to decrease development time overheads for TDD in embedded software development. We also identify and present obstacles to adaptation of MPH. In particular, MPH could be problematic to implement in software development involving real-time dependencies, legacy code and a high degree of system complexity. We present mitigations for each one of these issues and suggest directions for further investigations of the obstacles as part of future work.<br>I denna avhandling presenteras utveckling och utvärdering av en ny utvecklingsmetod för mjukvaruutveckling i inbyggda system. Långsam utvecklingshastighet ar ett stort hinder för applicerandet av Test Driven Utveckling (eng. Test-Driven-Development,TDD) inom inbyggda system. Mer specifikt, uppstår flaskhalsar i TDD cykeln på grund av koduppladdningar och dataöverföringar mellan utvecklingsmiljö (host) och plattformen för det inbyggda systemet (target). Vidare är användningen av "mock"-objekt (abstraherar bort hårdvaruberoenden for att möjliggöra tester i hostmiljö) kostsamt då implementatering och design av "mock"-objekten förlänger utvecklingstiden. Den förslagna modellen, Model-Pipe-Hardware (MPH), adresserar detta problem genom att introducera strikta designregler vilket möjliggör tester i hostmiljö utan användning av mocks. MPH bygger på en lagerprincip, en så kallad "trigger-event-loop" och en tillhörande hårdvaruarkitektur. Lagerprincipen möjliggör isolering mellan hårdvaru- beroende/oberoendekod medan trigger-event-loopen fungerar som en proxy mellan lagren. MPH presenteras och utvärderas genom en intervjustudie och ett industriseminarium på konsultbolaget Sigma Technology i Stockholm. Vidare implementeras nödvändig infrastruktur och MPH metoden har applicerarts på ett mindre industriellt utvecklingsprojekt. De kombinerade resultaten från intervjuer, seminarium implementering antyder att MPH har stor potential att öka utvecklingshastighet for TDD i inbyggda system. Vi identierar även möjliga hinder föor applicering av MPH i utveckling av inbyggda system. Mer specifikt kan MPH vara problematisk för inbyggda system som innefattar realtidskrav, så kallad "legacy kod" och för system med hög komplexitet. Vi föreslår möjliga lösningar för dessa problem och hur de bör utredas vidare som en del av framtida arbete.
7
Dreiseitel, Jiří. "Agilní metody vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-264956.
Full textAbstract:
The thesis deals with basic principles of agile software development and describes their advantages compared to the traditional approach. Siemens, s.r.o in Brno uses combination of Scrum and Kanaban as part of organizational processes, therefore the thesis focuses mainly on the method Scrum, Kanban, Scrum-ban and compares these methods with each other. The thesis also analyzes the existing project and results were consulted with the representative of the Siemens company together with the proposals for improvement. JIRA plugin was designed and implemented base on our mutual agreement. This module extends the current tool for analyzing agile projects, this leads to better support of decision making in the context of agile processes. Benefits and further upgrades are consulted at the end of the thesis.
8
Madhira, Phani Srikara Sastry. "Investigating the Applicability of Agile Practices in Software Organizations." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4377.
Full textAbstract:
Agile software development has gained significant importance the recent years. Software practitioners have recognized the importance of agile development due to the benefits offered. Therefore, agile software development has been identified as the replacement to traditional or plan driven style of development. There are different frameworks or methods, which follow agile principles, known as agile methodologies. SCRUM and XP are the most popular and widely used agile methods or framework. There are different types of agile methodologies, each containing a set of practices, which can be adapted and implemented in an organization. However, there is still a need for empirical studies to understand the factors like requirements/modifications, challenges and mitigation strategies/techniques, which can enable successful implementation of agile practices in software organizations. In this study, the primary objective is to provide a comprehensive model or framework to practitioners, which includes the list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing agile, and also pertaining to adoption/implementation of individual agile practices specific to SCRUM and XP. This model also includes the categorization of the requirements/modifications and challenges into different levels of an organization, to which they mostly apply. This conceptual model or framework can aid the practitioners in understanding and implementing agile practices in a better way in their organizations. In this study, an industrial survey is conducted in order to identify the list of important requirements/modifications that are needed to implement agile, challenges faced during implementation, and mitigation strategies/techniques needed to address the challenges. Also, categorization of the identified lists into different levels of the organization is also performed using survey. A systematic literature review is performed in order to identify the primary lists of requirements/modifications, challenges and mitigation strategies/techniques, which are further validated and classified using survey. Also, systematic literature review is used to identify the list of requirements/modifications, challenges and mitigation strategies/techniques that are needed while implementing individual agile practices specific to SCRUM and XP. Based on the systematic literature review, 53 primary studies were identified which are relevant to the research area. Upon analyzing the primary studies, the list of requirements/modifications, challenges and solutions are identified for generic agile adoption/implementation and also pertaining to individual practices specific to SCRUM and XP. Thereupon, an industrial survey is conducted where, identified list of requirements/modifications, challenges and mitigation strategies/techniques are provided to the respondents. Respondents were asked to classify the obtained aspects based on the level of importance. Also, they were asked to categorize the obtained requirements/modifications and challenges into different levels of an organization. The survey has obtained 48 responses from different parts of the world. From the results of survey, requirements/modifications, challenges and mitigation strategies/techniques are classified based on the level of importance. Also, requirements/modifications and challenges are categorized into different levels of an organization. Using the obtained factors, a conceptual model or framework was constructed for practitioners that can enable them to understand and implement agile practices in their organizations in a better way. To conclude this research, a comprehensive model or framework was constructed using the final list of important requirements/modifications, challenges and mitigation strategies/techniques while implementing/adopting agile and also pertaining to the individual agile practices, and also based on the categorization of the requirements and challenges into levels of an organization, where they are applicable. The final list of identified lists of requirements/modifications; challenges and mitigation strategies/techniques pertaining to individual agile practices can help practitioners to understand the implementation criteria of agile practices in software organizations. It was observed from the results of survey that perception of literature and practitioners are different in terms of usage of agile practices, as some practices, which were given high focus in the literature, were not given equal priority by the respondents. Empirical findings also help to identify change in policies and procedures and change to open workspace as most important requirements/modifications, organizational resistance and lack of motivated programmers as most critical challenges and proper training and inclusion of experts as most used mitigation strategies/techniques. Moreover, it was concluded that there is also a need for further full-scale empirical works on identifying the factors that affect adoption of agile. Practitioners can identify the benefits from this research and researchers can extend this work to remaining agile methodologies.<br>Agile systemutveckling har fått stor betydelse de senaste åren. Programvaru utövare har insett vikten av agila utvecklings grund av de förmåner som erbjuds. Därför har agile mjukvaruutveckling identifierats som ersättare till traditionella eller planen driven stil av utveckling. Det finns olika ramar eller metoder, som följer agila principer, så kallade agila metoder. SCRUM och XP är de mest populära och mest använda agila metoder eller ramverk. Det finns olika typer av agila metoder, var och en innehåller en uppsättning metoder, som kan anpassas och genomföras i en organisation. Det finns dock fortfarande ett behov av empiriska studier för att förstå de faktorer som krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som kan göra det möjligt för ett framgångsrikt genomförande av agila metoder i mjukvaruorganisationer. I denna studie, är det primära målet att ge en heltäckande modell eller ramverk för utövare, vilket inkluderar en lista över viktiga krav / modifieringar, utmaningar och begränsningsstrategier / tekniker samtidigt genomföra vig, och även avseende antagande / genomförande av enskilda agila metoder specifika SCRUM och XP. Denna modell innehåller även kategoriseringen av de krav / modifieringar och utmaningar i olika nivåer i en organisation, till vilken de oftast gäller. Denna konceptuella modell eller ramverk kan hjälpa utövarna att förstå och genomföra agila metoder på ett bättre sätt i sina organisationer. I denna studie är en industriell undersökning för att identifiera listan över viktiga krav / ändringar som behövs för att genomföra vig, utmaningar under genomförandet, och begränsnings strategier / tekniker som behövs för att ta itu med utmaningarna. Också, kategorisering av de identifierade listorna i olika nivåer i organisationen är också utföras med undersökningen. En systematisk litteraturöversikt görs för att identifiera de primära listor krav / modifieringar, utmaningar och begränsningsstrategier / tekniker, som är validerade längre och klassificerade med hjälp enkät. Dessutom är systematisk litteraturöversikt används för att identifiera en lista över krav / modifieringar, utmaningar och begränsningsstrategier / tekniker som behövs samtidigt genomföra enskilda agila metoder som är specifika för SCRUM och XP.<br>+918500053444
9
Eshtiagh, Peyman. "An evaluation of test processes in an agile environment." Thesis, KTH, Skolan för teknikvetenskaplig kommunikation och lärande (ECE), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-155399.
Full textAbstract:
The aim of this thesis is to improve the reliability and quality of new requested functionality, and existing modules, at Fortum HR System Solutions. This was conducted through an evaluation of the test processes by implementing principles of Software Testing and Test Management. For the study to successfully improve the testing performed at HR System Solutions, existing test processes were analyzed. The analysis was conducted by evaluating the current test processes using theoretical test evaluation styles called maturity models. The methodology of choice was the Testing Maturity Model (TMM), which was adapted to the nature of HR System Solutions requirements, experience and needs. The evaluation used qualitative methods together with pedagogical principles to conduct interviews and workshops to consolidate the theoretical evaluation. Interviews and workshops were conducted within the team of HR System Solutions, where all members of them team contributed to the thesis at some point. An external interview also took place for comparative study. Results of the evaluation, interviews and workshop were compiled and analyzed accordingly. With the analyzed results in place, flaws in the testing processes were apparent. A generalization of the flaws led to the conclusion in the form of a suggestion. The conclusive suggestion was for Fortum HR System Solutions to establish a test committee/group role within the team. Considering the current economical and organizational situation this job role would be a divided job role appointed to current members of the HR System Solutions team. The research creates a walkthrough on a potential method on understanding inefficiencies within testing processes of a company and providing a cause-based solution.<br>Undersökningen är inriktad på att förbättra tillförlitligheten och kvalitén på ny begärd funktionalitet, och befintliga moduler, på Fortum HR System Solutions. Detta genomfördes genom en utvärdering av testprocesser genom implementation av principer inom Software Testing samt Test Management. För att förbättra testningen som utförs på HR System Solutions var det nödvändigt att analysera de befintliga testprocesserna. Analysen genomfördes genom att utvärdera de nuvarande testprocesserna med hjälp av teoretiska utvärderingsmetoder som kallas Maturity Models. Den valda metoden var Testing Maturity Model (TMM) som tillämpades med avseende på HR System Solutions förutsättningar, erfarenheter och behov. Utvärderingen använder sig av kvalitativa metoder samt pedagogiska principer för att genomföra intervjuer och workshops stärka den teoretiska utvärderingen från TMM. Intervjuer och workshops genomfördes inom HR System Solutions arbetslag, där alla medlemmar bidrog till examensarbetet. Även en extern intervju gjordes i jämförande syfte. Resultatet av utvärderingen sammanställdes och analyserades i enlighet med de förnämnda teoretiska ramvärken. Med hjälp av analyserna visade sig bristerna hos HR System Solutions testprocesser. En generalisering av bristerna gjordes, vilket ledde till slutsatsen i form av ett förslag. Det slutliga förslaget innebar att Fortum HR System Solutions behöver upprätta en testkommitté/grupp inom arbetslaget. Undersökningen visar en potentiell metod för att förstå ineffektiviteten inom testprocesser i ett företag, och tillhandahålla en orsaks-baserad lösning.
10
Naseem, Junaid, and Wasim Tahir. "Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.
Full textAbstract:
Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.
11
Nascimento, Gustavo Vaz. "Um modelo de referência para o desenvolvimento ágil de software." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-07052008-170413/.
Full textAbstract:
A crescente procura por software de qualidade vem causando grande pressão sobre as empresas que trabalham com desenvolvimento de software. As entregas de produtos de software dentro do prazo e custo previstos vêm se tornando, a cada dia, um diferencial importante nesse ramo de atividade. Nesse sentido, as empresas procuram por metodologias que propiciem o desenvolvimento de produtos com qualidade, e que respeitem o custo e prazo previstos. Em resposta a essas necessidades, surgiu uma nova classe de metodologias de desenvolvimento de software, conhecidas como metodologias ágeis. Este trabalho apresenta um estudo realizado sobre as principais características existentes nessa nova classe de metodologias. Uma análise permitiu a identificação de semelhanças e diferenças existentes entre elas, o que possibilitou a criação de um modelo de referência para o desenvolvimento ágil de software. O modelo foi utilizado em uma avaliação de processo baseada no modelo de avaliação da ISO/IEC 15504. A avaliação permitiu a identificação de forças e fraquezas no processo avaliado e possibilitou a definição de ações de melhoria para que o processo avaliado se assemelhasse à um processo de desenvolvimento ágil. Palavra-chave: Metodologia ágil de desenvolvimento. Modelo de referência. Processo de desenvolvimento de software. Avaliação de processo de software<br>The vast demand for software with quality is causing a great pressure on the companies which work with software development. The delivery of software products within the schedule and cost is becoming, every day, an important issue in this area. Therefore, companies are seeking for methodologies to develop products with quality, within the timetable and the cost. Considering these needs, it became a new class of software development methodologies, known as agile methodologies. This research shows a work done upon the main existing characteristics in this new class of methodologies. An analysis allowed the identification of the existing similarities and differences among them, which it made possible to create a new reference model for agile software development. The agile model was used in process assessment based on assessment model from ISO/IEC 15504. The assessment alowed a identification of power and weakness on the process and alowed a definition of improvement action to the process with the intention of to approach the agile development process
12
Karvonen, T. (Teemu). "Continuous software engineering in the development of software-intensive products:towards a reference model for continuous software engineering." Doctoral thesis, Oulun yliopisto, 2017. http://urn.fi/urn:isbn:9789526216560.
Full textAbstract:
Abstract Continuous software engineering (CSE) has instigated academic debate regarding the rapid, parallel cycles of releasing software and customer experimentation. This approach, originating from Web 2.0 and the software-as-a-service domain, is widely recognised among software-intensive companies today. Earlier studies have indicated some challenges in the use of CSE, especially in the context of business-to-business and product-oriented, embedded systems development. Consequently, research must address more explicit definitions and theoretical models for analysing the prerequisites and organisational capabilities related to the use of CSE. This dissertation investigates various approaches to conducting empirical evaluations related to CSE. The study aims to improve existing models of CSE and to empirically validate them in the context of software companies. The study also aims to accumulate knowledge regarding the use of CSE, as well as its impacts. The case study method is applied for the collection and analysis of empirical data. Twenty-seven interviews are conducted at five companies. In addition, a systematic literature review is used to synthesise the empirical research on agile release engineering practices. Design science research is used to portray the model design and the evaluation process of this dissertation. Three approaches for evaluating CSE are constructed: (1) LESAT for software focuses on enterprise transformation using an organisational self-assessment approach, (2) STH+ extends the “Stairway to Heaven” model and evaluates company practices with respect to evolutionary steps towards continuous experimentation-driven development, and (3) CRUSOE defines 7 key areas and 14 diagnostic questions related to the product-intensive software development ecosystem, strategy, architecture, and organisation, as well as their continuous interdependencies. This dissertation states the relevance of CSE in the context of product-intensive software development. However, more adaptations are anticipated in practices that involve business and product development stakeholders, as well as company external stakeholders<br>Tiivistelmä Jatkuva ohjelmistotuotanto on herättänyt keskustelua nopeasta, samanaikaisesta ohjelmistojulkaisemisesta ja asiakaskokeiluista. Toimintatapa on peräisin Web 2.0 ja software-as-a-service yhteydestä, mutta se tunnetaan nykyään yleisesti ohjelmistoja kehittävissä yrityksissä. Aiemmat tutkimukset ovat osoittaneet haasteita jatkuvan ohjelmistotuotannon käytössä. Erityisesti haasteita on havaittu yritykseltä yritykselle liiketoiminnassa ja tuotepainotteisten sulautettujen järjestelmien yhteydessä. Näin ollen on havaittu tarve tutkimuksen avulla kehittää täsmällisempiä määritelmiä ja teoreettisia malleja, joilla voidaan analysoida jatkuvan ohjelmistotuotannon käyttöön liittyviä edellytyksiä ja organisaatioiden kyvykkyyksiä. Tässä väitöskirjassa tutkitaan malleja, joilla voidaan empiirisesti arvioida jatkuvaa ohjelmistotuotantoa. Tutkimuksella pyritään parantamaan nykyisiä malleja ja arvioimaan niiden käyttöä ohjelmistoyrityksissä. Lisäksi tutkimuksella pyritään kasvattamaan tietoa jatkuvasta ohjelmistotuotannosta ja sen vaikutuksista. Tiedon keräämiseen ja analysointiin käytettiin tapaustutkimus menetelmää. Kaksikymmentäseitsemän haastattelua tehtiin viidessä yrityksessä. Lisäksi tehtiin ketterään ohjelmistojulkaisuun keskittyvä systemaattinen kirjallisuuskatsaus. Väitöskirjassa käytetään Design Science Research menetelmää kuvaamaan tutkimuksen eri vaiheita, joissa malleja suunniteltiin ja arvioitiin. Tutkimuksessa rakennettiin kolme tapaa jatkuvan ohjelmistotuotannon arvioimista varten: (1) LESAT for Software keskittyy organisaation muutoskyvykkyyden arviointiin käyttäen itsearviointimenetelmää, (2) STH+, laajentaa ”Stairway to Heaven” mallia ja arvioi yrityksen käytäntöjä eri evoluutioaskelmilla matkalla kohti kokeilupainotteista tuotekehitystä, (3) CRUSOE määrittelee seitsemän pääaluetta ja 14 kysymystä liittyen tuotekehityksen ekosysteemiin, strategiaan, arkkitehtuuriin, organisointiin sekä näiden välisiin jatkuviin riippuvuuksiin. Väitöskirja osoittaa jatkuvan ohjelmistokehityksen olevan merkityksellinen myös tuotepainotteisessa ohjelmistokehityksessä. Nähtävissä kuitenkin on, että useita nykykäytäntöjä on tarvetta muokata. Erityisesti muokkaustarvetta on tuotekehityksen ja liiketoiminnan sidosryhmiin ja yrityksen ulkoisiin sidosryhmiin liittyvissä käytännöissä
13
Rybníček, Drahomír. "Obchodní model pro IT společnost." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2017. http://www.nusl.cz/ntk/nusl-318341.
Full textAbstract:
This thesis is focusing on design of business model for IT company acting in the domain of development and sales of information systems and related services. In the newly emerging business model there is an emphasis on differentiation from competition and to offer such conditions so the uncertainty of customer can be lowered, when the customer feels danger of obtaining inappropriate solution or unsatisfactory cooperation with a supplier. This business model aims to ensure obtaining of new customers.
14
Sikora, Martin. "Analýza a implementační model agilního a projektového řízení v softwarovém vývoji." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2016. http://www.nusl.cz/ntk/nusl-241108.
Full textAbstract:
The diploma thesis deals with an establishment of the agile and project management implementation model in a software development. Thesis analyzes these approaches in a software development team of an international organization and presents a solution of their usages in a process improvement defined by the CMMI model in selected processes areas.
15
Kajan, Miroslav. "Metody a organizace testování software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2015. http://www.nusl.cz/ntk/nusl-235007.
Full textAbstract:
This document's objective is to propose a set of methods for improvement of the organization and methodology of software testing and subsequent application of those in a real environment of the Siemens CZ company. The first part discusses the development models in terms of testing segment and the following section focuses specifically on the methodology of agile testing and development as a whole, including applicable metrics for evaluating various aspects of software exiting the testing phase. The third major section lets the reader get acquainted with the Siemens organization and methods of their software testing and by analyzing real-world project it assesses the strengths and weaknesses of the particular testing process and its management. The practical part of this thesis lies in the design and implementation of a plug-in for the JIRA environment. This tool is able to identify and quantify the long term status of the project phases of agile development and testing in a clear and interactive way, while the outputs are represented by clearly defined problems that can be more easily treated, as one can argue further progress.
16
Ress, Ana Paula Pereira de Moraes. "Um estudo sobre a integração CMMI e desenvolvimento ágil." Universidade de São Paulo, 2013. http://www.teses.usp.br/teses/disponiveis/3/3136/tde-14102014-151014/.
Full textAbstract:
É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração.<br>It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.
17
Matheson, Dan McKay [Verfasser]. "SAMEM: A Methodology for the Elicitation and Specification of Requirements for Agile Model-driven Engineering of Large Software Solutions / Dan McKay Matheson." Aachen : Shaker, 2019. http://d-nb.info/1188552244/34.
Full text
18
Babb, Jeffry. "TOWARDS A REFLECTIVE-AGILE LEARNING MODEL AND METHOD IN THE CASE OF SMALL-SHOP SOFTWARE DEVELOPMENT: EVIDENCE FROM AN ACTION RESEARCH STUDY." VCU Scholars Compass, 2009. http://scholarscompass.vcu.edu/etd/1763.
Full textAbstract:
The ascension and use of agile and lightweight software development methods have challenged extant software design and development paradigms; this is especially notable in the case of small-team and small-shop software development. In this dissertation, a Reflective-Agile Learning Method and Methodology (RALMM) for small-shop software development, is proposed to enhance communication and learning in the use of agile methods. The purpose of the inquiry in this dissertation pertains to: the nature of the professional practice of small team software development; the implications of the epistemology of Reflective Practice has for the professional practice of small-team software development; and whether the introduction of Reflective Practice to an extant agile methodology improves process, productivity and professional confidence for a small development team. This dissertation uses Dialogical Action Research (Mårtensson and Lee 2004), or Dialogical AR, a qualitative and interpretive research approach, to iteratively develop and refine the Reflective-Agile Learning Model and Method (RALMM). The proposed model and method also considers Hazzan and Tomayko’s (2002, 2004, and 2005) synthesis of Schön’s (1983, 1987) Reflective Practice and Extreme Programming (XP). RALMM is shaped by Argyris and Schön’s theories of practice (1974) and Organizational Learning (1978, 1996) and Schön’s ancillary work on generative metaphor (1979) and frames (Schön et al. 1994). The RALMM artifact was developed in a Dialogical AR Partnership using Lee’s (2007) framework for synthesizing design science and action research. The development and use of RALMM facilitated theorizing on the role of Reflective Practice in the successful use of agile methods. To assist in interpretation and analysis, the data collected during Dialogical AR cycles are analyzed using Strauss and Corbin’s (1998) Grounded Theory as a mode of analysis to guide in the coding and analysis of qualitative evidence from the research. As a result of this research, RALMM improved the practitioners’ processes and productivity. Furthermore, RALMM helped to establish, formalize and reinforce a team learning system for the continued development of the practitioners’ professional repertoire. Additionally, the iterative development of RALMM provides a basis for theorizing on Reflective Practice as an epistemology, paradigm, metaphor and frame of reference for the professional practice of small-shop software development.
19
Mazáková, Zuzana. "Využití agilní metodiky při řízení vývoje softwaru." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2018. http://www.nusl.cz/ntk/nusl-378375.
Full textAbstract:
Diplomová práce se zaměřuje na zefektivnění procesu řízení ve vývoji softwaru, a to integrováním agilní metodiky Scrum do projektu. Navrhnuté řešení obsahuje stěžejní principy a součásti metodologie a jejich konkrétní doporučenou aplikaci v projekte ABC v soulade s jeho specifikami.
20
SOARES, Felipe Santana Furtado. "Uma estratégia incremental para implantação de gestão ágil de projeto sem organizações de desenvolvimento de software que buscam aderência ao CMMI." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/18414.
Full textAbstract:
Submitted by Irene Nascimento (irene.kessia@ufpe.br) on 2017-03-14T18:24:41Z
No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
UFPE-Tese-FelipeFurtado-2015.pdf: 5186939 bytes, checksum: 3c19f526ae55d20b293ecbb65967ffa7 (MD5)<br>Made available in DSpace on 2017-03-14T18:24:41Z (GMT). No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
UFPE-Tese-FelipeFurtado-2015.pdf: 5186939 bytes, checksum: 3c19f526ae55d20b293ecbb65967ffa7 (MD5)
Previous issue date: 2015-05<br>A transição dos métodos tradicionais para os métodos ágeis de gerenciamento de projeto e as
mudanças necessárias para a obtenção de seus reais benefícios são difíceis de alcançar. A
mudança afeta não apenas o time envolvido com a gestão e o desenvolvimento de software,
mas também diversas áreas da organização e, principalmente, exige uma mudança cultural.
Aplicar métodos ágeis com aderênciaaos modelos de maturidade, como o Capability Maturity
Model Integration (CMMI) ou Organizational Project Management Maturity Model (OPM3),
tem sido o foco de discussão no meio acadêmico e no ambiente da indústria de software. As
duas abordagens, aparentemente, têm alguns princípios fundamentais e bases diferentes, mas,
por outro lado, adotá-las em conjunto é cada vez mais uma realidade para as organizações que
desejam produzir software com maior qualidade e acelerando o tempo de desenvolvimento.
No entanto, a pressa para chegar a níveis de maturidade, dentro de prazos que são cada vez
mais curtos, pode resultar em programas de melhoria com objetivos únicos de adesão a tais
modelos, e, muitas vezes, reflete na realização de atividades desnecessárias e geração de
documentação excessiva. Neste contexto, os métodos ágeis são mais atraentes, pois são mais
leves e aparentemente oferecem um desenvolvimento mais rápido com um custo mais baixo.
Assim, processos, modelos e frameworks que resultem em maturidade de processos baseados
em princípios ágeis têm sido alvo comum entre as empresas de software. Considerando o alto
índice de falha na adoção de agilidade, este trabalho busca responder como é possível definir
práticas de gestão de projetos aderentes ao CMMI, utilizando uma estratégia ágil em
organizações de desenvolvimento de software de forma gradativa e disciplinada. Neste
cenário, o presente trabalho propõe uma estratégia incremental baseada no modelo de
maturidade CMMI, fazendo uso das melhores práticas da Agile Project Management (APM) e
dos principais Métodos Ágeis: Scrum, Feature Driven Development (FDD), Lean, Kanban,
Crystal, Extreme Programming (XP). O método utilizado para avaliação da pesquisa foi
baseado em dois grupos focais e um survey com grupos de especialistas da academia e da
indústria. Cada grupo com suas especialidades sugeriu mudanças na estratégia ao longo de
sua construção e confirmou a sua completude, clareza, e adequação de uso para a realidade da
indústria, mostrando ser viável a sua utilização para gestão ágil de projetos em conjunto com
o CMMI.<br>The transition from traditional for agile project management methods and the necessary
changes to obtain its real benefits are difficult to achieve. The change affects not only the
team involved with management and software development, but also several organizational
areas and, especially, requires a cultural change. Apply agile methods complying to maturity
models such as Capability Maturity Model Integration (CMMI) or Organizational Project
Management Maturity Model (OPM3), has been the focus of discussion in academic field and
in software industry environment. Both approaches appear to have some fundamental
principles and different bases, but on the other hand, adopt them together is becoming a
reality for organizations that wish to produce software with higher quality and faster
development time. However, the rush to reach maturity levels within shorter time limits, may
result in improvement programs with unique objectives of adherence to these models, and
often reflected on unnecessary activities and excessive documents generation. In this context,
agile methods are more attractive because they are lighter and provide an apparently faster
development at a lower cost. Thus, process, model and frameworks that result in mature
processes based on agile principles have been a common target among software companies.
Considering the high failure rate in the adoption of agility, this work seeks to answer how it is
possible to define project management practices adherent to CMMI using an agile strategy in
software development organizations in a gradual and disciplined manner. In this scenario, this
work proposes an incremental strategy based on the CMMI maturity model, making use of the
best practices of Agile Project Management (APM) and the main agile methods: Scrum,
Feature Driven Development (FDD), Lean, Kanban, Crystal, Extreme Programming (XP).
The method used to evaluate the research was based on two focus groups and a survey with
experts from academy and industry.Each group with its specialties suggested changes in
strategy throughout its construction and confirmed its completeness, clarity, and
appropriateness of use to the reality of the industry, proving to be viable its use for agile
project management in conjunction with CMMI.
21
Wickström, Carina, and Robin Holmquist. "The Solo First Pair Second Programming Model." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-299589.
Full textAbstract:
Software is fundamental to life in modern society. We have come to depend on it for critical aspects such as managing bank transactions and medical records. However, code defects in software is a common issue, and software not working properly has the potential to cause major damage to both humans and the environment. Many attempts have been made in order to improve software development in order to reduce code defects, among other aspects. One such attempt is the invention of the practice pair programming, where two programmers share and work together on a single workstation. The more traditional way of developing software is solo programming, where each developer is assigned an individual workstation. However, the issue with code defects still remains. Hence, there is a need for better methods for reducing software defects. The purpose of this thesis is to create a software development model for reducing software defects. The model suggested in this thesis is a combined practice where coding with solo programming is followed by re-coding with pair programming called Solo First Pair Second Programming (SFPSP). The goal is to help software development teams to develop more reliable software. Our research was qualitative with support from quantitative data. The research included a literature study and an action study. The literature study was done in order to create a first version of SFPSP entirely based on literature, whereas the action study was done in order to evaluate as well as refine SFPSP based on practical experience. The results of this thesis is the practice SFPSP as well as an evaluation of said practice. Our evaluation shows that SFPSP leads to fewer code defects compared to solo programming. However, the cost with regard to development time and effort is significantly higher for SFPSP compared to solo programming. SFPSP is based on both theoretical and practical knowledge, and has therefore a solid foundation to build upon. Our literature study verified that no practice like SFPSP existed before this thesis.<br>Programvara är grundläggande för livet i det moderna samhället. Vi är beroende av det för kritiska aspekter som att hantera banköverföringar och medicinska journaler. Kodfel i programvara är dock ett vanligt problem, och programvara som inte fungerar som den ska kan orsaka stora skador på både människor och miljön. Många försök har gjorts för att förbättra programvaruutveckling med målet att minska bland annat kodfel. Ett sådant försök är uppfinningen av praxisen parprogrammering, där två programmerare delar och arbetar tillsammans på en enda arbetsstation. Det mer traditionella sättet att utveckla programvara är soloprogrammering, där varje utvecklare tilldelas en individuell arbetsstation. Dock kvarstår problemet med kodfel. Därför finns det ett behov av bättre metoder för att minska kodfel. Syftet med denna avhandling är att skapa en programvaruutvecklingsmodell för att minska kodfel. Modellen som föreslås i denna avhandling är en kombinerad praxis där kodning med soloprogrammering följs av omkodning med parprogrammering, kallad Solo First Pair Second Programming (SFPSP). Målet är att hjälpa programvaruutvecklingsteam att utveckla mer pålitlig programvara. Vår forskning var kvalitativ med stöd av kvantitativ data. Forskningen omfattade en litteraturstudie och en aktionsstudie. Litteraturstudien gjordes för att skapa en första version av SFPSP helt baserad på litteraturen, medan aktionsstudien gjordes för att utvärdera och förfina SFPSP baserat på praktisk erfarenhet. Resultaten av denna avhandling är praxisen SFPSP samt en utvärdering av denna praxis. Vår utvärdering visar att SFPSP leder till färre kodfel jämfört med soloprogrammering. Dock visar den att kostnaden med avseende på utvecklingstid och ansträngning är betydligt högre för SFPSP jämfört med soloprogrammering. SFPSP bygger på både teoretisk och praktisk kunskap och har därför en stabil grund att bygga på. Vår litteraturstudie verifierade att det inte fanns någon praxis som SFPSP före denna avhandling.
22
Gudmundsson, Sofia, and Anaïs Lachini. "Designing Business Models of Tomorrow : Exploring the Expansion of Cleantech-as-a-Service through an Agile approach." Thesis, Linnéuniversitetet, Institutionen för marknadsföring (MF), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-104645.
Full textAbstract:
Background: Three mega trends are profoundly changing today’s market dynamics; climate change, digitalization, and globalization. The increasing interconnectivity and omnipresence of digital technologies are blurring the boundaries of the physical and virtual reality, implying a shift in how digital companies create value and internationalize. Also, new policies and higher customer demand in greener and smarter technologies have created new opportunities for value creation to develop cleaner technologies that foster the growth of clean-technology firms. To be competitive and persist in a sustainable and digital economy, firms must be able to cope with changing market conditions. Strategic agility can support to avoid rigidity and benefit from change, which is fostered by strong dynamic capabilities. Knowledge gaps: The study aims to address shortcomings of digital sustainability business models and specifically characterize the emerging sector of sustainable software companies offering Cleantech-as-a-Service applications. The international potential of these ventures recognizes the need to elaborate on internationalization drivers. The globally competitive environment enforces the need to be strategically agile, whereby applying agile principles to an international context can bring a comprehensive view of internationalizing digital sustainability ventures’ critical capabilities and business model characteristics. The study will also assert the role of collaborative ecosystems in an entrepreneurial internationalization. Purpose: This study will explore the emergence of Cleantech-as-a-Service and investigate how these digital entrepreneurs achieve strategic agility in global pivoting and competitive environments. Our exploratory research aims to apply agile principles to entrepreneurial internationalization strategies, where we through six in-depth interviews will discover the role of digital cleantech firms’ dynamic business models, capabilities, and ecosystems when entering a foreign market. Theoretical framework: The conceptual frame of references is based on two major sections where the first considers the context of digital and sustainable firms and exhibits the essences of digital and sustainable business model designs and how to sustain competitiveness through the interrelation of dynamic capabilities and strategic agility. In the second section the study brings forward theory supporting the exploration of an agile internationalization for digital firms, such as virtual markets and ecosystems. The key theoretical forthcomings are summarized into a conceptual framework that combines the role and interplay of entrepreneurs, business models, as well as networks and ecosystems on the basis of strategic agility and dynamic capabilities, that jointly foster an agile and virtual internationalization. Methodology: The interpretive research used an explorative and abductive approach to perform a qualitative multiple case design. The empirical study was based on six Cleantech-as-a-Service companies where in-depth semi-structured interviews were conducted with the informants of significant positions. The thematic and content data analysis supported the identification of common patterns and themes through coding which guided the subsequent analysis chapter. Findings: Our study revealed characteristics and success factors of Cleantech-as-a-Service ventures operating on global volatile markets, which adopt a leagile approach. The findings supported a definition of the concept but also identified the dynamic capabilities and flexible business models leveraged to sustain international competitive agility. The key agile capabilities relate to networking, experimenting, and learning whereas business model characteristics confer resiliency, interdependency, and efficiency.
23
Ruprecht, Marek. "Agilní modelováni při vývoji software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2011. http://www.nusl.cz/ntk/nusl-412841.
Full textAbstract:
The thesis is focused on software development process and its products from initial designs through the way of implementation until final delivery to customer. The thesis brings up some basic facts about software engineering with further detailed description of one of its parts, the modern models of software life cycles with focus on the agile life cycle because of its significant benefits and effective implementation. This model is represented by Agile Model Driven Development which has been submitted not only theoretically but in practice. Finally, there is also a short description of Unified Modeling Language which is used as a modeling language.
24
Řezáč, Jakub. "Zdokonalování procesů vývoje software." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2009. http://www.nusl.cz/ntk/nusl-236682.
Full textAbstract:
This master's thesis is oriented on software development processes improvement techniques. It presents modern approaches of process development and analyses problems of their management and usage in various life cycle phases. In connection with these techniques it brings draft of support tool, which increases automatization of processes development with pertinent cooperation with other tools, as one of presumptions of improvement of their quality.
25
Cintra, Caroline Carbonell. "A implementação de um processo de engenharia de requisitos baseado no Processo Unificado da Rational (RUP) alcançando nível 3 de Maturidade da Integração de Modelos de Capacidade e Maturidade (CMMI) incluindo a utilização de práticas de métodos ágeis." reponame:Biblioteca Digital de Teses e Dissertações da UFRGS, 2006. http://hdl.handle.net/10183/8128.
Full textAbstract:
Este trabalho descreve a definição e institucionalização de um processo de engenharia de requisitos que está em conformidade com as áreas de processo do CMMI (Capability Maturity Model) de Gerência de Requisitos e Desenvolvimento de Requisitos e cujos componentes (atividades, papéis, produtos de trabalho) são baseados em RUP (Rational Unified Process). A principal contribuição deste estudo é a definição de um processo de engenharia de requisitos baseado em abordagens de desenvolvimento diferenciadas, que foi implantado em uma organização específica, com foco em praticidade, eficiência e retorno do investimento. A implantação do processo em projetos reais permitiu sua experimentação, avaliação e refinamento, validando as alternativas de integração utilizadas para empregar as abordagens de desenvolvimento escolhidas. Complementando o processo proposto, como decorrência do foco em eficiência, são consideradas possibilidades de emprego de práticas de métodos ágeis na execução do processo, com o intuito de aumentar a produtividade do mesmo, sustentando sua garantia de qualidade. O processo proposto é descrito, do método de concepção aos passos envolvidos e artefatos gerados em cada atividade. Também são comentadas as etapas e áreas de trabalho envolvidas na institucionalização do trabalho.<br>This research depicts the definition and institutionalization of a requirements engineering process which is in conformance to CMMI (Capability Maturity Model) Requirements Management and Requirements Development process areas. The proposed process components (activities, roles, work products) are based on Rational Unified Process (RUP) process framework. The proposed process main contribution is the definition of a requirements engineering process, leveraging such diverse development approaches, which was implemented in a specific organization, focusing on practicality, efficiency and return on investment. Implementing such process in real projects has promoted its experimentation, evaluation and refinement, validating the integration alternatives used to bring together the chosen development approaches. The possibility of employing agile methods practices through the process execution is discussed, aiming at increasing the process productivity, while assuring product quality. The proposed process details are described, from method conception to each activity steps and generated artifacts. The process institutionalization phases and work areas are also commented.
26
Miko, Jeffrey Allen. "Collaboration Strategies to Reduce Technical Debt." ScholarWorks, 2017. https://scholarworks.waldenu.edu/dissertations/4236.
Full textAbstract:
Inadequate software development collaboration processes can allow technical debt to accumulate increasing future maintenance costs and the chance of system failures. The purpose of this qualitative case study was to explore collaboration strategies software development leaders use to reduce the amount of technical debt created by software developers. The study population was software development leaders experienced with collaboration and technical debt at a large health care provider in the state of California. The data collection process included interviews with 8 software development leaders and reviewing 19 organizational documents relating to software development methods. The extended technology acceptance model was used as the conceptual framework to better understand the social and cognitive influences on the perceived usefulness of collaboration in reducing technical debt. An inductive analysis of the data was used for coding, triangulation, and identifying themes related to the use of collaboration strategies to reduce technical debt. Prominent themes included using collaboration at all stages of development, using continuous verification processes, promoting a participatory culture, and using tools to support distributed teams. The study findings showed an environment that promotes collaboration, a culture that encourages participation, and accessibility to collaborative tools that may reduce technical debt in software projects. The results of this study may contribute to positive social change by demonstrating how individuals with diverse backgrounds and different perspectives can work together to improve critical software that people depend on every day.
27
Ittner, Jan. "Software assisted tailoring of process descriptions." Saarbrücken VDM Verlag Dr. Müller, 2006. http://d-nb.info/987892932/04.
Full text
28
Korraprolu, Srinivasa Abhilash. "Evaluation of the Relevance of Agile Maturity Models in the Industry : A Case Study." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-16788.
Full textAbstract:
Background. Over the years, agile software development has become increasingly popular in the software industry. One of the reasons is that agile development addressed the needs of the organisations better than the traditional models, such as the waterfall model. However, the textbook version of agile development still leaves something to be desired. This could be learnt by observing the implementation of agile methods/frameworks in the industry. The teams often customize agile methods to suit their context-specific needs. When teams in the industry decide to adopt the agile way of working, they are confronted by a choice¾either they have to implement all the agile practices at a time or adopt them over the time. The former choice has shown to come with risks and, therefore, was found that practitioners generally preferred the latter. However, agile practices are not independent, they have dependencies amongst them. A new approach to agile development emerged in the recent years known as Agile Maturity Models (AMMs). AMMs claim to offer a better path to agile adoption. In AMMs, the practices are typically introduced gradually in a particular order. However, these AMMs are multifarious and haven’t been sufficiently evaluated¾especially in the industry practice. Thus, they need to be evaluated in order to understand their relevance in the industry. Objectives. The goal is to evaluate the relevance of AMMs in the industry. By finding relevant AMMs, they could be used to alleviate the formation of agile teams and contribute toward their smoother functioning. By finding those that aren’t, this research could act as a cautionary to those practitioners who could potentially implement these AMMs and risk failure. The objectives are: identifying the agile practice dependencies in the AMMs; finding the agile practice dependencies in an agile team by conducting a case study in the industry; comparing the dependencies from the case study with those in the AMMs.
Methods. The agile maturity models were identified and analysed. A case study was conducted on an agile team to identify the dependencies between the agile practices in the industry practice. Semi-structured interviews were conducted with members of the agile team. Qualitative coding was used to analyse the collected data. The dependencies from the case study were compared with the AMMs to achieve the aim of this research. Results. It was found that dependencies between individual agile practices in the AMMs were almost never possible to be found. However, practices suggested in each maturity levels were derived. Hence, the dependencies were found in the maturity-level level. From the case study, 20 agile practice dependencies were found. 7/8 AMMs were found to be not relevant. 1 AMM couldn’t be evaluated as it heavily relied on the practitioner’s choices. Conclusions. The researchers could use the evaluation method presented in this thesis to conduct more such evaluations. By doing so, the dynamics present in the industry teams could be better understood. On their basis, relevant AMMs could be developed in the future. Such AMMs could help practitioners leverage agile development.
29
Collins, Eliane Figueiredo. "Modelo de automação de testes funcionais para desenvolvimento ágil de software." Universidade Federal do Amazonas, 2013. http://tede.ufam.edu.br/handle/tede/3295.
Full textAbstract:
Made available in DSpace on 2015-04-22T22:00:48Z (GMT). No. of bitstreams: 1
Eliane Figueiredo Collins.pdf: 2314673 bytes, checksum: 8403bd67cffed913ac9029447401f980 (MD5)
Previous issue date: 2013-04-25<br>CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>For some time, the professional software development companies are looking for new technical alternatives in order to optimize their processes, to deliver products to market as soon as possible and to meet customer expectations, increasingly demanding and intolerant of software failures. In this sense, the agile software development is gaining more space and consequently the software testing area which was previously considered a separate phase of development has changed over time to adapt to this new reality. The test automation activity is seen as key of agile development, but many teams still don t know how it should be done, who should take responsibility and run it and the correct procedures for this activity to be successful. Although the literature mentions about the particularities activities and best practices in this scenario, there are few related works and lack of experience reports or case studies that show, in practice, examples of use this from start to finish the automation strategy adopted. This paper aims to contribute to improving the quality of agile processes, and proposes an approach that involves the application of agile manifesto values in the activities of test automation, which can be used regardless of agile methodology adopted. In this study, observations were made on empirical about testing practices in agile projects developed at Nokia Technology Institute (INdT) and an experimental implementation of this approach at the Center for Electronic and Information Technology (CETELI), Federal University of Amazonas (UFAM). Experimental reports are available with different strategies for the automation of software testing and identification of some important issues to deal with difficulties in adapting testers and developers in this new scenario.<br>Há algum tempo as empresas desenvolvedoras de software profissional vêm buscando novas alternativas técnicas com o objetivo de otimizar seus processos, entregar produtos para o mercado o mais cedo possível e ainda atender as expectativas dos clientes cada vez mais exigentes e intolerantes a falhas de software. Com isso, as metodologias ágeis de desenvolvimento de software estão ganhando mais espaço e consequentemente a área de testes de software que antes era considerada uma fase separada do desenvolvimento vem passando por mudanças para se adaptar a esta nova realidade. A atividade de automação de teste passou a ser vista como peça chave para o desenvolvimento ágil, porém muitas equipes ainda não sabem como ela deve ser feita, quem deve assumir a responsabilidade e execução dela e os procedimentos para que essa atividade seja bem sucedida. Embora a literatura mencione particularidades sobre as atividades realizadas e as melhores práticas nesse cenário, são poucos os trabalhos relacionados e há falta de relatos de estudos de caso ou exemplos de utilização que mostrem, na prática, do início ao fim, a estratégia de automação adotada. Este trabalho tem como objetivo contribuir para a melhoria da qualidade dos processos ágeis, propondo uma abordagem que envolve a aplicação de valores presentes no manifesto ágil nas atividades de automação de teste, que podem ser utilizadas independentemente da metodologia ágil adotada.
Nesta pesquisa, foram realizadas observações empíricas sobre as práticas de testes em projetos ágeis desenvolvidos no Instituto Nokia de Tecnologia (INdT) e um experimento de aplicação dessa abordagem no Centro de Tecnologia Eletrônica e da Informação (CETELI), da Universidade Federal do Amazonas (UFAM). São disponibilizados relatos experimentais com diferentes estratégias relativas a automação de teste de software e a identificação de algumas questões importantes para lidar
30
Villena, Moya Agustín Antonio. "Un Modelo Empírico de Enseñanza de las Metodologías Agiles." Tesis, Universidad de Chile, 2008. http://repositorio.uchile.cl/handle/2250/101998.
Full textAbstract:
Las metodologías ágiles de desarrollo de software, y en particular Extreme Programming
(XP), constituyen una de las tendencias de mayor impacto en la industria del desarrollo de
software en la última década, gracias a su enfoque centrado en la generación temprana
de valor y en su acento en el aspecto humano del desarrollo de software. Su adopción sin
embargo ha demostrado ser bastante compleja debido a los cambios de paradigma que
ellas plantean.
Desde los inicios de estas metodologías surgió el interés de incorporar esta nueva
mirada como una forma de enriquecer la formación de los futuros ingenieros de software. En
este trabajo se plantea que un buen aprendizaje de las metodologías ágiles de desarrollo de
software puede ser logrado por los alumnos a través de una experiencia educativa teóricopráctica
basada en la aplicación de dichas metodologías en proyectos reales. Este enfoque
ha sido aplicado desde el año 2002 en el curso CC62V “Taller de metodologías ágiles de
desarrollo de software” delDepartamento de Ciencias de la Computación de la Universidad
de Chile, y en esta investigación se pone a prueba esta hipótesis, a partir del análisis de una
de las instancias del curso realizada entre los meses de agosto y noviembre del año 2005.
Para realizar este análisis se construyó un modelo evaluativo de aprendizaje basado
en cómo las metodologías ágiles, y en particular Extreme Programming (XP), organizan
el entorno de un proyecto de desarrollo de software para mantener la sincronía entre
los cambiantes elementos que allí están en juego. Dichos elementos son el problema de
negocios, la tecnología, la experiencia y destrezas del equipo de desarrollo, y el producto
en desarrollo.
El modelo de evaluación fue aplicado sobre los trabajos generados por los alumnos de
la versión del curso usado como experimento de esta investigación, complementados con
las observaciones realizadas por el profesor en la sala de clases, y otras evidencias tales
como las opiniones de los clientes y una encuesta de evaluación de impacto hecha a los
alumnos aproximadamente 6 meses después de finalizado el curso.
Con respecto al impacto en el aprendizaje de los alumnos, se observó una comprensión
y aplicación generalizada del marco de prácticas de XP, aunque el nivel de logro estuvo
muy relacionado al entorno de trabajo logrado por cada uno de los proyectos realizados. En
particular se encontró que algunos elementos no considerados en la hipótesis original, tales
como la complejidad del problema a resolver y la relación con el cliente, tenían también
un impacto relevante sobre el éxito de los proyectos, y no sólo los aspectos pedagógicos.
Se comprobó la eficacia de este modelo pedagógico que promueve el equilibro entre
teoría y práctica, el ambiente humano de equipo y de colaboración con el cliente y las
destrezas entrenadas. Por su parte, la práctica de XP más destacada por los alumnos es
la “programación en parejas”, que presenta la mejor evaluación durante el curso y es la
más aplicada a posteriori. Otra práctica que causa mucho interés es el “desarrollo guiado
por test”, pero se indican problemas de tiempo y experiencia para poder aplicarla después
del curso.
En lo que se refiere al modelo pedagógico aplicado para que los alumnos conozcan e
internalicen las prácticas de XP, se determina que las claves de su éxito se encuentran en: reproducir de manera fiel el ambiente de aprendizaje colaborativo acelerado que
se genera en la práctica profesional de las metodologías ágiles, y complementar dicho
ambiente con una leve capa de acciones docentes orientadas a reflexionar y retroalimentar
el dominio de la metodología.
31
Sabar, Suneel. "Software Process Improvement and Lifecycle Models in Automotive Industry." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-69640.
Full textAbstract:
The quality of a product depends on the quality of the underlying process is a well known fact. Software development organizations have been struggling to decrease their cost, increase their ROI, reduce time-to-market, and enhance the quality of their products. This all depends upon the improvement in the processes they are following inside their organizations. A number of software process improvement models exist in market, e.g., CMMI, SPICE and Automotive SPICE. But before an organization can improve its development and management processes, it is very important to know whether it is following the right processes. There exist a number of software development process models, mainly categorized into Traditional and Agile, which provide the step-by-step guidance to develop and manage the software projects.The current thesis presents a study of software process improvement models in automotive industry, their weaknesses and strengths and presents a comparison of how do they relate to each other. This thesis also explores some software development models which are more famous in automotive industry, and the applicability of process improvement models in conjunction with the Agile software development models. A case study was performed at an automotive software supplier organization to investigate the experience of combining Agile practices with organization’s company-tailored software development model that was incorporating Automotive SPICE standards.
32
Koutsoumpos, Vasileios, and Iker Marinelarena. "Agile Methodologies and Software Process Improvement Maturity Models, Current State of Practice in Small and Medium Enterprises." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4284.
Full textAbstract:
Abstract—Background: Software Process Improvement (SPI) maturity models have been developed to assist organizations to enhance software quality. Agile methodologies are used to ensure productivity and quality of a software product. Amongst others they are applied in Small and Medium – sized Enterprises (SMEs). However, little is known about the combination of Agile methodologies and SPI maturity models regarding SMEs and the results that could emerge, as all the current SPI models are addressed to larger organizations and all these improvement models are difficult to be used by Small and Medium – sized firms. Combinations of these methodologies could lead to improvement in the quality of the software products, better project management methodologies and organized software development framework. Objectives: The aim of this study is to identify the main Agile methodologies and SPI maturity models applied in SMEs, the combinations of these methodologies, and the results that could emerge. Through these combinations, new software development frameworks are proposed. What is more, the results of this study can be used as a guide with the appropriate combination for each SME, as a better project management methodology or as improvement in the current software engineering practices. Methods: A Systematic Literature Review was conducted, resulting in 71 selected relevant papers ranging from 2001 to 2013. Besides, a survey has been performed from June 2013 to October 2013, including 49 participants. Results: Seven Agile methodologies and six different SPI maturity models were identified and discussed. Furthermore, the combination of eight different Agile methodologies and Software Process Improvement maturity models is presented, and as well as their benefits and drawbacks that could emerge in Small and Medium – sized firms. Conclusion: The majority of the Agile methodologies and SPI maturity models are addressed to large or very large enterprises. Thus, little research has been conducted for SMEs. The combinations of the Agile methodologies and SPI maturity models are usually performed in experimental stages. However, it has been observed that such type of combination could present numerous benefits, which can also be applicable in SMEs as well. The combinations that are most common are the CMMI and XP, CMMI and Scrum, CMMI and Six Sigma, and the PRINCE2 and DSDM.<br>0034-636835645
33
Santos, Eloisa Cristina Silva. "Integração da abordagem Domain-Driven Design e de técnica Behaviour-Driven Development no desenvolvimento de aplicações web." Universidade Federal de São Carlos, 2015. https://repositorio.ufscar.br/handle/ufscar/7588.
Full textAbstract:
Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2016-09-30T12:23:06Z
No. of bitstreams: 1
DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5)<br>Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2016-09-30T17:56:23Z (GMT) No. of bitstreams: 1
DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5)<br>Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2016-09-30T17:56:32Z (GMT) No. of bitstreams: 1
DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5)<br>Made available in DSpace on 2016-09-30T18:05:54Z (GMT). No. of bitstreams: 1
DissECSS.pdf: 2536269 bytes, checksum: a856f5027d19c2aaadf2834a69af7ff4 (MD5)
Previous issue date: 2015-06-01<br>Conselho Nacional de Desenvolvimento Científico e Tecnológico (CNPq)<br>The agile methods of software development have emerged as an alternative to
traditional approaches, to spend less time on documentation and more time with solving
problems interactively and iteratively. In this context, the development approach Domain
Driven Design (DDD) is a way of developing software in which the application design
process is guided by a domain model. In conjunction with the DDD development
approach, the existence of tests during the implementation of an application is required to
ensure quality. Objective: This work aims to study the agile development approach
Domain-Driven Design (DDD) and the software test techniques Test-Driven Development
(TDD) and Behaviour-Driven Development (BDD). A case study was built to exemplify the
integration of each test technique with DDD. The case study was developed with the
support of the Apache Isis framework, from a well-defined domain model. Methodology:
Based on the literature, the concepts of the DDD development approach and of the TDD
and BDD test techniques, that provided the comparison between the techniques, and
later, the implementation to illustrate this research, were extracted. The Apache Isis
framework was used in this work because it allows develop DDD applications quickly.
During the development of the sample system of this work, the possibility of creating an
automatic generator tests and scenarios for BDD was noted. Results: A case study was
created using the concepts of DDD and tests, with TDD and BDD. Furthermore, a
prototype of tests and scenarios generator for software projects that use DDD, through
the Apache Isis framework and tests using BDD, was developed. Conclusions: The
combination of test techniques mentioned with DDD aim to boosting the development of
applications, since DDD is not associate with any test technique. Writing scenarios with
ubiquitous language is a great advantage to integrate DDD and BDD, because it allows a
clear understanding for all involved in the project. Moreover, the creation of automatic
generator speeds up the testing phase, and can detect errors that might go unnoticed or
only be found as the project evolved.<br>Os métodos ágeis de desenvolvimento de software surgiram como uma
alternativa às abordagens tradicionais, com o intuito de despender menos tempo com
documentação e mais com a resolução de problemas de forma interativa e iterativa.
Neste contexto, a abordagem de desenvolvimento Domain-Driven Design (DDD)
representa uma forma de desenvolver software em que o processo de design de uma
aplicação é guiado pelo modelo de domínio. Em conjunto com a abordagem de
desenvolvimento DDD, a existência de testes durante a implementação de uma
aplicação é necessária para garantir a qualidade. Objetivo: Este trabalho teve como
objetivo o estudo da abordagem ágil de desenvolvimento Domain-Driven Design (DDD) e
as técnicas de teste de software Test-Driven Development (TDD) e Behaviour-Driven
Development (BDD). Um estudo de caso foi construído para exemplificar a integração de
cada técnica de teste com o DDD. O estudo de caso foi desenvolvido por meio do
framework Apache Isis, a partir de um modelo de domínio bem definido. Metodologia:
Com base na literatura foram extraídos os conceitos da abordagem de desenvolvimento
DDD e das técnicas de testes TDD e BDD que proporcionaram a comparação entre as
técnicas e posterior implementação para exemplificar a pesquisa. O framework Apache
Isis foi utilizado neste trabalho porque permite desenvolver aplicações com DDD de
forma rápida. No decorrer do desenvolvimento do sistema exemplo deste trabalho,
notou-se a possibilidade da criação de um gerador automático de testes e cenários para
BDD. Resultados: Foi criado um estudo de caso empregando os conceitos de DDD e
testes com o TDD e com o BDD. Além disso, foi desenvolvido um protótipo de gerador
de testes e cenários para projetos de software que empregam DDD, por meio do
framework Apache Isis e testes utilizando BDD. Conclusões: A junção das técnicas de
testes citadas com o DDD visa potencializar o desenvolvimento de aplicações, uma vez
que o DDD não aborda nenhuma técnica de teste. A escrita de cenários em linguagem
ubíqua é um grande diferencial ao integrar DDD e BDD, pois permite um claro
entendimento a todos os envolvidos do projeto. Ademais, a criação do gerador
automático agiliza a fase de testes, sendo possível detectar erros que poderiam não ser
notados ou apenas serem encontrados com a evolução do projeto.
34
Cordeiro, José Henrique Dell'Osso. "Ambidestria em empresas desenvolvedoras de software: barreiras para adoção de metodologias ágeis e seu impacto na escolha do modelo organizacional." Universidade de São Paulo, 2014. http://www.teses.usp.br/teses/disponiveis/3/3136/tde-18032015-153429/.
Full textAbstract:
Organizações desenvolvedoras de software enfrentam hoje em dia o desafio de atuar concomitantemente em projetos que exigem tanto a prática de Metodologias Tradicionais quanto a de Metodologias Ágeis, metodologias de desenvolvimento de software com características opostas e conflitantes. Para atender a essa demanda as empresas têm adotado a Ambidestria Organizacional no desenvolvimento de softwares, criando estruturas organizacionais, processos e equipes capacitadas para atuar com ambas as metodologias de forma simultânea. Vários modelos podem ser adotados para a criação da Ambidestria Organizacional, mas pouco se sabe sobre como cada um deles surge e se desenvolve nas empresas. Nesta pesquisa objetivou-se conhecer um dos aspectos que podem influenciar a seleção do modelo de Ambidestria: as barreiras que uma organização pode enfrentar ao introduzir uma Metodologia Ágil em ambiente que já pratica alguma modalidade de Metodologia Tradicional. Através de dados secundários e do método de Estudo de Casos foi possível evidenciar a influência de algumas dessas barreiras no tipo de ambidestria escolhido pelas empresas, concluindo ainda que os impactos das barreiras de introdução de uma metodologia ágil podem ser muito diferentes quando comparamos sua ocorrência entre empresas desenvolvedoras de software para uso próprio e empresas desenvolvedoras de software sob encomenda, influenciando-as de modo diferente na escolha do modelo para a criação da Ambidestria Organizacional. Os resultados obtidos e as conclusões presentes neste estudo estabelecem, portanto, importante contribuição para pesquisas futuras, evidenciando que estudos sobre a Ambidestria Organizacional no campo do desenvolvimento de software devem ser realizados levando-se em consideração os diferentes perfis de empresa e as relações dessas empresas com seus clientes de projeto.<br>Software development organizations face nowadays challenges in conducting simultaneous projects, applying at the same time both Traditional and Agile Methodologies, software development processes with opposite and conflicting characteristics. In order respond to this challenges this companies adopt Organizational Ambidexterity in software development, creating organizational structures, processes and teams able to deal with both practices simultaneously. Different models exist for creating Organizational Ambidexterity, but there is a lack of knowledge about how each of these models emerge and grow at the companies. In this research we focused in understanding just one of the topics that influences the selection of the ambidexterity model: the barriers companies faces adopting Agile Methodologies on an environment where Traditional Methodologies are in use. Through secondary data analysis and Case Study methodology it was possible to reveal evidences of the influences that some of these barriers puts over the ambidexterity model selection, also concluding that barriers in agile methodologies introduction may be different when comparing their effects over on-demand software development companies and companies which develop software for their own use, influencing both their choices of ambidexterity model in different ways. The results and conclusions we present in this work, bring important contributions for future research, showing that future Organizational Ambidexterity in software development needs to attempt to different companies profile and their relationship with the projects customer.
35
Huo, Ming Computer Science & Engineering Faculty of Engineering UNSW. "A systematic framework of recovering process patterns from project enactment data as inputs to software process improvement." Publisher:University of New South Wales. Computer Science & Engineering, 2009. http://handle.unsw.edu.au/1959.4/43683.
Full textAbstract:
The study of the software development process is a relatively new research area but it is growing rapidly. This development process, also called 'the software life cycle' or 'the software process', is the methodology used throughout the industry for the planning, design, implementation, testing and maintenance that takes place during the creation of a software product. Over the years a variety of different process models have been developed. From the numerous process models now available, project managers need validation of the choice he/she has made for a software development model that he/she believes will provide the best results. Yet the quality software so sought after by software project managers can be enhanced by improving the development process through which it is delivered. Well tested, reliable evidence is needed to assist these project managers in choosing and planning a superior software process as well as for improving the adopted software process. While some guidelines for software process validation and improvement have been provided, such as CMMI, quantitative evidence is, in fact, scarce. The quantitative evidence sometimes may not be able to be obtained from high level processes that refer to a planned process model, such as a waterfall model. Furthermore, there has been little analysis of low level processes. These low level processes refer to the actions of how a development team follow a high level software process model to develop a software product. We describe these low level processes as project enactment. Normally there is a gap between the high level software process and the project enactment. In order to improve this software development process, this gap needs to be identified, measured and analyzed. In this dissertation, we propose an approach that examines the deviation between a planned process model and the project enactment of that plan. We measure the discrepancy from two aspects: consistency and inconsistency. The analytical results of the proposed approach, which include both qualitative and quantitative data, provide powerful and precise evidence for tailoring, planning and selecting any software process model. The entire approach is composed of four major phases: 1) re-presentation of the planned process model, 2) pre-processing the low level process data, 3) process mining, and 4) analysis and comparison of the recovered process model and planned process model. We evaluate the proposed approach in three case studies: a small, a medium, and a large-sized project obtained from an industrial software development organization. The appropriate data on low level processes is collected and our approach is then applied to these projects individually. From each case study we then performed a detailed analysis of the inconsistencies that had surfaced as well as the consistencies between the plan and the enactment models. An analysis of the inconsistencies revealed that several 'agile' practices were introduced during the project's development even though the planned process model was initially based on 'ISO-12207' instead of the 'agile' method. In addition, our analysis identifies the patterns in the process that are frequently repeated. The outcome of the case studies shows that our approach is applicable to a range of software projects. The conclusions derived from these case studies confirmed that our approach could be used to enhance the entire software development process, including tailoring and assessment.
36
Romanha, Silas Dias [UNESP]. "Um modelo de fábrica de software em Instituições de Ensino Superior." Universidade Estadual Paulista (UNESP), 2016. http://hdl.handle.net/11449/144720.
Full textAbstract:
Submitted by Silas Dias Romanha (silas.romanha@outlook.com) on 2016-11-24T13:52:23Z
No. of bitstreams: 1
Silas_Romanha_Final_PósDefesa.pdf: 2308555 bytes, checksum: f4345354ab7a259801798a5686fc5c86 (MD5)<br>Approved for entry into archive by Felipe Augusto Arakaki (arakaki@reitoria.unesp.br) on 2016-11-29T11:59:15Z (GMT) No. of bitstreams: 1
romanha_sd_me_guara.pdf: 2308555 bytes, checksum: f4345354ab7a259801798a5686fc5c86 (MD5)<br>Made available in DSpace on 2016-11-29T11:59:15Z (GMT). No. of bitstreams: 1
romanha_sd_me_guara.pdf: 2308555 bytes, checksum: f4345354ab7a259801798a5686fc5c86 (MD5)
Previous issue date: 2016-05-30<br>Este trabalho aborda os aspectos relacionados à implantação de Fábrica de Software (FS) em Instituições de Ensino Superior (IES) no Brasil e busca identificar fatores que influenciam tais instituições na decisão de adotar o referido modelo, assim como os fatores de risco e dificuldades normalmente encontradas durante o processo. A análise realizada neste estudo permite que IES possam se atentar a aspectos que facilitem a implementação de uma Fábrica de Software em seu ambiente acadêmico. O trabalho utiliza como método a pesquisa de campo, a pesquisa documental e apresenta uma análise dos resultados com as instituições pesquisadas. A partir dos resultados observados nestas IES, é apresentada uma proposta de implementação e gerenciamento de Fábrica de Software Acadêmica (FSA), aprovada e implementada na Associação Educacional Dom Bosco (AEDB), incluindo seus resultados parciais.<br>This paper addresses the issues related to Software Factory deployment (FS) in Higher Education Institutions (HEIs) in Brazil and aims to identify factors that influence such institutions in the decision to adopt that model, as well as the risk factors and difficulties usually during the process. The analysis in this study allows IES can pay attention to aspects that facilitate the implementation of a Software Factory in their academic environment. The work uses as a method of field research, desk research and analyzes the results of the surveyed institutions. The results observed in these HEIs, the study presents a proposal for deployment and management Academic Software Factory (FSA), approved and implemented in Associação Educacional Dom Bosco (AEDB), including its partial results.
37
Mallmann, Paulo Roberto. "Um modelo abstrato de gerência de software para metodologias ágeis." Universidade do Vale do Rio dos Sinos, 2011. http://www.repositorio.jesuita.org.br/handle/UNISINOS/3987.
Full textAbstract:
Submitted by Silvana Teresinha Dornelles Studzinski (sstudzinski) on 2015-06-24T15:07:11Z
No. of bitstreams: 1
PauloRoberoMallmann.pdf: 3006057 bytes, checksum: 27b9834787f2288724786de5609f80fd (MD5)<br>Made available in DSpace on 2015-06-24T15:07:11Z (GMT). No. of bitstreams: 1
PauloRoberoMallmann.pdf: 3006057 bytes, checksum: 27b9834787f2288724786de5609f80fd (MD5)
Previous issue date: 2011<br>CAPES - Coordenação de Aperfeiçoamento de Pessoal de Nível Superior<br>Nos dias atuais uma boa gerência de projetos tem se tornado um fator competitivo no mercado pois influencia diretamente na qualidade do software. Muitas empresas e organizações voltadas para o desenvolvimento de software investem na melhoria de seus processos de desenvolvimento. No entanto, o mercado atual está exigindo destas empresas uma maior rapidez e uma adaptação a ambientes de negócio bastante dinâmicos. Para atender a esta realidade surgiram as metodologias ágeis que dão suporte a esta nova realidade. No entanto, as ferramentas atuais de gerência de projetos mais utilizadas não apresentam uma solução que permite o planejamento integrado de atividades gerenciais e de atividades de desenvolvimento. Esta deficiência de integração pode resultar em distorções no planejamento de projetos ocasionando atrasos na entrega do software. Diante disso, o objetivo deste trabalho foi criar um ambiente de gerência de software para metodologias ágeis que permitisse uma gerência de projetos de software de forma personalizada em ambientes de desenvolvimento que utilizam conceitos e características de metodologias ágeis. Para isso ser possível, foi definido um modelo dinâmico e modular que contempla todos os aspectos relacionados à gerência de projetos e metodologias ágeis que pode ser instanciado gerando modelos concretos específicos para cada projeto. Esta dinamicidade dada ao modelo foi o grande diferencial frente aos outros trabalhos avaliados. Baseado no modelo abstrato proposto foi criado um ambiente de gerência de projetos que explorou todo o seu potencial. Este ambiente é apoiado por um conjunto de agentes de software que mantêm o modelo concreto atualizado. Sobre o modelo concreto, podem ser extraídos relatórios gerenciais e gráficos de gantt dinâmicos que o deixam ainda mais flexível, de forma a dar ao gestor do projeto uma visão macro e precisa do andamento das atividades. Como forma de validar o trabalho proposto, foi realizado um estudo de caso em uma empresa externa. A aplicação desenvolvida foi utilizada durante o desenvolvimento de um projeto real e trouxe como resultado concreto uma maior segurança para a gestão de projetos. Sua utilização permitiu detectar falhas rapidamente dando mais tempo para ajustar os impactos no cronograma, antes feitos somente através de conversas individuais ou reuniões de acompanhamento diretamente com a equipe.<br>Nowadays a good project management has become a competitive factor in the market because it directly influences the quality of software. Many companies and organizations for the development of software invest in improving their development processes. However, the current market is requiring these companies to more quickly and adapt to highly dynamic business environments. To meet this reality emerged agile methodologies that support this new reality. However, current tools in project management more used does not have a solution that enables integrated planning of management activities and development activities. This deficiency of integration can result in distortions in the planning of projects causing delays in delivery of the software. Therefore, the objective was to create an environment management software that allows an agile project management software in a customized way in development environments that use concepts and characteristics of agile methodologies. To make this possible, we defined a modular dynamic model and covers all aspects related to project management and agile methodologies that can be instantiated by generating concrete models for each specific project. This dynamics model was given to the great advantage compared to other studies evaluated. Based on the proposed model was created a project management environment that exploited its full potential. This environment is supported by a set of software agents that maintain the upgraded concrete model. On the concrete model can be extracted and management reports gantt dynamic that makes them even more flexible so as to give the project manager and have a macro view of the progress of activities. In order to validate the proposed work, we performed a case study in a foreign company. The developed application was used during the development of a real project as a concrete result and brought greater security to project management. Its use enabled to detect failures quickly giving more time to adjust to the impacts on schedule, before being made only through individual conversations or meetings to follow up directly with the team.
38
Almeida, Luís Fernando Magnanini de. "Um modelo para apoiar a gestão do conhecimento no gerenciamento ágil de projetos de software." Universidade Federal de São Carlos, 2016. https://repositorio.ufscar.br/handle/ufscar/8657.
Full textAbstract:
Submitted by Alison Vanceto (alison-vanceto@hotmail.com) on 2017-03-21T12:14:55Z
No. of bitstreams: 1
TeseLFMA.pdf: 6039987 bytes, checksum: 0c2336ab8f5bc28819f69b3f22ff44fb (MD5)<br>Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2017-04-20T14:03:16Z (GMT) No. of bitstreams: 1
TeseLFMA.pdf: 6039987 bytes, checksum: 0c2336ab8f5bc28819f69b3f22ff44fb (MD5)<br>Approved for entry into archive by Ronildo Prado (ronisp@ufscar.br) on 2017-04-20T14:03:24Z (GMT) No. of bitstreams: 1
TeseLFMA.pdf: 6039987 bytes, checksum: 0c2336ab8f5bc28819f69b3f22ff44fb (MD5)<br>Made available in DSpace on 2017-04-20T14:08:51Z (GMT). No. of bitstreams: 1
TeseLFMA.pdf: 6039987 bytes, checksum: 0c2336ab8f5bc28819f69b3f22ff44fb (MD5)
Previous issue date: 2016-12-08<br>Não recebi financiamento<br>The Agile Project Management (GAP) emerges as a response to criticisms made to Traditional Project Management Methods for being prescriptive, bureaucratic, and not very
dynamic, thus limited when applied in innovation-intensive and knowledge-intensive
environments. The main differences between those approaches are the self-management
teams, use of the concept of vision rather than scope, iterations, greater customer involvement
and pursuit for simplicity. All have an impact on how Knowledge Management (KM) is
performed, in particular, the prioritization of the use of tacit rather than explicit knowledge.
Several authors approach the intercession between agile project management and knowledge management theories, however, they made little progress in their proposals for management models. Through systematic theoretical reviews and case studies, we advance in this aspect, proposing a Conceptual Model for Knowledge Management in Agile Project Management. The main peculiarities are: consider both intra and interproject knowledge; consider GAP differentials; focus on the project team; use GAP rituals to potentiate the KM; and the applicability to any agile method.<br>O Gerenciamento Ágil de Projetos (GAP) surge como resposta às críticas aos métodos
tradicionais de gerenciamento de projetos quanto a serem prescritivos, engessados e pouco
dinâmicos, desse modo, limitados em ambientes de inovação e intensivos em conhecimento.
As principais diferenças entre as abordagens são a autogestão, uso do conceito de visão no
lugar de escopo, as iterações, o maior envolvimento do cliente e busca por simplicidade e redução da documentação. Todas têm impacto na forma como a gestão do conhecimento (GC)
é realizada, em particular, a priorização do uso do conhecimento tácito ao invés do explícito.
Diversos autores abordam a interseção entre as teorias de gerenciamento ágil de projetos e
gestão do conhecimento, no entanto, avançam pouco em propostas de modelos de gestão.
Esse trabalho, por meio de revisões teóricas sistemáticas e estudos de casos, contribui nesse
aspecto, propondo um Modelo para apoiar a Gestão do Conhecimento no Gerenciamento Ágil
de Projetos. Como suas principais particularidades estão: considerar tanto o conhecimento intra como interprojetos; contemplar os diferenciais do GAP; ter como foco a equipe de projetos; utilizar os rituais do GAP em favor da GC; além de poder ser aplicado a qualquer método ágil.
39
Franco, Eduardo Ferreira. "Um modelo de gerenciamento de projetos baseado nas metodologias ágeis de desenvolvimento de software e nos princípios da produção enxuta." Universidade de São Paulo, 2007. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-09012008-155823/.
Full textAbstract:
Procurando obter ganhos sustentáveis de produtividade e qualidade no desenvolvimento de software, diversos modelos, formas de organização do trabalho e abordagens inovadoras foram desenvolvidos para auxiliar os gerentes de projeto. O presente trabalho propõe um modelo de gerenciamento de projetos, baseado nas metodologias ágeis de desenvolvimento de software (Extreme Programming e o Scrum), e nos princípios e valores do pensamento enxuto, originado na manufatura automobilística japonesa. Após a proposição do modelo, ele é aplicado em um estudo de caso, avaliando os resultados obtidos na combinação entre as metodologias ágeis e nos princípios e valores da produção enxuta. Em seguida, este modelo é analisado qualitativamente com o intuito de determinar suas vantagens de utilização e seu escopo de aplicação. Para tanto, recorreu-se a uma avaliação do modelo proposto e o tradicional modelo cascata, ainda amplamente adotado no setor de software, e mapeando como este modelo contorna os problemas apontados na literatura, advindos da utilização do modelo cascata.<br>Looking for sustainable gains in productivity and quality in the development of software, several models, forms of work organization and innovative approaches were developed to support software development managers. The present work proposes a model of project management, based on agile software development methodologies (Extreme Programming and Scrum) and on lean principles and values borrowed from the Japanese automobile manufacturing. After describing the proposed model, it is applied in a case study, describing the results of combining the agile software development methodologies with the lean production principles and values. After this, the model is qualitatively analyzed to determine its advantages and its scope of application. For this, the proposed model is evaluated with the traditional waterfall model - until now widely adopted in the software industry - and mapping how it addresses problems, cited in the literature, derived from the use of the waterfall model.
40
Redfearn, Brady Edwin. "User Experience Engineering Adoption and Practice: A Longitudinal Case Study." BYU ScholarsArchive, 2013. https://scholarsarchive.byu.edu/etd/3762.
Full textAbstract:
User Experience Engineering (UxE) incorporates subject areas like usability, HCI, interaction experience, interaction design, "human factors", ergonomics", cognitive psychology", behavioral psychology and psychometrics", systems engineering", [and] "computer science," (Hartson, 1998). It has been suggested that UxE will be the main success factor in organizations as we enter the "loyalty decade" of software development, where the repeat usage of a product by a single customer will be the metric of product success (Alghamdi, 2010; Law & van Schaik, 2010, p. 313; Nielsen, 2008; Van Schaik & Ling, 2011). What is relatively unknown in the current academic literature is whether existing UxE methodologies are effective or not when placed in a longitudinal research context (Law & van Schaik, 2010). There is room for the exploration of the effects of long-term UxE practices in a real-world case study scenario. The problem, addressed in this study, is that a lack of the application of UxE-related processes and practices with an industrial partner had resulted in customer dissatisfaction and a loss of market share. A three-year case study was performed during which 10 UxE-related metrics were gathered and analyzed to measure the improvements in the design of the customer's experience that long-term UxE practices could bring to a small corporate enterprise. The changes that occurred from the corporate and customer's point of view were analyzed as the customer's experience evolved throughout this long-term UxE study. Finally, an analysis of the problems and issues that arose in the implementation of UxE principles during the application of long-term UxE processes was performed. First-hand training between the research team and company employees proved essential to the success of this project. Although a long-term UxE process was difficult to implement within the existing development practices of the industrial partner, a dramatic increase in customer satisfaction and customer engagement with the company system was found. UxE processes led to increased sales rates and decreased development costs in the long-term. All 10 metrics gathered throughout this study showed measurable improvements after long-term UxE processes and practices were adopted by the industrial partner.
41
FREIRE, Arthur Silva. "Modelo de redes bayesianas para melhoria do trabalho em equipe em projetos ágeis de desenvolvimento de software." Universidade Federal de Campina Grande, 2016. http://dspace.sti.ufcg.edu.br:8080/jspui/handle/riufcg/766.
Full textAbstract:
Submitted by Maria Medeiros (maria.dilva1@ufcg.edu.br) on 2018-05-22T12:37:25Z
No. of bitstreams: 1
ARTHUR SILVA FREIRE -DISSERTAÇÃO (PPGCC) 2016.pdf: 2232664 bytes, checksum: 7d856251235ae5bacc2b971e556d50e3 (MD5)<br>Made available in DSpace on 2018-05-22T12:37:25Z (GMT). No. of bitstreams: 1
ARTHUR SILVA FREIRE -DISSERTAÇÃO (PPGCC) 2016.pdf: 2232664 bytes, checksum: 7d856251235ae5bacc2b971e556d50e3 (MD5)
Previous issue date: 2016<br>Capes<br>A utilização de métodos ágeis requer que os indivíduos e as interações entre eles sejam considerados mais importantes que processos e ferramentas. Além disso, equipes ágeis precisam ser auto-organizáveis para garantir rápida agregação de valor e responsividade à mudança. Para isso, é necessário que todos os membros da equipe colaborem entre si e entendam o conceito de responsabilidade e comprometimento por parte de todos. Na literatura, é destacado o impacto positivo que fatores relacionados ao Trabalho em Equipe têm sobre o sucesso de projetos geridos com métodos ágeis. Em alguns trabalhos, ferramentas para avaliar e identificar oportunidades de melhoria do Trabalho em Equipe são apresentadas. Entretanto, no contexto em que se insere este trabalho, elas apresentam limitações, pois não focam em projetos ágeis, dependem apenas de avaliação subjetiva, ou não levam em consideração fatores-chave essenciais do ponto de vista da qualidade do Trabalho em Equipe. Portanto, neste trabalho, é apresentado um modelo de Redes Bayesianas para avaliar e identificar oportunidades de melhoria do Trabalho em Equipe em projetos de software geridos com métodos ágeis. A motivação para utilizar Redes Bayesianas advém da sua adequação para modelar incertezas em um determinado domínio, além da facilidade para modelar e quantificar os relacionamentos entre os fatores-chave que influenciam a qualidade do Trabalho em Equipe. Além do modelo, também é apresentado um procedimento para auxiliar na sua utilização. O modelo e o procedimento foram avaliados em um estudo de caso com três equipes de desenvolvimento de software. De acordo com os resultados do estudo de caso, foi possível concluir que o modelo mensura a qualidade do Trabalho em Equipe precisamente, ajudando na identificação de oportunidades de melhoria desse fator, e o custo-benefício de sua utilização como procedimento proposto é positivo.<br>Agile methods consider individuals and interactions more important than processes and tools. In addition, agile teams are required to be self-organized to ensure rapid aggregation of value and responsiveness to change. Thereby, it is necessary that team members collaborate to embrace the concept of whole-team responsibility and commitment. In the literature, it is shown that teamwork factors are critical to achieve success in agile projects. Some researchers have proposed tools for assessing and improving teamwork quality. However, in the context of agile software development, these tools are limited because they don’t focus on agile projects, depend on subjective assessment, or don’t include important teamwork quality key factors. Therefore, we present a Bayesian Network model to assess and improve agile teams’ teamwork quality. The motivation to use Bayesian Networks comes from its suitability for modeling uncertainties in a given domain, in addition to the easiness to model and quantify the relationships between the teamwork quality key factors. Besides the model, a procedure for using the model is also presented. Both model and procedure were evaluated in a case study with three units of analysis (i.e., agile software development teams). According to the case study results, the model measures the teamwork quality precisely, assisting on the identification of improvement opportunities for this factor, and the cost-benefit for using it with the presented procedure is positive.
42
ALMEIDA, NETO Humberto Rocha de. "Um modelo de maturidade para governança ágil em tecnologia da informação e comunicação." Universidade Federal de Pernambuco, 2015. https://repositorio.ufpe.br/handle/123456789/17340.
Full textAbstract:
Submitted by Irene Nascimento (irene.kessia@ufpe.br) on 2016-07-12T19:02:01Z
No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Tese Humberto Rocha - M3 - CORRIGIDA - 27.01.22016 - FINAL - SEM ASSINATURAS.pdf: 7669370 bytes, checksum: b59a4824a693e49ccfb1316ab17c75ba (MD5)<br>Made available in DSpace on 2016-07-12T19:02:02Z (GMT). No. of bitstreams: 2
license_rdf: 1232 bytes, checksum: 66e71c371cc565284e70f40736c94386 (MD5)
Tese Humberto Rocha - M3 - CORRIGIDA - 27.01.22016 - FINAL - SEM ASSINATURAS.pdf: 7669370 bytes, checksum: b59a4824a693e49ccfb1316ab17c75ba (MD5)
Previous issue date: 2015-07-15<br>A Governança Ágil em Tecnologia da Informação e Comunicação (TIC) é uma área em ascensão que vem sendo sugerida como uma proposta inovadora pautada nos princípios e valores do Manifesto para Desenvolvimento Ágil de Software. O uso de tais princípios e valores tem como principal objetivo a minimização da burocracia na Governança convencional. Alguns autores têm apontado que a maioria das iniciativas para Governança são burocráticas e que a adoção de abordagens mais ágeis ainda é considerada uma tarefa desafiadora. Isto se dá principalmente devido a multidisciplinaridade e relativa incipiência da área. Se por um lado há um conjunto bem estabelecido de princípios e valores ágeis em domínios subjacentes à Governança Ágil em TIC (a exemplo de Desenvolvimento de Software), por outro lado, alguns de seus domínios ainda requerem evolução (a exemplo de Gerenciamento de Serviços, Operações, Infraestrutura, entre outras). Diante deste contexto, esta tese de doutorado propõe um modelo de maturidade denominado MAnGve Maturity Model (M3). O M3 apoia a evolução sistemática e gradual de maturidade em Governança Ágil em TIC. Para tal, o modelo de maturidade proposto estrutura seu conhecimento por meio de cinco níveis de maturidade. Estes níveis foram construídos a partir de um amplo estudo de base teórica (uma revisão ad hoc e uma revisão sistemática da literatura) envolvendo principalmente as áreas de: Agilidade no desenvolvimento de software; Governança em TIC; e modelos de maturidade e capacidade. Por fim, o M3 foi submetido a avaliações por meio de métodos científicos (dois surveys e um focus group) que nortearam melhorias ao modelo proposto. Os resultados destas avaliações apontam o M3 como uma iniciativa relevante e inovadora para este recente campo de pesquisa<br>Agile Governance in Information and Communication Technology (ICT) is an area on the rise that has been suggested as an innovative proposal based on the principles and values of the Manifesto for Agile Software Development. The use of these principles and values aims to minimize bureaucracy in conventional Governance. Some authors have pointed out that most initiatives for Governance are bureaucratic and that adopting more agile approaches is still considered a challenging task. This is mainly due to multidisciplinary and relative incipiency of the area. On the one hand there is a well-established set of agile principles and values in domains behind the Agile Governance in ICT (for example, Software Development), on the other hand, some of its domains still require evolution (like Service Management, Operations Infrastructure, etc.). Given this context, this doctoral thesis proposes a maturity model called MAnGve Maturity Model (M3). The M3 supports the systematic and gradual evolution of maturity in Agile Governance in ICT. To this end, the proposed maturity model structure their knowledge through five maturity levels. These levels were constructed from a large study of theoretical basis (ad hoc review and systematic literature review) mainly involving areas: Agile software development; Governance in ICT; and capability maturity models. Finally, M3 was subjected to evaluations by scientific methods (surveys and focus groups) that guided the improvements in proposed model. Their results indicate the M3 as an important and innovative initiative for this recent field of research.
43
Garcia, Fernando Andre Zemuner. "Liderança e desempenho da equipe de desenvolvimento de software: influência do tipo de gestão de projetos." Universidade Nove de Julho, 2017. http://bibliotecatede.uninove.br/handle/tede/1696.
Full textAbstract:
Submitted by Nadir Basilio (nadirsb@uninove.br) on 2017-08-04T16:01:17Z
No. of bitstreams: 1
Fernando Andre Zemuner Garcia.pdf: 3727885 bytes, checksum: 69021978691074b2fb37201b781421e7 (MD5)<br>Made available in DSpace on 2017-08-04T16:01:17Z (GMT). No. of bitstreams: 1
Fernando Andre Zemuner Garcia.pdf: 3727885 bytes, checksum: 69021978691074b2fb37201b781421e7 (MD5)
Previous issue date: 2017-04-28<br>The team leadership is a topic that have been studied in the last 70 years by several authors, to understand their challenges and exploit the opportunities of the same within organizations and more recently within the design environment. The team leadership has changed considerably over the years because of changes in the culture and how businesses and designs come dealing with their employees and subordinates. Because it is an important factor for the team’s performance the leaders are changing the forma of lead, so that impose the wills and simply ordering already no longer part of the current management methods, having to be a shared leadership or based on exchanges so that the led can follow their leader. With the transformation of companies, many have adopted the Project management to develop their products or internal systems, making the leader Always seek greater adaptability to lead and generate the success or profit expected for companies. This dissertation seeks to identify the influence of the type of leadership in performance of the project team as the methods applied in the management of software development projects. The study was conducted via an online electronic questionnaire distributed to team leaders or projects members who have participated in software developments projects. After analyzing the data collected, it was identified that the project management method does not affect the existing relationship between the types of leadership studied and the performance of the team. Another important factor derived from the analysis is that transactional and transformational leadership are positively related to team performance, despite the weak relationship existing for transactional leadership, while empowerment leadership is strongly related to team performance, but in a negative way. The derivation of the analyzes is that companies working with software development projects must invest in leadership development as a measure to increase team performance, especially the transformational leaders, a style that presented the highest positive relation to team performance Among the three leaderships studied, regardless of the method of project management used.<br>A liderança de equipes é um tema que vêm sendo estudado nos últimos 70 anos por diversos autores, com a finalidade de entender seus desafios e explorar as oportunidades da mesma dentro das organizações e mais recentemente dentro do ambiente de projetos. A liderança de equipes sofreu grandes transformações ao longo dos anos devido a modificação da cultura e da forma como as empresas vêm lidando com os seus empregados e subordinados. Por se tratar de um fator importante para a performance da equipe, os líderes vêm alterando a forma de liderar, impor as vontades e simplesmente ordenar já não fazem mais parte dos métodos de gerenciamento atuais, tendo que haver uma liderança compartilhada ou baseada em trocas para que os liderados possam seguir o seu líder. Com a transformação das empresas, muitas adotaram o gerenciamento de projetos como forma de desenvolver seus produtos ou sistemas internos, fazendo com que o líder busque sempre uma maior adaptabilidade para liderar e gerar o sucesso ou lucro esperado para as empresas. Esta dissertação buscou identificar a influência do tipo de liderança na performance da equipe de projetos, conforme os métodos aplicados na gestão de projetos de desenvolvimento de software. O estudo foi realizado via questionário eletrônico distribuído de forma on-line para líderes de equipes ou membros de projetos que participaram de projetos de desenvolvimento de software. Após as análises dos dados coletados, foi identificado que o método de gestão de projetos não afeta a relação existente entre os tipos de liderança estudados e a performance da equipe. Outro fator importante derivado das análises é que as lideranças transacional e transformacional se relacionam de forma positiva com a performance da equipe, apesar da fraca relação existente para a liderança transacional, enquanto que a liderança empoderamento se relaciona de forma forte com a performance da equipe, porém de forma negativa. A derivação das análises é que as empresas que trabalham com projetos de desenvolvimento de software devem investir no desenvolvimento da liderança como medida para incrementar o desempenho da equipe, principalmente os líderes transformacionais, estilo que apresentou a maior relação positiva com a performance de equipe dentre as três lideranças estudadas, independentemente do método de gerenciamento de projetos utilizado.
44
Cosic, Admir, and Michel Antonio. "Processförbättring med hjälp av TMMi-Modellen : Utvärdering av en testprocess på ett medelstort företag." Thesis, Linnéuniversitetet, Institutionen för datavetenskap, fysik och matematik, DFM, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-22385.
Full textAbstract:
Storleken och komplexiteten på dagens system och applikationer ökar. Detta leder till att kraven på system och applikationer ökar också eftersom kunderna kräver av dagens system full funktionalitet inom olika typer av distribuerade miljöer. Kunder är inte bara intresserade av funktionerna i systemen och applikationerna, de förväntar sig också att systemet skall vara av god kvalitet. Av dessa skäl är det mycket viktigt att testa system och applikationer för att säkerställa att de uppfyller kundernas förväntningar. Däremot är det inte bara själva mjukvarans kvalitets frågor som organisationer behöver ha i åtanke, en lika viktig del är själva testprocessens kvalitet. För att öka testprocessens kvalitet krävs det en utvärdering av processen. Utvärderingen identifierar processens styrkor, svagheter och möjligheter. I detta examensarbete har vi utvärderat tesprocessen på ett utvecklingsföretag. Utvärderingen har baserats på anvisningar och rekommendationer från TMMi-modellen, Test Maturity Model Integrated. Vi hade som mål att lyfta fram förbättringsförslag till företagets testprocess. Efter utvärderingen kom vi fram till vilken mognadsnivå verksamheten utifrån TMMi-modellen samt en mängd förbättringsförslag för att höja mognadsnivån på testprocessen.
45
Lima, Erica Esmeraldo Figueiredo. "Agile development model for certifiable medical device software." Master's thesis, 2020. https://hdl.handle.net/10216/129850.
Full textAbstract:
Este estudo tem como objetivo ilustrar como está o estado atual quando o assunto é software de dispositivo médico utilizando agile. Apresenta as necessidades dos regulamentos e padrões para ser um software de dispositivo médico certificável e como essa é a maneira mais segura e de qualidade de fazê-lo.
O problema que muitas empresas se sentem obrigadas a usar a cachoeira ainda quando é um projeto muito complexo ou tem muitas regulamentações como única forma de construir software. A área médica não é diferente; é um desafio ser ágil e ainda cumprir todos os regulamentos e padrões.
Este artigo irá ilustrar alguns trabalhos que outros já fizeram utilizando agile e tentar encontrar a melhor forma de proceder por validação, através de um caso acadêmico e entrevistas e finalmente contribuir com uma proposta de processo final.
Keywords: Desenvolvimento Ágil, Metodologias Ágeis, Dispositivos médicos, Scrum, Processo, Regulamentação, Processos do ciclo de vida de software, Gerenciamento de riscos, Melhoria de processos de software (SPI), FDA, Indústria de dispositivos médicos.<br>This study aims to illustrate how is the current state when the subject is medical device software using agile. Introduces the needs of the regulations and the standards to be a certifiable medical device software and how this is the safer and quality way to do it.
The problem that many companies feel obligated to use the waterfall still when it is a project too complex or have many regulations as the only way to build software. The medical area is not different; it is challenging to put agile and still comply with all regulations and standards.
This paper will illustrate some works that other papers have already done using agile and try to find the best way to proceed by validation, through one academic case and interviews and finally contribute with a final proposed process.
Keywords: Agile development, Agile methodologies, Medical device, Scrum, Process, Regulation, Software life cycle processes, Risk Management, Software Process Improvement (SPI), FDA, Medical device industry.
46
Lima, Erica Esmeraldo Figueiredo. "Agile development model for certifiable medical device software." Dissertação, 2020. https://hdl.handle.net/10216/129850.
Full textAbstract:
Este estudo tem como objetivo ilustrar como está o estado atual quando o assunto é software de dispositivo médico utilizando agile. Apresenta as necessidades dos regulamentos e padrões para ser um software de dispositivo médico certificável e como essa é a maneira mais segura e de qualidade de fazê-lo.
O problema que muitas empresas se sentem obrigadas a usar a cachoeira ainda quando é um projeto muito complexo ou tem muitas regulamentações como única forma de construir software. A área médica não é diferente; é um desafio ser ágil e ainda cumprir todos os regulamentos e padrões.
Este artigo irá ilustrar alguns trabalhos que outros já fizeram utilizando agile e tentar encontrar a melhor forma de proceder por validação, através de um caso acadêmico e entrevistas e finalmente contribuir com uma proposta de processo final.
Keywords: Desenvolvimento Ágil, Metodologias Ágeis, Dispositivos médicos, Scrum, Processo, Regulamentação, Processos do ciclo de vida de software, Gerenciamento de riscos, Melhoria de processos de software (SPI), FDA, Indústria de dispositivos médicos.<br>This study aims to illustrate how is the current state when the subject is medical device software using agile. Introduces the needs of the regulations and the standards to be a certifiable medical device software and how this is the safer and quality way to do it.
The problem that many companies feel obligated to use the waterfall still when it is a project too complex or have many regulations as the only way to build software. The medical area is not different; it is challenging to put agile and still comply with all regulations and standards.
This paper will illustrate some works that other papers have already done using agile and try to find the best way to proceed by validation, through one academic case and interviews and finally contribute with a final proposed process.
Keywords: Agile development, Agile methodologies, Medical device, Scrum, Process, Regulation, Software life cycle processes, Risk Management, Software Process Improvement (SPI), FDA, Medical device industry.
47
Chen, Chia-Wen, and 陳嘉雯. "Building a CMMI-based Agile Software Development Process Model for Small and Medium Software Organizations." Thesis, 2004. http://ndltd.ncl.edu.tw/handle/10892612925872118359.
Full textAbstract:
碩士<br>中國文化大學<br>資訊管理研究所碩士在職專班<br>92<br>Many software organizations often encounter some common problems, such as un-clear or changing customers’ demands, delay of project schedule, runaway costs, diffi-culties in using, maintaining, or expanding software, and other uncertainties. Many tries have been devoted to resolve these problems through technical or management meth-ods.
The purpose of this research is to build a CMMI-based Agile Software Develop-ment Process Model in the manner with lower cost, less span of time and more flexibil-ity that fit well into Taiwan’s software industrial environment. Through adaptive method is able to justify the degree of essentials of each practice deciding if it is really essential or not.
The main principle of Agile Software Development Methods, earmark: “quick re-sponse to the changing requirements within limited time.” and adopt the method to ease off the cost of implementing CMMI.
The model, will serve as a reference for those organizations which want to improve their work performance or pursue improvement of the software process. By using this model, they can improve operation process, enhance quality of products, and further in-crease their international competitive competencies.
In addition, this research improves the result of the study of Chia-Lin Tsai in 2003, making outputs of the expert system more completeness.
48
Ferreira, Natasha Nicolette Vito. "Enhancing the throughput of software development projects using a model that improves the process of release management." Thesis, 2014. http://hdl.handle.net/10210/11341.
Full textAbstract:
M.Sc. (Computer Science)<br>The process that involves creating and altering software systems can be defined as the software development lifecycle. People often use methodologies and methods in order to develop these systems with success factors such as people, processes and technology. The lifecycle is comprised of the following stages: • Planning • Requirements definition • Design • Development • Integration and testing • Installation • Acceptance. The underlying issue in such a lifecycle is that project defects are identified late within the lifecycle and therefore, the process of rectifying these problems becomes costly. Ultimately, an ideal product is one with minimal or zero defects which can be achieved with a software project that prevents or detects defects earlier within the cycle. Release management can be described as the process involving decision-‐making regarding the implementation and releasing of a software product. A conceptual framework exists which stipulates the stages involved in the development process of a software application. Several models exist that describe the SDLC in different approaches. A philosophy is adopted within the RAD model, known as Agile and is beneficial since it minimises future scope creep and scope changes. Development occurs in shorter intervals. Over and above the stages and values in this methodology, the Agile methodology includes incremental changes which are then captured in the scheduled software releases. The purpose of the research presented in this dissertation is to incorporate findings where large companies with global IT projects can adopt the Agile conceptual framework and to testify whether all types of IT projects will benefit from a frequent release approach to the delivery of the project. Three different projects across a large South African financial institution that specialises in corporate organisation banking and core-‐banking functionality will be studied and presented as case studies. Release management will also be studied from an organisational perspective with the following banking institution in context. Data will be retrieved by carrying out interviews and surveys with appropriate stakeholders, and therefore, analysed to generate a valid conclusion.
49
Morais, Ana Mafalda de Sousa. "Mapping CMMI process areas to agile best practices." Master's thesis, 2019. http://hdl.handle.net/10362/60403.
Full textAbstract:
Dissertation presented as the partial requirement for obtaining a Master's degree in Information Management, specialization in Information Systems and Technologies Management<br>To maintain competitiveness, software development companies are pressured to deliver products in less time, without compromising on quality and budget. To meet this demand, companies often adopt Agile software development techniques that enable shorter delivery times through constant smaller deliveries and shorter interactive cycles in software development processes. Although the innovation and the decrease of development time provided by these techniques, companies have perceived that quality is a differentiated factor and feel the urge to maintain the quality of their software to stand out from the competitors. At this point CMMI is presented as a reference model that contains a set of practices which lead to the maturity of organizations with focus on the improvement of organization processes and reduction of processes risk of failure increasing quality. In contrast with Agile, that puts individuals and their interactions in higher importance than processes and tools and where being adaptable to changes is more important than following strictly what was planned, CMMI it is a strict traditional approach that implies extensive formalism and focus on the processes. Derived of those apparent opposite beliefs, Agile development methods and CMMI best practices are frequently perceived to be at odds with each other. There is a great discussion about CMMI ability to be Agile and Agile methods to adapt to CMMI requirements without losing agility. This study aims to map CMMI for development process areas to Agile best practices to help in the understanding of the compatibilities and incompatibilities regarding the integration of CMMI and Agile. That will guide companies into the successful integration of Agile and maturity models together taking full advantage of their capabilities leading to enhanced software development. With the integration of those two approaches it is expected that Agile practices can help mature organizations to become more flexible, and CMMI could help Agile organizations to increase processes quality, fulfilling their goals and having their competitiveness sustained.
50
Burkhardt, Rainer, and Volker Gruhn. "Agile Software Engineering: A New System for an Expanding Business Model at SCHUFA." 2004. https://ul.qucosa.de/id/qucosa%3A32363.
Full textAbstract:
A software development unit called to renew or replace an existing corporate system may face some special problems in an established company with a lot of well-trained behavioral patterns and thought structures fitting to the legacy system only. The challenge is not just to be on a journey and reach the destination with the development team but keeping accompanied by the stakeholders during the travel. In this article we describe how Agile Software Engineering can be introduced to an in-house development structure of a company. We describe how agile process elements and model driven approaches can be combined in order to achieve a light weight, flexible and incremental software engineering process. We also show the resulting organizational structure of a development department and have a closer look to the management actions that must be taken to introduce agility to the internal team and the stakeholders all over the company.