Дисертації: "Agile 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.

Повний текст джерела

Анотація:

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 та ін.

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.

Повний текст джерела

Анотація:

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 та ін.

3

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.

Повний текст джерела

Анотація:

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 та ін.

4

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

Повний текст джерела

Анотація:

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 та ін.

5

Alotaibi, Minahi. "Modelling security requirements through extending Scrum agile development framework." Thesis, De Montfort University, 2016. http://hdl.handle.net/2086/12491.

Повний текст джерела

Анотація:

Security is today considered as a basic foundation in software development and therefore, the modelling and implementation of security requirements is an essential part of the production of secure software systems. Information technology organisations are moving towards agile development methods in order to satisfy customers' changing requirements in light of accelerated evolution and time restrictions with their competitors in software production. Security engineering is considered difficult in these incremental and iterative methods due to the frequency of change, integration and refactoring. The objective of this work is to identify and implement practices to extend and improve agile methods to better address challenges presented by security requirements consideration and management. A major practices is security requirements capture mechanisms such as UMLsec for agile development processes. This thesis proposes an extension to the popular Scrum framework by adopting UMLsec security requirements modelling techniques with the introduction of a Security Owner role in the Scrum framework to facilitate such modelling and security requirements considerations generally. The methodology involved experimentation of the inclusion of UMLsec and the Security Owner role to determine their impact on security considerations in the software development process. The results showed that overall security requirements consideration improved and that there was a need for an additional role that has the skills and knowledge to facilitate and realise the benefits of the addition of UMLsec.

Стилі APA, Harvard, Vancouver, ISO та ін.

6

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.

Повний текст джерела

Анотація:

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 та ін.

7

Chandraseharan, Narendhira Ram. "Improving Adherence to Agile Manifesto Principles in Agile Methodology – A Case Study." The Ohio State University, 2013. http://rave.ohiolink.edu/etdc/view?acc_num=osu1366222792.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

8

Malone, Michael W. "Process subversion in Agile Scrum software development| A phenomenological approach." Thesis, Capella University, 2014. http://pqdtopen.proquest.com/#viewpdf?dispub=3632735.

Повний текст джерела

Анотація:

This qualitative study examined the ways in which process subversion, defined as any attempt, conscious or unconscious, to work around, ignore, or turn to one's own purposes an established process, occurs in Scrum software development. Scrum is a software development methodology that uses self-managing teams and a well-defined process but does not dictate developer practices. It has been shown in previous research that problems with Scrum can cause issues with productivity and software quality. This descriptive phenomenological study specifically examined the ways in which process subversion was experienced by Scrum Masters. The Scrum Master is a coach and facilitator to the development team in Scrum. The study revealed a wide variety of perceptions of the Scrum Master's role as well as sources of subversion ranging from individuals on the development team to the structure of the organization. The study also revealed the creativity used by some Scrum Master in responding to such subversion. This study is important because it fills a gap in the extant literature in dealing with the problems that occur when an organization attempts to use Scrum as its development process, and provides insights that may be helpful in either mitigating the effects of such subversion or preventing it outright.

Стилі APA, Harvard, Vancouver, ISO та ін.

9

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.

Повний текст джерела

Анотація:

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 та ін.

10

Azarkerdar, Samira. "Agile Testing in Scrum : - A Study of Major Factors for Successful Agile Testing Implementations in the View of Agile Testers." Thesis, Uppsala universitet, Institutionen för informatik och media, 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-418140.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

11

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.

Повний текст джерела

Анотація:

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 та ін.

12

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.

Повний текст джерела

Анотація:

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 та ін.

13

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.

Повний текст джерела

Анотація:

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 та ін.

14

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

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

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.

Повний текст джерела

Анотація:

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 та ін.

16

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.

Повний текст джерела

Анотація:

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 та ін.

17

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.

Повний текст джерела

Анотація:

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 та ін.

18

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.

Повний текст джерела

Анотація:

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 та ін.

19

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.

Повний текст джерела

Анотація:

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 та ін.

20

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.

Повний текст джерела

Анотація:

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 та ін.

21

Ostreus, Amelie, and Jenny Brandt. "Agile project management: Scrum in large project - how is the internal communication affected?" Thesis, Malmö universitet, Fakulteten för teknik och samhälle (TS), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:mau:diva-20153.

Повний текст джерела

Анотація:

Idag använder de flesta mjukvaruföretag agil utveckling och en av de vanligaste agila metoderna är Scrum. Under de senaste åren har det blivit vanligt att använda Scrum i större projekt trots dess anpassning för mindre projekt. Följaktligen har olika ramverk utvecklats för att skala Scrum till mer än ett team och för att stödja metoden i större projekt. Det finns flera kommunikativa utmaningar i denna transformationen som har resulterat i en förändring i det smidiga arbetet som påverkar teamets sätt att kommunicera och samverka. Detta ställer nya krav på samarbete och samordningen mellan de olika team som arbetar med samma projekt. I denna studie har målet varit att med hjälp av en kvalitativ ansats undersöka hur kommunikationen påverkas av det faktum att något som ursprungligen var anpassat för mindre projekt, nu ska användas för stora projekt där många parter är involverade och beroende av varandras arbete. Slutsatserna har dragit utifrån kombinationen av en teoretisk referensram och sex intervjuer med Scrum masters och teammedlemmar. Studien visar på att en stor kommunikativ utmaning är att ha en fortlöpande kommunikation mellan teamen och att uppnå en samverkan trots den distanseringen som följer vid skalning. Strategier för hur skalningen av Scrum ska ske på bästa sätt skiljer sig åt, men det finns en enighet om att strukturer, ett gemensamt “språk” och vision krävs för att samarbetet mellan teamen skall fungera effektivt och för att den interna kommunikationen ska bli lyckad.
Today, most software companies use agile development and one of the most common agile methods is Scrum. In recent years, it has become common to use Scrum in larger projects despite its adaptation for smaller projects. Consequently, different frameworks have been developed for scaling Scrum to more than one team and to support the method in larger projects. There are several communicative challenges to this transformation and the transformation has resulted in a change in the agile work that affects the team's way of communicating and interacting. Which puts new demands on collaboration and coordination between the different teams working on the same project. The aim in this study has been to investigate how communication is affected by the fact that something that was originally adapted for smaller projects should now be used for large projects where many different parties are involved and dependent on each other´s work using a qualitative approach. The conclusions have been based on the combination of a theoretical framework and six interviews with Scrum Masters and team members. The study shows that a major communicative challenge is to have continuous communication between the teams and to achieve a collaboration despite the distancing that comes with scaling. Strategies for how to scale Scrum separates, but there is a consensus that structures, a common “language” and vision are required for an effective collaboration between the teams and for internal communication to be successful.

Стилі APA, Harvard, Vancouver, ISO та ін.

22

Koskela, Niklas, and Carolina Aspfjäll. "Agile Risk Management." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44975.

Повний текст джерела

Анотація:

This thesis was done in collaboration with Volvo Cars to inspect their risk management process in light of their recent change to an agile way of working. The question was if their actual risk management differentiates from their directive and if the company could in any way improve their agile risk management. By having qualitative semi-structured interviews with employees in the IT section of the company, we got the picture that not many knew about the IT Risk Management Directive that explains the process, but they are still working within its guidelines. Other sections of the company that is still working traditionally might also benefit from changing to an agile way. However, that would depend on the size of their projects and what kind of work they do since the agile methodology is more turned towards smaller projects that can change direction quickly.

Стилі APA, Harvard, Vancouver, ISO та ін.

23

Norinder, Oskar, and Retta Tsehaye. "Identifierade hinder och utmaningar inom Scrum för spelutveckling och dess lösningsförslag." Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-231111.

Повний текст джерела

Анотація:

Den här studien undersöker hinder och utmaningar som uppstår inom spelutveckling. Mer precist undersöks arbetsmetoden Scrum, som är ett agilt ramverk. Metoden som användes i studien är en kvalitativ undersökning. Semistrukturerade intervjuer genomfördes med personer som har erfarenhet inom Scrum för spelutveckling, för att identifiera deras hinder och utmaningar, men även för att ta fram lösningsförslag. Följaktligen är frågeställningen, ”Vilka hinder och utmaningar identifieras då man använder Scrum inom spelutveckling, och hur kan dessa lösas?”. Lösningsförslagen togs fram med hjälp av både intervjuobjekt och relaterad forskning. Resultatet gav att det fanns hinder och utmaningar inom fem områden. Planering av arbete, spelutvecklingens många discipliner, spelutvecklingens långa projekt, Pre-production fasen och problem som uppstår på grund av själva Scrum-ramverket. Planeringen av arbetet var ett hinder eftersom den bland annat innefattar estimering av arbete, klarkriterium, och vad som skall göras. Lösningsförslagen var att andra metoder skall användas med Scrum, bland annat för att ersätta problemen man har i utforskande faser eller när man har estetiska mål. Kortfattat så fungerar Scrum när det finns information om vad som skall göras och när det skall göras. Problematiken är att den informationen inte alltid är given inom spelutveckling
This study researches issues and challenges that arise within game development. More specific it examines the Scrum methodology, which is an agile framework. A qualitative research method was conducted for this study. In order to identify impediments and challenges, but as well proposals for solutions, semi-structured interviews were conducted with participants who have experience from Scrum within game development. Therefore, the research question in this study is “Which issues and challenges can be identified within game development, and how could they be solved?”. The proposed solutions were constructed with help from both the interviewees and related research. The results of the study located issues and challenges in five different areas. Planning work, the many different discipline present in game development, the long development time for game projects, the Pre-production phase, and the problems that arise from the Scrum framework itself. Planning the work was an impediment because it includes estimating the amount of work, definition of done and what to do. The proposed solutions were, to use other methods together with Scrum, for instance to replace the problems in explorative phases or when working with aesthetic goals. In short, Scrum works when there exists information about what to do and when to do it. The problem is that the information is not always available within game development.

Стилі APA, Harvard, Vancouver, ISO та ін.

24

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.

Повний текст джерела

Анотація:

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 та ін.

25

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.

Повний текст джерела

Анотація:

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 та ін.

26

Lööf, Anton, and Filip Svärd. "Kunskapsöverföring i gränslandet : En studie av systemutvecklingsteam under ett projektmetodikskifte på Folksam." Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-297694.

Повний текст джерела

Анотація:

Enligt det kunskapsbaserade perspektivet är kunskap organisationens viktigaste resurs. Inom dagens organisationer har olika enheter möjligheter att lära av varandra och dra nytta av den kunskapsmängd som genereras internt. För att detta ska lyckas krävs effektiva och utvecklade processer för kunskapsöverföring. I den genomförda studien undersöks hur kunskap överförs mellan systemutvecklingsteam under ett skifte från en vattenfallsmetodik till en agil metodik på företaget Folksam. Uppsatsen syftar även till att besvara vilka faktorer som främjar och hindrar kunskapsöverföring under ett metodikskifte. Med anledning av att allt fler organisationer övergår till en agil projektmetodik samt att forskningen inom den studerade kontexten är begränsad, anses en studie inom området väl motiverad. Studiens teoretiska ramverk tar sin utgångspunkt i kunskapsbegreppet där en diskussion kring de två dominerande kunskapsepistemologierna mynnar ut i uppsatsens förståelse för kunskapsbegreppet. Vidare diskuteras hur kunskapsöverföring kan förstås genom modifiering och förflyttning av kunskapsreservoarer, vilka utgörs av organisationens individer, verktyg och aktiviteter. Ramverket inkluderar också teorier rörande faktorer som påverkar kunskapsöverföring. Den insamlade empirin består huvudsakligen av intervjuer och observationer och visar att kunskapsöverföring mellan team sker i relativt liten utsträckning samt att de tillfällen då kunskap har överförts till stor del organiserats av de agila coacher som Folksam har konsulterat. Kunskapsöverföring främjas på grund av den liknande teamkontexten och på grund av den kunskapsstruktur som den agila metodiken medför, men hindras i och med att teamen inte är motiverade till eller inser värdet av kunskapsöverföring, vilket har sin grund i att teamen har kommit olika långt i övergången till den nya metodiken.
According to the knowledge-based view of the firm, knowledge is an organizations’ most important resource. In today’s organizations, different units have the opportunity to learn from each other and make use of the knowledge that is being generated internally. However, in order for this to succeed there is a need for effective and well-developed processes for the transfer of knowledge. In the performed study, research has been done on how knowledge is transferred between system development teams during a shift from a waterfall methodology to an agile methodology at the company Folksam. The paper also aims to answer what factors that facilitate and what factors that impede knowledge transfer during a methodology shift. As an increasing numbers of organizations change to an agile methodology and previous research within the specific context is limited, a study within the area is well motivated. The theoretical framework is based on the concept of knowledge itself where a discussion of the two dominating epistemological perspectives is concluded in the thesis understanding of knowledge. Further, knowledge transfer is being defined as either a modification or transfer of knowledge reservoirs, comprised by the organization’s individuals, tools and activities and in which knowledge is embedded. The theoretical framework also includes factors influencing knowledge transfer. The empirical foundation consists mainly of interviews and observations and shows that inter-team knowledge transfer is limited, and that the occasions where transfer does take place are generally organized by the agile coaches consulted by Folksam. When knowledge transfer takes place it is facilitated by the similar team context and by the knowledge structure entailed by the agile methodology, but impeded by the team members not being motivated or able to realize the benefits with knowledge transfer, which is rooted in the teams being in different stages of the transition to the new methodology.

Стилі APA, Harvard, Vancouver, ISO та ін.

27

Tošner, Jiří. "Aplikace agilní metodiky Scrum a využití podpůrných softwarových nástrojů." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2015. http://www.nusl.cz/ntk/nusl-225252.

Повний текст джерела

Анотація:

Agile software development methodologies are very popular for their efficiency and flexibility. This thesis focuses on agile software development methodology called Scrum. Basic description and comparison of traditional and agile methodologies is mentioned at first. Attention is paid to methodology Scrum which is shown on an example of usage by a specific company. It is convenient to use some software tool for organization of Scrum methodology. Therefore, an overview of the most common tools and basic comparison of software tools for organizing this methodology is presented. Conclusion of this thesis is recommendation for improvements for the investigated team, based on issues which were identified.

Стилі APA, Harvard, Vancouver, ISO та ін.

28

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

Повний текст джерела

Анотація:

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 та ін.

29

Ghahestani, Shervin, and Pauline Korssell. "Agil transformation för produktutveckling i mjukvarubranschen : Ett arbete om upplevda utmaningar och fördelar med agilt arbetssätt." Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-290047.

Повний текст джерела

Анотація:

Allt fler aktörer uppkommer på den redan konkurrenskraftiga marknaden vilket ställer höga krav på utveckling av nya innovativa produkter för företag inom mjukvarubranschen. Detta leder till att företag måste förändra sin struktur och sitt arbetssätt för att kunna anpassa sin produktutveckling efter kunderna och marknaden. Ett sätt för företag att kunna fortsätta vara konkurrenskraftiga och bemöta marknadens behov är att implementera agila arbetssätt. Syftet med detta arbete är att bidra till ökad kunskap kring hur produktutvecklingsprocessen för en agil transformation från beslut till implementation kan ske i mjukvarubranschen. Arbetet har undersökt tre frågeställningar relaterade till agil transformation i mjukvarubranschen. Inledningsvis genomfördes en litteraturstudie för att erhålla en ökad förståelse för produktutveckling i mjukvarubranschen och för det agila arbetssättet. Vidare utfördes en kvalitativ semistrukturerad intervjuundersökning med fyra respondenter från tre företag där samtliga arbetar med agila arbetssätt och produktutveckling inom mjukvarubranschen. Den kvalitativa studien undersökte vilka utmaningar och potentiella fördelar en agil transformation kan generera samt vad som kännetecknar en lyckad agil transformation. Utifrån resultatet av denna studie utformades ett antal kategorier som kan användas som riktlinjer för hur en organisation kan gå tillväga vid en agil transformation i mjukvarubranschen. Studien visar att en agil transformation är en komplex och tidskrävande process. Utmaningar med agil transformation innefattar att ett agilt arbetssätt ofta blir beroende av en nyckelperson, det kräver en hög samverkan och ökad förståelse för varandras arbetsuppgifter samt ett anpassningsbart tankesätt som är mottagligt för förändring. Däremot genererar den agila transformationen fördelar så som en ökad produktivitet och användarnöjdhet, minskat antal defekter och en kortare ledtid hos samtliga företag. För att lyckas med en agil transformation visar studien på att ett företags medarbetare bör vara mottagliga för förändring och att motivet till transformationen borde komma inifrån organisationen. Sammanfattningsvis resulterade den agila transformationen i en förbättrad mjukvaruutveckling.
A large number of businesses are emerging on the already competitive market which places high demands on the development of new innovative products for companies in the software industry. As a result, companies must change the structure of the organization and their methods. Due to this, they have to customize their product development in order to meet the requirements of the customers and the markets demand and maintain their competitiveness. One way for companies to stay competitive is by implementing agile working methodologies. This study aims to contribute with knowledge and investigate the processes of an agile transformation from decision-making to implementation in the software industry. The study has examined three problem statements related to the agile transformation in the software industry. Initially a literature review was performed to gain an insight into product development in the software industry and the agile working methodologies. Furthermore, a semi structured qualitative interview was conducted which involved four respondents from three companies that work with agile working methodologies and product development in the software industry. This qualitative study examined the challenges and possible opportunities that an agile transformation generates as well as the characteristics of a successful transformation. Based on the result of this study, several categories were chosen and treated as guidelines for how an organization in the software industry can approach the agile transformation and proceed with it successfully. The results of the study demonstrate that an agile transformation is a complex and time-consuming process. The many challenges involving the agile transformation includes that the agile working methodology often becomes dependent of a single key person, it also requires collaboration, an increased understanding of each other’s work as well as an adaptable mindset that is receptive towards change. However, the agile transformation enables advantages amongst all the companies such as an increased productivity and user satisfaction, decreased number of defects as well as a reduced leadtime. To succeed with an agile transformation, it is of importance that a company’s employees are receptive towards change and that the motive behind the transformation comes internally within the organization. In conclusion, the agile transformation improved and strengthened the companies’ software development.

Стилі APA, Harvard, Vancouver, ISO та ін.

30

Tománek, Martin. "Řízení projektů agilního vývoje softwaru na základě PRINCE2 a Scrum." Doctoral thesis, Vysoká škola ekonomická v Praze, 2010. http://www.nusl.cz/ntk/nusl-203723.

Повний текст джерела

Анотація:

Software development projects often fail. Recently the agile software development frameworks have been massively adopted and used to overcome the root causes of the project failure. The use of the agile frameworks results in the more successful delivery of smaller software development projects. Companies however implemented in the past many generic project management frameworks and still use them to manage the full portfolio of their projects especially the medium and large software development projects. In such cases the agile development teams are organized in projects that are managed by project managers according to these generic project management frameworks. Both these frameworks must be analysed and tailored carefully to be successfully applied together. The objective of this dissertation thesis is to design the agile software development project management framework based on PRINCE2 and Scrum frameworks. The benefits of this new framework are the enrichment of the simple agile framework Scrum by project management elements and the enrichment of the generic project management framework PRINCE2 by the agile principles and agile team management practices. The first part of the thesis is focused on the analysis of project management and agile development frameworks. The main focus is on the current usage, the measurement of the project success and the identification of problems that the projects face to. Prior to the design of the new framework the research was executed in the global company to discover the specific problems in software development projects and to measure the actual project success rate. The framework is then designed in the next part. The framework was successfully implemented in the same global company and the project success rate was again analysed. The result is positive and the implementation of this framework resulted in the improved project success rate. Also two additional case studies were conducted to check the viability of the designed framework.

Стилі APA, Harvard, Vancouver, ISO та ін.

31

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

Повний текст джерела

Анотація:

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 та ін.

32

Cho, Juyun Joey. "An Exploratory Study on Issues and Challenges of Agile Software Development with Scrum." DigitalCommons@USU, 2010. https://digitalcommons.usu.edu/etd/599.

Повний текст джерела

Анотація:

The purpose of this dissertation was to explore critical issues and challenges that might arise in agile software development processes with Scrum. It also sought to provide management guidelines to help organizations avoid and overcome barriers in adopting the Scrum method as a future software development method. A qualitative research method design was used to capture the knowledge of practitioners and scrutinize the Scrum software development process in its natural settings. An in-depth case study was conducted in two organizations where the Scrum method was fully integrated in every aspect of two organizations' software development processes. One organization provides large-scale and mission-critical applications and the other provides small- and medium-scale applications. Differences between two organizations provided useful contrasts for the data analysis. Data were collected through an email survey, observations, documents, and semi-structured face-to-face interviews. The email survey was used to refine interview questions; all of the interviews were audio-taped and transcribed, and later coded for analysis. Triangulation in the data collection process provided useful information for different perspectives on the issues, allowed for cross-checking, and yielded stronger substantiation of concepts and common categories. The research presented four common categories of issues and challenges of the Scrum method, and management guidelines to help organizations that are already using the Scrum method or planning to employ it in the future. The framework for a hybrid software development model is then proposed as a future study.

Стилі APA, Harvard, Vancouver, ISO та ін.

33

Chumpitaz, Brayan, Junior Rubio, Sandra Rodriguez, and Alexandra Hinostroza. "Application of the scrum framework to optimize time in construction projects." Institute of Electrical and Electronics Engineers Inc, 2020. http://hdl.handle.net/10757/656412.

Повний текст джерела

Анотація:

El texto completo de este trabajo no está disponible en el Repositorio Académico UPC por restricciones de la casa editorial donde ha sido publicado.
Currently, the construction industry is characterized by a high competition between its companies. Due to this, companies must guarantee that the performance of their projects is possible by using an appropriate management system which allows an adequate planning of activities, since selecting an inadequate system can cause serious inconveniences such as having rework and increase cost and time in projects. Therefore, the construction industry is constantly searching for management models that can minimize the previously mentioned inconveniences in order to differentiate themselves and take advantage of their competitors. Precisely, the Scrum framework, conceived in the software engineering industry, is an alternative to traditional projects management, offering an exponential improvement in communication for project teams and improving the planning of activities, through an iterative framework that allows flexibility for changing requirements, reduces uncertainty and creates reliability for what was planned. Thus, this research adapts and applies the Scrum framework within a construction project, optimizing considerably the execution time.

Стилі APA, Harvard, Vancouver, ISO та ін.

34

Hark, Dominik H. [Verfasser]. "Agile Programmierung : Lehren aus dem privaten Baurecht für eine agile Programmierung (insbesondere durch den Einsatz von SCRUM) / Dominik H. Hark." Frankfurt a.M. : Peter Lang GmbH, Internationaler Verlag der Wissenschaften, 2020. http://d-nb.info/1223113027/34.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

35

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.

Повний текст джерела

Анотація:

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 та ін.

36

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.

Повний текст джерела

Анотація:

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 та ін.

37

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.

Повний текст джерела

Анотація:

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 та ін.

38

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.

Повний текст джерела

Анотація:

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 та ін.

39

Gergeľ, Frederik. "Optimalizace projektového řízení zavedením agilní metodiky." Master's thesis, Vysoké učení technické v Brně. Fakulta podnikatelská, 2019. http://www.nusl.cz/ntk/nusl-402039.

Повний текст джерела

Анотація:

The thesis deals with optimization of project management in a custom web development company. The theoretical part is devoted to the description of traditional and agile approaches of project management. The analytical part describes the current state of project management. The main part of the thesis consists of optimization of project management by agile SCRUM method, case study implementation and evaluation of benefits and costs of introduced change.

Стилі APA, Harvard, Vancouver, ISO та ін.

40

Shafie, Maryam. "Förbättrad metod för tidig mobilisering av planerat kejsarsnittförlösta En kvalitativ studie av patienternas upplevelser." Thesis, Hälsohögskolan, Högskolan i Jönköping, HHJ. Kvalitetsförbättring och ledarskap inom hälsa och välfärd, 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:hj:diva-27530.

Повний текст джерела

Стилі APA, Harvard, Vancouver, ISO та ін.

41

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.

Повний текст джерела

Анотація:

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 та ін.

42

Viklund, Anton, and Elias Ahlman. "Systemförvaltning med en agil metod : En fallstudie om Scrum inom systemförvaltning." Thesis, Mittuniversitetet, Avdelningen för informationssystem och -teknologi, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:miun:diva-31374.

Повний текст джерела

Анотація:

At present, the area of agile management methods is a relatively unexplored area. The purpose of this study has been to investigate how well suited agile methods are for use in IT-maintenance. This has been done by collecting material on the subject, which acted as a base for a case study. In the study, the collected material from the investigated company, external companies and observations performed at the investigated company has been analyzed against existing theory in the field. Furthermore, conclusions have been drawn from information gathered during the course of the study. Based on this survey, it can be noted that in the activities that were investigated, an implemented agile method can add value to the maintenance operation. These added values present themselves in the form of a better and clearer structure, better communication and more effective working methods. One of the biggest challenges of agile agility in management has proved to be cross-functionality in the team. In this case as well as in other theoretical cases, the lack of cross functionality has been something identified. The theoretical cases show that the introduction of an agile method helps maintenance teams to become cross-functional. In the business investigated in this study, there were only indications stating that the business had started a transition to a cross-functional team. The fact that no definitive link between agile methods and transition to cross-functionality was identified in this case is considered to be due to the fact that the agile work was at an earlier stage. In conclusion, this study shows that agile methods are well-suited for use in maintenance, but some modifications to the agile approach need to be implemented.
I dagsläget är området agila metoder inom systemförvaltning ett relativt outforskat område. Syftet med denna studie har varit att undersöka hur väl lämpade agila metoder är för en förvaltande verksamhet. Detta har gjorts genom att bakgrundsmaterial i ämnet samlats in, för att bilda en teoretisk grund för en fallstudie. I studien har det insamlade materialet från det undersökta företaget, externa företag samt egna observationer som utförts på fallföretaget analyserats gentemot existerande teori inom området, varefter egna slutsatser dragits. Utifrån studien kan det konstateras att i den verksamhet som undersökts har en implementerad agil metod tillfört värde till verksamheten. Detta i form av en bättre och tydligare struktur, bättre kommunikation och ett effektivare arbetssätt. En av de största utmaningarna med att arbeta agilt inom systemförvaltning har visat sig vara tvärfunktionalitet i teamet. I detta fall såväl som i andra teoretiska fall har avsaknaden av tvärfunktionalitet varit något som identifierats. De teoretiska fallen påvisar att införandet av en agil metod har hjälpt förvaltningsteamen att bli tvärfunktionella. I verksamheten som undersöktes uppmärksammades enbart indikationer på att verksamheten påbörjat en övergång till ett tvärfunktionellt team. Att ingen definitiv koppling mellan agila metoder och övergång till tvärfunktionalitet identifierades i detta fall anses bero på att det agila arbetet befann sig i ett tidigare skede. Avslutningsvis styrker studien att agila metoder är väl lämpade för användning inom systemförvaltning, men vissa modifikationer i det agila arbetssättet behöver genomföras.

Стилі APA, Harvard, Vancouver, ISO та ін.

43

Devarapalli, Surendra. "AGILE BUSINESS INTELLIGENCE DEVELOPMENT CORE PRACTICES." Thesis, Högskolan i Borås, Institutionen Handels- och IT-högskolan, 2013. http://urn.kb.se/resolve?urn=urn:nbn:se:hb:diva-17241.

Повний текст джерела

Анотація:

Today we are in an age of Information. The systems that effectively use the vast amount of data available all over the world and provide meaningful insight (i.e. BI systems) for the people who need it are of critical importance. The development of such systems has always been a challenge as the development is outweighed by change. The methodologies that are devised for coping with the constant change during the system development are agile methodologies. So practitioners and researchers are showing keen interest to use agile strategies for the BI projects development.The research aims to find out how well the agile strategies suit for the development of BI projects. The research considers a case study in a very big organization as BI is organization centric. There by assessing the empirical results that are collected from interviews the author is trying to generalize the results. The results for the research will give an insight of the best practices that can be considered while considering agile strategies and also the practical problems that we may encounter on the journey. The findings have implications for both business and technical managers who want to consider agile strategies for the BI/DW development projects.
Program: Masterutbildning i Informatik

Стилі APA, Harvard, Vancouver, ISO та ін.

44

Zubova, Jelena. "Laiko įverčių analizė ir vizualizavimas tiriamajį darbą organizuojant remiantis "Agile" praktikomis." Master's thesis, Lithuanian Academic Libraries Network (LABT), 2014. http://vddb.library.lt/obj/LT-eLABa-0001:E.02~2012~D_20140701_163839-11850.

Повний текст джерела

Анотація:

Magistro baigiamajame darbe „Laiko įverčių analizė ir vizualizavimas tiriamąjį darbą organizuojant remiantis „Agile“ praktikomis“ yra išanalizuota darbo organizavimo procesų ir projektų valdymo metodų mokslinė ir metodinė literatūra, palyginti dažniausiai naudojami darbo organizavimo metodai su klasikiniais metodais, ištirti bei susisteminti darbo organizavimo procesų ir projektų valdymo metodai. Darbe pateiktas darbo proceso užbaigimo laikotarpio prognozių sudarymo metodas, leidžiantis apskaičiuoti projekto užbaigimo laikotarpį. Taip pat pateiktas aprašyto metodo praktinis pavyzdys su apskaičiuotų reikšmių lentelėmis bei diagramomis. Darbe pateiktas pagerintas darbo proceso vaizdavimo metodas, leidžiantis įvertinti ir aiškiau pavaizduoti besikeičiančią darbų apimtį tarp iteracijų ir iteracijų metu. Iki šiol šaltiniuose buvo pateikiami metodai, nagrinėjantys tik statinės darbų apimties vaizdavimą. Šis darbas galėtų būti naudingas daugelyje veiklos sričių. Pasirinkus dėstytojo specialybę, įgytas žinias galima pritaikyti laboratorinių, praktinių bei kursinių darbų organizavimo procese. Šios žinios galėtų būti naudingos visur, kur tik gali prireikti darbo organizavimo žinių bei įgūdžių.
Analysis of time estimates and visualization organizing reseach according to Agile practices Student: Jelena Zubova Supervisor: Dr. Rimgaudas Laucius In the Master Thesis "Analysis of time estimates and visualization organizing research according to Agile practices" the following tasks are accomplished: scientific and methodical literature related to the process of work organizing and the methods of project management is reviewed; the commonly used methods of work organizing are compared to the classic methods; the methods of work organizing and project management are analyzed and systematized. The method of forecasting the time of working process is presented in the Thesis. The method allows calculating the time of working process. The example of application of this method is presented as well including tables with calculated values and diagrams. The improved method of working process visualization is presented in the Thesis. The method allows evaluating and depicting the changing volume of work between iterations as well as during iterations in a more readable way. So far only the methods dealing with the visualization of static volume of work have been proposed in the literature. The Thesis could be useful in many fields. In regard to teaching, the acquired knowledge could be used when organizing laboratory works, practicals and project works. The knowledge could be useful in every area that requires the skills of work organizing.

Стилі APA, Harvard, Vancouver, ISO та ін.

45

Caiman, Elin. "Psykologisk säkerhet i scrum-team : en fallstudie om kulturella skillnader." Thesis, Luleå tekniska universitet, Institutionen för ekonomi, teknik och samhälle, 2017. http://urn.kb.se/resolve?urn=urn:nbn:se:ltu:diva-63962.

Повний текст джерела

Анотація:

Syfte - Att skapa en djupare förståelse för hur kulturskillnader påverkar arbetet med scrum, med specifikt fokus på psykologisk säkerhet. Metod – En kvalitativ fallstudie med induktiv ansats har gjorts där semistrukturerade intervjuer tillsammans med observationer har använts för att samla in data. Tillsammans med litteratur har sedan en innehållsanalys gjorts. Resultat – Studien har identifierat tre dimensioner som är viktiga att beakta vid arbetet med scrum. Dessa dimensioner är Inställningen till människan, Hanteringen av människan och Beteenden av människan, och belyser hur kulturskillnader skapar olika förutsättningar för psykologisk säkerhet i scrum-team. Vidare kan dessa insikter leda till ett förbättrat arbete med scrum och i förlängningen skapa mer innovativa och konkurrenskraftiga scrum-team och organisationer. Teoretiska implikationer – Studien bidrar till litteraturen om psykologisk säkerhet med en empirisk förankrad teori som visar hur kulturskillnader skapar olika konsekvenser för psykologisk säkerhet. Mer specifikt visar den hur dessa kulturskillnader hänger samman och påverkar varandra. Ett andra bidrag som den här studien gör är att skapa djupare förståelse för hur implementering av scrum och agil övergång med fördel bör ske i en ny kultur, som karaktäriseras av hög maktdistans, osäkerhetsundvikande och kollektivism. Praktiska implikationer – Studiens resultat visar att de identifierade kulturskillnaderna hänger ihop vilket innebär att samtliga behöver adresseras för att skapa ett psykologiskt säkert scrum-team i en ny kultur. Psykologisk säkerhet är en förutsättning för självorganiserade team, så som scrum-team, och därmed är studiens resultat av intresse för gruppchefer på samtliga företag som arbetar med scrum, både i olika nationella kontexter och med multinationella team samt i globala virtuella team.
Purpose – To create a deeper knowledge for how cultural differences influences the work with scrum, with specific focus on psychological safety. Method – A qualitative case study with an inductive approach have been carried out where semi-structured interviews together with observations have been used to collect data. Together with literature a content analysis was then preformed. Result – The study has identified three dimensions that are important to consider when working with scrum. These dimensions are Attitude to the human, Managing the human and Behaviors of the human, and these show how cultural differences creates different basis for psychological safety in scrum teams. Moreover, these insights can lead to improved work with scrum and in turn create more innovative and competitive scrum teams and organizations. Theoretical implications – The study contributes to the literature about psychological safety with empirical theory that shows how cultural differences creates different consequences for psychological safety. More specifically, it shows how these differences in culture are related to one another and affects each other. Another contribution of this study is that the result creates a deeper understanding of how the implementation of scrum and agile transitioning best can be done in a new culture, specifically that is characterized by high power distance, uncertainty avoidance and collectivism. Practical implications – The study shows that the identified differences in culture are related to each other, which means that all needs to be addressed to create a psychological safe scrum team in a new culture. Psychological safety is a prerequisite for self-organized teams, such as scrum teams, and thus the result is of interest for group managers in all companies and organizations working with scrum, both in different cultural contexts and with multinational teams as well as in global virtual teams.

Стилі APA, Harvard, Vancouver, ISO та ін.

46

Ansari, Asif Akhtarhussain. "Decoding Agile: Challenges and Solutions A Qualitative study of the transition to Agile method." Thesis, Uppsala universitet, Institutionen för samhällsbyggnad och industriell teknik, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-448176.

Повний текст джерела

Анотація:

The needs of the consumer are drastically changing with increased awareness, technology, and innovation. Information technology services are no longer part of the support function but a full-scale solution; the increased demand for personalized, real-time, and hassle-free services has burdened software solution providing companies. Over the last decade, Agile project management has gained popularity among various industries and specifically in the Information Technology industry and is often considered a silver bullet to solve different software project management challenges. Agile project management revolutionized the way software projects are developed and organized. However, organizations find it challenging to implement agile principles as the process requires an organization-wide cultural and social transformation. Managers face several barriers when they try to bring agile approaches in traditional organizations regarding technology, mindset, practices. It’s not adequate to just start learning and implementing new ways of working. The transition process needs parallel or equally salient activities of dealing with challenges on the organization and team level. This study provides insights for software organizations willing to undergo an agile transition that needs an initial understanding of various challenges, which can be a potential pitfall in the transition process.

Стилі APA, Harvard, Vancouver, ISO та ін.

47

Spasibenko, Nikolay, and Besiana Alite. "Project Suitability for Agile methodologies." Thesis, Umeå universitet, Handelshögskolan vid Umeå universitet, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-18428.

Повний текст джерела

Анотація:

Software projects are known for their failure rate, where many are being delivered late, over budget or being canceled while in development. The reason to it is changing requirements and intangibility of the software. Being so abstract it is difficult to imaging all the aspects of the software at the requirements stage. Also technology is playing a major role since processing power, storage space, and data transfer speeds are improving from year to year. Agile methodologies are addressing projects with unclear requirements making process of implementing new specifications along the project much easier and less costly. However the success rate of the software projects did not improve much since the introduction of Agile methodologies. This thesis is looking at what type of projects fit different methodologies and what are factors which practitioners should take into account when selecting methodology for a particular project, The thesis opens up with introduction which sets the research question and provides a brief background to the research topic. In subsequent chapter literature review is conducted to find out what does literature and other researchers have said on the same topic. Third chapter discusses underlying research philosophy and discusses the data collection tools. Next chapter discusses the findings of the research. Interviews has been conducted with project management professionals from Sweden, US, UK and Canada. It was identified through the analysis of patters that Agile methodologies are not well suited for projects involving databases, embedded development and computationally complex projects. Through the analysis of the questionnaire several project characteristics were identified which suit Agile methodologies better than traditional ones: unclear requirements, high risk of failure etc… In the last chapter the thesis concludes the findings and its theoretical and practical implications.

Стилі APA, Harvard, Vancouver, ISO та ін.

48

Naseem, Junaid, and Wasim Tahir. "Study and analysis of the challenges and guidelines of transitioning from waterfall development model to Scrum." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2679.

Повний текст джерела

Анотація:

Software engineering practices have experienced significant changes over the period of past two decades. Keeping in view the competitive market trends, now is the high time for many organizations to shift from traditional waterfall models to more agile technologies like Scrum [22][23]. A change of this magnitude is often not easy to undertake. The reason that both software engineering techniques are different in many respects, organizations require considerable amount of analysis of the whole transitioning process and possible scenarios that may occur along the way. Small and medium organizations are normally very skeptical to the change of this magnitude. The scale of change is not limited to only software processes, in fact, difficult part is to deal with old attitudes and thinking processes and mold them for the new agile based Scrum development. The process of change therefore need to be understood in the first place and then carefully forwarded to the implementation phase.

Стилі APA, Harvard, Vancouver, ISO та ін.

49

Nord, Olsson Hjalmar, and Daniel Wiskman. "Motivation och Agila aktiviteter : En fallstudie om hur agila aktiviteter motiverar deltagare i ett utvecklarteam på Tradera." Thesis, Uppsala universitet, Företagsekonomiska institutionen, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:uu:diva-304079.

Повний текст джерела

Анотація:

Studiens syfte har varit att undersöka hur agila aktiviteter kan bidra till att motivera deltagare i ett agilt utvecklarteam. För att besvara studiens syfte genomfördes en fallstudie under nio veckor där ett utvecklarteam på företaget Tradera observerades. Utöver observationerna gjordes även intervjuer med en majoritet av teamets medlemmar. Genom att kombinera den klassiska motivationsteorin Job Characteristics Modell med scrumteori utvecklades en konceptuell analysmodell. Den konceptuella analysmodellen operationaliserar egenskaper hos de agila aktiviteterna som enligt teorin ger upphov till hög arbetsmotivation. Genom intervjuerna operationaliseras begreppet motivation – där en intervjuteknik som använts i tidigare studier för att mäta motivation anammats. Resultatet av studien visar att de agila aktiviteterna planeringsmöte, demonstration och återblicksmöte i det studerade utvecklarteamet på Tradera innehar egenskaper som skapar förutsättning för hög arbetsmotivation. I en teoretisk men inte empirisk mening stöds sambandet mellan egenskaperna och hög arbetsmotivation. Där berättelser från teammedlemmar om episoder av hög motivation kopplat till de agila aktiviteterna ger en indikation på att egenskaperna hos aktiviteterna gett upphov till psykologiska tillstånd som resulterat i en hög arbetsmotivation.
The purpose of this paper is to examine how agile activities can act as motivators for members of an agile development team. In order to serve this purpose a field study of nine weeks was carried out during which an agile development team at Tradera were observed. In addition to the field study interviews where conducted with a majority of the team members. A classical motivational theory in the form of Job Characteristics Model (JCT) and theory about scrum was used to form a conceptual analysis model. The model operationalizes characteristics of the agile activities, which according to JCT creates high work motivation. The concept of motivation was operationalized through the use of an interview technique that has been used in numerous previous studies in order to measure motivation and other non-tangible factors. The study shows that the agile activities planning session, demonstration and retrospective used by the development team at Tradera has inherent characteristics that creates a setting in which high work motivation has the possibility of being prevalent. In a theoretical, but not empirical, way the results of the study supports a connection between the presence of the characteristics in the agile activities and high motivation. Where stories from team members of episodes of high motivation during the agile activities gives an indication of the activities.

Стилі APA, Harvard, Vancouver, ISO та ін.

50

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.

Повний текст джерела

Анотація:

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 та ін.

Дисертації з теми "Agile Scrum"

Оформте джерело за APA, MLA, Chicago, Harvard та іншими стилями