Dissertations / Theses: 'Agile methods'

1

Vaarala, Robert, and Johan Svernell. "Agila metoder i stora företag : Hinder och möjligheter under initiativfasenvid implementation av agila metoder." Thesis, Uppsala universitet, Industriell teknik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-216493.

Full text

Abstract:

Som svar på ökade krav på IT-relaterade produkter har de så kallade agilautvecklingsmetoderna uppfunnits. Förespråkare för agila metoder hävdar att bättreresultat kan uppnås genom minskning av tydliga, strikta kravspecifikationer,dokumentation och planering inom projekt till förmån för ett större fokus på småsjälvorganiserande arbetsgrupper och ett iterativt utvecklingssätt. De värderingar och den praxis som är förknippade med agila metoder ter sig vara meranpassade för små företag , på grund av den tunga betoningen på små självständigagrupper och brist på formell styrning och kontrakt. Syftet med detta examensarbete harsin grund i den oppositionen. Vilka omständigheter uppstår när en avdelning på ett stortföretag vill omvandla sin projektmetodik till en agil? Specifikt utförs en fallstudie på enutvecklingsavdelning ett stort IT-företag med över 69 000 anställda världen över. I det studerade fallet visar resultaten att intresset för agila metoder är korrelerat mednärheten till mjukvaruutvecklingsprocessen . Mjukvaruutvecklarna i studien anser att detfinns stora problem med dagens utvecklingsprocess och fann bristen av flexibilitet ikravhantering samt begränsat kundengagemang oerhört frustrerande. Andragruppmedlemmar var mindre bekymrade. Genom att anamma företagets lednings samtkundens synsätt blev det klart att mer agila utvecklingsprocesser försvårar strategiskplanering av företags totala projektportföljer. Författarna föreslår att en agil transformation inom ett stort företag kräver starkaförespråkare inte bara från utvecklarlaget utan även från företagets affärssida samtkunden. Anammandet av agila metoder ställer stora krav på tillit i relationen mellanutvecklingsteam och ledning samt mellan utvecklingsteam och kund, eftersomsamarbetet till lägre grad bör styras av strikta kravspecifikationer som speglas i fastakontrakt.

APA, Harvard, Vancouver, ISO, and other styles

2

Gkritsi, Aikaterini. "Agile game : a project management game for agile methods." Thesis, University of Southampton, 2010. https://eprints.soton.ac.uk/272766/.

Full text

Abstract:

Since mid-1990s, companies have adopted agile methods and incorporated them in their development methodologies. For this reason, future project managers and developers need to have a full understanding of these methods. At present, the university’s approach to agile methods is theoretical and is not reflected during the development of a product and their practical use. The purpose of this project is the creation of a software system in the form of a game, named Agile Game, which simulates their use. The system is designed for use as supplementary material in lectures, to help students understand agile methods, to present their use within a project, and to demonstrate how they differ from traditional project management methodologies. The final system, which is web based, was implemented using PHP, MySQL and JavaScript. It was fully tested against the requirements and evaluated by peer students. The evaluation showed that the majority of users were satisfied with the system but they thought that it should contain more detailed information at every step of the game. For this reason, some parts of the design and the content were reviewed to meet user requirements.

APA, Harvard, Vancouver, ISO, and other styles

3

Jalali, Samireh. "Efficient Software Development Through Agile Methods." Licentiate thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-00528.

Full text

Abstract:

Context: Distributed teams characterize Global Software Engineering (GSE). GSE stakeholders are from different cultures, geographic places and potentially time zones. These conditions have significant consequences on communication, coordination and control of software projects. Given these constraints, distributed teams need to highly rely on each other. Trust is the glue that holds them together and enables more open communication, which increases their performance and quality of delivered products. Simultaneously, in striving for more efficient software development approaches, Agile values and principles were formulated. Agile methods encourage establishing close collaboration between customers and developers, continuous requirements gathering and frequent face-to-face communications. Objective: The major objective of the research is to study efficient software development approaches particularly in (globally) distributed settings. Thus, the dynamics of trust in GSE are investigated for bringing useful trust improvement suggestions to project managers. Furthermore, Agile practices that have been efficiently applied in GSE are identified through two different systematic literature review approaches (i.e. systematic literature review and backward snowballing). The differences identified in the use of Agile practices lead to a need to better understand and assess Agility. Method: The research methods, include systematic literature reviews and case studies, are applied in different empirical cases. Then, a variety of secondary data collection methods are utilized such as semi-structured interviews, questionnaires, open discussions and presentations. Result: Achieving trust was realized to be crucial and the success factor for trust was the “awareness” of particular GSE challenges, which shall be communicated properly to all distributed team members and proper actions shall be taken to address them. Besides, the literature indicated several successful combinations of Agile and GSE. However, despite utilizing two different literature search methods the identified patterns were similar. The most common practices were “standup meetings” and “sprints/iterations”. Nevertheless, the current literature reports “Agile” as a general term and “distributed team” as the most common team/organization setting, which motivated examining the applicability of existing Agile assessment tools in an industrial setting. We found one of the studied tools sufficiently applicable in the context of the case organization. Conclusions: Trust achievement is crucial for efficient GSE collaborations regardless of the applied software development approach. Although Agile promotes trust among team members, it was formulated without considering teams’ distribution. Hence, combining Agile and GSE is challenging. The literature contains several successful cases of implementing Agile in GSE while practitioners and researchers are not yet consistent regarding their perception of Agile practices and documenting them. Therefore, they need to collaborate closely, illustrate the practices, agree on the terminology, how to document the context, and how to profile/assess Agility. For this purpose, we examined the applicability of a set of Agile assessment tools and proposed one tool for the case organization.

APA, Harvard, Vancouver, ISO, and other styles

4

Wellme, Martin. "Architects working agile : Methods and challenges." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-253046.

Full text

Abstract:

Enterprise Architecture (EA) is a discipline which is used for describing and designing anorganisation's infrastructure and business processes. Agile methods are known for providingflexibility and adaptability in software development but can be applied to other areas as well.Nowadays, almost all aspects of a business should advance quickly which creates new challengesthat did exist before and the agile way of working is very suitable these situations. This thesis looksinto the challenges employees currently face when working with EA and how agile methods can beused to solve these issues.To investigate this, 19 interviews have been done at an international manufacturer where itsemployees were asked about how they work, which agile practices they use and the challenges theyface. The results of those interviews are presented statistically and compared to the literature reviewas well as two additional interviews done outside of the company in order to find agile methods thatcould be possible solutions to the company's challenges.The interviews showed that the employees already work agile with most of them working iterative,incremental and implementing changes based on feedback from the business which are allprominent agile methods. A few challenges which can be solved through agile were found, one ofthose is better project prioritisation found in Kanban to solve the lack of resources. Another practiceis to have forums, inspired by SAFe ART, between different roles to address the lack ofcoordination and contact between them. The location of the EA office was a challenge which couldbe solved through a non-agile way, by moving it away from the IT department and closer to thebusiness or alternatively move it higher up within the IT organisation. Enterprise arkitektur (EA) är en disciplin som används för att beskriva och designa en organisationsinfrastruktur och affärsprocesses. Agila metoder är kända för att ge flexibilitet ochanpassningsförmåga inom mjukvaruutveckling men kan också användas inom andra områden. Inuläget ska nästan alla aspekter av ett företag ska gå snabbt vilket skapar nya utmaningar och detagila arbetssättet är mycket lämpligt för dessa situationer. Den här avhandlingen undersöker deutmaningar som de anställda möter när de arbetar med EA and hur agila metoder kan användas föratt lösa dessa problem.För att undersöka det här, har 19 intervjuer gjorts hos en internationell tillverkare där deras anställdablivit frågade om hur de arbetar, vilka agila metoder de använder och vilka utmaningar de möter.Resultatet av intervjuerna presenteras statistiskt och jämförs med litteraturstudien samt med tvåytterligare intervjuer som har gjorts utanför företaget för att hitta agila metoder som kan varamöjliga lösningar till företagets problem.Intervjuerna visade att de anställda redan arbetar agilt med de flesta av dem arbetar iterativt,inkrementellt and implementerar förändringar baserat på feedback från verksamheten som alla äruppmärksamma agila metoder. Några av utmaningarna kan lösas med hjälp av agila metoder, en avdem är en bättre prioritering av projekt som finns i Kanban för att lösa bristen på resurser. En annanmetod är att ha forum, inspirerade av SAFe ART, mellan olika roller för att åtgärda bristen påkoordination och kontakt mellan dem. Placeringen av EA-kontoret var en utmaning som kundelösas på ett icke-agilt sätt, genom att flytta det bort från IT-avdelningen och närmare verksamheteneller alternativt flytta det högre upp inom IT-organisationen.

APA, Harvard, Vancouver, ISO, and other styles

5

Ollonqvist, K. (Kalle). "Moving from traditional software development methods to agile methods." Bachelor's thesis, University of Oulu, 2018. http://urn.fi/URN:NBN:fi:oulu-201806092553.

Full text

Abstract:

In this literature review, using existing research and sources, benefits and challenges of agile software development methods were discussed. Agile methods were also compared to traditional software development methods. Agile was defined and its four points of value were listed. This provided a basis for discussing the benefits and challenges of agile compared to the traditional software development methods. Customer involvement was found to have a positive effect on customer satisfaction in agile. The development team that was using agile as their development method was able to deliver something of value for the customer faster. This was useful if the company had to race to market. However, a software project that was developed with waterfall was found to be more predictable, especially if the development team was experienced. This was in part due to the customer not being able to change the requirements of the product they had ordered, and in part of the progressive or onward-moving development process typical to waterfall. Also, planning is a big part of waterfall development and it affects the predictability and measurability of the project as well. One of the biggest challenges when moving to agile from a traditional development method was changing the fundamental mindset of the people working in the organization. Especially the management-style needed to change from command-and-control management to leadership-and-collaboration. One of the challenges was that customer involvement might become a burden if the customer is continuously changing the requirements. Moving to agile from a traditional development method is not easy and it could lead to adding more sprints to the software development process than was planned.

APA, Harvard, Vancouver, ISO, and other styles

6

Tamari, Matteo. "Scrum e Kanban: framework e strumenti di supporto. Prospettive di applicazione nel progetto Agile methods for Agile working." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2020. http://amslaurea.unibo.it/22159/.

Full text

Abstract:

Da anni ormai, specialmente nel campo dell'ingegneria del software, vengono utilizzati modelli e framework Agili per lo sviluppo software. Essi hanno cambiato radicalmente il concetto di produzione, portandola a un livello più alto sia in termini di velocità rispetto alla consegna sia di qualità del prodotto consegnato; inoltre, tali modelli e framework vengono oggigiorno applicati anche al di fuori dello sviluppo software e questo dimostra che il loro impiego non ha limiti e barriere. In questo elaborato vengono presentati due tra i più conosciuti: Scrum e Kanban. Lo studio approfondito di entrambi ha permesso di cogliere i campi nei quali uno si applica meglio dell'altro, a seconda del contesto (natura della committenza, numero dei membri e background del team, dimensione del progetto, etc.) nel quale il prodotto richiesto si trova e degli strumenti dei quali Scrum e Kanban dispongono, come la "board", sia fisica sia virtuale. In riferimento a tali strumenti viene trattato dettagliatamente il funzionamento di Jira Software, il quale consente di migliorare la produttività dei team che collaborano anche a distanza, integrando perfettamente i modelli e framework Agili al suo interno. Successivamente, viene illustrata un’applicazione dei modelli Agili al di fuori dello sviluppo software; tale applicazione si divide in tre principali fasi: inception, construction e validation. In particolare, viene descritta come è stata affrontata la fase di inception, che consiste di un’analisi approfondita allo scopo di comprendere lo stato attuale del team, ovvero gli strumenti utilizzati, le metodologie applicate, la gestione delle commesse e dei servizi esterni, con il fine ultimo di far comprendere i vantaggi dati dall'essere Agili e di trasmetterli nei processi lavorativi che ogni elemento svolge ogni giorno sul posto di lavoro.

APA, Harvard, Vancouver, ISO, and other styles

7

Lindström, Lovisa. "Implementering av agila metoder : Varför företag väljer att införa agila metoder i projekt och verksamhet." Thesis, Karlstads universitet, Handelshögskolan (from 2013), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-71456.

Full text

Abstract:

Compared to traditional project management methods, agile methods are new. The use of project work keeps increasing, including the number of projects, with varying characteristics. In a world with a growing speed of change and with growing demands, there’s a need for adjustment, something which agile methods offer. However, agile methods are not suitable for all types of projects. The aim of the study was to broaden the understanding of what motivates implementation and usage of agile methods in projects and operations, challenges and advantages that can emerge through implementation and usage of agile methods, and if expectations of agile methods were confirmed. The study was qualitative and was made through semi-structured interviews, which were recorded and later transcribed. Collected data was analyzed based on thematic qualitative analysis. A total of three analyses were made - one per research question. All together the three analyses resulted in a total of thirteen themes. Motives for working agile varied, whereas primary motives for implementing and working with agile methods were increased efficiency, increased participation, and increased visualization of work. During on-going implementation, knowledge and training was crucial, including management, employees and customers. Agile methods were adjusted to reality and operations. Customers wanted to take part in working with agile methods, while their knowledge was inadequate. Expectations that existed before the implementation were confirmed. Agile methods hold what it promises.

APA, Harvard, Vancouver, ISO, and other styles

8

Ekström, Axel, and Emma Pettersson. "Agile project management in the design stage – Construction projects possibilities to apply agile methods." Thesis, KTH, Fastigheter och byggande, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-190210.

Full text

Abstract:

The construction industry has a clear process it follows therefore the working method within it also has become rigid. Through long time the stage-gate model has been used by the project management. Construction projects are often complex, have long stages and long decisions routes. When a stage is completed questions have been raised and lead to that change is needed to be made before moving on to next stage. This takes time, costs more than calculated and the function gets compromised. The purpose with this thesis is to investigate if the current project management approach can be performed more efficiently by applying agile project management to the design stage. This thesis is performed with a qualitative research approach. It started with a thoroughly literature review of relevant topics such as agile project management, the construction process and change management. When a solid base of knowledge was gathered about the research area an interview study was conducted and a survey was sent out. The findings are a result from the interview study and the survey. The interview questions and findings are divided into four focus areas of agile project management which are project planning, meeting structure, group collaboration and communication. The discussion connects the literature with the information from the interviews and the discussion is presented with the reflections from the authors. The conclusions present the answers on the research questions. The final chapter about further research is presenting perspectives that have not been answered in this thesis. The thesis concludes that project management methods within construction projects are not as rigid as it is described in the literature. The lack of knowledge and awareness of other working methods creates a culture of "this is how it always has been done" within the four focus areas of agile project management. All of the reference projects were time pressured and it was in those situations where ii most tendencies to adjust management method was shown. The studied projects had fixed meeting structures and when emergency occurred, extra meetings were held. The project management teams had good collaboration due to that they were co-located and not too big groups. The co-location also facilitated the communication which was compared to team members that were not co-located and struggled with the communication. The communication generally worked well vertically and was struggling horizontally. Agile project management cannot be achieved to 100% and it is difficult to apply all of its characteristics on the construction industry since it was developed from the software industry which has other traits than construction. On the other hand, agile project management is a mindset of continuously improvement and flexibility of the used working methods which can be used by the construction industry. The construction industry has to follow some specific processes such as applying for building permits and is affected by political decisions. Therefore the current project management methods are restricted to follow certain frameworks. The framework is hard to change though it leaves space for changed methods and attitudes within the framework and the design stage. All types of construction projects can use the agile mindset and it is important that the whole organization relates to the agile mindset to achieve greatest outcome. Steps towards agile can be done in current projects by emphasis more on reconciliations and let the projects progression decide the meeting structure. Byggprocessen är en väletablerad process inom byggindustrin som byggprojekt genomgår. Genom de tydliga och historiska riktlinjerna som processen följer har byggindustrin fått anseendet att vara stel och konservativ. För att hantera byggprocessen har projektledningen följt Stage-gate modellen med tydliga delmål och beslutsgrindar. Byggprojekt är ofta komplicerade och stora vilket leder till långa beslutsvägar. När ett projekt når en grind vid ett avslut av ett delmål uppstår ofta frågor som leder till förändringar av delmålet. För att behandla förändringarna så behöver processen genomgå ett omtag, att göra om delmålet innan processen kan gå vidare till nästa delmål. Omtagen tar tid, kostar pengar och det kompromissas med funktionen. Denna uppsats har som mål att undersöka om den aktuella projektledningsmetoden kan effektiviseras genom att introducera agil projektledning i projekteringen. Uppsatsen genomförs med en kvalitativ metod. Det första steget är att finna relevant litteratur om berörda ämnen som agil projektledning, byggprocessen och förändringsledning. Med fördjupad kunskap och förståelse inom ämnena genomfördes en intervjustudie och en enkät sändes ut. Resultaten identifierades från intervjuerna och svaren från enkäten. Intervjufrågorna och resultatet är uppdelat i fyra olika agila kategorier som anses gå att applicera på byggindustrin. Kategorierna är projektplanering, mötesstruktur, gruppsamarbete och kommunikation. Resultatet följs utav diskussionen som binder samman litteraturen med resultatet och författarnas reflektioner. Därefter presenteras slutsatsen och avslutningsvis rekommenderas frågeställningar till fortsatta undersökningar. Projektledningsmetoderna som används inom byggprojekt upplevdes inte lika stela som litteraturen beskriver dock fanns det lite kunskap och medvetenhet om andra typer av projektledningsmetoder. Avsaknaden är en bidragande faktor till att den upplevda kulturen anses vara konservativ. Inom de fyra kategorierna fanns det möjligheter till att arbeta mer agilt. När projekten är tidspressade visades mest benägenhet på att förändra projektledningsmetoden. Detta kunde ses tydligt på mötesstrukturen i projekten där den var fast ifrån början men blev mer rörlig då kritiska situationer uppstod. Gruppsamarbetet fungerade bra inom projektledningen för att de var samlokaliserade och inte för stora grupper. Detta underlättade även för en fungerande kommunikation då det märktes att de som inte var samlokaliserade hade svårigheter med kommunikationen. De horisontella kommunikationsvägarna hade generellt sett svårare att fungera än de vertikala kommunikationsvägarna. Eftersom agilt inte är en standard utan är ett arbetssätt som alltid strävar efter att förbättras är det svårt att uppnå ett 100 % agilt arbetssätt. Inom byggindustrin finns vissa ramverk som ska följas vilket gör att projektledningen begränsas. Med fasta ramverk finns lite utrymme för förändring men det finns möjlighet till att förändra processen och tankesättet inom ramverket. Alla typer av byggprojekt kan därför anamma delar av agil projektledning och för att uppnå största möjliga effekt gäller det att hela organisationen är engagerad. Andra enkla steg för att arbeta mer agilt inom projektledningen är att lägga mer vikt vid avstämningsmöten och låta projektets utveckling bestämma mötesstrukturen.

APA, Harvard, Vancouver, ISO, and other styles

9

Lagré, Mårten. "Varför arbetar vissa utvecklingsteam agilt med kravhantering och vissa inte? : En fallstudie på Lantmäteriet." Thesis, Högskolan Dalarna, Informatik, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:du-25514.

Full text

Abstract:

Kravhantering inom systemutveckling utgör basen för vad som ska utvecklas. Agila systemutvecklingsmetoder blir vanligare för varje dag som går. Det har dock ofta visat sig finnas utmaningar med hur man anpassar just kravhanteringen till de agila metoderna. Verksamheter har olika förutsättningar för att arbeta agilt. Lantmäteriet i Gävle uttryckte ett behov att undersöka varför den agila praxis man hade inte följdes av alla utvecklingsteam i samband med kravhanteringen. Syftet med denna uppsats var därför att undersöka varför vissa utvecklingteam i en verksamhet arbetade agilt med sin kravhantering medan vissa inte gjorde det. För att undersöka detta utförde jag en fallstudie där jag med hjälp av enkäter och intervjuer samlade in data från både utvecklare och personer på verksamhetssidan som var inblandade i kravhanteringen. Resultaten visade att orsakerna till att en agil kravhantering fungerade så olika var flera. Genom att använda en tematisk analys kunde jag urskilja några framträdande orsaker. Kommunikation och flexibilitet samt kunskap och förståelse för olika perspektiv var teman som utgjorde positiva faktorer. De teman som istället utgjorde negativa faktorer var bland andra otydliga roller, brist på direktiv, en övertro till metoder och processer, osynk mellan verksamhet och IT, prioriteringsproblem, förvaltningsplaner, attityder och IT-arkitektur. Requirements engineering within software development is the foundation of what needs to be developed. Agile methods in software development become more common every day. It has however often been shown that there are certain challenges with how to adopt the requirements engineering to the agile methodology. Businesses have different preconditions for agile methods. Lantmäteriet in Gävle had a need to examine why not all the developing teams followed agile methods within the requirements engineering process. The purpose with this thesis was thus to examine why some developing teams in an organization worked in an agile manner with the requirements engineering, and some did not. To do this I performed a case study where I collected data through questionnaires and interviews from both developers and people from the business side. The results showed that the reasons for these differences were multiple. Communication and flexibility, and knowledge and understanding for different perspectives were the positive factors. The themes that hindered an agile way of working were, among others, unclear roles, lack of direction, too much reliance on methods and processes, discrepancy between business and IT, prioritizing issues, management plans, attitudes and IT architecture.

APA, Harvard, Vancouver, ISO, and other styles

10

Soundararajan, Shvetha. "Agile Requirements Generation Model: A Soft-structured Approach to Agile Requirements Engineering." Thesis, Virginia Tech, 2008. http://hdl.handle.net/10919/34511.

Full text

Abstract:

The agile principles applied to software engineering include iterative and incremental development, frequent releases of software, direct stakeholder involvement, minimal documentation and welcome changing requirements even late in the development cycle. The Agile Requirements Engineering applies the above mentioned principles to the Requirements Engineering process. Agile Requirements Engineering welcomes changing requirements even late in the development cycle. This is achieved by using the agile practice of evolutionary requirements which suggests that requirements should evolve over the course of many iterations rather than being gathered and specified upfront. Hence, changes to requirements even late in the development cycle can be accommodated easily. There is however, no real process to the agile approach to Requirements Engineering. In order to overcome this disadvantage, we propose to adapt the Requirements Generation Model (a plan-driven Requirements Engineering model) to an agile environment in order to structure the Agile Requirements Engineering process. The hybrid model named the Agile Requirements Generation Model is a soft-structured process that supports the intents of the agile approach. This model combines the best features of the Requirements Generation Model and Agile Software Development. Master of Science

APA, Harvard, Vancouver, ISO, and other styles

11

Jedyk, Marcin. "Using Feature Models For Reusability In Agile Methods." Master's thesis, METU, 2011. http://etd.lib.metu.edu.tr/upload/12613338/index.pdf.

Full text

Abstract:

The approach proposed in this thesis contributes to implementing source code reuse and re-engineering techniques for agile software development. This work includes an introduction to feature models and some of the Feature Oriented Software Development (FOSD) practices to achieve a lightweight way of retrieving source code. A Feature model created during the course of following FOSD practices serves as an additional layer of documentation which represents the problem space for the developed application. This thesis proposes linking source code with such a feature model for the purpose of identifying and retrieving code. This mechanism helps with accessing the code segment corresponding to a feature with minimal effort, thus suits agile development methods. At the moment, there is a gap between feature oriented approaches and agile methods. This thesis tries to close this gap between high-level approaches for software modelling (feature modelling) and agile methods for software development.

APA, Harvard, Vancouver, ISO, and other styles

12

Svensson, Harald. "Developing support for agile and plan-driven methods." Doctoral thesis, KTH, Mikroelektronik och Informationsteknik, IMIT, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-554.

Full text

Abstract:

Software development processes provide means to develop software in a structured and disciplined way. Although these processes provide support for how to develop software, there is still a challenge to successfully apply them in practice. Thus, there is a need to support management of software development processes so that their use generate as good results as possible. The thesis presents support for agile and plan-driven methods, which represent different approaches for developing software. The support for agile methods was developed after performing a case study and a survey, in order to gather empirical data. The support for plan-driven methods was developed after applying a combination of research methods such as a controlled experiment, grounded theory and theoretical analysis. The developed support for managing agile and plan-driven methods is based on the results from an extensive empirical basis consisting of five studies, with both qualitative and quantitative approaches. The developed support for agile methods consists of a set of guidelines for organizations to consider when introducing agile methods. The developed support for plan-driven methods concerns support for the Business Process Analyst role to manage its work in a software development context. Further, the Personal Software Process is allocated to several roles in order to increase its applicability. QC 20101001

APA, Harvard, Vancouver, ISO, and other styles

13

Al-kfairy, Mousa. "Toward Agile development methods & Non-functional requirements." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-54656.

Full text

Abstract:

In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.

APA, Harvard, Vancouver, ISO, and other styles

14

Gillo, Nilsson Catherine, and Daniel Karlsson. "Implementing Agile project methods in globally distributed teams." Thesis, Karlstads universitet, Handelshögskolan, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-35321.

Full text

Abstract:

The objective of the study was to generate a ‘theory’/ ‘hypothesis’ on the important factors to focus on in implementing agile project methods in globally distributed teams. Using the grounded theory method, five key categories emerged from the so-called theoretical sampling, which entails the joint collection of data, coding and analysis. The study involved 33 individuals in four different companies, three in the Philippines and one in Sweden. The data collected for this thesis consisted of individual interviews in the Philippines and Sweden (Sept-Dec 2014), focus group sessions, observations of formal agile practices and experiences in the substantive area, conducted in the Philippines during the period Sept-Nov 2014. The following five key categories emerged as the main concerns of the individuals involved in implementing agile project methods in globally distributed teams in software development projects: (i) Working Communication, (ii) Self-organizing Teams, (iii) People-centric organization, (iv) Continuous Learning and (v) Sustaining Infrastructure. The respondents meant that these concerns should be addressed and resolved in such a way that the implementation of Agile project methods would resemble the case of a collocated Agile project team. The key categories, their fundamental characteristics and the subconcepts behind them were presented and analyzed in relation to the empirical data.The analysis included reported incidents and direct citations from the respondents, focus groups and from observations during the field study, in order to shed light on the process used to arrive to the categories, as well as explain the characteristics of the concepts in the emerging ‘grounded hypothesis’.

APA, Harvard, Vancouver, ISO, and other styles

15

Kuziwa, Ally, and Kazibwe Flavia Ndagire. "Application of Agile Methods in Distributed Software Development." Thesis, Umeå universitet, Institutionen för informatik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-122495.

Full text

Abstract:

Agile software development methods are characterized by developer’s empowerment through self-organization, incremental requirements and constant knowledge sharing. Despite some effort to elaborate how successfully agile methods can be applied in co-located development teams, little is known on how the same is done when the development teams are distributed. Our research focus is to uncover factors that influence the successful application of agile methods in distributed development teams using a software development company as our case study. With three distributed teams applying different agile methods, we conducted focused ethnography alongside interviews to comprehend what and how various factors under distributed development teams influence successful agile methods application. It seems, all that matters is team structure, team spirit, effective communication, product requirements, and knowledge sharing. The team structure has more influence than other factors and therefore our suggestions for successful application of agile methods in distributed software development is to focus on the development team, above all factors. The analysis shows that the development methods themselves have little to do with the successful application of agile methods in distributed software development teams.

APA, Harvard, Vancouver, ISO, and other styles

16

Minot, Scott James. "Injecting Safety-Critical Certification Into Agile Software Methods." Thesis, North Dakota State University, 2013. https://hdl.handle.net/10365/27046.

Full text

Abstract:

Agility offers an adaptable and changeable environment within software development. The benefits that agile methods provide for software development are becoming an even greater possibility in safety-critical software programs. These certified programs go through a rigorous process to ensure the safety of all people involved. As the systems become more complex and there is a need for adaptability, the benefits of agile could save companies considerable time and money without sacrificing the safety factor. In this paper, I will provide ways of incorporating certification for highly critical systems by using a form of agility tailored to fit certification requirements. With time reduction and an increasing ability to change safety-critical software, it will show that it can be a viable option to deploy.

APA, Harvard, Vancouver, ISO, and other styles

17

Wallström, Andreas. "Guidance on Implementing Agile Software Development Methods within a Traditional Environment." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-296990.

Full text

Abstract:

Agile software development methods keep increasing in popularity. Many organizations who are using traditional software development methods, such as water-fall and stagegate based methods are switching to agile software development methods. This transition can be challenging, especially for organizations using project governance models that hinder the adoption of agile practices. This study aims to provide guidance to managers on how to introduce agile software development methods in such traditional organizations. The study is a single-case study on a large governmental agency in Sweden. Eight interviews with developers, team-leads and managers were conducted. The study identifies practical tools and ideas that managers can use to introduce a shared definition of agile, adopting an agile mindset, dedicated teams, and CI&CD. Together, this guidance supports managers with the introduction of agile software development methods in organizations utilizing traditional project governance structures and traditional software development methods. Agila systemutvecklingsmetoder fortsätter öka i popularitet. Många organisationer som använder sig av traditionella systemutvecklingsmetoder så som vattenfallsmodellen byter till agila systemutvecklingsmetoder. Denna övergång kan vara utmanande, speciellt för organisationer som använder sig av projektbaserade förvaltningsmodeller som hindrar implementeringen av agila metoder. Den här studien syftar till att ge vägledningen till chefer kring hur de kan introducera agila systemutvecklingsmetoder iden nyss nämnda typen av traditionella organisationer. Studien är en fallstudie gjort på en stor myndighet i Sverige. Åtta intervjuer med systemutvecklare, lag-ledare och chefer har utförts. Studien identifierar verktyg och idéer som chefer kan använda sig avför att introducera en delad gemensam definition av agilt, anamma ett agilt tankesätt, introducera dedikerade teams och CI&CD. Tillsammans hjälper de här verktygen med introduktionen av agila systemutvecklingsmetoder i organisationer som använder sig av traditionella systemutvecklingsmetoder och förvaltningsmodeller.

APA, Harvard, Vancouver, ISO, and other styles

18

Hanna, Andy, and Ninos Bethzazi. "The Role of the Manager in an Agile Organization : A Case Study at Scania AB." Thesis, KTH, Industriell ekonomi och organisation (Inst.), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-235400.

Full text

Abstract:

As the world of business changes at a pace higher than ever before, there is an increased need for organizations to rapidly adapt and respond to these internal and external changes, whether they are technological, political, social or environmental. In management, agility is a term frequently used today in response to this new business environment, which often includes the use of agile methodologies for product development. As organizations adopt agile methodologies, old traditional management and leadership models fade. This void is being filled by new and emerging agile leadership models. Additionally, self-organizing and cross-functional teams become key concepts. All these transformations are bound to culminate in a considerable alteration in the role of the manager. This study examines the new role of the manager in an organization transitioning to agile. To answer the research questions, changes in the key work activities of the manager were evaluated, as well as how changes in interplay and interaction between the manager and the group could affect the role. Furthermore, the aim was also to identify some of the main challenges and barriers that arise. This was studied qualitatively through a literature review. Also, a case study was conducted at the software development department at Scania AB, where ten managers and one employee was interviewed. A survey was also sent out to the group members at this department, with 150 respondents. Findings indicated that most work activities did not change. Some of them changed in character due to introducing an agile method and due to internal, structural changes. In one case, the work focus shifted from one activity to another. In the interplay with the group, the manager now has new roles to consider, while his role becomes more of an empowerer and meets new leadership models. With this organizational change, there are also new opportunities of delegating work activities to a higher extent. The main challenges that were identified regarded communication and coordination, control, and mastering agile methods. Affärsvärlden möter förändringar i en allt snabbare takt än tidigare, varför organisationer måste bemöta och förhålla sig till både de interna och externa förändringar som sker, vare sig dessa är teknologiska, politiska, sociala eller miljömässiga. Inom ledarskap används idag termen agilt allt mer, som svar på detta nya affärsklimat, vilket ofta inkluderar användandet av agila metoder inom produktutveckling. Då allt fler organisationer inför användandet av agila metoder, tappar också de traditionella ledarskapsmodellerna sin roll. Detta gap som uppstår har kommit att fyllas av nya agila ledarskapsmodeller. Vidare blir också självstyrande och tvärfunktionella grupper viktiga koncept. Dessa förändringar medför en avsevärd förändring av chefsrollen. Denna studie undersöker hur chefsrollen förändras i en organisationen som blir allt mer agil. För att svara på forskningsfrågorna undersöktes hur huvudarbetsuppgifterna förändrats, men också hur förändringar i samspelet och interaktionen mellan chefen och gruppen kan komma att påverka chefsrollen. Vidare undersöktes också vilka huvudsakliga utmaningar och hinder som uppstod. En kvalitativ litteraturstudie utfördes i studien. Också en fallstudie på avdelningen för mjukvaruutveckling på Scania AB utfördes, där tio gruppchefer och en annan anställd intervjuades. En undersöknings skickades också ut till gruppmedlemmar på denna avdelningar, med totalt 150 svar.Resultatet påvisade att de flesta arbetsuppgifter inte förändrades. Vissa av dessa förändrades i karaktär och i utförandet, till följd av införandet av en agil metod och strukturella förändringar i företaget. I ett fall skiftade arbetsfokus från en arbetsuppgift till en annan. I samspelet mellan chef och grupp har nu chefen nya roller att ta hänsyn till. Chefens roll blir mer av en facilitator, där nya ledarskapsmodeller också står till mötes. Chefen har också större möjligheter till delegering av arbetsuppgifter än tidigare. De utmaningar som identifierades rörde kommunikation och koordination, kontroll, och hanteringen av agila metoder.

APA, Harvard, Vancouver, ISO, and other styles

19

Henriksson, Emma, and Julia Svensson. "Agilt inköp av IT : En kvalitativ studie inom offentlig sektor." Thesis, Luleå tekniska universitet, Institutionen för ekonomi, teknik och samhälle, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-74412.

Full text

Abstract:

Traditionellt har inköpsprocessen inom offentlig sektor utgått från projektmodellen vattenfall med tydliga faser och milstolpar. För att skapa större flexibilitet och effektivitet har IT-branschen frångått den traditionella projektmodellen och istället övergått till agila arbetsmetoder. En utmaning som uppstått genom detta är att inköpsprocessen inom den offentliga sektorn sällan är anpassad till agila arbetssätt. Den offentliga sektorn är en stor inköpare av IT men en betydande del av de offentliga IT-projekten misslyckas idag i form av överskriden budget. En orsak till detta kan vara att den traditionella inköpsprocessen har svårt att möta de förutsättningar som krävs för ett agilt arbetssätt, då den hindrar effektiviteten och måluppfyllelsen vid inköp av IT. I denna studie undersöks vilka möjligheter och utmaningar som finns inom en agil inköpsprocess för IT, samt hur en agil inköpsprocess skulle kunna struktureras och tillämpas i syfte att öka effektiviteten, kundnyttan och harmoniseringen mellan inköp av IT och implementeringen. En kvalitativ studie har genomförts där primärdata insamlats genom intervjuer. Totalt har 23 djupintervjuer genomförts med olika aktörer inom inköpsprocessen såsom beställare, upphandlare och leverantörer. Den största delen av datainsamlingen är genomförd på Luleå kommun men intervjuer har även utförts med externa respondenter med kunskap om agila arbetssätt inom offentlig sektor. Intervjuerna har analyserats genom en tematisk analys, som resulterat i ett flertal identifierande möjligheter och utmaningar för agilt inköp av IT samt ett ramverk för agilt inköp av IT. Studien visar att det finns både möjligheter och utmaningar inom en agil inköpsprocess för IT. Offentliga organisationer som bland annat genomsyras av de agila grundvärderingarna, med motiverade och förändringsbenägna individer och förtroende för leverantörer har goda möjligheter att arbeta med agilt inköp. Utmaningar finns inom ett ökat behov av struktur, högre grad av effektstyrning, proaktiv uppföljning, en förändrad anbudsutvärdering och en kulturell omställning. I studien har ett ramverk för agilt inköp av IT inom offentlig sektor framtagits. Ramverket är baserat på den nationella inköpsprocessen och de agila grundvärderingarna. Inom varje fas i inköpsprocessen presenteras aktiviteter som bidrar till att skapa en agil inköpsprocess. Aktiviteterna innefattar bland annat att skapa självorganiserande team, ställa krav på effektmål, skapa en jämn riskfördelning och arbeta med incitament för effektivitet. Studien bidrar med ny kunskap inom hur ett agilt arbetssätt kan anammas inom inköpsprocessen för IT inom offentlig sektor. Genom att använda det agila ramverket kan offentliga organisationer skapa en ökad harmonisering mellan inköpsprocessen och implementeringen av IT, med förhoppningen att det ökar effektiviteten och kundnyttan. Traditionally, the public procurement process has originated in the waterfall project model, with distinct phases and gates. To gain more flexibility and efficiency, the IT industry have adapted agile project methods instead. A challenge that has arisen due to this change is that the traditional procurement process rarely is adapted to agile project methods. Furthermore, the public sector is a large buyer of IT, but a significant part of all public projects within IT are failing in terms of exceeded budget. One reason for this could be that the traditional procurement process has difficulties in meeting the conditions required for agile methods, since it prevents the efficiency and goal achievement of IT procurement. In this study, the possibilities and challenges of an agile procurement process for IT was researched. The study also included how the procurement process could be structured and applied, with the aim to increase the efficiency, the customer value and the harmonization between procurement of IT and the implementation. The research questions were answered by a qualitative study where primary data was collected through interviews. A total of 23 deep interviews were conducted with different participants in a procurement process such as purchasers, suppliers and clients. The largest amount of data was collected at Luleå kommun, but interviews were also conducted with external respondents with knowledge of agile methods in the public sector. The interviews were analyzed through a thematic analysis, which resulted in several opportunities and challenges concerning agile procurement, together with a framework for agile procurement of IT. The study shows that there are both opportunities and challenges in an agile procurement process of IT. Public organizations that for example is permeated of the agile ground values, with motivated individuals with a likeness of change and trust towards the suppliers, have good opportunities to work with agile procurement. Challenges exists in an increased need of structure, a change in purchasing and contract procedures and the need of education and a culture shift. In the study, a framework for agile procurement of IT in the public sector has been developed. The framework is based on the national procurement process in Sweden and the agile ground values. In each procurement process phase activities that characterize agile methods are presented. The activities include for example creating self-organizing teams, setting requirements based on impact goals, creating a model for shared risk and work with incentives for efficiency. The study contributes to new knowledge of how agile methods can be incorporated in the public procurement process. By using the agile framework public organization can increase the harmonization between the procurement process and the implementation of IT, with the aim to increase the customer value and efficiency.

APA, Harvard, Vancouver, ISO, and other styles

20

Boström, Gustav. "Simplifying development of secure software : Aspects and Agile methods." Licentiate thesis, KTH, Numerical Analysis and Computer Science, NADA, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-3913.

Full text

Abstract:

Reducing the complexity of building secure software systems is an important goal as increased complexity can lead to more security flaws. This thesis aims at helping to reduce this complexity by investigating new programming techniques and software development methods for implementing secure software. We provide case studies on the use and effects of applying Aspect-oriented software development to Confidentiality, Access Control and Quality of Service implementation. We also investigate how eXtreme Programming can be used for simplifying the secure software development process by comparing it to the security engineering standards Common Criteria and the Systems Security Engineering Capability Maturity Model. We also explore the relationship between Aspect-oriented programming and Agile software development methods, such as eXtreme Programming.

APA, Harvard, Vancouver, ISO, and other styles

21

Boström, Gustav. "Simplifying development of secure software : aspects and agile methods /." Stockholm : Department of Computer & Systems Sciences, Stockholm University and The Royal Institute of Technology, 2006. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-3913.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Trippner, Dietmar, and Karsten Theis. "Agile PLM Strategy Development - Methods and Success Factors [Präsentationsfolien]." Saechsische Landesbibliothek- Staats- und Universitaetsbibliothek Dresden, 2016. http://nbn-resolving.de/urn:nbn:de:bsz:14-qucosa-214705.

Full text

Abstract:

Aus "Ausgangssituation und Herausforderungen": "Produktionsunternehmen und insbesondere die Automobilindustrie unterliegen einem permanent wachsenden Wettbewerbsdruck. Ursache hierfür sind anhaltende rasante gesellschaftliche, politische, gesetzliche und technologische Veränderungen in einem globalen Markt. Daraus resultieren steigende Anforderungen an die zu entwickelnden und herzustellenden Produkte sowie die hierfür geeigneten Technologien, Prozesse, Organisationen und Qualifikationen der Mitarbeiter. Die dafür notwendige Innovationskraft eines Unternehmens ist für den Erhalt und Ausbau der Wettbewerbsfähigkeit eine Grundvoraussetzung und spielt im globalen Markt eine entscheidende Rolle (Tri, 2003). Die „Digitale Transformation“ ist in diesem Kontext eine der ganz großen Herausforderungen, die die Produktionsunternehmen in den kommenden Jahren meistern müssen. ..."

APA, Harvard, Vancouver, ISO, and other styles

23

Silva, Tiago Silva da. "A framework for integrating interaction design and agile methods." Pontifícia Universidade Católica do Rio Grande do Sul, 2012. http://hdl.handle.net/10923/1487.

Full text

Abstract:

Made available in DSpace on 2013-08-07T18:42:27Z (GMT). No. of bitstreams: 1 000438706-Texto+Completo-0.pdf: 5157206 bytes, checksum: c5422795c48935a5ef9a79af5999aa0c (MD5) Previous issue date: 2012 Agile development has become mainstream regarding software development processes. Along the increasing understanding of the importance of good User eXperience came the need to integrate these two areas. However, Agile development have a distinct culture that at first glance seems to conflict with User-Centered Design. Therefore, integrating these two areas becomes a challenging task. This thesis focuses on integrating these areas, providing a set of practices and artifacts to support Agile teams and Interaction Designers to overcome this challenge. A Systematic Literature Review was conducted in order to identify existing approaches regarding the integration of Agile and Interaction Design. A framework was proposed gathering the most common practices and artifacts identified in this review. Conducting Action Research in two companies from two different countries tried out this proposal. Thus, the result of this research is a framework proposal for integrating Interaction Design and Agile Development. Desenvolvimento Ágil tem estado em evidência no que diz respeito à processos de desenvolvimento de software. Juntamente com o crescimento da conscientização sobre a importância de uma boa Experiência de Usuário surgiu a necessidade de integrar estas duas áreas. Entretanto, o desenvolvimento Ágil possui uma cultura distinta que, num primeiro momento, parece entrar em conflito com o Design Centrado no Usuário. Assim, a integração destas duas áreas torna-se um desafio. Esta tese focaliza na integração destas duas áreas, fornecendo um conjunto de práticas e artefatos para apoiar equipes Ágeis e Designers de Interação a superar tal desafio. Uma Revisão Sistemática foi realizada a fim de identificar propostas de integração de métodos Ágeis e Design de Interação. Com base na reunião das práticas e artefatos mais comuns identificados na revisão, um framework foi proposto. A fim de verificar tal proposta, Pesquisas-Ação foram realizadas em duas organizações de dois diferentes países. Desta forma, o resultado desta pesquisa é a proposta de um framework para integrar Design de Interação e desenvolvimento Ágil.

APA, Harvard, Vancouver, ISO, and other styles

24

Aslam, Gulshan, and Faisal Farooq. "A comparative study on Traditional Software Development Methods and Agile Software Development Methods." Thesis, Tekniska Högskolan, Högskolan i Jönköping, JTH. Forskningsområde Informationsteknik, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-15383.

Full text

Abstract:

Everyone is talking about the software development methods but these methods are categorised into the different parts and the most important are two categories, one is agile software development methods and second is using the traditional software development methods. Agile software methods are relatively considered to be quick and for the small teams. Our main mission is to check which method is better from each other, so for that purpose we go out in the software development market to meet the professional to ask about their satisfaction on these software development methods. Our research is based on to see the suitable method for the professionals; see the challenges on the adoptability of methods and which method is quicker. To perform this study we have gone through a survey questionnaire, and results are analysed by using mixed method approach. Results shows that professionals from both types of methods are satisfied but professionals with traditional methods are more satisfy with their methods with respect to development of quality software, whereas agile professionals are more satisfied with their methods with respect of better communication with their customers. With agility point of view, our study says that both methods have characteristics which support agility but not fully support, so in such case we need to customize features from both types of methodologies.

APA, Harvard, Vancouver, ISO, and other styles

25

Fuchs, Christoph [Verfasser]. "Agile Methods in the Digital Transformation – Exploration of the Organizational Processes of an Agile Transformation / Christoph Fuchs." Berlin : epubli, 2019. http://d-nb.info/1202665128/34.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Kessing, David, and Manuel Löwer. "Vergleich der Motivationsprofile von Scrum-Teammitgliedern mit dem Agilen Manifest zur Entwicklung von Gamification-Strategien." Thelem Universitätsverlag & Buchhandlung GmbH & Co. KG, 2021. https://tud.qucosa.de/id/qucosa%3A75929.

Full text

Abstract:

Agile Methoden sind in der industriellen Anwendung Stand der Technik, wobei Scrum das am häufigsten verwendete Prozess-Framework zur effektiven Entwicklung komplexer Produkte ist. Entworfen wurde Scrum von Ken Schwaber und Jeff Sutherland, die ebenfalls 2001 das agile Manifest mitentwickelten, welches die vier Werte und zwölf Prinzipien für die Arbeit mit agilen Methoden definiert. Scrum zeichnet sich unter anderem durch flache Hierarchien aus. Hierdurch erhalten Mitarbeitende zunehmend Verantwortung und es entsteht aufgrund der vermehrt stattfindenden Kommunikation eine erhöhte Transparenz in allen Prozessen. Diese Eigenschaften bringen viele Vorteile aber auch Herausforderungen mit sich. Einerseits kann hohe Transparenz durch Offenlegung der Arbeit zu Unsicherheit seitens der Mitarbeitenden führen, andererseits sorgt die erhöhte Verantwortung auch für einen größeren Einfluss der einzelnen Team-Mitglieder auf das Ergebnis der Arbeitsprozesse. Die Motivation und Leistungsbereitschaft der Mitarbeitenden sind demzufolge ausschlaggebend für die erfolgreiche Produktentwicklung mit Scrum. Gamification ist ein neuer, vielversprechender Ansatz zur Steigerung der Motivation und wird dabei definiert als „die Verwendung von Spiel-Designelementen in Nicht-Spielkontexten“. Die dieser Veröffentlichung zugrundeliegende Forschung bildet die Grundlage zur Entwicklung von dedizierten Gamification-Strategien mit dem Ziel der Optimierung von Motivation und folglich der Leistung der Mitarbeitenden im Scrum-Entwicklungsprozess.

