izpis_h1_title_alt

Primer prehoda na agilno metodologijo razvoja programske opreme
ID MERČUN, JURE (Author), ID Šajn, Luka (Mentor) More about this mentor... This link opens in a new window

.pdfPDF - Presentation file, Download (262,13 KB)
MD5: 109FACF46C80F4BF361AA38DFB3F32CA
PID: 20.500.12556/rul/d4d02c90-6873-4700-a5f3-d22d4c6768ae

Abstract
Diplomska naloga temelji na konkretnem primeru prehoda s tradicionalnih na agilne metodologije razvoja programske opreme na projektu s področja načrtovanja virov podjetja, ki poteka v enem od slovenskih podjetij. Opisuje težave, s katerimi se je razvojna ekipa spopadala pri tradicionalni metodi dela, in razloge za prehod na agilne metodologije. Opisane so tri agilne metodologije, na kratko ekstremno programiranje in kanban, ter bolj podrobno Scrum, ki je bil na koncu izbran za vodenje projekta. Poleg metodologije so opisane tudi prilagoditve, ki so bile izvedene na projektu, kjer smo zaradi specifik projekta ocenili, da osnovna metodologija ni ustrezna. Sledi analiza, v kolikšni meri so bile v uvodu opisane težave s tem odpravljene. Na koncu so opisane še morebitne izboljšave v prihodnosti.

Language:Slovenian
Keywords:projektno vodenje, razvoj programske opreme, agilne metodologije, scrum.
Work type:Bachelor thesis/paper
Organization:FRI - Faculty of Computer and Information Science
Year:2014
PID:20.500.12556/RUL-29616 This link opens in a new window
Publication date in RUL:29.09.2014
Views:2023
Downloads:615
Metadata:XML RDF-CHPDL DC-XML DC-RDF
:
Copy citation
Share:Bookmark and Share

Secondary language

Language:English
Title:Implementing agile methodology in software development
Abstract:
This thesis is based on an actual case of transitioning from a traditional to an agile software development methodology on an enterprise resource planning project, which is being developed in one of Slovenian companies. It describes the problems, that the development team faced with the traditional method and the reasons for transitioning to an agile methodology. It includes brief descriptions of extreme programming and kanban, and a more in depth description of Scrum, which was the chosen methodology for the project. It also describes certain customizations of the method, which were deemed necessary due to specific nature of the project, followed by an analysis of the original problems and how they were affected by the change in methodology. In the end, possible improvements for the future are addressed.

Keywords:project management, software development, agile software development, scrum.

Similar documents

Similar works from RUL:
Similar works from other Slovenian collections:

Back