Dissertations / Theses: 'And Scrum'

1

Custódio, Pedro Miguel Caiado. "Scrum para lean : como tornar o scrum mais lean." Master's thesis, Instituto Superior de Economia e Gestão, 2015. http://hdl.handle.net/10400.5/10342.

Full text

Abstract:

Mestrado em Gestão de Projetos
A aplicação do conceitos lean na gestão de projetos de desenvolvimento de software tem vindo a despertar cada vez mais o interesse dos gestores de projeto, dadas as evidências apresentadas na literatura de como estes conceitos conseguem aumentar o desempenho dos projetos, reduzindo custos, ao mesmo tempo que geram mais valor para os clientes. As experiências que reportam a aplicação destes conceitos, comparam a aplicação do lean com as metodologias ágeis de gestão de projetos de software, denominadas como agile, indicando as suas limitações e como o lean pode contribuir para a eliminação ou redução das mesmas. Este estudo trás uma abordagem diferente dado que a investigação foca-se em como a aplicação dos conceitos lean consegue contribuir para a evolução de uma metodologia ágil de gestão específica, o Scrum. Para tal, foram identificados quais os princípios e conceitos que atualmente os praticantes de Scrum já aplicam, e com que resultados. Com a análise dos resultados obtidos conclui-se que há conceitos lean que, quando corretamente aplicados, conseguem contribuir positivamente para a evolução do Scrum.
The application of lean concepts in software development project management has been increasingly arouse the interest of project managers, given the evidence presented in literature that show how these concepts can increase projects performance, reducing costs at the same time that generate more value for customers. The experiences that report on the application of these concepts, compare the application of lean with Agile project management, presenting their limitations and how lean can help to eliminate or reduce them. This study brings a different approach as the research focuses on how the application of lean concepts can contribute to the evolution of one specific agile methodology, Scrum. To do this, the principles and concepts that Scrum practitioners currently apply and with what results were identified. The results analysis shows that there are lean concepts that, when properly applied, can contribute positively to the evolution of Scrum.

APA, Harvard, Vancouver, ISO, and other styles

2

Stenehall, Johan, and Solmaz Rahmani. "Mjukvaruprojekt och konsekvenserna av Scrum." Thesis, Linköping University, Department of Computer and Information Science, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-51828.

Full text

Abstract:

Under sent 1990-tal började utvecklare att bli mer och mer missnöjda med rådande arbetsformer i projekt. Utvecklarna upplevde att modeller som vattenfallsmodellen inte längre speglade verkligheten för utvecklingen. Detta missnöje resulterade i att en mängd nya arbetsmodeller uppstod och 2001 samlades de under Agile Manifesto. Agile lägger tyngdpunkten på individfokus, fungerande mjukvara, kundsamarbete och föränderlighet. Scrum är just nu ett av de mest populära ramverken inom agile.Tieto har använt sig av agile och då främst Scrum i sina projekt sedan tidigt 2000-tal och haft lyckat resultat. Projekten som använt Scrum har levererat i tid och haft nöjda kunder. Dock har Tieto inte utrett vilka konsekvenser Scrum får för ett projekt. Denna studies fokus låg på att undersöka konsekvenserna av att använda Scrum i ett projekt. Detta gjordes med hjälp av intervjuer, observationer och en enkät där arbetet för ett antal Scrum-projekt studerades. Resultatet jämfördes sedan med rådande litteratur inom ämnet samt studier från The Standish group, VersionOne och Yahoo!.Rapportens slutsats är att Scrum påverkar mer än bara arbetssättet och att dessa effekter måste betänkas. Många positiva konsekvenser av användandet av Scrum kunde ses men även ett antal risker upptäcktes. För ett lyckat Scrum-projekt behövs en delaktig produktägare, en engagerad ScrumMaster och ett team som tycker om att ta eget ansvar.

During the late 1990s, developers became more and more dissatisfied with the current way of working in the projects. Developers felt that models such as the waterfall model did not reflect the reality of how software development works in practice. This dissatisfaction led to the development of new models and in 2001 they gathered under the same name in the Agile Manifesto. Agile focuses on working software, customer collaboration and variability. Scrum is currently one of the most popular frameworks in agile.Tieto has implemented agile and particularly Scrum in their projects since early 2000 and have had success. The projects that used Scrum delivered on time and had satisfied customers. However Tieto has not investigated the impact Scrum has on projects. This study focus was on examining the consequences of using Scrum in a project. This was done through interviews, observations and a survey in which the work of a number of Scrum projects were studied. The result was then compared with the current literature in the subject, and studies by The Standish Group, VersionOne and Yahoo!.The report concludes that Scrum affects more than just the way of working and that these effects must be taken under consideration. Many positive consequences of the use of Scrum could be seen but also a number of risks were detected. For a successful Scrum project one needs an involved product owner, a committed ScrumMaster and a team that likes to take responsibility.

APA, Harvard, Vancouver, ISO, and other styles

3

Börjesson, Johan, and Kim Ehrenpohl. "Scrum i ett småskaligt projekt." Thesis, Uppsala universitet, Institutionen för informatik och media, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-229799.

Full text

Abstract:

Den agila utvecklingsmetoden scrum är en erkänd metodik inom systemutveckling som möjliggör noggrann utvärdering, testning och iteration inom utvecklingsprojekt. Scrum appliceras i projekt där scrumteamet normalt består av 3-9 personer. Vi presenterar i detta examensarbete resultat från en deltagande observation i ett småskaligt, tidsintensivt utvecklingsprojekt. Vi beskriver konsekvenserna av att med ett team bestående av två personer applicera scrum i ett utvecklingsprojekt med scrumartefakter såsom sprinter, dagliga scrummöten och produktbackloggar.

APA, Harvard, Vancouver, ISO, and other styles

4

Wallström, Alexander, and Jonas Svensson. "Scrum - införandet i en projektorganisation." Thesis, Högskolan i Borås, Akademin för textil, teknik och ekonomi, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-10273.

Full text

Abstract:

Målet med examensarbetet är att ta reda på förutsättningarna för att implementera Scrum i en projektorganisation. Arbetet går alltså ut på att ta reda på hur en projektorganisation skulle kunna göra när de börjar arbeta med Scrum och vad det skulle kunna få för effekter. Arbetet görs hos Swisslog, en projektorganisation som figurerar i hela världen med kontor i Göteborgsområdet. För examensarbetet är Swisslog endast ett exempelföretag, målet är att se hur det kan införas även på andra projektorganisationer. Till en början utfördes intervjuer med relevant personal inom exempelföretaget samt en form av benchmarking, då besök hos tre andra organisationer med liknande problemställningar gjordes. Intervjuerna var semistrukturerade, och ett antal frågor utformades, frågorna var inte likadana till alla tre företag då de har nått helt olika framgång med sitt Scrumarbete. Det första företaget hade jobbat med Scrum i ca ett år men utan framgång, här kretsade frågorna mest kring hur och varför de inte lyckats fullt ut med sitt Scrumarbete. Det andra företaget hade jobbat med Scrum i ett flertal år och gått igenom hela den fasen som företag nummer ett var mitt uppe i, här kretsade frågorna mer kring vad som har varit de viktigaste faktorerna till att de lyckats så bra med Scrum. Företag nummer tre var ett konsultbolag där vi träffade en organisationskonsult som var specialiserad på agilt förbättringsarbete och Scrum. Vid tiden för detta besök fanns en ganska klar uppfattning om vad Scrum innebar och hur arbetet med Scrum sker. Intervjun gick mer ut på att få tankar bekräftade och få lite tips om hur vi skulle kunna gå vidare. Scrum har visat sig vara ett effektivt verktyg för att leda samt planera flera olika projekt. Det har dock visat sig att detta skulle innebära en stor förändring för företagen då de i dagsläget jobbar med projekten i slutna grupper. Projektorganisationerna skulle behöva lägga stor vikt på att utbilda personalen i hur arbetet med Scrum ska genomföras, då det i dagsläget endast är ett utbrett arbetssätt inom IT-sektionerna. Det har visat sig att Scrum skulle kunna vara ett effektivt verktyg att arbeta med inom projektorganisationer för de gör det lättare att samköra flera projekt med delade resurser istället för att låta varje projekt köras enskilt. Scrum har visat sig vara ett effektivt verktyg vid själva utförandet av projekten, då det ger en väldigt överblickande bild av hur projektet fortgår. Många av Scrumartefakterna kan direkt användas inom en projektorganisation, till exempel kan backloggen direkt översättas till en "att göra lista" där alla projektets delmoment finns specificerade. Under arbetets gång har det inte funnits särskilt många avgränsningar men en stor avgränsning som gör att vi inte kan utvärdera själva implementationen är tid. Projektorganisationer är överlag inte vana vid att använda sig av Scrum och kräver därför mycket utbildning, det kommer garanterat även ta lång tid vid själva implementeringen och därav kan vi inte verkställa våra resultat.

APA, Harvard, Vancouver, ISO, and other styles

5

Danielsen, Nils, and Maximilian Fritsch. "Platsoberoende Scrum-utveckling : - En fallstudie." Thesis, Luleå tekniska universitet, Institutionen för system- och rymdteknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-86168.

Full text

Abstract:

Syften med denna uppsats är att kartlägga hur utvecklare upplever platsoberoende scrum-utveckling, vilken problematik som uppstår samt om effektiviteten påverkas. För att uppnå studiens syfte och besvara de frågeställningar som formulerats i rapporten har data samlats in. Denna data har dels varit kvantitativ, där data har samlats in från en verksamhet som bedriver systemutveckling med metodiken scrum. Data har även varit kvalitativ där data i form av intervjuer har samlats in. Den insamlade datan har sedan analyserats för att kunna svara på forskningsfrågorna. Efter genomförd analys har slutsatser dragits för att kunna uppfylla uppsatsen ursprungliga syfte. Den insamlade empirin tyder på att det finns viss problematik relaterad till kommunikation som blir tydlig när arbetet bedrivs platsoberoende. Den insamlade datan tyder även på en försämrad upplevelse av den sociala miljön när arbetet bedrivs platsoberoende. Slutligen tyder även det analyserade resultatet på en minskad effektivitet när arbetet övergått till platsoberoende. Det teoretiska ramverket ligger som grund för att redogöra för befintliga teorier som är relevanta för undersökningen. Rapporten redogör för befintliga teorier som är relaterade till platsoberoende arbete, agil utveckling, scrum utveckling samt hur effektivitetet av scrum-utveckling kan mätas.
The purpose of this thesis is to map how individuals experience remote scrum development, what problems arise and whether efficiency is affected. In order to achieve the purpose of the study and answer the research-questions formulated in the report, data has been collected. This data has been partly quantitative, where data has been collected from a business that conducts system development with the methodology scrum. Data has also been qualitative where data in the form of interviews have been collected. The collected data has then been analyzed in order to answer the research questions. After completing the analysis, conclusions have been drawn in order to fulfill the thesis' original purpose. The collected empirical evidence indicates that certain problems related to communication become clear when the work is conducted remote. The data collected also indicates a deteriorating experience of the social environment when the work is conducted remote. Finally, the analyzed result also indicates a reduced efficiency when the work has shifted to remote. The theoretical framework is the basis for presenting existing theories that are relevant to the study. The report describes existing theories that are related to site-independent work, agile development, scrum development and how the effectiveness of scrum development can be measured.

APA, Harvard, Vancouver, ISO, and other styles

6

Cifuentes, Vargas Tim. "Mobilt säljstöd utvecklat med scrum." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-134534.

Full text

Abstract:

Det här är ett examensarbete gjort på uppdrag av Gastrogate AB. Målet med examensarbetet är att utvärdera projektmetodiken Scrum i en grupp med endast en utvecklare. För att undersöka detta applicerades metoden genom att utveckla ett mobilt säljstöd i from av en mobilapplikation. Under projektet förarbete beslutades det att applikationen skulle byggas för iPad i Objective-C. Projektmetodiken anpassades för en projektgrupp med endast en utvecklare. Tillexempel hölls inga dagliga möten och rollen Scrum master tilldelades utvecklaren. Arbetet delades upp i tre sprintar. I början av varje sprint hölls ett möte där implementerad funktionalitet visades upp och reflekterades över. Under mötet planerades även den efterföljande sprinten. Resultatet av studien visar att det är möjligt att genomföra projekt med metodiken Scrum även om projektgruppen är väldigt liten. Flera av Scrums fördelar kan ändock tillgodoräknas. En grupp bestående av endast en utvecklare är dock i minsta laget och fördelarna med Scrum blir sannolikt fler om gruppen består av åtminstone två utvecklare.

APA, Harvard, Vancouver, ISO, and other styles

7

Forsö, Olle, and Filip Erić. "Scrum och utmaningar : En kvalitativ studie om vilka utmaningar praktiserande står inför agila arbetsmetoden Scrum." Thesis, Linnéuniversitetet, Institutionen för informatik (IK), 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-66887.

Full text

Abstract:

Agila arbetsmetoder bygger på iterativ utveckling och snabba leveranser. Dennakandidatuppsats har genomförts mot praktiserande som har erfarenhet av att arbeta enligt agila arbetsmetoder. Då IT-projekt misslyckas i stor omfattning och kritik riktas mot Scrum är temat för denna uppsats aktuell. Syftet med studien var att undersöka vilka utmaningar praktiserande står inför när dearbetar enligt den agila arbetsmetoden Scrum. För att undersöka detta genomfördes enkvalitativ datainsamling i form av intervjuer på fem deltagare som har erfarenhet av att arbeta med Scrum. Kategoriseringar gjordes utifrån empirin och teorin har sedan förstärktdessa kategoriseringar. Undersökningen kom fram till att praktiserande av Scrum stod inför utmaningar inom Agil definition och Scrum, att samarbeta enligt Scrum samt resultat och målbild.
Agile methods are based on iterative development and fast delivery. This essay has beenconducted against practitioners who have experience working in accordance with agilemethods. As IT projects fail to a large extent and criticism is directed against Scrum,makes the topic of the essay relevant. The purpose of the study was to investigate the challenges that practitioners face when they work according to the agile method Scrum. To investigate this, a qualitative data collection was conducted by interviewing five respondents who have experience working with Scrum. Categorizations were made based on empirical theory, and the theory has then reinforced these categorizations. The investigation found that practitioners face challenges that can be divided into agile definition and Scrum, cooperation according to Scrum, as well as results and goals.

APA, Harvard, Vancouver, ISO, and other styles

8

Backlund, Johan, and Johan Eriksson. "Vad innebär övergången till Scrum? : En studie som undersöker hur Scrum påverkar systemutvecklingsarbetet i globala organisationer." Thesis, Umeå universitet, Institutionen för informatik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-79512.

Full text

Abstract:

Currently many organizations are transitioning from the traditional approach to the agile approach regarding systems development methods. It is evident that research has mainly focused on smaller organizations transitioning, whilst less focus has been given t0 larger organizations. We find this interesting and the purpose of this study is to gain a deeper and broader knowledge concerning the following research question: How is system development work affected by a change from traditional system development methods to Scrum in large global organizations. We also investigate how Scrum can be adapted to complex projects with an internal client. The study is based on a case study, which takes a qualitative approach with semi-structured interviews for information gathering and was conducted on a major Swedish telecom company. The company initiated the transition process approximately two years ago, with the transition still ongoing. The study indicates that the main reason for adopting the agile way of working was to optimize the development process by enhancing the effectiveness. Furthermore additional effects that were gained due to the change, for example a higher grade of team spirit and a more transparent development process. Furthermore we identified where the organization had made changes on the method, Scrum, this due to different reasons such as company size and the complex nature of the projects. Finally, the study showed that even though an organization choose to embrace agile methods, the practical context in which it is introduced can lead to it being adapted to the point where it deviates from its most central theoretical underpinnings.

APA, Harvard, Vancouver, ISO, and other styles

9

Calmstierna, Alma. "Framgångsfaktorer för användning av Scrum inom Scrum-team i ett konsultföretag : En fallstudie inom ÅF Karlstad." Thesis, Karlstads universitet, Handelshögskolan (from 2013), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-73260.

Full text

Abstract:

Det har funnits problem med systemutvecklingsprojekt som använder agila utvecklingsmetoder, vilka har misslyckats genom att exempelvis bli försenade och senare komma att kräva dyrt underhållsarbete. Scrum är en agil systemutvecklingsmetod som är den mest använda på marknaden. För att organisationer ska lösa problem med det mänskliga arbetet i grupp, hur de ska arbeta och vilka regler de ska ha, behöver de anpassa sig och förstå hur de ska tillämpa Scrum-ramverket, för att bli mer smidiga och stabila som de strävar efter med Scrum-metoden. Det finns oerhört många utmaningar med Scrum-metoden och därför behöver framgångsfaktorer identifieras för Scrum-användandet. Syftet med denna kandidatuppsats i informatik är att identifiera framgångsfaktorer för användning av Scrum inom Scrum-team i ett konsultföretag. I kandidatuppsatsen tillämpades fallstudiemetoden, eftersom relationer undersöks i uppsatsstudien och metoden är lämplig för det. Fallföretaget är konsultföretaget ÅF som arbetar med Scrum för systemutveckling. Uppsatsstudien genomfördes med stöd av ett sonderande samtal, semi-strukturerade intervjuer och en ostrukturerad observation med Scrum-projektmedlemmar på ÅF. Slutsatserna av uppsatsstudien är att det finns flera viktiga framgångsfaktorer för ett lyckat användande av Scrum. De viktigaste visade sig vara Engagemanget, som måste vara högt hos både individerna i Scrum-teamet, ledningen och kund för att Scrum-arbetet ska bli bra. Samarbetet måste fungera inom Scrum-teamet och med kunden. Även Kommunikationen behöver fungera bra, genom ansikte mot ansikte och olika kommunikationskanaler. Ytterligare en framgångsfaktor som identifierades är Förändringsbenägenhet, att individerna i Scrum-team ska vara öppna för förändring och kunna anpassa sitt arbete efter situationen, samt vara en lagspelare.

APA, Harvard, Vancouver, ISO, and other styles

10

Kawamoto, Sandra. "Scrum-DR: uma extensão do framework Scrum aderente ao CMMI-DEV utilizando técnicas de Design Rationale." Universidade de São Paulo, 2017. http://www.teses.usp.br/teses/disponiveis/3/3141/tde-12032018-153055/.

Full text

Abstract:

Os métodos ágeis introduziram uma nova abordagem de desenvolvimento de software, enfatizando os indivíduos, o produto e a comunicação. Prometem alta satisfação do cliente, baixo índice de erros, tempo de desenvolvimento mais rápido e uma solução para a rápida mudança de requisitos. Por outro lado, modelos de qualidade de software, como o CMMI, prometem previsibilidade, estabilidade e segurança, melhorando a qualidade dos produtos e dos processos da empresa. O intuito desta pesquisa é unir estas duas abordagens na tentativa de aproveitar as vantagens de ambas. Como resultado, apresenta-se o framework Scrum-DR, uma extensão do Scrum, aderente às diretrizes do CMMI-DEV na categoria Suporte. O Scrum-DR possui características do desenvolvimento ágil de software e contempla a utilização de técnicas de Design Rationale, apresentando um modelo que soluciona uma importante questão nas metodologias ágeis.
Agile methods introduced a new approach to software development, emphasizing individuals, product, and communication. They promise high customer satisfaction, low error rates, faster development time and a solution for rapidly changing requirements. On the other hand, software quality models, such as CMMI, promise predictability, stability and security, improving the quality of the company\'s products and processes. The purpose of this research is to link these two approaches in an attempt to take advantage of both. As a result, the Scrum-DR framework, a Scrum extension, adhering to the CMMI-DEV guidelines in the Support category is presented. Scrum-DR has characteristics of agile software development and contemplates the use of Design Rationale techniques, presenting a model that solves an important issue in agile methodologies.

APA, Harvard, Vancouver, ISO, and other styles

11

Servadei, Giacomo. "The Scrum approach to software development." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2015. http://amslaurea.unibo.it/8255/.

Full text

Abstract:

Agile methodologies have become the standard approach to software development. The most popular and used one is Scrum. Scrum is a very simple and flexible framework that respond to unpredictability in a really effective way. However, his implementation must be correct, and since Scrum tells you what to do but not how to do it, this is not trivial. In this thesis I will describe the Scrum Framework, how to implement it and a tool that can help to do this. The thesis is divided into three parts. The first part is called Scrum. Here I will introduce the framework itself, its key concepts and its components. In Scrum there are three components: roles, meetings and artifacts. Each of these is meant to accomplish a series of specific tasks. After describing the “what to do”, in the second part, Best Practices, I will focus on the “how to do it”. For example, how to decide which items should be included in the next sprint, how to estimate tasks, and how should the team workspace be. Finally, in the third part called Tools, I will introduce Visual Studio Online, a cloud service from Microsoft that offers Git and TFVC repositories and the opportunity to manage projects with Scrum. == Versione italiana: I metodi Agile sono diventati l’approccio standard per lo sviluppo di software. Il più famoso ed utilizzato è Scrum. Scrum è un framework molto semplice e flessibile che risponde ai cambiamenti in una maniera molto efficace. La sua implementazione deve però essere corretta, e visto che Scrum ci dice cosa fare ma non come farlo, questo non risulta essere immediato. In questa tesi descriverò Scrum, come implementarlo ed uno strumento che ci può aiutare a farlo. La tesi è divisa in tre parti. La prima parte è chiamata Scrum. Qui introdurrò il framework, i suoi concetti base e le sue componenti. In Scrum ci sono tre componenti: i ruoli, i meeting e gli artifact. Ognuno di questi è studiato per svolgere una serie di compiti specifici. Dopo aver descritto il “cosa fare”, nella seconda parte, Best Practices, mi concentrerò sul “come farlo”. Ad esempio, come decidere quali oggetti includere nella prossima sprint, come stimare ogni task e come dovrebbe essere il luogo di lavoro del team. Infine, nella terza parte chiamata Tools, introdurrò Visual Studio Online, un servizio cloud della Microsoft che offre repository Git e TFVC e l’opportunità di gestire un progetto con Scrum.

APA, Harvard, Vancouver, ISO, and other styles

12

Srirangarajan, Ananth Lall Pradeep Umphress David A. "The scrum process for independent programmers." Auburn, Ala, 2009. http://hdl.handle.net/10415/1617.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Burzala, Matúš. "Nasazení metodiky SCRUM při vývoji software." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2021. http://www.nusl.cz/ntk/nusl-444610.

Full text

Abstract:

Diplomová práca sa zaoberá porovnaním metodiky použitej na projekte vývoja software a metodiky SCRUM. V rámci práce sú zmapované všetky role, udalosti a artefakty projektu u ktorých sú následne identifikované ich odlišnosti od definície metodiky SCRUM. Práca ďalej obsahuje návrh toho, čo je potrebné upraviť, alebo zmeniť, aby sa dosiahla správna aplikácia metodiky SCRUM a tým pádom aj optimalizácia vývojového procesu.

APA, Harvard, Vancouver, ISO, and other styles

14

Mtango, Prosper. "Using Scrum in offshore software projects." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-67518.

Full text

Abstract:

Due to its growth at exponential rate offshore software development has become a common way of producing software by software organizations from highly industrialized countries in Europe and North America. Previous studies have revealed that some of these organizations use agile project management frameworks in managing and running their offshore software projects. Blending agile principles and offshore software development appears to raise a contradiction as the two notions have opposite characteristics. This research focuses the implementation of agile project management frameworks such as Scrum in offshore software projects. The research project was performed by reviewing relevant literature and analyzing the results obtained from the interviews conducted to Cambio Healthcare Systems AB, a Swedish software company that offshore its software projects with Creative Technologies Pty Ltd located in Sri Lanka. The interviews were conducted to Swedish based staff involved in offshore software projects with their Sri Lankan partners. The research findings indicate that offshore software development is a challenging business and requires close monitoring to minimize its challenges. Some of the challenges include dispersion, loss of communication richness and cultural differences between the parties involved. Moreover even though the agile project management frameworks and offshore software development principles differ in nature, the findings have revealed that software organizations such as Cambio make use of these differences to minimize the challenges they face in their respective offshore software projects. The main conclusions drawn from this research is that there is not much evidence that the application of agile project management frameworks such as Scrum is feasible enough to combat the challenges. This research suggests for further research studies to collect information from staff in both offshore and onshore sites in order to formulate enough evidence on whether to apply these strategies or not.

APA, Harvard, Vancouver, ISO, and other styles

15

Sousa, Fátima Carina Gonçalves. "Utilização do modelo SCRUM na Megasis." Master's thesis, Instituto Superior de Economia e Gestão, 2018. http://hdl.handle.net/10400.5/20214.

Full text

Abstract:

Mestrado em Gestão de Sistemas de Informação
O presente Trabalho Final de Mestrado tem como objetivo descrever todas as atividades desenvolvidas durante a realização do estágio curricular no Centro de Business Intelligence da Megasis/TAP IT, colocando em prática e consolidando conhecimentos adquiridos ao longo do mestrado. Aborda um conjunto de atividades que permitem a automatização de vários processos manuais associados ao modelo Agile de desenvolvimento de software e dá também a conhecer como é aplicada a metodologia Scrum num departamento de Business Intelligence. O relatório começa por dar conta da revisão da literatura explicando o que é o scrum, quem são os participantes e quais as coreografias. De seguida, são descritas as atividades desenvolvidas no estágio, desde o enriquecimento do modelo de dados de scrum com novos conceitos como também a criação de relatórios e dashboards, sendo estes o output final da solução de BI. É feita uma análise critica comparando a literatura existente e as atividades do estágio assim como uma apreciação pessoal sobre as mesmas. As atividades são descritas e acompanhadas com o anexo de imagens dos vários dashboards criados.
The purpose of this master's Report is to describe all the activities developed during the internship at the Megasis/TAP IT Business Intelligence Center, putting into practice and consolidating knowledge acquired through out the master's program. It addresses a set of activities that allow the automation of several manual processes associated with the Agile model of software development. It also shows how the Scrum model is applied in a Business Intelligence Department. The literature review describes topics such scrum, the participants and the events. What it comes next is the description of the activities of the internship, the enrichment of the model of scrum with new concepts and last the dashboards and reports that are the BI final solution output. A critical analysis, as well as a personal assessment, is made comparing the existing literature and the internship activities. The activities are described and accompanied by image attachments of the various dashboards created.
info:eu-repo/semantics/publishedVersion

APA, Harvard, Vancouver, ISO, and other styles

16

Fakih, Israa, and Christilinda Göstasson. "Upplevda problem med projektstyrningsmetoden Scrum i systemutvecklingsprojekt : En studie av Scrums-relaterade problem hos IT- företag i Borlängeregion." Thesis, Högskolan Dalarna, Informatik, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:du-10209.

Full text

Abstract:

Många projekt misslyckas och en av anledningarna är dålig styrning av projektet i allmänhet och inom IT branschen i synnerhet. Baserad på kritik av de traditionella metoderna under de senaste åren, så har det uppkommit flera lättrörliga metoder som kallas Agila metoder. Scrum är den mest kända Agila metoden som används idag. Metoden lovar goda resultat, men i en artikel ur tidningen Computer Sweden (feb 2009) står det ”siffror visar att nio av tio Scrumprojekt misslyckas”. Artikeln triggade vårt intresse av att ta reda på vilka problem specifika för Scrum som många har kritiserat och valde därför att rikta in vår studie mot detta. Uppsatsen syftar till att undersöka om lokala IT-företag i Borlänge, Headlight, Sogeti ochstatliga nätkapacitetleverantören Trafikverket ICT lider av det allmänna problem som de andra Scrumanvändarna upplever i samband med användningen av metoden. Denna uppsats har fokus på fyra problemområden: bristfällig dokumentation, sämre effektivitet i arbetsprocessen, sämre effektivitet i arbetsprocessen i stora projekt samt bristande stöd för utvärdering. För vår studie har litteraturstudier och intervjuer genomförts. Intervjuserier gjordes på elva personer hos våra fallföretag. Målgruppen för våra intervjuer är Product Owner (PO) ScrumMaster (SM) och utvecklare. Vi kan efter genomförd studie dra slutsatsen att de allmänna upplevda problem som de andra Scrumanvändaren upplever har vi även kunnat identifiera hos våra fallföretag. Resultaten har bekräftats med insamlade data och vår teoretiska ram. I diskussionen presenterar vi rekommendationer för att undvik relaterade problem med Scrum.

APA, Harvard, Vancouver, ISO, and other styles

17

Andersson, Jakob, Haglund Emil Castillo, and Lars Kennemark. "Scrum Master - en roll med många roller - Hur realiseras rollen som Scrum Master i praktiken kontra teorin?" Thesis, Örebro universitet, Handelshögskolan vid Örebro Universitet, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:oru:diva-56974.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Koka, Andile. "Software quality assurance in scrum projects: a case study of development processes among scrum teams in South Africa." Thesis, Cape Peninsula University of Technology, 2015. http://hdl.handle.net/20.500.11838/1400.

Full text

Abstract:

Thesis Submitted in fulfilment of the requirements for the degree Master of Technology in Information Technology in the Faculty of Informatics and Design at the Cape Peninsula University of Technonlogy
The use of Information and Communication Technology (ICT) in business has evolved to such an extent that many organizations (if not all) rely on Information Technology (IT) systems to better manage their processes, get competitive advantage, improve performance (efficiency and effectiveness), provide quality services on time and most importantly to keep customers happy. This has changed the way people communicate and conduct businesses, lowering processing cost, time and improving a return on investment. Therefore, high quality software systems are essential. Organizations adopt Agile Scrum methodologies in order to develop applications that help them to obtain a return on investment quickly, to improve customer satisfaction and to maintain competitive advantage. However, the IT industry is yet to develop error-free software that meets the expected quality standards. Therefore, the aim of this study was to explore the extent to which software quality assurance measures can be understood and applied to maximize the quality of software projects developed under Scrum methodology. A qualitative research method informed by an interpretive approach was used to collect and analyse data. Following the purposive sampling technique, five Scrum teams operating in different environments and two academics from one academic institution were interviewed. Structuration Theory (ST) was then used as an analytical framework to analyse data and to improve the understanding of Scrum practices and related quality assurance (QA) processes. Drawing on the major terms of ST, the contextual terrain of the Scrum development process was mapped. It reflected that rules are important aspects of Scrum functions. However, rules are not as strictly applied as in the traditional methodologies. The developer skill, project type and size have a direct influence on the practice/s. In Scrum, rules are flexible in that they can be modified to meet the environment and conditions of the team. Equally significant are resources, most particularly, time and the human resources in the form of developers and Scrum leaders. Otherwise, unit testing, user acceptance testing, close collaboration and code reviews were perceived as the most important practices in Scrum projects. In view of the findings, recommendations can be summed up into 4 main points; (1) that to ensure quality assurance in Scrum, Scrum teams, especially team leaders, should enforce compliance to standards, regardless of time pressures and tight deadlines; (2) It seems that the practice of working with the client to test final products as a quality assurance mechanism is working for all parties. This practice is encouraged and must be maintained; (3) Code reviews must be enforced, and that organisations invest in resources including the constant training of developers; (4) Project product owners, project managers, team leaders and business analysts should regularly meet with the user to verify requirements prior to the implementation phase. Active stakeholder involvement can minimize development costs and time.

APA, Harvard, Vancouver, ISO, and other styles

19

Chiste, Brandão Ana Beatriz. "Risk Management in Software projectsusing Scrum framework." Thesis, KTH, Tillämpad maskinteknik (KTH Södertälje), 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-122857.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Tobias, Eklund, and Joakim Spehar. "CPlanner : Kursplaneringsprototyp med Design Science och Scrum." Thesis, Uppsala universitet, Institutionen för informatik och media, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-202215.

Full text

Abstract:

Utveckling av planeringssystem är ett komplext designproblem som kräver både en hög grad av flexibilitet men även struktur. I samband med planering är det ett flertal aktörer, aktiviteter och resurser som måste beaktas. Kunnandet när det gäller planering finns ofta koncentrerad till ett fåtal nyckelpersoner. Det är därför ingen tillfällighet att många företag, organisationer och även universitet idag bedriver sin planering i beprövade enanvändarsystem som Excel fast att det finns starkt behov för standardiserat fleranvändarsystem. Uppsala universitet är inget undantag trots dess storlek med över 40 000 studenter, 6 200 anställda, 130 utbildningsprogram och 2000 fristående kurser. Kursplaneringen bedrivs med hjälp av enanvändarsystem där man är beroende av ett antal nyckelpersoner för att planeringen skall fungera. Uppsatsens syfte är att undersöka och belysa den problematik som finns i samband med utveckling av planeringssystem genom att utveckla en prototyp för ett kursplaneringssystem. Den forskningsstrategi som används är Design Science och den utvecklingsmetodik som används är Scrum. Prototypen har utvärderats regelbundet under utvecklingen genom formativ utvärdering. Uppsatsens kunskapsbidrag utgörs av metodkunskap som visar hur Scrum och Design Science kan kombineras samt modellkunskap som visar den grundläggande strukturen för ett kursplaneringssystem.
Development of planning system is a complex design problem that requires both a high degree of flexibility but also structure. In the context of planning, there are several actors, activities and resources that must be considered. Expertise in planning is often concentrated in a few key individuals. It is therefore no coincidence that many businesses, organizations and even universities currently conducts its planning in proven single-user system like Excel even though there is a strong need for standardized multi-user system. Uppsala University is no exception, despite its size, with over 40,000 students, 6,200 employees, 130 programs and 2000 courses. Course planning is conducted using single-user system and which is dependent on a number of key individuals to plan to work. The essay aims to investigate and illustrate the problems that are associated with the development of the planning system by developing a prototype of a course scheduling system. The research strategy used is Design Science and the development methodology that is used is Scrum. The prototype has been evaluated regularly during development through formative evaluation. The essays knowledge contribution is methodological knowledge that shows both how Scrum and Design Science can be combined and model knowledge, which shows the basic structure of a course scheduling system.

APA, Harvard, Vancouver, ISO, and other styles

21

Girot, Etienne. "Practical implementation of SCRUM and associated practices." Thesis, Linköpings universitet, Institutionen för datavetenskap, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-100123.

Full text

Abstract:

Even though Scrum is nowadays widely known in the Software Industry field and its theoretical frame extensively described in the literature, its implementation is far from being straightforward. As a matter of fact, the literature describes a meta-process that new practitioners must adapt to their project specific constraints. However, this practical aspect is crucial and very scarcely tackled. To that extend, this thesis work describes the difficulties we faced while putting Scrum into practice and how, through the study of the project contextual factors, the insight of a Proof Of Concept and the support of a couple of agile practices, we worked it out.

APA, Harvard, Vancouver, ISO, and other styles

22

Jungstedt, Philip, and Charlie Moy. "Scrum - en analys av praktik och problematik." Thesis, Uppsala universitet, Institutionen för informatik och media, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-256782.

Full text

Abstract:

Agila metoder blir allt vanligare bland IT företag i hela världen. I dagsläget är de vanligare ände traditionella metoderna inom utveckling. Bland dessa metoder återfinns Scrum som denvanligaste metoden.Detta arbete har som syfte att analysera hur Scrum tillämpas inom organisationer för attfungera på ett praktiskt plan, eftersom alla företag inte ser likadana ut och inte stöter påsamma problem. Till grund för analysen har en litteraturstudie utförts gällande de olika agilametoderna för att hitta likheter och olikheter. Baserat på resultaten från denna studie harintressenter identifierats och intervjuats för att sedan göra en jämförande analys på metodenoch litteraturen. Slutligen sammanfattas resultaten med fokus på skillnader mot teorin ochproblem som uppstår med tillämpningen av Scrum.Detta arbete tydliggör de problem som företagen upplevt med metoden och ger en vidareförklaring på dessa.

APA, Harvard, Vancouver, ISO, and other styles

23

Kanane, Aahd. "Challenges related to the adoption of Scrum." Thesis, Umeå universitet, Institutionen för informatik, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-90159.

Full text

Abstract:

Software development projects took an important turn after the emergence of agilesoftware development methods. Indeed, this kind of projects has always been managed in atraditional way that requires an elaborate effort of planning. A way considered as inflexibleand that goes against the constantly changing and hardly predictable nature of softwaredevelopment projects. Agility offers more flexibility as far as requirements and changemanagement are concerned. In this study, the focus is placed on one of the most popularagile software development methods, namely Scrum. It investigates the challenges relatedto the adoption of Scrum, and for this the case of a company operating in the financial ITsector and that has been using Scrum for 5 years is examined. This case displays that thenature of Scrum makes that there is not a single way of adopting it. Adopting Scrum ismore a process of continuous adaptation and improvement, therefore facing challenges isan inseparable part of this process.

APA, Harvard, Vancouver, ISO, and other styles

24

Zikopi, Eleni. "A case study research on Scrum Framework." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-255005.

Full text

Abstract:

Agile methods have been widely implemented in the industry while teaching these methods is a substantial part of Computer Science and Engineering program curricula. Evidencedriven data of agile practices, methods, and tools have been extracted based on empirical studies with students, however, there is an important need for more anecdotal evidence to confirm these findings. In order to fill this gap, this paper explores the perceptions and the applicability of the Scrum Framework in a student research team in an industrial context. Empirical data have been gathered through interviews with the case study participants combined with a survey. The analysis reveals that student experiences are mainly positive and that they can easily grasp the benefits of Scrum Framework. The challenges of implementing Scrum in such a setting mainly concern the balance between coach and self-organization, formulating accurate user stories when researching, finding the most suitable estimation method, as well as planning when conducting research. The empirical findings may potentially be extrapolated in student scrum teams or even in industrial settings. Finally, this research paper should encourage other researchers to investigate the adoption of Scrum in a student setting.
Agila metoder har implementerats i stor utsträckning inom branschen, medan undervisning i dessa metoder är en väsentlig del av utbildningarna för datavetenskap och teknik. Bevisdriven data om agila arbetssätt, metoder och verktyg har tagits fram från empiriska studier med studenter, men det finns ett viktigt behov av mer anekdotiska bevis för att bekräfta dessa resultat. För att fylla detta gap utforskar den här rapporten uppfattningarna och tillämpligheten av ramverket Scrum i ett studentforskningsteam i ett industriellt sammanhang. Empiriska data har samlats genom intervjuer med deltagarna i fallstudien i kombination med ett frågeformulär. Analysen visar att studentupplevelserna är främst positiva och att man lätt kan förstå fördelarna med Scrum. Utmaningarna med att implementera Scrum i en sådan miljö gäller främst balansen mellan coaching och självorganiserande, formulera exakta användarhistorier när man forskar, finner den mest lämpliga uppskattningsmetoden samt planerar forskningsrelaterat arbete. De empiriska fynden kan eventuellt extrapoleras i Scrumteam med studenter eller till och med i industriella miljöer. Slutligen bör detta forskningsarbete uppmuntra andra forskare att undersöka införandet av Scrum i ett studentkontext.

APA, Harvard, Vancouver, ISO, and other styles

25

Rutfors, Jacob, and Herman Guss. "Innovationsbenägenhet inom mjukvaruprojekt : En studie om Scrum." Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-393586.

Full text

Abstract:

Ämnet innovation har avhandlats gediget inom företagsekonomin. De specifika villkoren för innovation inom olika branscher är emellertid lika välgranskade. Denna studie undersöker Scrum, vilket är ett agilt utvecklingsramverk populärt bland mjukvaruutvecklingsföretag, och sammanlänkar det med de teoretiska modellerna innovationsvärdekedjan och innovationshantering för att dra slutsatser om hur Scrum påverkar innovationsprocesser samt hur det kan bistå företag i att hantera de utmaningar, risker och möjligheter som kan uppstå i samband med innovation. För detta används en kvalitativ metod baserad på intervjuer med aktiva utvecklare på tre företag. Resultaten pekar på att Scrum hjälper utvecklare att hantera risker i innovationsprocesser genom att alterera dem på ett sådant sätt att tiden mellan produktutveckling och återkoppling på utfört arbete minskar, samt att Scrums rolltilldelning bidrar till företagets länkar mellan produktägare och intressenter. De dagliga ceremonierna inom Scrum utgör eventuellt även ett mindre bidrag till en innovativ organisationskultur. Dessa slutsatser antyder att Scrum utgör ett stöd i mjukvaruutvecklingsföretags innovationshantering. Fortsatta studier rekommenderas med förslag på en processtudie av enskilda mjukvaruutvecklingsprojekt.

APA, Harvard, Vancouver, ISO, and other styles

26

Iyju, Rini. "Challenges In Transitioning From Waterfall To Scrum." DigitalCommons@CalPoly, 2015. https://digitalcommons.calpoly.edu/theses/1479.

Full text

Abstract:

In today's fast-paced, fiercely competitive world; speed and flexibility are essential. Companies are increasingly realizing that the sequential approach to developing new product simply will not get the job done. The goal of this thesis is to investigate critical issues and challenges that occur during the transition from a traditional software development methodology such as Waterfall to Scrum. During the last decade, Scrum has gained a vast success in software development due to its lightweight character and efficient way of handling the challenges of increased market speed, change and product complexity. This thesis is based on a sequential exploratory mixed methods research model, which uses both qualitative as well as quantitative research methods to investigate the problem. The rationale for this is that neither method is sufficient by itself to capture the trends and details of situations. When used in combination, both quantitative and qualitative methods complement each other and provide a more complete picture of the research problem. There are six main results from this thesis. First the main challenges are identified. Second, they are ranked based on their frequency of occurrence and thirdly, based on their importance. Fourth, the correlation between the frequency of occurrence of challenge and their importance is measured. This thesis also examines the varied perspectives of Scrum Coaches and Scrum Practitioners regarding the frequency of challenges as the fifth result and regarding the importance of challenges as the sixth result.

APA, Harvard, Vancouver, ISO, and other styles

27

Svoboda, Radek. "Efektivní využití SCRUM metodiky ve vývojovém týmu." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2017. http://www.nusl.cz/ntk/nusl-318346.

Full text

Abstract:

The master thesis focuses on more efficient application of Scrum methodology in a development team within specific company. The thesis takes an advantage from the SW-CMM philosophy applied in agile environment in order to achieve better effectivity. Theorethical base is utilized for a comparison with current state in the company described in analytical part. Proposals for a solution of current situation are based on drawback detection. Proposals are subject for risk analysis followed by precaution. Costs of proposals implementation with included precautions are evaluated in economic evaluation part. This part also contains benefits of proposals.

APA, Harvard, Vancouver, ISO, and other styles

28

Krbušek, Adam. "Použití metodiky SCRUM v inovačním procesu firmy." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-261990.

Full text

Abstract:

Diploma thesis deals with SCRUM methodology and its uses in innovation management. The main objective of the thesis is creation of a specific framework which will enable to use SCRUM methodology in the innovation process. The thesis is divided into three parts. The first part presents theoretical framework important for the main research. This part contains literature review and research dedicated to the SCRUM methodology and innovation process. The second part of the thesis deals with mapping of the SCRUM methodology to Hladik's innovation process. This part also contains own design of the innovation management process. The third part of the thesis is dedicated to the case study. The case study uses described innovation management process for verification of the hypothesis saying that is possible to use SCRUM methodology in the innovation process. The author's contribution lies in creation of a framework which provides agile alternative to the classical innovation management models.

APA, Harvard, Vancouver, ISO, and other styles

29

Henrysson, Daniel. "Scrum – en fallstudie från lokala företags perspektiv." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5209.

Full text

Abstract:

Through a case study, I wanted to find out what advantages and disadvantages local companies consider with scrum and what they think about its future. To find out what scrum is, I read the literature and scientific articles and then wrote surveys based on my thoughts. Further, I also wanted to find out if it’s possible to use scrum in a school environment and therefore I visited a high school class who used scrum in one of their projects. The result was good but could have been better as it requires more training of scrum to understand everything. The surveys were distributed to various local companies. After having received a lot of answers, I concluded that the clear priority was the most positive feature of scrum and the most negative was that it was difficult to get the rest of the organization to understand scrum, which creates problems. Both high school class and local companies believe in scrum’s future, even if they think scrum will be partially modified to adapt to the software-development in the future. According to the survey responses, the most important to get the projects to be successful both now and in the future is that everyone who work with scrum is right educated.
Genom en fallstudie ville jag ta reda på vilka fördelar respektive nackdelar de lokala företagen ser med scrum och vad de anser om dess framtid. För att ta reda på vad scrum är har jag läst litteraturstudier och vetenskapliga artiklar för att sedan kunna skriva enkäter som bygger på mina funderingar. Fortsättningsvis ville jag även ta reda på om man kan använda scrum i skolmiljön och har därför besökt en gymnasieklass som använt sig utav scrum i deras projekt. Resultatet blev bra, men hade kunnat bli bättre då det krävs mer utbildning av scrum för att förstå allt. Enkäterna lämnades ut till olika lokala företag. Efter att ha fått in en hel del svar kom jag fram till att klara prioriteringar var den mest positiva egenskapen med scrum och den mest negativa var att det var svårt att få den övriga organisationen att förstå scrum, vilket skapar problem. Både gymnasieklassen och de lokala företagen tror på scrums framtid, även om de tror att scrum kommer att vara till viss del modifierad för att anpassa sig till hur mjukvaru-utvecklningen sker framöver. Enligt enkätsvaren så är det viktigaste för att få projekten att bli framgångsrika både nu och i framtiden att alla som arbetar med scrum som arbetsmetod är rätt utbildade.

APA, Harvard, Vancouver, ISO, and other styles

30

Prihodko, Jana. "Anpassning av Scrum-metod : För förbättrade mjukvaruutvecklingsprojekt." Thesis, KTH, Skolan för informations- och kommunikationsteknik (ICT), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-205186.

Full text

Abstract:

Mjukvaruutveckling kräver bra arbetsmetoder för att man ska kunna leverera effektivt och välfungerande mjukvara. För att lyckas med detta behöves en bra arbetsmetod som de kan arbeta efter. Agila metoder blir mer populära att arbeta med när det gäller mjukvaruutveckling i dagens teknikföretag. Fler företag går över att arbeta efter agila metoder med projekt istället för den traditionella vattenfallsmetoden. Anledningen till detta är att fler och fler företag misslyckas att leverera projekten i tid med vattenfallsmetoden vilket medför mer kostnader för företag. Agila metoder hjälper däremot företag att få struktur som leder till bättre arbetssätt som i sin tur resulterar i att projekten blir avslutade i tid. Denna studie undersökte användning och anpassningar av agila metoden Scrum på en bank och om detta har medfört några förbättringar i arbete med mjukvaruutvecklingsprojekt. Undersökningen genomfördes med hjälp av intervjuer med Scrummästare, Agila coacher, produktägare samt chefer som arbetar med Scrum-metoden. Resultatet visar att agila metoden Scrum ger mer struktur samt transparens till projekt. Anpassningar till produktägarrollen på företaget har medfört att rätt uppdrag blir prioriterade och teamen får en tydlig backlogg att arbeta efter. Arbetet enligt Scrummetoden har hjälpt team att få en tydlig struktur och ökat leverans av projekt.
Software development requires good working methods to be to deliver efficient and effective software. To achieve this, companies require a good working method that they can work with. Agile methods are becoming more popular to work with when it comes to software development in today's technology companies. More companies are beginning to work with agile methods for project management instead of the traditional waterfall method. The reason for this is that more and more companies fail to deliver projects on time with the waterfall method, which means more costs for companies. The reason for this is that more and more companies fail to deliver projects on time with the waterfall method, which means more costs for companies. Agile methodologies however help companies to get structure that led to better work, which in turn results in that projects are completed on time. This study examined the usage and customization of agile method Scrum in a bank, and if this has led to some improvements in the work of software development projects. The investigation was conducted through interviews with Scrum Master, Agile coaches, product owners and managers who work with the Scrum method. The result shows that the agile method Scrum provides more structure and transparency to projects. Adaptations to the product owner role in the company has led to that right assignment are prioritized and teams get a clear backlog to work with. The work with the Scrum method has helped the team to have a clear structure and increased delivery of projects.

APA, Harvard, Vancouver, ISO, and other styles

31

Johansson, Angelica, and Emelie Mörk. "Integrering av ett UX-perspektiv i Scrum." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-31541.

Full text

Abstract:

En integrering av UX i Scrum har genom tidigare studier visat sig vara komplex och utmanande. Utmaningarna kan bero på skillnader i arbetssätt hos de olika områdena, och att viss motstridighet finns i grundläggande värderingar. Trots att agil utveckling och UX har samexisterat i mer än ett decennium är ett generellt tillvägagångssätt för att integrera UX i agila metoder som Scrum ännu inte fastställt. För att undersöka hur UX kan integreras i Scrum har vi ställt frågan: “Hur kan ett UX-perspektiv integreras i en Scrum-process?” Genom vår studie har vi identifierat utmaningar med integreringen av ett UX-perspektiv i Scrum, och vi har valt ut fyra UX-tekniker i syfte att adressera de identifierade utmaningarna. Frågan studeras genom en kvalitativ ansats där datainsamlingsmetoder som intervjuer, observationer och workshoppar legat i fokus. De primära deltagarna i studien är ett mjukvaruutvecklingsteam på ett världsomfattande telekommunikationsföretag. Studien bidrar med kunskap kring hur identifierade utmaningar med att integrera ett UX-perspektiv i Scrum kan hanteras i praktiken. Detta visas genom en modell som beskriver var och när UX-teknikerna med störst potential kan integreras i en Scrumprocess, samt hur denna integrering kan gå till.

Tilldelad stipendium för bästa uppsats inom Informatik på Högskolan i Halmstad, 2016.

APA, Harvard, Vancouver, ISO, and other styles

32

TOLEDO, Ana Carolina Oran Fonseca e. "Um estudo sobre as principais dificuldades dos Scrum Masters em relação ao uso de ferramentas para auxiliar suas atividades." Universidade Federal de Pernambuco, 2010. https://repositorio.ufpe.br/handle/123456789/2176.

Full text

Abstract:

Made available in DSpace on 2014-06-12T15:55:13Z (GMT). No. of bitstreams: 2 arquivo2167_1.pdf: 1826122 bytes, checksum: 4cff3c9619edbf08bed786053187ac24 (MD5) license.txt: 1748 bytes, checksum: 8a4605be74aa9ea9d79846c1fba20a33 (MD5) Previous issue date: 2010
Com a mudança das metodologias tradicionais para as metodologias ágeis de gerenciamento de projetos, houve também a evolução dos profissionais que atuam nessa área. Com isso, metodologias como o Scrum passaram a ganhar espaço e quebrar paradigmas nas grandes organizações, promovendo o aparecimento de novos papéis relacionados à gestão de projetos, tais como os Scrum Masters. Estes profissionais, comparados ao gerente de projeto do futuro, têm a responsabilidade não de impor suas ordens, mas sim facilitar o trabalho de pessoas em um projeto. Entretanto, percebeu-se, com os profissionais entrevistados que há uma diferença entre os fundamentos teóricos e a prática quanto às atividades desempenhadas por estes profissionais e a respeito das ferramentas disponíveis para ajudá-los nas suas atividades diárias. Desta forma o objetivo geral desta pesquisa é analisar as principais dificuldades dos Scrum Masters em relação ao uso de ferramentas para auxiliar suas atividades. Para tanto foi realizado um estudo aprofundado com utilização de questionário aplicado a uma amostra de 13 profissionais a respeito das atividades desempenhadas por eles em um projeto que utiliza Scrum, verificando também quais as ferramentas utilizadas pelos mesmo que os auxiliam na execução de suas atividades. Foi verificado ainda se essas ferramentas atendiam às necessidades destes profissionais enquanto Scrum Masters. A partir dos dados coletados, foi possível, entre outros resultados, identificar as reais atividades executadas pelos Scrum Masters no seu dia-a-dia, as quais incluem além daquelas descritas na literatura, outras atividades complementares. Percebeu-se, também que as ferramentas utilizadas por estes profissionais não atendem satisfatoriamente suas necessidades em suas atividades diárias. Assim, foi realizada uma análise comparativa entre os dados coletados nas entrevistas com os Scrum Masters e aqueles obtidos nas revisões bibliográficas que resultou no desenvolvimento de uma ferramenta chamada JustScrum, a qual disponibiliza as funcionalidades listadas nos questionários pelos Scrum Masters, a fim de unir em uma única ferramenta as funcionalidades essenciais desejadas pelos entrevistados para auxiliá-los nas suas atividades profissionais

APA, Harvard, Vancouver, ISO, and other styles

33

Lervåg, Alf Børge Bjørdal. "A Case Study of a Norwegian Scrum Project." Thesis, Norwegian University of Science and Technology, Department of Computer and Information Science, 2006. http://urn.kb.se/resolve?urn=urn:nbn:no:ntnu:diva-9456.

Full text

Abstract:

In this paper I present a case study of a Norwegian development project where the development team adopted practices from Scrum in the middle of the development effort. My study shows that the developers were happy with this new development method, and among other things thought it gave them a better focus and structure for their work. Since the team only adopted practices from the Scrum method, I look at the differences between their method and Scrum and suggest a few improvements to their method based on my knowledge of Scrum and development methods in general.

APA, Harvard, Vancouver, ISO, and other styles

34

Kodali, Manvisha. "TRACEABILITY OF REQUIREMENTS IN SCRUM SOFTWARE DEVELOPMENT PROCESS." Thesis, Mälardalens högskola, Akademin för innovation, design och teknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-28326.

Full text

Abstract:

Incomplete and incorrect requirements might lead to sub-optimal software products, which might not satisfy customers’ needs and expectations. Software verification and validation is one way to ensure that the software products meets the customers’ expectations while delivering the correct functionality. In this direction, the establishment and the maintenance of traceability links between requirements and test cases have been appointed as promising technique towards a more efficient software verification and validation. Through the last decades, several methodologies supporting traceability have been proposed, where most of them realize traceability by implicitly exploiting existing documents and relations. Nevertheless, parts of the industry is reluctant to implement traceability within software development processes due to the intrinsic overhead it brings. This is especially true for all those light-weight, code-centric software development processes, such as scrum, which focus on the coding activities, trying to minimizing the administrative overhead. In fact, the lack of documentation finishes to hamper the establishment of those trace links which are the means by which traceability is realized. In this thesis, we propose a methodology which integrates traceability within a scrum development process minimizing the development effort and administrative overhead. More precisely we i) investigate the state-of-the-art of traceability in a scrum development process, ii) propose a methodology for supporting traceability in scrum and iii) evaluate such a methodology upon an industrial case study provided by Westermo.

APA, Harvard, Vancouver, ISO, and other styles

35

Taborga, Jorge. "Toward Adaptive Stage Development in Software Scrum Teams." Thesis, Saybrook University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10930703.

Full text

Abstract:

Over the last 70 years, teams have become the ubiquitous unit of work in our organizations. The software industry heavily utilizes the Scrum methodology to develop software. Scrum is a team-based methodology that requires the constant formation and development of team capabilities. Researchers and practitioners dealing with work team dynamics have relied on the popular team developmental stages of forming, storming, norming, and performing, defined by Dr. Bruce Tuckman in 1965. However, this framework was conceived primarily from articles dealing with therapy groups and not modern teams. This study expands the body of research in work team stage development applied to Scrum, a methodology that itself has no social science foundation and minimal theoretical coverage.

A combined case study and grounded theory method is used to leverage the strengths of both to investigate the developmental stage of 5 Scrum teams at a high-tech company. A questionnaire along with team interviews were utilized to gather data on how teams relate to developmental factors found in the literature. Descriptive analytics were leveraged to uncover the questionnaire findings, and grounded theory analysis was applied to code interview answers into usable concepts, categories, and themes. Themes were further explored concerning their causal relationships.

The study proposed and validated 12 theoretical factors that contribute to the stage development of Scrum teams across 4 distinct stages. These factors interconnect and form 4 quadrants with unique dynamics associated with a team’s mission, structure, execution, and teaming. Furthermore, higher stage teams proved to be self-managed and adaptable and able to handle higher task complexity. Leaders were observed shifting roles as teams evolved through stages. This latter finding is consistent with the theoretical model of Kozlowski, Watola, Jensen, Kim, and Botero. The research also identified common challenges that teams encounter in their development.

The findings from this study can help organizations who practice Scrum become more intentional about the development of their teams toward adaptability. A concerted effort by software organizations to optimize the evolution of teams across the factors found in the study could yield significant benefits, particularly for missions dealing with high complexity and innovation needs.

APA, Harvard, Vancouver, ISO, and other styles

36

Kubalcová, Monika. "ITIL v prostředí agilního vývoje software metodikou Scrum." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2014. http://www.nusl.cz/ntk/nusl-235418.

Full text

Abstract:

This thesis follows concept of integration ITIL library and agile methodology Scrum into the IT company developing IT services. After theoretical analysis of both concepts and analysis of chosen company, we will develope methodology, which will tie both process approaches and ensure their perfect synergy. As a methodology support, web application was developed. It evaluates effectivness of processes using key informations and their plot representation. Proposed methodology was presented in the AVG Technologies, which used described processes as template for its internal proceses. Main result of the thesis is set of templates describing processes, which could be specified and applied in companies using Scrum together with ITIL for their development.

APA, Harvard, Vancouver, ISO, and other styles

37

Greň, Lukáš. "Softwarová podpora projektového řízení s využitím metodiky Scrum." Master's thesis, Vysoké učení technické v Brně. Fakulta informačních technologií, 2011. http://www.nusl.cz/ntk/nusl-412833.

Full text

Abstract:

Department of Research and Development of company Seznam.cz plans and implements its projects using Scrum agile development methodology. The company inquires an information system that captures the process of development. The information system must capture all company's dissimilarities from generic process and the system must be connected to other company's systems.

APA, Harvard, Vancouver, ISO, and other styles

38

Kulhánková, Barbora. "Behaviour Driven Development a Scrum v korporátním prostředí." Master's thesis, Vysoká škola ekonomická v Praze, 2015. http://www.nusl.cz/ntk/nusl-204867.

Full text

Abstract:

Agile software development methodologies these days are not used only in small enterprises or startups, they are getting spread around large enterprises as well. An evidence of this fact could be, that Scrum is nowadays the most commonly used approach to software development. So this thesis focuses on usage of agile approaches, Scrum methodology in particular, in large enterprises. Author presents an approach called Behaviour Driven development and proposes how this approach could help dealing with imperfections or barriers of Scrum when used in large enterprises. The major outcome of this thesis is author's own methodology called ScrumFlow, based on Scrum methodology and extended by Behaviour Driven Development approaches. ScrumFlow methodology is published on a website and available for free.

APA, Harvard, Vancouver, ISO, and other styles

39

Zhao, Chengqian. "Impact of National Culture Dimensions on Scrum Implementations." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2109.

Full text

Abstract:

Context. Scrum is one of the most common used Agile method. It is based on empiricism. Scrum only provides a framework but the detailed implementations in practice are very different. and the environment has a big influence on it. National culture is proven to have an impact on Agile methodology. The implementation of Scrum practices should be influenced by national culture as well. Objectives. This paper reveals the relationship between national culture and Scrum implementation. It explores in which aspects that national culture has an influence on the implementation of Scrum practices and how the different national culture dimensions affect the implementations. Methods. A literature review is used to build a theoretical framework. This framework includes the potential relationships between national culture and Scrum practices, which are our hypotheses. Afterward, interview is used in a company that has Scrum teams in both Sweden and China. Their implementations of Scrum practices are interviewed and analyzed based on our hypotheses. Results. A framework of deducted relationship between Hofstede’s national culture dimensions and Scrum practices is built. National culture is found to have an influence on the implementations of five Scrum practices. Conclusions. National culture is found to have an influence on Scrum implementations. National culture through power distance dimension has the most impact on implementations of no title practice, manage burn down chart practice and no interference practice. National culture differences in the aspect of individualism dimension also affect the practice like no title in teams. Uncertainty avoidance degree in different nations also has the most impact on Scrum implementation such as using burn down chart practice and time-boxed dimensions. Moreover, influence from national culture in China makes the Scrum implementations more consistency than the influence from national culture in Sweden.

APA, Harvard, Vancouver, ISO, and other styles

40

Juhlin, Annica. "Scrum master in a global distributed development team." Thesis, Blekinge Tekniska Högskola, Avdelningen för för interaktion och systemdesign, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4927.

Full text

Abstract:

Companies around the world work more globally than ever and it reflects in the system development projects that run. The companies work span continents and the employees work together over the borders. This way of working, the global distributed, brings a number of opportunities for the company but also presents a lot of problems. The distributed way of working means that the teams and/or individuals are divided. I wanted to connect this way of working with the agile framework Scrum, partly due to my own interest on the subject and partly as it is a contradiction to me, distributed work and Scrum, therefore a challenge to combine. To be able to investigate this way of working I got in touch with two companies that work globally and distributed, using the Scrum technique, I read literature and papers on the subject to be able to reach my conclusions. My conclusions are based on the success factors I found in both the literature and the dialogs performed. The study shows three important qualities in a leader, a scrum master, in a globally distributed development team: Coaching leadership, clear leadership and smaller distributed teams not individuals.

APA, Harvard, Vancouver, ISO, and other styles

41

Sulemani, Kashif Ali, and Muhammad Nadeem Nasir. "Communication Support to Scrum Methodology in Offshore Development." Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2815.

Full text

Abstract:

In today world, the software companies are expanded above the continents. The software development work span continents and the distributed team work together over the borders. The agile development methodology demands close collaboration with client, rapid requirements change and an iterative development of fixed length. When this way of agile approach is applied in a distributed project, it requires frequent communication and knowledge exchange among the dispersed team members and need collaboration with customer over distance. Besides the geographical, the linguistic and the different time zone barriers in a distributed project, the computer mediated tools suppose being useful media in connecting and to coordinating among dispersed colleague in a project. Though, these tools depict variant effectiveness in communication exchange, however, there efficient use connects peoples at the two sites. The aim of this thesis study is to explore the communication channel support to the Scrum practices in a distributed project. The purpose of the research is to analyse collaboration and communication in distributed teams working together through computer mediated technology. For this purpose, a company case is studied doing a distributed agile project. The author’s insight the communication and information exchange through the ICT in an agile project. Based on the case analysis, the authors suggest the recommendations for implementing and establishing agile practices in a distance project.
Mobil: +46700381303

APA, Harvard, Vancouver, ISO, and other styles

42

Levin, Martin. "SCRUM som utvecklingsmetod : Så fungerar det i verkligheten." Thesis, Uppsala universitet, Data- och systemvetenskap, 2011. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-148639.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Zhang, Yanpeng, and Ce Zhou. "Introducing Domain Specific Language for Modeling Scrum Projects." Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-13328.

Full text

Abstract:

Context. A clear software process definition is important because it can help developers to share a common understanding and improve the development effectiveness. However, if the misconceptions or misunderstandings are introduced to the team during the process definition, it will bring numerous uncertain problems to the projects and reduce the productivity. Scrum is one of the most popular Agile development processes. It has been frequently used in software development. But the misunderstanding of usage of the Scrum method always leads to situations where teams cannot achieve the hyper-productivity even failure. Therefore, introducing a reasonable graphical language for describing the Scrum process may help learners to gain a correct and common understanding of the Scrum method. Objectives. In this study, we introduce a graphical Domain Specific Language for modeling the Scrum process and specific Scrum projects. Further, we evaluated the proposed language to figure out if and how this language can help developers learn Scrum method and understand the specific Scrum projects. For the first, we decide to extract the essential elements and their relative relationships of the Scrum process, and based on that, we define and specify the graphical language. After that, we evaluate the proposed graphical language to validate whether this language can be considered as useful to help developers to learn Scrum method and understand the specific Scrum projects. Methods. In order to define the graphical language, we studied and reviewed the literature to extract the essential elements and their relationships for describing the Scrum process. Based on that, we defined and specified the graphical DSL. With the aim of evaluating the proposed graphical language, we performed the experiment and survey method. This experiment was conducted in an educational environment. The subjects were selected from the undergraduate and master students. At the same time, we carried out a survey to capture the developers‘ opinions and suggestions towards the proposed language in order to validate its feasibility. Results. By studying the literature, we listed and specified the essential elements for describing the Scrum process. By executing the experiment, we evaluated the efficiency and effectiveness of learning Scrum in using the proposed language and the natural language. The result indicates that the graphical language is better than the natural language in training Scrum method and understanding specific Scrum projects. The result shows that the proposed language improved the understandability of the Scrum process and specific Scrum projects by more than 30%. We also performed a survey to investigate the potential use of the proposed graphical DSL in industry. The Survey results show that participants think the proposed graphical language can help them to better understand the Scrum method and specific Scrum projects. Moreover, we noticed that the developers who have less Scrum development experience show more interests in this proposed graphical language. Conclusions. To conclude, the obtained results of this study indicate that a graphical DSL can improve the understandability of Scrum method and specific Scrum projects. Especially in managing the specific Scrum project, subjects can easily understand and capture the detailed information of the project described in the proposed language. This study also specified the merits and demerits of using the graphical language and textual language in describing the Scrum process. From the survey, the result indicates that the proposed graphical language is able to help developers to understand Scrum method and specific Scrum projects in industry. Participants of this survey show positive opinion toward the proposed graphical language. However, it is still a rather long way to applying such a graphical language in Scrum projects development because companies have to consider the extra learning effort of the graphical DSL.

APA, Harvard, Vancouver, ISO, and other styles

44

(UPC), Universidad Peruana de Ciencias Aplicadas. "Gestión De Proyectos Ágil Con Scrum - SI453 201801." Universidad Peruana de Ciencias Aplicadas (UPC), 2018. http://hdl.handle.net/10757/623300.

Full text

Abstract:

Curso electivo de especialidad de Gestión de Proyectos Ágil con Scrum, en la carrera de Ingeniería de Software y de carácter teórico-práctico dirigido a los estudiantes del octavo ciclo, que busca desarrollar la competencia específica de diseño de procesos y sistemas acorde al ABET Student Outcome (c). El curso corresponde al área de formación en gestión de proyectos y equipos de trabajo siendo de carácter teórico-práctico con mayor énfasis en la parte práctica. Tiene como su propósito más importante proveer el conocimiento para poder participar en "equipos ágiles" y desarrollar las habilidades de gestión, comunicación y colaboración necesarias para el desarrollo de proyectos.

APA, Harvard, Vancouver, ISO, and other styles

45

Sincharoenpanich, Puangpetch, and Nunthapin Chantachaimongkol. "Critical factors for implementing the Scrum software development methodology." Thesis, Mälardalens högskola, Akademin för ekonomi, samhälle och teknik, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-18203.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Jia, Yuan. "Examining Usability Activities in Scrum Projects – A Survey Study." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-176192.

Full text

Abstract:

Over the past decades, usability techniques have been introduced into software development practices. At the same time many development organizations have started to use the agile development process – Scrum – to plan and organize their software projects. Little is known about how usability activities are used in Scrum projects and therefore a survey was distributed worldwide to explore this topic. The results from the study shed new light on how IT professionals rate the usability techniques used in Scrum and if the usage of one technique is correlated with other techniques. The results indicate that the most commonly used usability technique in Scrum is workshops, followed by user stories, lo-fi prototyping, interviews and meetings with users, all used by more than half of the participants. A highly ranked usability technique by the IT professionals is formal usability evaluation with users, which is interesting since that technique is not commonly used.

APA, Harvard, Vancouver, ISO, and other styles

47

Moradi, Fatemeh. "User Experience and Scrum Teams in the Games Industry." Thesis, Uppsala universitet, Institutionen för informationsteknologi, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-207835.

Full text

Abstract:

The way the Scrum development process is implemented in video games industry in relation to the communication among the team members and their definition of User eXperience (UX) was studied in this research. The aim of this study is to analyze the role of "communities of practice” among the team members and investigate better ways for improving UX and user involvement by analysing results from interviews with developers active in video games industry. The results from the interviews show that the game developing companies form strong “communities of practice” and the Scrum process helps in nourishing them. The video ames industry has its unique character; both in relation to how the Scrum development process is implemented and the way users are involved. Being aware of this uniqueness and valuing it could be a start for developing more suitable methods and defining novel ways of user involvement for developing games with better UX.

APA, Harvard, Vancouver, ISO, and other styles

48

Eriksson, Johan. "Bättre med Scrum? : En studie om den "nya" utvecklingsmodellen." Thesis, Linnaeus University, School of Computer Science, Physics and Mathematics, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-75.

Full text

Abstract:

The Thesis purpose is in the context of system development validate the Scrum Methodology. Projects concerning information technology are difficult to manage and tend to fail in quality, time or costs. Scrum presents a new view of the system development. Better cooperation between customers and developers, continuous follow-up on daily basis and extensive communication in the development team are all characteristics of Scrum. Scrum is described as a new paradigm by its founders but has been criticized by experts of system development too. This Thesis discuss if Scrum is a better way to develop software than older models like the Rational Unified Process and the Spiral Model with focus in five factors. The result of the study is that Scrum has given system development new ways to manage requirements and methods to push the project forward. Lack of management commitment and user involvement can be better with Scrum if the model is used in the right way. Answers concerning coding and testing differ between the respondents in the study which makes it different to make conclusions regarding this factor.

Syftet med uppsatsen är att i en systemutvecklingskontext beskriva de problem som gör att IT-projekt misslyckas och utvärdera om användningen av den agila utvecklingsmodellen Scrum reducerar problemen. IT-projekt tenderar att misslyckas och de bakomliggande orsakerna är flera. Uppsatsen grupperar misslyckande av IT-projekt i fem faktorer. Ledningsstöd, användarmedverkan, projektstyrning, kravhantering samt kodning och test. Scrum är en agil systemutvecklingsmodell som av sina skapare beskrivits som ett paradigmskifte inom systemutvecklingen. Korta tidsintervaller, självgående systemutvecklare, daglig uppföljning är några av Scrums kännetecken. För att besvara syftet har en kvalitativ datainsamlingsmetod använts. En intervjuserie med tio intervjuer och en observation ligger till grund för undersökningens resultat. All insamlad data är insamlad på fallföretaget Banverket Verksamhetsstöd IT. Undersökningen har visat att Scrum ger en del nya angreppssätt främst avseende projektstyrning och kravhantering. Scrum innehåller möjligheter för ökad användarmedverkan och ledningsstöd men det krävs konkreta åtgärder från projektorganisationen om det ska lyckas fullt ut. Uppfattningar kring kodning och test skiljer sig åt beroende på vilken respondent som frågas. Det tyder på att det saknas tydliga rutiner i det här avseendet. Slutsatsen blir därmed att Scrum reducerar några av de problem som finns i IT-projekt och därmed med fördel kan användas som en best practice.

APA, Harvard, Vancouver, ISO, and other styles

49

Baccolini, Giulia. "I modelli agili di sviluppo software: il caso Scrum." Bachelor's thesis, Alma Mater Studiorum - Università di Bologna, 2014. http://amslaurea.unibo.it/7213/.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Tomar, Amit Kumar. "Study of scrum framework usage in non-software systems." Thesis, Massachusetts Institute of Technology, 2017. http://hdl.handle.net/1721.1/114079.

Full text

Abstract:

Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, System Design and Management Program, 2017.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 65-66).
The Agile Software development methodologies have changed the way software products and services are delivered in a continuous manner. Some of these Agile Software Development methodologies have been very successful in increasing the pace of innovation and raising the productivity at workplace. But there has been a constant pushback in the non-software industries against adopting some of these Agile development methodologies citing various reasons. The scope of this thesis is to identify few scenarios from non-software industries to evaluate how the Scrum framework, which is one of the various Agile methodologies, has been successful to raise the productivity and the value delivery to clients. Few of the case studies were studied and their gist is presented in this thesis. More specifically, it is reported in this thesis how the Scrum framework is adopted and adapted to a specific type of industry or product.
by Amit Kumar Tomar.
S.M. in Engineering and Management

APA, Harvard, Vancouver, ISO, and other styles

Dissertations / Theses on the topic 'And Scrum'

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