APA, Harvard, Vancouver, ISO, and other styles

27

Lambert, Tracy. "CROSS SECTIONAL STUDY OF AGILE SOFTWARE DEVELOPMENT METHODS AND PROJECT PERFORMANCE." NSUWorks, 2011. http://nsuworks.nova.edu/hsbe_etd/56.

Full text

Abstract:

Agile software development methods, characterized by delivering customer value via incremental and iterative time-boxed development processes, have moved into the mainstream of the Information Technology (IT) industry. However, despite a growing body of research which suggests that a predictive manufacturing approach, with big up-front specifications, detailed estimates, and speculative plans applicable to manufacturing domains, is the wrong paradigm for software development, many IT organizations are still hesitant to adopt agile approaches (Larman, 2004). This study extends research based on the Unified Theory of Acceptance and Use of Technology (Venkatesh, Morris, Davis, & Davis, 2003) into the domain of business processes. Specifically, processes related to the `behavioral intent' to adopt agile software development methods. Further, it investigated relationships between adoption and the impact on project performance attributes. A sample was obtained from a population of IT practitioners from within the IT industry. The sampling frame consisted of members from the global Software Process Improvement Network (SPIN) chapters, Agile User Groups, and I.T. industry conference promoters and presenters. Independent variables included performance expectancy, effort expectancy, social influence, and facilitating conditions, with the dependant variable being behavioral intent to adopt agile software development methods. The independent variable of agile software development adoption and dependent variables of project performance were also included as well as predictive models relating adoption to on-time delivery of project functionality and stakeholder satisfaction. The variables in the study were measured via a 65-item questionnaire based on previous scales, and tested to ensure validity and reliability. The research questions were developed to identify correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and the behavioral intent to adopt agile software development methods. Additional questions measured the correlation between adoption and key project performance attributes. The research found positive correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and behavioral intent to adopt agile software development methods, positive correlations between adoption and on-time delivery of project functionality and stakeholder satisfaction, and weak positive correlations with post delivery defects and project success rates.

APA, Harvard, Vancouver, ISO, and other styles

28

Wahlqvist, Daniel. "Rapid software development : ANALYSIS OF AGILE METHODS FOR APP STARTUPS." Thesis, KTH, Skolan för datavetenskap och kommunikation (CSC), 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-170572.

Full text

Abstract:

This thesis is focused on software development using so called Agile methods. The scope of research is startup companies creating consumer apps. The thesis work was performed at a Swedish app startup; Storypic/Accelit AB. An overview of current research on Agile methods is given. A qualitative case study was undertaken in four parts; 1. Observing the team 2. Testing business hypotheses 3. Interviews with the team and 4. User feedback. Analyzing the findings some conclusions are drawn:  An agile software development method is superior to a procedural one, in the context of a startup with limited time and resources.  Agile methods respond well to change.  A pragmatic, “cherry picking” approach can be a successful strategy for a startup. Finally, recommendations are given for further development.

APA, Harvard, Vancouver, ISO, and other styles

29

Arimoto, Mauricio Massaru. "Agile development of open educational resources." Universidade de São Paulo, 2016. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-31102016-103914/.

Full text

Abstract:

Over the years, the rapid advance of the computer and communication technologies has significantly changed the way in which the society communicates and conducts business. Similarly, changes have occurred in the way in which educational resources are designed, developed and made available to learners. Following this trend, the development and adoption of Open Educational Resources (OERs) has been gaining more supporters across the world, as a means to expand access to knowledge and improve education. Indeed, the free and open distribution of educational resources helps disseminate knowledge, facilitates access to information and promotes the democratisation of access to education, benefiting society as a whole. While OERs can bring benefits to, and impact on education, there are still challenges to their widespread production and adoption. One of the challenges faced by developers (including educators and practitioners) of OERs is to produce quality and relevant learning materials, capable of being reused and adapted in different contexts and learning situations. Also, there is a need for mechanisms that provide higher productivity of the development process and quality of the resulting OERs. This work aims to investigate the development of OERs and establish flexible approaches to effectively support the design and creation of these resources. In this context, an agile method for the development and sharing of OERs, named AM-OER, was established. It is grounded on practices of Software Engineering and on practices of Learning Design. Such practices are embedded in the development of OERs aiming at improving quality and facilitating reuse and adaptation. The ultimate aim of AM-OER is to support the development of quality OERs, able to motivate and guide learners in the process of knowledge construction. Preliminary empirical assessments were conducted to validate AM-OER through its application in the design and creation of courses in the free and open source software development and software testing domain. The results obtained so far have shown that the method is feasible and effective for the design and creation of OERs. Ao longo dos anos, o rápido avanço nas tecnologias computacionais e de comunicação vem alterando de forma significativa o modo com que a sociedade se comunica e conduz seus negócios. De forma análoga, mudanças vêm ocorrendo na maneira com que os recursos educacionais são projetados, desenvolvidos e disponibilizados aos aprendizes. Seguindo essa tendência, o desenvolvimento e a adoção de Recursos Educacionais Abertos (REAs) vêm ganhando cada vez mais adeptos em todo o mundo, como uma forma de ampliar o acesso ao conhecimento e melhorar a educação. De fato, a distribuição livre e aberta de recursos educacionais contribui para a disseminação de conhecimento e facilita o acesso à informação, além de promover a democratização do acesso à educação, beneficiando a sociedade como um todo. Embora REAs possam trazer benefícios e impacto sobre a educação, ainda existem muitos desafios para sua ampla produção e adoção. Um dos desafios enfrentados pelos desenvolvedores (incluindo educadores e praticantes) de REAs é produzir materiais de aprendizagem de qualidade, capazes de serem reusados e adaptados a diferentes contextos e situações de aprendizagem. Evidencia-se também a necessidade de mecanismos que propiciem o aumento da produtividade do processo de desenvolvimento e da qualidade dos REAs elaborados. Este trabalho tem como objetivo investigar o desenvolvimento de REAs e estabelecer abordagens flexíveis para apoiar efetivamente o projeto e a criação desses recursos. Nesse contexto, um método ágil para o desenvolvimento e disponibilização de REAs, AM-OER, foi estabelecido. O método é fundamentado em práticas da Engenharia de Software e práticas de projeto de aprendizagem (Learning Design), incorporadas no desenvolvimento de REAs no intuito de melhorar a sua qualidade e facilitar o reúso e adaptação. O objetivo final do método é apoiar o desenvolvimento de REAs de qualidade, capazes de motivar e guiar os aprendizes no processo de construção de conhecimento. Avaliações empíricas preliminares foram conduzidas para validar o AM-OER por meio de sua aplicação no projeto e criação de cursos nos domínios de desenvolvimento de software livre e teste de software. Os resultados obtidos até o momento demonstram que o método é viável e eficaz no projeto e criação de REAs.

APA, Harvard, Vancouver, ISO, and other styles

30

Khac, Do Nguyen. "Situated cognition and Agile software development: A comparison of three methods." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-62824.

Full text

Abstract:

Agile programming methods have become popular in software development projects. These methods increase productivity and support teamwork processes. In this thesis, we have analyzed three well-known Agile methods - Scrum, Extreme Programming and Crystal Orange - from the perspective of situated cognition to investigate how well the methods support cognition. Specifically, we looked at how the methods aid memory and attention through the use of external representations. The study suggests that the methods support different aspects of situated cognition reasonably well. However, among the investigated methods, Scrum stands out due to aspects of task representation (progress charts), its approaches to externalize what-to-do (memory), and the means to focus on the important programming tasks for the day (attention).

APA, Harvard, Vancouver, ISO, and other styles

31

Guarino, de Vasconcelos Luis Eduardo, André Yoshimi Kusumoto, Nelson Paiva Oliveira Leite, and Cristina Moniz Araújo Lopes. "Using Agile Methods for Software Development in R&D Scenario." International Foundation for Telemetering, 2015. http://hdl.handle.net/10150/596431.

Full text

Abstract:

ITC/USA 2015 Conference Proceedings / The Fifty-First Annual International Telemetering Conference and Technical Exhibition / October 26-29, 2015 / Bally's Hotel & Convention Center, Las Vegas, NV Due to the quick change of business processes in organizations, software needs to adapt quickly to meet new requirements by implementing new business rules. In Research and Development (R&D) scenario, the research is highly non-linear and changes are inevitable. In this context, it is known that traditional methodologies (e.g. waterfall) may lead to the detection of failures late, increase the time and cost of development and maintenance of software. On the other hand, agile methodologies are based on Test- Driven Development (TDD), maintain the technical debt under control, maximize the Return on Investment and reduce the risks for customers and companies. In this paper, we show the use of Scrum and TDD in the development of an experimental tool that aims to make the calibration in real time of the rudder of a fighter aircraft. The preliminary results allowed to increase the coverage testing of the software and hence the quality of the tool.

APA, Harvard, Vancouver, ISO, and other styles

32

Quea, Camila, Karla Sánchez, David Mauricio, Carlos Raymundo, and Francisco Dominguez. "Agile and sustainable methods to implement 6S in textile manufacturing MSEs." International Institute of Informatics and Systemics, IIIS, 2019. http://hdl.handle.net/10757/656358.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Varatharajah, Thujeepan. "Integrating UCD with Agile Methods : From the perspective of UX-Designers." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-262705.

Full text

Abstract:

With the increasing popularity of Agile methods in software development projects, an emerging question is how Agile incorporates user needs to their process – which is the staple of User Centered Design (UCD). Existing reports indicate that integrating Agile and UCD has shown to improve the process and end product and that they are a natural fit. However, there is also a general lack of guidelines of how an effective integration may be done, and further research is requested. This study aims to provide that by portraying some aspects of how Agile and UCD may be integrated in practice, but also some factors that may affect such an integration. This is done through an empirical study, by gaining insights from the perspective of UX-designers who are part of Scrum teams. TenUX-designers took part in semi-structured interviews, and based on a thematic analysis, results are portrayed in terms of suggested factors to consider when integrating Agile and UCD methods. Samtidigt som Agila metoder ökar i popularitet inom mjukvaruutvecklingsprojekt, så uppstår även frågan om hur Agilt arbete integrerar användarcentrerade krav i sin process ett område som är i fokus inom Användarcentrerad Design (ACD). Tillgängliga rapporter indikerar på att integrationen av Agilt och ACD har givit förbättrade processer och slutprodukt, samt att båda processer är kompatibla med varandra. Det anses dock finnas en brist på riktlinjer i hur man kan integrera båda processer, och det efterfrågas vidare studier i ämnet. Denna studie ämnar till att erbjuda just detta genom att presentera några faktorer av hur Agilt och ACD kan integreras i praktiken, men också exempel på faktorer som kan påverka hur väl integration lyckas. Detta tas fram genom en empirisk studie, genom att ta del av insikter från UX-designers som jobbar i olika Scrum projekt. Tio UX-designers deltog i semistrukturerade intervjuer, och baserat på en tematisk analys så presenteras resultat i form av föreslagna faktorer att ta del av när man vill integrera Agila och ACD metoder.

APA, Harvard, Vancouver, ISO, and other styles

34

Caron, Valentina <1994&gt. "From traditional system toward agile methods: Digital transformation challenge in Vodafone." Master's Degree Thesis, Università Ca' Foscari Venezia, 2020. http://hdl.handle.net/10579/16617.

Full text

Abstract:

L' argomento che tratterò è come le metodologie Agile sono state inserite all’interno dei processi dell'azienda Vodafone. Partendo da una panoramica generale della struttura aziendale farò un confronto con quanto affermato in letteratura al fine di contestualizzare il cambiamento di digitalizzazione, andando più in profondità per capire perché e come un'organizzazione dovrebbe applicare metodi agili. Il focus della tesi sarà sul dipartimento IT e su come Vodafone ha applicato la trasformazione digitale nel contesto agile, descrivendo la struttura del dipartimento prima e dopo al fine di individuare quali sono e saranno i rischi, le problematiche e i fallimenti connessi al cambiamento. Un punto cruciale per dare al case study una visione completa del processo di trasformazione è esaminare come cambia la governance IT rispetto a un'organizzazione tradizionale.

APA, Harvard, Vancouver, ISO, and other styles

35

Yuonan, Jacob, and Rustam Mamedov. "Agile Project Management in Banking : A study of how agile methods are modified to suit the context of a bank." Thesis, Södertörns högskola, Företagsekonomi, 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:sh:diva-40982.

Full text

Abstract:

Whilst there are studies that have been researching application of agile methods in different contexts, research have mainly been focused on the software industry. As the world becomes increasingly more digitised, the banking industry is having to keep up with this development and become more digital. Consequently, banks need to incorporate new flexible methods to keep up with the increasing demand for new digital products and features. However, the digital transformation and development processes are not as straightforward as in other industries because banks operate in regulated markets, making the application of agile methods more difficult. This study aimed to investigate and expand the knowledge of how agile methods are applied within the product developing processes in banks as well as what the challenges are with adopting such methods. Semi-structured interviews and internal documents were used to gather data regarding how a bank applies these methods. The main findings show that the bank applied agile methods and adapted them to suit their needs. Key themes identified from the data are agile framework adaptation, collaboration, motivation, and regulatory and internal challenges. The adaptation of specific frameworks is driven by the profile of the specific team as well as the nature of each project in a particular product area. Similarly, to pure agile methods, the motivation of workers is important for maximising productivity in the product development process. Internal and external collaboration was found to involve the interaction of internal teams and co-workers as well as receiving feedback from customers to improve their products. An important challenge in maximising agility is this sector is the regulatory environment in which banks operate in. The findings from this study contribute to the field by giving insight into how agile methods can be adapted in the context of banking by adding to existing literature.

APA, Harvard, Vancouver, ISO, and other styles

36

Mählberg, Esbjörn. "Agilt - men agilt nog?" Thesis, Uppsala universitet, Informationssystem, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-155302.

Full text

Abstract:

This paper aims to investigate whether a small organization with small development teams can find a value in leaving a functioning development process to follow a formal systems development methodology, if these organizations can find support in an agile systems development method and in such case the method needs to be adjusted according to the organizations unique conditions. A traditional plan-driven system development methodology includes a number of phases that are carried out sequentially and a completed phase can basically not be resumed. All requirements are specified at the beginning of a project and at the end of the project only one delivery of software take place. This can cause difficulties in for example dealing with changing requirements. Agile system development methods intend to deal with changing requirements and to enable continuous delivery of valuable, working software. In this paper, both the traditional plan-driven methods and agile methods will be explained. Research methodology and existing system development theories will be discussed and a company where the study has been conducted will be presented. The company's current work processes are analyzed and presented, and all collected data will be reviewed. The results of the paper shows that no initial adaptation of agile methods, Scrum in this specific case, needs to be implemented and that there is no evidence to suggest that small organizations with small development teams can not work after a formal agile methodology. Finally, a general discussion of the study will be conducted and conclusions whether the study objective has been achieved or not will be discussed. Denna uppsats ämnar undersöka huruvida en mindre organisation med små utvecklingsteam kan finna ett värde i att lämna en fungerande utvecklingsprocess för att följa en formell systemutvecklingsmetod, ifall dessa organisationer kan hitta ett metodstöd i agila systemutvecklingsmetoder och om metoderna i så fall behöver anpassas utefter organisationens unika förutsättningar. En traditionell plandriven systemutvecklingsmetod innehåller ett antal faser som genomförs sekventiellt och en slutförd fas kan i stort sett inte återupptas. Alla krav specificeras i början av ett projekt och endast en leverans av mjukvara sker. Detta kan medföra svårigheter med att hantera till exempel förändrade krav. Agila systemutvecklingsmetoder har för avsikt att hantera förändrade krav samt möjliggöra kontinuerliga leveranser av värdefull och fungerande programvara. Under uppsatsen kommer såväl traditionella plandrivna metoder som agila metoder att förklaras närmare. Metodval för forskningen och befintliga systemutvecklingsteorier kommer att diskuteras och ett företag där studien har bedrivits kommer att presenteras. Företagets nuvarande arbetsprocess analyseras och presenteras och alla datainsamlingar kommer att gås igenom. Resultatet av uppsatsen visar på att inga initiala anpassningar av agila metoder, Scrum i det här specifika fallet, behöver genomföras och att det inte finns något som tyder på att små organisationer med små utvecklingsteam inte kan arbeta efter en formell agil metod. Slutligen kommer en allmän diskussion om studien att föras och slutsatser gällande om syftet med studien har uppnåtts kommer att diskuteras.

APA, Harvard, Vancouver, ISO, and other styles

37

Moraes, Marcela Balbino Santos de. "RiPLE-SC: na agile scoping process for software product lines." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2322.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:56:44Z (GMT). No. of bitstreams: 2 arquivo2982_1.pdf: 2135820 bytes, checksum: df75cf5b4604b648bc295b0acd5b0db0 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010 Fundação de Amparo à Ciência e Tecnologia do Estado de Pernambuco As constantes mudanças e a busca por novos benefícios na indústria de software possibilitam o surgimento de novas áreas de pesquisa. Neste contexto, uma tendência que tem apresentado importantes benefícios é a área de desenvolvimento ágil de linhas de produtos de software. Linhas de produtos de software é uma importante estratégia de reuso para minimizar custos e tempo de entrega das aplicações, além de maximizar a qualidade e a produtividade do desenvolvimento de software. Entretanto, desenvolver linhas de produtos requer esforços e custos iniciais para apresentar resultados significativos, uma vez que envolve planejamento sistemático, gerenciamento de pontos comuns e variáveis dos produtos e design flexível e detalhado, aspectos que aumentam sua complexidade. Por outro lado, a abordagem ágil apresenta como foco o código e tem seu desenvolvimento realizado de forma iterativa. Além disso, esta metodologia encoraja práticas e valores como comunicação face a face, pequenas iterações, planejamento e design simples e incremental. Comparando linhas de produtos de software e métodos ágeis, diferentes aspectos são identificados. No entanto, pesquisas recentes mostram similaridades entre elas, como: aumento de qualidade e produtividade no desenvolvimento de software e redução de custos e tempo de entrega das aplicações. Portanto, visando diminuir custos e esforços iniciais necessários para adoção de uma linha de produtos de software, este trabalho propõe um processo de escopo ágil para linhas de produtos de software, unindo os benefícios das duas abordagens. O processo proposto é avaliado através de um estudo de caso industrial

APA, Harvard, Vancouver, ISO, and other styles

38

Islam, Mohammad Shahidul, and Sentayehu Tura. "Exploring the difference between Agile and Lean:A stakeholder perspective." Thesis, Uppsala universitet, Informationssystem, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-202724.

Full text

Abstract:

In this thesis, we have identified the difference between Agile and Lean methodsbased on stakeholder’s perspectives. To achieve the goal we have dealwith only Agile and Lean principles. In addition, in order to identify thestakeholders from Agile and Lean principles we have used the relevant practicesfrom both sides. As the principles of Agile manifesto are directly followedby most of the organizations, we have also used Agile principles directlyin this research. On the other hand lean methods have no pure principles,as a result we have used the most common and popular lean principlesderived from different authors. We have only considered the mostrelevant principles that might be useful in software development. To achievea stronger result of this thesis we have also considered stakeholder theory.Moreover we have identified the stakeholder’s involvement with Agile/Leanprinciples and stakeholder theory.

APA, Harvard, Vancouver, ISO, and other styles

39

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 text

Abstract:

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 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

APA, Harvard, Vancouver, ISO, and other styles

40

FAROOQ, USMAN, and MUHAMMAD UMAR FAROOQ. "EXPLORING THE BENEFITS AND CHALLENGES OF APPLYING AGILE METHODS IN OFFSHORE DEVELOPMENT." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5551.

Full text

Abstract:

Context: Global software development is the emerging trend in today’s world as it provides the software companies with certain advantages like access to skill and cheap labor, low development cost etc. There are also many challenges and risks involved in globally distributed software project as compare to co-located projects like communication, coordination and control etc. due to geographical separation. There is also a recent interest in applying agile methods in offshore projects in order to minimize certain offshore challenges. Agile methods in collocated environment demands high communication, coordination and collaboration between the team members. However implementing agile methods in distributed environment is beneficial and challenging too, because of inherited GSD challenges. Therefore, it is necessary to carefully understand the benefits and challenges of applying agile methods in distributed project before actually initiating the development. Objectives: This research study aims to look at current empirical evidence regarding benefits and challenges of applying agile methods in offshore projects, in order to understand it properly. Furthermore, we have examined that which of the benefits and challenges reported in literature can be seen in practice. This helped us in finding out the similarities and differences between the benefits and challenges that are reported in literature and in practice. Methods: To fulfill our aims and objectives we have first conducted the detailed systematic review analysis of the empirical studies from year 2000-2010. The systematic review approach helped us to collect and summarize the empirical data available regarding the benefits and challenges of applying agile methods in offshore projects. The research studies were identified from the most authentic databases that are scientifically and technically peer reviewed such as Inspec and Compendex, IEEE Xplore, ACM digital library, Springer Link, Science Direct, Google Scholar, Scopus, ISI Web of Knowledge and Willey Inter Science Journal Finder. Furthermore, industrial survey was conducted in order to identify whether the benefits and challenges enlisted in literature can be confirmed by practitioners. This helped us in determining the similarities and differences between benefits and challenges that are reported in empirical literature and industrial survey. Results: From systematic review results, we have found the list of benefits and challenges of most applied agile practices such as daily scrum meetings, sprint planning meetings, sprint review meetings, retrospective meetings, pair programming, short release and on-site customer. The most common benefits related to above identified agile practices are early problem identification, project visibility, increase communication, coordination and collaboration, trust, clarification of work and requirements, early client feedback and customer satisfaction. Similarly the most common challenges associated with above identified agile practices are lack of linguistic skills, culture differences and temporal differences. From survey result, it was found that the majority of benefits and challenges identified through literature review are prevalent in software industries to some extent. We were able to identify the benefits and challenges of agile practices such as daily scrum, sprint planning meetings, sprint review, retrospective meetings and short release. The most common benefits of above identified agile practices highlighted by survey participants are project visibility, early problem identification, increase coordination, opportunity for knowledge sharing and transferring, immediate feedback from client, and opportunity for understanding the task properly. Similarly the most common challenges identified by survey participants are language problems, temporal difference and difficult to explain and understand problems or issues over communication technologies. However, there are certain challenges like trust and culture issues, which have received most attention in the empirical literature, but are not identified by majority of industry respondents. Conclusions: From the information attained so far regarding the benefits and challenges of agile methods in offshore projects, we observed that there is an emerging trend of using agile methods in offshore projects and practitioners actually found it beneficial. The benefits of agile practices does not achieve straightaway there are certain challenging factors of GSD too, which can restrict the implementation or make the methodology not useful such as communication, coordination and collaboration. These challenges are usually occurred due to geographical separation, lack of trust and linguistic skills, culture difference etc. The presented work add contribution in a sense as to the best of our knowledge no systematic review effort has been done in this area with specifically focuses on highlighting the benefits and challenges. From survey results we found that majority of benefits and challenges highlighted by survey participants are to some extent same with what we have already studied in literature. However there are certain important challenges which have received most attention in empirical literature but were less identified by the survey participants like trust issue and culture difference. The benefits and challenges identified through industrial survey do not add much information into our attention. This does not mean that all possible benefits and challenges of applying agile methods in offshore project have been explored. The responses which were received from industry practitioners were quite few to make any kind of arguments. There is a probability that we missed the important benefits and challenges related to particular agile practices during our industrial survey. Therefore we conclude that a much thorough and inclusive answers should be required to identify the benefits and challenges of applying agile methods in offshore projects.

APA, Harvard, Vancouver, ISO, and other styles

41

Tonin, Graziela Simone. "Technical debt management in the context of agile methods in software development." Universidade de São Paulo, 2018. http://www.teses.usp.br/teses/disponiveis/45/45134/tde-30072018-142720/.

Full text

Abstract:

The technical debt field covers an critical problem of software engineering, and this is one of the reasons why this field has received significant attention in recent years. The technical debt metaphor helps developers to think about, and to monitor software quality. The metaphor refers to flaws in software (usually caused by shortcuts to save time) that may affect future maintenance and evolution. It was created by Cunningham to improve the quality of software delivery. Many times the technical debt items are unknown, unmonitored and therefore not managed, thus resulting in high maintenance costs throughout the software life-cycle. We conducted an empirical study in an academic environment, during two offerings of a laboratory course on Extreme Programming (XP Lab) at University of São Paulo and in two Brazilian Software Companies (Company A and B). We analyzed thirteen teams, nine in the Academy and four in the Companies environment. The teams had a comprehensive lecture about technical debt and several ways to identify and manage technical debt were presented. We monitored the teams, performed interviews, did close observations and collected feedback. The obtained results show that the awareness of technical debt influences team behavior. Team members report thinking and discussing more on software quality after becoming aware of technical debt in their projects. We identified some impacts on the teams and the projects after having considered technical debt. A conceptual model for technical debt management was created including ways of how identifying, monitoring, categorizing, measuring, prioritizing, and paying off the technical debt. A few approaches and techniques for the technical debt management, identification, monitoring, measure, and payment are also suggested. A metáfora de dívida técnica engloba um importante problema da engenharia de software e essa é uma das razões pelas quais este campo tem recebido uma grande atenção nos últimos anos. Essa metáfora auxilia os desenvolvedores de software a refletirem sobre e a monitorarem a qualidade de software. A metáfora se refere a falhas no software (geralmente causadas por atalhos para economizar tempo) que podem afetar a futura manutenção e evolução do mesmo. A metáfora foi criada por Cunningham com o objetivo de melhorar a qualidade das entregas de software. Muitas vezes as dívidas técnicas não são conhecidas, monitoradas e nem geridas, resultando em um alto custo de manutenção ao longo do ciclo de vida do software. Logo, conduziu-se um estudo empírico na academia, durante duas ofertas da disciplina de Programação Extrema (XP Lab) na Universidade de São Paulo e em duas empresas Brasileiras de desenvolvimento de software (Empresa A e B). Foram analisados treze times, sendo nove na academia e quatro nas empresas. Os times tiveram uma apresentação sobre dívida técnica e foram apresentadas algumas sugestões de abordagens para gerir dívida técnica. Monitorou-se os times, foram realizadas entrevistas, observações fechadas e informações foram coletadas. Os resultados mostraram que considerar dívida técnica influenciou o comportamento dos times. Eles reportaram que após considerar dívida técnica passaram a refletir e discutir mais a qualidade do software. Identificou-se alguns impactos nos times e nos projetos depois de considerarem dívida técnica. Um modelo conceitual para gestão de dívida técnica foi criado, incluindo formas, técnicas e abordagens de como identificar, monitorar, categorizar, medir, priorizar e pagar os itens de dívida técnica.

APA, Harvard, Vancouver, ISO, and other styles

42

Schtein, Igor A. "Management Strategies for Adopting Agile Methods of Software Development in Distributed Teams." ScholarWorks, 2018. https://scholarworks.waldenu.edu/dissertations/5417.

Full text

Abstract:

Between 2003 and 2015, more than 61% of U.S. software development teams failed to satisfy project requirements, budgets, or timelines. Failed projects cost the software industry an estimated 60 billion dollars. Lost opportunities and misused resources are often the result of software development leaders failing to implement appropriate methods for managing software projects. The purpose of this qualitative multiple case study was to explore strategies software development managers use in adopting Agile methodology in the context of distributed teams. The tenets of Agile approach are individual interaction over tools, working software over documentation, and collaboration over a contract. The conceptual framework for the study was adapting Agile development methodologies. The targeted population was software development managers of U.S.-based companies located in Northern California who had successfully adopted Agile methods for distributed teams. Data were collected through face-to-face interviews with 5 managers and a review of project-tracking documentation and tools. Data analysis included inductive coding of transcribed interviews and evaluation of secondary data to identify themes through methodological triangulation. Findings indicated that coaching and training of teams, incremental implementation of Agile processes, and proactive management of communication effectiveness are effective strategies for adopting Agile methodology in the context of distributed teams. Improving the efficacy of Agile adoption may translate to increased financial stability for software engineers across the world as well as accelerate the successful development of information systems, thereby enriching human lives.

APA, Harvard, Vancouver, ISO, and other styles

43

Modi, Sunila. "Exploring the emergence of collaborative practices in globally distributed agile software development." Thesis, Brunel University, 2018. http://bura.brunel.ac.uk/handle/2438/16368.

Full text

Abstract:

Agile software development approaches have emerged as a response to perceived frustrations of more heavyweight plan-driven methods, and have now become well established within the information systems field. More recently, there has been a tremendous growth in applying agile methods in globally distributed settings. In light of this, there is a pressing need to understand how agile practices are adapted which were originally conceived for collocated settings, and now actually being used in globally distributed settings, taking into account the challenges posed by such contexts. The aim of this thesis is to contribute to this research gap, with a quest to better understand and unpack the "black-box" of how collaborative practices evolve within global agile settings. The value of this research lies in improving and advancing our understanding of the challenges the team members go through in adapting agile practices in global contexts. The research also explores how collaborative practices can support agility in globally distributed settings. In order to contribute to knowledge and increase conceptual clarity, there is a need to carry out in-depth and in-situ research within an organisational context. By taking a socio-technical perspective this study intends to extend our existing knowledge on how collaborative practices are evolving in real-time practice within globally distributed agile settings. The empirical evidence is drawn from a globally distributed team, operating in a global financial bank with offices based in London and Delhi. Interpretive research methods including semi-structured interviews and observations are used to understand team members' experiences of developing collaborative practices in a globally distributed context. Although existing literature on agile software development acknowledges the intrinsic significance of collaboration for effective functioning of agile methods, current studies fail to demonstrate a situated practice perspective on how collaborative practices are adapted in globally distributed settings. This study enlists the analytical concepts of boundary objects and Pickering's "mangle of practice" to better understand the process of how collaborative practices evolve in globally distributed agile teams. The resulting analysis provides us with a much more nuanced understanding of how interactions take place in developing collaborative practices in globally distributed contexts. The findings reveal that collaborative practices within such settings tend not to follow from pre-set expectations of how agile practices should work, but are temporally emergent. Team members have to revise collaborative practices through an ongoing process of mutual "tuning" within their situated contexts, in order to achieve a gradual state of interactive stability or a steadiness of practices. The results demonstrate how actors address the challenges in developing shared understandings to drive forward the joint software development process across global locations and move towards supporting agility within the projects. The thesis presents a pluralistic conceptual framework called the Collaborative Tuning Approach, which aids in gaining critical insights of issues related to adapting agile practices and also demonstrates how collaborative practices can act as enabler to achieving agility in such settings. The framework explains the challenges the team members face and how these are overcome when attempting to modify practices and indeed how these evolve through an ongoing state of flux and uncertainty leading to hybrid agile practices.

APA, Harvard, Vancouver, ISO, and other styles

44

Palúch, Filip. "Zavedení agilních metod v praxi." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2019. http://www.nusl.cz/ntk/nusl-402033.

Full text

Abstract:

This diploma thesis is focused on current situation analysis of the company with particular designed change of project management. This change is aimed to set up a Scrum agile method. Basics of Scrum agile method are explained in the first chapter of this diploma thesis. Based on the knowledge gained from analitical chapter of this thesis there are designed specific changes according Scrum principles in the last chapter.

APA, Harvard, Vancouver, ISO, and other styles

45

Persson, Johan. "Communication through boundary objects in distributed agile teams : An integration of user-centered design and agile development." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-109324.

Full text

Abstract:

The use of agile methods continues to increase within software development but the agile processes do not contain the necessary steps to account for the user and realize the usability of the system. It seems it is therefore necessary to integrate the UCD methodology and agile methodology. What this integration should look like is not always apparent as the integration needs to be adapted to the specific context in each organization. Accompanied by a pre-study which identified difficulties with the integration, the current study examines how UCD specialists experience the communication through boundary objects in distributed agile teams. Furthermore the study examines how the understanding of the user is communicated to the developers in the agile teams and the potential of doing so with a design rationale. A case study was therefore performed with interviews of six UCD specialists to try to answers these questions. A content analysis was performed in relation to each research question and identified a number of themes relating to the experiences concerning; (1) communication through boundary objects, (2) how an understanding of the user is communicated, and (3) opinions of using design rationale for this purpose. Some of the conclusions drawn are that boundary objects only aim at communicating the interaction with the system, that they should be viewed as communication aids as they are not stand-alone and making them comprehensive would be even more time consuming. Furthermore, personas are not deemed fitting for communicating the understanding of the user to developers. This should instead be done by allowing developers to participate in user research.

APA, Harvard, Vancouver, ISO, and other styles

46

Neveryd, Malin. "Integrating Usability Evaluation in an Agile Development Process." Thesis, Linköpings universitet, Interaktiva och kognitiva system, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-102922.

Full text

Abstract:

Medius is a software company which provides IT-solutions that streamlines and automates business processes. The purpose with this thesis was to investigate the possibility to integrate usability evaluation in the development process of Medius software MediusFlow. How such integration would be done, and which usability evaluation methods could be used. To be able to provide a suggestion, a prestudy was conducted, this in order to get a good overview of Medius as a company as well as the development process of MediusFlow. With the prestudy as a basis, the main study was conducted, and four different usability evaluation methods were chosen. In this study, the four chosen methods were Cognitive Walkthrough, Coaching Method, Consistency Inspection and Question-Asking protocol. These usability evaluation methods were carried out, evaluated and analyzed. Based on the studies and the literature, a suggestion regarding integration of usability evaluations was made. The result from this case study was presented as a process chart, where the different phases in Medius software development process are matched together with suiting usability evaluation methods. The relevant phases and their suggested methods: Preparation phase - Cognitive Walkthrough and Coaching Method in combination with Thinking-Aloud and Interviews Hardening phase - Coaching Method in combination with Thinking-Aloud and Interviews, as well as Consistency Inspection Maintenance - Field observation This result is a part of the overall work towards a more user-centered design of the software.

APA, Harvard, Vancouver, ISO, and other styles

47

NYMAN, NICK. "Threat Awareness in Agile Environments : Creating a Developer-Driven Threat Modeling Process for Agile Software Development Teams." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-276440.

Full text

Abstract:

Agile principles for software development are now the industry standard for innovative projects. Agile is often hailed for being flexible, but there is also a commonly held 'truth' that agile principles and software security do not work well together. For this reason it is not uncommon to place all security responsibilities with a separate team, which goes against the agile principles of being team-centered and may affect flexibility or timeframe of a project. Additionally, software security is difficult and requires extensive experience and knowledge, something that varies a lot among software developers. This study presents a threat modeling process tailored for the specific needs and capabilities of the agile developer team. The process combines features of attack trees and abuser stories with other supplementary techniques in a pedagogical instruction manual to create an accessible and easy-to-get-started method intended to be driven by the developers themselves. The process has been developed through extensive review of extant threat modeling methods and the circumstances of the agile team, and trialed through user tests at an agile ITorganization in the financial services. Agila principer för mjukvaruutveckling är nu industristandard för innovativa projekt. Agila metoder hyllas ofta för sin flexibilitet men det finns också en vidspridd uppfattning att agila metoder och mjukvarusäkerhet inte går bra ihop. Av den anledningen är det inte ovanligt att säkerhetsansvar och -uppgifter drivs av en separat säkerhetsgrupp, vilket går emot de agila principerna om fokus på utvecklarteamet. Detta kan få effekter både för projektets flexibilitet och dess tidsram. Dessutom är IT-säkerhet ett svårt ämne som kräver både erfarenhet och avsevärd kunskap, något som funnits variera mycket bland mjukvaruutvecklare. Den här studien presenterar en hotmodelleringsprocess som skräddarsytts för utvecklarteamets specifika behov och styrkor. Processen kombinerar funktioner från attackträd och abuser stories med andra, komplementära tekniker i en pedagogisk instruktionsmanual för att leverera en lättillgänglig och snabbstartad metod menad att drivas av utvecklarna själva. Processen har utvecklats genom omfattande studier av etablerade hotmodelleringsprocesser, samt den agila teammiljön, och testats och vidareutvecklats genom användartester hos en agil IT-organisation inom finansbranschen.

APA, Harvard, Vancouver, ISO, and other styles

48

Dogs, Carsten, and Timo Klimmer. "An Evaluation of the Usage of Agile Core Practices : How they are used in industry and what we can learn from their usage." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4725.

Full text

Abstract:

In this thesis we investigate the usage of several agile software development methods as well as the usage of certain agile core practices. By conducting a web survey, we examine what makes these practices beneficial and what tends to make them rather less suitable for certain situations. Based on the results, we finally set up some recommendations for practitioners to reflect upon and improve their own software development process. Concerning these recommendations as well as the list of the investigated practices, we hope (and are almost sure) that there are some practices or ideas contained which are worth at least thinking about. The main findings of this thesis are: - Agile software development methods have already entered the professional market but they are still no cure-all. In many cases they also produce only middle-quality software. Nevertheless, there is – even if only little – evidence that at least XP projects meet the requirements of the customer better than traditional, non-agile methods. - For a successful software development project it is important that it has a suitable requirements engineering process, that the produced software is tested sufficiently (using automated regression testing among other types of testing), that there is a good communication between the customer and the developer side, that the risks of the project are considered, that the pros and cons of practices are considered and that processes are improved continuously. - Besides, it is important to consider the whole context when implementing a certain practice. For some contexts, certain practices do not fit for their purpose and this has to be realized. However, certain shortcomings of a specific practice might be reduced or even eliminated if implemented in combination with other practices.

APA, Harvard, Vancouver, ISO, and other styles

49

Gabrielsson, Linnea, and Zanwer Hasan. "The Influence of Agile Project Management on Knowledge Sharing in a Team : A Study Conducted at an Engineering Consultancy Firm." Thesis, KTH, Fastigheter och byggande, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-255857.

Full text

Abstract:

Several studies have been conducted regarding the importance of knowledge managementwithin an organization. Furthermore, due to the successful outcome of the implementation ofagile project management approaches within the IT-sector, they have been implemented inother sectors as well. The purpose of this master thesis is to examine how agile projectmanagement influences knowledge sharing within a project team in an engineeringconsultancy firm.The study was conducted through a qualitative approach at a Swedish engineeringconsultancy firm. Data was gathered from observations of project meetings and interviewswith consultants involved in projects that have implemented agile methods. Moreover,interviews were conducted with external experts with expertise in agile project managementin order to obtain additional perspective. Semi-structured interviews were conducted withmodified questions for consultants and agile experts. Thereafter, the empirical findings wereinterpreted by the theoretical concepts in order to sum up the report with conclusions.Firstly, the study confirmed that the implemented agile methods influence explicit knowledgesharing whereas the tacit knowledge sharing is not enabled sufficiently within a project team.Secondly, it could be concluded that the implemented agile methods influence projecttransparency, team-collaboration and communication. This positive influence enablesknowledge sharing within a project team. Lastly, the conducted research concluded that agilemethods influence consultants to share knowledge due to the nature of required inputs inthese methods. Since tacit and explicit knowledge sharing and its documentation is equallyimportant for the success of a project and the consultancy company subsequently, thisresearch has concluded that a hybrid of traditional management approaches and agile methodsis essential to share and document both types of knowledge for alike consultancy firms.Consequently, the research findings resulted in recommendations which aim to improve theprocess of creating and implementing a hybrid of management approaches. Flera studier har genomförts avseende betydelsen av kunskapshantering inom en organisation.Som en följd av flera framgångsrika resultat av implementerade metoder inom agilaprojektledning inom IT-sektorn har dessa metoder även börjat implementeras i andra sektorerSyftet med detta examensarbete är att undersöka hur agil projektledning påverkarkunskapsdelning i ett projektteam i ett tekniskt konsultföretag.Studien genomfördes med ett kvalitativt tillvägagångssätt vid ett tekniskt konsultföretag iSverige. Data samlades genom observationer av projektmöten och intervjuer med konsultersom deltar i projekt där agila metoder har implementerats. Dessutom genomfördes intervjuermed externa experter med kompetens inom agil projektledning för att få ytterligareperspektiv. Semi-strukturerade intervjuer genomfördes med modifierade frågor för konsulteroch agila experter. Därefter tolkades de empiriska resultaten med de teoretiska koncepten föratt sammanfatta studien med slutsatser.För det första konstaterade studien att de implementerade agila metoderna påverkar denexplicita eller uttalade kunskapen medan den underförstådda eller tysta kunskapsdelningeninte påverkas tillräckligt inom ett projektteam. För det andra kan det konstateras att deimplementerade agila metoderna påverkar ett projekts transparens, samarbetet i ett team ochkommunikation. Detta positiva inflytande möjliggör en kunskapsdelning inom ettprojektteam. Slutligen konstaterade studien att agila metoder påverkar konsulternas vilja attdela med sig av kunskap på grund av metodernas karaktärer vilka fordrar input. Eftersom tystoch explicit kunskapsdelning är lika viktiga för ett projekts framgång har den härundersökningen dragit slutsatsen att en hybrid av traditionell projektledning och agila metoderär avgörande för att upprätthålla båda typerna av kunskapsdelning för konsultföretag avlikadant slag. Forskningsresultaten resulterade följaktligen i rekommendationer som syftar tillatt förbättra processen att skapa och genomföra en hybrid av projektledningsmetoder.

APA, Harvard, Vancouver, ISO, and other styles

50

Nuottila, J. (Jouko). "Flexibility in agile projects:contracting practices and organisational arrangements." Doctoral thesis, Oulun yliopisto, 2019. http://urn.fi/urn:isbn:9789526224190.

Full text

Abstract:

Abstract The adoption of agile methods in software projects has been fast. The majority of new software projects utilises agile methods, and they have radically changed the internal dynamics of software development projects. This has created a need for adjustments in the management of software projects. The current literature rarely discusses the early phases of agile projects: contracting and organising agile projects. The literature also lacks investigations on the project management practices of agile projects. This dissertation focuses on flexibility as it occurs in agile software projects. The main objective of this research is to explore the nature of flexibility in agile software projects and study the challenges of project contracting and management in leveraging agile development methods. The research was conducted as a mixed methods research. The research findings contribute to the emerging literature on agile project management. Secondarily, the results contribute to proactive contracting literature. The results indicate that agile methods can be used to increase flexibility and efficiency in software projects, but flexibility needs to be planned by projects parties. This planning activity already starts in the negotiation phase, and it is optimally summarised in the project contract. Thus, it is also important that lawyers contributing to project contracts are aware and informed of the business contexts. The traditional project management approach needs adjustments in adopting agile practices. This research reports several categories of challenges faced in adopting agile practices and increasing flexibility in projects. The results also indicate that projects delegate part of the decision-making authority to implementation teams in order to increase flexibility. By taking some of the decisions closer to project implementation, flexibility can be used to manage uncertainties caused by a complex environment Tiivistelmä Ketterien kehitysmenetelmien käyttö ohjelmistoprojekteissa on yleistynyt nopeasti. Suurin osa alkavista ohjelmistoprojekteista käyttää jo ketteriä menetelmiä ja niiden soveltaminen on muuttanut radikaalisti kehitysprojektien sisäistä dynamiikkaa. Tämän vuoksi on syntynyt tarve tarkastella tarkemmin ketterien projektien johtamista. Kirjallisuudessa on harvoin tarkasteltu ketterien projektien alkuvaiheita, sopimuskäytäntöjä ja organisoitumista. Kirjallisuudessa ei myöskään vielä käsitellä ketterien projektien projektinhallinnan käytänteitä. Tämä väitöskirjatutkimus tarkastelee joustavuutta, joka ilmenee ketterissä ohjelmistoprojekteissa. Työn päätavoite on tarkastella joustavuuden luonnetta ketterissä ohjelmistoprojekteissa ja tutkia mitä haasteita ketterien menetelmien käyttö aiheuttaa projektin sopimusprosesseissa ja projektinhallinnassa. Väitöskirjatutkimus on toteutettu monimetelmätutkimuksena. Tutkimustulokset kohdistetaan tuoreeseen tieteelliseen projektitutkimuksen keskusteluun ketteristä projektinhallintamenetelmistä. Toisekseen, väitöskirja osallistuu ennakoivaa sopimista käsittelevään oikeustieteellisen tutkimusalan keskusteluun. Tutkimustulokset osoittavat, että ketteriä menetelmiä voidaan käyttää lisäämään joustavuutta ja tehokkuutta ohjelmistoprojekteissa, mutta joustavuus tulee olla suunniteltua, jotta siitä voidaan hyötyä. Joustavuuden käytön suunnittelu alkaa jo projektin neuvotteluvaiheessa ja kirjaukset joustavuuden hyödyntämisestä on optimaalisesti kirjattu jo projektisopimukseen. Tämän vuoksi on tärkeää, että sopimuksen muotoiluun osallistuvat juristit ovat hyvin perillä liiketoiminta-alasta ja ovat tietoisia, että sopimus tulee sisältämään joustavuusnäkökohtia tarkoituksellisesti. Perinteinen projektinhallinta kaipaa myös muutoksia ketterien projektien johtamiseen. Tutkimus osoittaa seitsemän pääkategoriaa haasteita, joita yritykset kohtaavat siirtyessään käyttämään ketteriä menetelmiä. Tutkimus osoittaa myös, että ketterissä projekteissa päätöksenteko on joustavuuden lisäämiseksi hajautettu itseohjautuville tiimeille. Kun päätöksentekovaltaa siirretään lähemmäs varsinaista kehitystyötä, voidaan joustavuuden avulla hallita epävarmuutta kompleksissa ympäristössä

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'Agile methods'

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles