Relevant bibliographies by topics / And Scrum

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'And Scrum'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

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

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'And Scrum.'

Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.

You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.

Journal articles on the topic "And Scrum"

1

Bradley, Edward J., Bob Hogg, and David T. Archer. "Effect of the PreBind Engagement Process on Scrum Timing and Stability in the 2013–16 Six Nations." International Journal of Sports Physiology and Performance 13, no. 7 (August 1, 2018): 903–9. http://dx.doi.org/10.1123/ijspp.2017-0531.

Full text
Abstract:
This study examined whether changes in scrum engagement laws from the “crouch-touch-set” in 2013 to the “PreBind” engagement from 2014 onward have led to changes in scrum characteristics, specifically timing, in international rugby union. Duration and outcomes were identified for all scrums occurring in the 2013–16 Six Nations (N = 60 games) using video analysis. Scrum duration increased after the introduction of the PreBind engagement from 59 s in 2013 to 69 s in 2016 (P = .024, effect size = 0.93). A significant increase in mean contact duration per scrum occurred when prebinding was adopted (P < .05), moving from 7.5 s under the crouch-touch-set process to 8.5, 10.0, and 10.8 s with PreBind in 2014, 2015, and 2016 (effect size = 0.71, 2.05, and 3.0, respectively). The number of scrum resets and collapsed scrums, along with early engagement and pulling down infringements, was lower under the PreBind process. Overall, the PreBind engagement resulted in longer scrums with significant increases observed in overall and contact durations, with improved stability-related characteristics. The longer contact time is a consequence of increased stability with a shift from high-energy impact to a sustained push phase with a lower force that is a benefit to player welfare.
APA, Harvard, Vancouver, ISO, and other styles
2

Gonçalves, Luis. "Scrum." Controlling & Management Review 62, no. 4 (April 25, 2018): 40–42. http://dx.doi.org/10.1007/s12176-018-0020-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gloger, Boris. "Scrum." Informatik-Spektrum 33, no. 2 (March 3, 2010): 195–200. http://dx.doi.org/10.1007/s00287-010-0426-6.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Alsaber, Leanah, Ebtesam Al Elsheikh, Sarah Aljumah, and Nor Shahida Mohd Jamail. "“Scrumbear” framework for solving traditional scrum model problems." Bulletin of Electrical Engineering and Informatics 10, no. 1 (February 1, 2021): 319–26. http://dx.doi.org/10.11591/eei.v10i1.2487.

Full text
Abstract:
Software engineering is a discipline that is little understood by people. It defines how software is developed and maintained to meet the clients’ requirements. Software engineers follow certain systems and standards in their work to meet the clients’ desires. It is on this background that engineers follow specific models in coming up with the final product. One of the models highly used is scrum, which is one of the agile methodologies. However, despite being highly used, it has inherent flaws that need to be corrected. Those flaws are product owner continues changing; do not accept changes in working scrum, sprint’s release time limitation, finally wasting team time within each sprint. This paper presents a new framework, which is an updated version of the current Scrum, to overcome the scum models mentioned issues. In this study, a new framework is presented in a way that is understandable and needed by software developer’s team upon the collected qualitative and quantitative data. The implementation was by making some changes to the current scrum model leading to the “Scrumbear”, certain flaws can be corrected. One of the presented changes involve adding the control master rule to ensure controlling the requirements changing.
APA, Harvard, Vancouver, ISO, and other styles
5

Lallemand, Benjamin, Christophe Clanet, Sylvain Blanchard, Patricio Noriega, Julien Piscione, Olivier Chaplain, Didier Retière, and Caroline Cohen. "Peak Compression Force Physics in Rugby Union Scrum." Proceedings 49, no. 1 (June 15, 2020): 151. http://dx.doi.org/10.3390/proceedings2020049151.

Full text
Abstract:
Scrums play a major role in Rugby Union games, and are historically known as a showdown between the two packs of opposing teams, composed of their eight forwards players organized in a 3-4-1 configuration, respectively. We investigate scrum mechanics by working with professional male forward players from Racing 92, a high-level French Rugby club, and measuring the forces they apply on the French Rugby Federation instrumented scrum machine. Signal analysis reveals two major phases in the force production during a scrummaging effort: an impulsive engagement force, and then a force sustained for a few seconds. We experimentally compare individual performances of the engagement phase. We discuss the influence of the mass and the engagement speed of the players, and we introduce the model we are investigating to describe the individual impact on a scrum machine. We expect this model to be the elementary component of a collective model of a pack.
APA, Harvard, Vancouver, ISO, and other styles
6

Kanwal, Madiha. "Technology Integration Pattern For Distributed Scrum of Scrum." IOSR Journal of Computer Engineering 4, no. 4 (2012): 13–23. http://dx.doi.org/10.9790/0661-0441323.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Pawar, Rupali Pravinkumar, and Kirti Nilesh Mahajan. "Implementation of Change Management in Software Development by using Scrum Framework." International Journal of Advanced Research in Computer Science and Software Engineering 7, no. 7 (July 30, 2017): 400. http://dx.doi.org/10.23956/ijarcsse.v7i7.164.

Full text
Abstract:
This paper will focus on implementation of change management in Scrum software development framework . Scrum is one of the mostly used software development framework from the Agile software development methodology. Scrum is based on iterative and incremental process. It is suitable for unstable requirements. The use of Scrum proved to be beneficial due to tight schedule and loosely defined user requirements that often changed during the development. The aim of the paper to study implementation process of change management in Scrum . First part of paper gives detailed information of Scrum framework. The middle of the paper presented the organizational process of agile software development using Scrum. Finally, the paper point out key points for managing changes in Scrum implementation. The primary data collection method was interviews of the industry expertise. The secondary source of data is reference books and Internet articles. This paper will help to understand basics of Scrum software development framework and process of change management in developing projects by using Scrum framework.
APA, Harvard, Vancouver, ISO, and other styles
8

Holtzhausen, Nico, and Jeremias J. de Klerk. "Servant leadership and the Scrum team’s effectiveness." Leadership & Organization Development Journal 39, no. 7 (September 3, 2018): 873–82. http://dx.doi.org/10.1108/lodj-05-2018-0193.

Full text
Abstract:
Purpose Scrum is a development methodology that has been rapidly gaining popularity over the last decade particularly for software development teams. The Scrum master is sometimes viewed as a servant leader of the Scrum team. The purpose of this paper is to investigate to what extent Scrum masters actually make use of servant leadership and how this impacts on the team’s effectiveness via mediating processes. Design/methodology/approach The research followed a quantitative approach. An online questionnaire was prepared and completed by 71 Scrum team members (excluding Scrum masters) and 22 Scrum masters in more than ten organizations based in Western Cape, South Africa. Findings Scrum masters in this sample extensively used the servant leadership approach, but those who are also appointed as formal team leaders are seen to be considerably better servant leaders by team members. There is a moderately strong correlation between servant leadership of the Scrum master and team effectiveness. It was found that high levels of psychological safety do not necessarily translate into team performance. Research limitations/implications Research was only performed at the unit level of analysis and not the team or organizational level. This was a cross-sectional study and variations over time were not considered. Practical implications The results confirm the importance of servant leadership skills when identifying and developing Scrum masters, appointing the formal team leader role in Scrum teams and implementing Scrum practices effectively. Originality/value As could be established, this is the first time that the role of servant leadership in Scrum teams was formally investigated.
APA, Harvard, Vancouver, ISO, and other styles
9

Ramos, Aline Bentes, and Dalton Chaves Vilela Junior. "A Influência do Papel do Scrum Master no Desenvolvimento de Projetos Scrum." Revista de Gestão e Projetos 08, no. 03 (December 1, 2017): 80–99. http://dx.doi.org/10.5585/gep.v8i3.556.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Kalyani, Darshita, and Devarshi Mehta. "Study of Agile Scrum and Alikeness of Scrum Tools." International Journal of Computer Applications 178, no. 43 (August 19, 2019): 21–28. http://dx.doi.org/10.5120/ijca2019919318.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "And Scrum"

1

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

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

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

Full text
Abstract:

Under sent 1990-tal började utvecklare att bli mer och mer missnöjda med rådande arbetsformer i projekt. Utvecklarna upplevde att modeller som vattenfallsmodellen inte längre speglade verkligheten för utvecklingen. Detta missnöje resulterade i att en mängd nya arbetsmodeller uppstod och 2001 samlades de under Agile Manifesto. Agile lägger tyngdpunkten på individfokus, fungerande mjukvara, kundsamarbete och föränderlighet. Scrum är just nu ett av de mest populära ramverken inom agile.Tieto har använt sig av agile och då främst Scrum i sina projekt sedan tidigt 2000-tal och haft lyckat resultat. Projekten som använt Scrum har levererat i tid och haft nöjda kunder. Dock har Tieto inte utrett vilka konsekvenser Scrum får för ett projekt. Denna studies fokus låg på att undersöka konsekvenserna av att använda Scrum i ett projekt. Detta gjordes med hjälp av intervjuer, observationer och en enkät där arbetet för ett antal Scrum-projekt studerades. Resultatet jämfördes sedan med rådande litteratur inom ämnet samt studier från The Standish group, VersionOne och Yahoo!.Rapportens slutsats är att Scrum påverkar mer än bara arbetssättet och att dessa effekter måste betänkas. Många positiva konsekvenser av användandet av Scrum kunde ses men även ett antal risker upptäcktes. För ett lyckat Scrum-projekt behövs en delaktig produktägare, en engagerad ScrumMaster och ett team som tycker om att ta eget ansvar.


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

APA, Harvard, Vancouver, ISO, and other styles
3

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

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

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

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

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

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

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

Full text
Abstract:
Det här är ett examensarbete gjort på uppdrag av Gastrogate AB. Målet med examensarbetet är att utvärdera projektmetodiken Scrum i en grupp med endast en utvecklare. För att undersöka detta applicerades metoden genom att utveckla ett mobilt säljstöd i from av en mobilapplikation. Under projektet förarbete beslutades det att applikationen skulle byggas för iPad i Objective-C. Projektmetodiken anpassades för en projektgrupp med endast en utvecklare. Tillexempel hölls inga dagliga möten och rollen Scrum master tilldelades utvecklaren. Arbetet delades upp i tre sprintar. I början av varje sprint hölls ett möte där implementerad funktionalitet visades upp och reflekterades över. Under mötet planerades även den efterföljande sprinten. Resultatet av studien visar att det är möjligt att genomföra projekt med metodiken Scrum även om projektgruppen är väldigt liten. Flera av Scrums fördelar kan ändock tillgodoräknas. En grupp bestående av endast en utvecklare är dock i minsta laget och fördelarna med Scrum blir sannolikt fler om gruppen består av åtminstone två utvecklare.
APA, Harvard, Vancouver, ISO, and other styles
7

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

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

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

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

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

Full text
Abstract:
Det har funnits problem med systemutvecklingsprojekt som använder agila utvecklingsmetoder, vilka har misslyckats genom att exempelvis bli försenade och senare komma att kräva dyrt underhållsarbete. Scrum är en agil systemutvecklingsmetod som är den mest använda på marknaden. För att organisationer ska lösa problem med det mänskliga arbetet i grupp, hur de ska arbeta och vilka regler de ska ha, behöver de anpassa sig och förstå hur de ska tillämpa Scrum-ramverket, för att bli mer smidiga och stabila som de strävar efter med Scrum-metoden. Det finns oerhört många utmaningar med Scrum-metoden och därför behöver framgångsfaktorer identifieras för Scrum-användandet. Syftet med denna kandidatuppsats i informatik är att identifiera framgångsfaktorer för användning av Scrum inom Scrum-team i ett konsultföretag. I kandidatuppsatsen tillämpades fallstudiemetoden, eftersom relationer undersöks i uppsatsstudien och metoden är lämplig för det. Fallföretaget är konsultföretaget ÅF som arbetar med Scrum för systemutveckling. Uppsatsstudien genomfördes med stöd av ett sonderande samtal, semi-strukturerade intervjuer och en ostrukturerad observation med Scrum-projektmedlemmar på ÅF. Slutsatserna av uppsatsstudien är att det finns flera viktiga framgångsfaktorer för ett lyckat användande av Scrum. De viktigaste visade sig vara Engagemanget, som måste vara högt hos både individerna i Scrum-teamet, ledningen och kund för att Scrum-arbetet ska bli bra. Samarbetet måste fungera inom Scrum-teamet och med kunden. Även Kommunikationen behöver fungera bra, genom ansikte mot ansikte och olika kommunikationskanaler. Ytterligare en framgångsfaktor som identifierades är Förändringsbenägenhet, att individerna i Scrum-team ska vara öppna för förändring och kunna anpassa sitt arbete efter situationen, samt vara en lagspelare.
APA, Harvard, Vancouver, ISO, and other styles
10

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

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

Books on the topic "And Scrum"

1

Gloger, Boris. Scrum. München: Carl Hanser Verlag GmbH & Co. KG, 2011. http://dx.doi.org/10.3139/9783446426528.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Palmer, Tom. Scrum! Edinburgh: Barrington Stoke, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Gloger, Boris. Scrum. München: Carl Hanser Verlag GmbH & Co. KG, 2013. http://dx.doi.org/10.3139/9783446433946.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Union, Rugby Football. Scrum half. London: RFU, 1995.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

M, Quigley Jon, ed. Scrum project management. Boca Raton, FL: CRC Press, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Maximini, Dominik. The Scrum Culture. Cham: Springer International Publishing, 2018. http://dx.doi.org/10.1007/978-3-319-73842-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Maximini, Dominik. The Scrum Culture. Cham: Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-11827-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Nyamsi, Eric A. Projektmanagement mit Scrum. Wiesbaden: Springer Fachmedien Wiesbaden, 2019. http://dx.doi.org/10.1007/978-3-658-27486-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

'Kym', Pham Phuong-Van, ed. Scrum in Action. Boston: Course Technology, 2011.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
10

Mircea, Mihăieș, ed. Ghilotina de scrum. Iași: Polirom, 2002.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "And Scrum"

1

Dalton, Jeff. "Scrum of Scrums." In Great Big Agile, 227–28. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4206-3_53.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Dalton, Jeff. "Scrum Wall/Scrum Board." In Great Big Agile, 229–30. Berkeley, CA: Apress, 2018. http://dx.doi.org/10.1007/978-1-4842-4206-3_54.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Fiedler, Martin. "Scrum." In Lean Construction – Das Managementhandbuch, 229–39. Berlin, Heidelberg: Springer Berlin Heidelberg, 2017. http://dx.doi.org/10.1007/978-3-662-55337-4_14.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Schröder, Axel. "Scrum." In Agile Produktentwicklung, 34–39. München: Carl Hanser Verlag GmbH & Co. KG, 2018. http://dx.doi.org/10.3139/9783446458154.002.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Hanser, Eckhart. "Scrum." In Agile Prozesse: Von XP über Scrum bis MAP, 61–77. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12313-9_5.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Schröder, Axel. "Scrum." In Agile Produktentwicklung, 31–37. München: Carl Hanser Verlag GmbH & Co. KG, 2017. http://dx.doi.org/10.3139/9783446452459.002.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Gloger, Boris. "Prinzipien, Geschichte(n), Hintergründe." In Scrum, 1–57. München: Carl Hanser Verlag GmbH & Co. KG, 2016. http://dx.doi.org/10.3139/9783446448360.001.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Gloger, Boris. "Die Rollen – klare Verantwortlichkeiten." In Scrum, 59–107. München: Carl Hanser Verlag GmbH & Co. KG, 2016. http://dx.doi.org/10.3139/9783446448360.002.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Gloger, Boris. "Strategisches Planen in Scrum." In Scrum, 109–50. München: Carl Hanser Verlag GmbH & Co. KG, 2016. http://dx.doi.org/10.3139/9783446448360.003.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Gloger, Boris. "Der Sprint – das Produkt entsteht." In Scrum, 151–203. München: Carl Hanser Verlag GmbH & Co. KG, 2016. http://dx.doi.org/10.3139/9783446448360.004.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "And Scrum"

1

Ereiz, Zoran, and Denis Music. "Scrum Without a Scrum Master." In 2019 IEEE International Conference on Computer Science and Educational Informatization (CSEI). IEEE, 2019. http://dx.doi.org/10.1109/csei47661.2019.8938877.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Maranzato, Rafael P., Marden Neubert, and Paula Herculano. "Moving back to scrum and scaling to scrum of scrums in less than one year." In the ACM international conference companion. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2048147.2048186.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Agarwal, Puneet. "Continuous SCRUM." In the 4th India Software Engineering Conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/1953355.1953362.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Marchi, Michael. "Weaponized Scrum." In 2009 Agile Conference (AGILE). IEEE, 2009. http://dx.doi.org/10.1109/agile.2009.33.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Bates, Christopher D., and Simeon Yates. "Scrum down." In the 2008 international workshop. New York, New York, USA: ACM Press, 2008. http://dx.doi.org/10.1145/1370114.1370118.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Hron, Michal, and Nikolaus Obwegeser. "Scrum in Practice: an Overview of Scrum Adaptations." In Hawaii International Conference on System Sciences. Hawaii International Conference on System Sciences, 2018. http://dx.doi.org/10.24251/hicss.2018.679.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Greening, Daniel R. "Enterprise Scrum: Scaling Scrum to the Executive Level." In 2010 43rd Hawaii International Conference on System Sciences. IEEE, 2010. http://dx.doi.org/10.1109/hicss.2010.186.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Koc, Guler, and Murat Aydos. "Trustworthy scrum: Development of secure software with scrum." In 2017 International Conference on Computer Science and Engineering (UBMK). IEEE, 2017. http://dx.doi.org/10.1109/ubmk.2017.8093383.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

De Castro, Ronney Moreira, Sean Wolfgand Matsui Siqueira, Denilson Novais De Almeida, and Felipe Calegario Nascimento. "AGILITY SCRUM - Um Jogo para Ensino da Metodologia SCRUM." In XXV Workshop sobre Educação em Computação. Sociedade Brasileira de Computação - SBC, 2017. http://dx.doi.org/10.5753/wei.2017.3537.

Full text
Abstract:
Tendo em vista as dificuldades encontradas por docentes e discentes no ensino e no aprendizado da Metodologia Ágil Scrum como prática de Engenharia de Software, este artigo descreve uma abordagem diferente. A partir da criação de um jogo não computacional, os discentes puderam vivenciar uma experiência prática do uso da metodologia, o que por sua vez trouxe uma melhor aceitação, assimilação e resultado nos exercícios e trabalhos realizados, indicando assim um bom aproveitamento e eficácia na aplicação do conteúdo proposto pelos docentes.
APA, Harvard, Vancouver, ISO, and other styles
10

Sheth, Bhaven. "Scrum 911! Using Scrum to Overhaul a Support Organization." In 2009 Agile Conference (AGILE). IEEE, 2009. http://dx.doi.org/10.1109/agile.2009.23.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "And Scrum"

1

Miller, Arthur J., and Bruce D. Cornuelle. Optimizing Scrum Mesoscale Eddy Forecasts. Fort Belvoir, VA: Defense Technical Information Center, September 2000. http://dx.doi.org/10.21236/ada609847.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Miller, Arthur J., and Bruce D. Cornuelle. Optimizing Scrum Mesoscale Eddy Forecasts. Fort Belvoir, VA: Defense Technical Information Center, September 1999. http://dx.doi.org/10.21236/ada630760.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Carew, J. F., E. C. Selcow, and A. Aronson. PIUS scram reactivity analysis. Office of Scientific and Technical Information (OSTI), July 1994. http://dx.doi.org/10.2172/10167000.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Peterman, Dean R. Static Irradiated ALSEP Scrub Section. Office of Scientific and Technical Information (OSTI), April 2017. http://dx.doi.org/10.2172/1483803.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Hansen, T. SCRAM-SHA-256 and SCRAM-SHA-256-PLUS Simple Authentication and Security Layer (SASL) Mechanisms. RFC Editor, November 2015. http://dx.doi.org/10.17487/rfc7677.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Treat, Michael R. Pre-Clinical Validation of Robotic Scrub Technician. Fort Belvoir, VA: Defense Technical Information Center, January 2006. http://dx.doi.org/10.21236/ada450682.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Baumann, N. P., and G. P. Flach. Nuclear heating in He-3 fast SCRAM rods. Office of Scientific and Technical Information (OSTI), September 1989. http://dx.doi.org/10.2172/6975970.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hungate, Bruce. Synthesis of Scrub-Oak Ecosystem Responses to Elevated CO2. Office of Scientific and Technical Information (OSTI), November 2014. http://dx.doi.org/10.2172/1163898.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Platter-Reiger, M. F. Lessons Learned during a Coastal Sage Scrub Restoration Project. Fort Belvoir, VA: Defense Technical Information Center, June 1991. http://dx.doi.org/10.21236/ada238637.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

MacAllister, Bruce, and Mary G. Harper. Management of Florida Scrub for Threatened and Endangered Species. Fort Belvoir, VA: Defense Technical Information Center, December 1998. http://dx.doi.org/10.21236/ada360686.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'And Scrum' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography