Usporedba tradicionalnog i agilnog načina vođenja projekata u razvoju softverskih proizvoda

master's thesis

• Title (english): Comparison of traditional and agile way of project management in software development
• Author: Luka Marić
• Mentor: Mislav Ante Omazić (mentor); MBZ: 246615
• Committee member: Mislav Ante Omazić (predsjednik povjerenstva)
• Committee member: Andrija Sabol (član povjerenstva)
• Committee member: Martina Sopta (član povjerenstva)
• Granter: University of Zagreb; Faculty of Economics and Business; Zagreb
• Defense date and country: 2020-03-13, Croatia
• Scientific / art field, discipline and subdiscipline: SOCIAL SCIENCES; Economics

Abstract

Svako poduzeće koje se bavi razvojem nekog oblika softverskih proizvoda mora usvojiti određenu, dobro definiranu, metodologiju tj. upravljački okvir za razvoj takvih proizvoda. Te projektne metodologije olakšavaju upravljanje procesima u proizvodnji softvera visoke kvalitete. Procesi razvoja softverskih proizvoda se uglavnom sastoje od sljedećih faza: detaljna analiza zahtjeva, dizajn, implementacija, testiranje, puštanje u produkciju i održavanje. U svijetu razvoja softverskih proizvoda, danas postoje dva najpopularnija načina upravljanja projektima: tradicionalni i agilni način razvoja. Tradicionalna metodologija i modeli proizašli iz nje zahtijevaju dobro osmišljen plan, slijedni napredak faza te definiran skup zahtjeva za razliku od agilnih načina koji imaju manje stroge smjernice, a karakterizira ih iterativan i inkrementalan pristup razvoju proizvoda. Agilni načini tako dozvoljavaju neodređeni broj repeticija pojedinih faza koje jednom kada su završene rezultiraju upotrebljivim inkrementom proizvoda s novim setom funkcionalnosti. Cilj ovoga rada je opisati vodopadni model kao najpopularniji oblik primjene principa tradicionalne metodologije te Scrum upravljački okvir kao najpopularniji oblik primjene principa agilnog načina razvoja proizvoda. Opisom projekata iz poslovne prakse pokušat će se pokazati kako se teorijski principi primjenjuju u praksi te postoje li neki faktori na koje bi se trebala obratiti posebna pažnja prilikom odlučivanja o primjeni pojedine metodologije vođenja projekta.

Abstract (english)

Each company engaged in the development of some form of software products must adopt a specific, well-defined methodology, i.e.management framework for the development of such products. These project methodologies facilitate the management of processes in the production of high quality software. Software product development processes mainly consist of the following stages: detailed requirements analysis, design, implementation, testing, production release and maintenance. In the world of software product development, there are two most popular ways of managing projects today: the traditional and the agile methods of development. The traditional methodology and models derived from it require a well-designed plan, sequential phase progress, and a defined set of requirements, as opposed to agile modes that have less stringent guidelines, characterized by an iterative and incremental approach to product development. The agile development thus allows for an indefinite number of repetitions of individual stages that, once completed, result in a usable product increment with a new set of functionalities. The aim of this paper is to describe the waterfall model as the most popular form of applying the principles of the traditional methodology and the Scrum framework as the most popular form of applying the principles of the agile product development. The description of the projects in business practice aims to show how the theoretical principles are implemented in practice and whether there are some factors that should be paid special attention to when deciding on the application of a particular project management methodology.

• Keywords: projektni menadžment; softverskih inženjering; metodologije razvoja softverskih proizvoda; tradicionalna metodologija; agilne metodologije; vodopadni model; Scrum
• Keywords (english): project management; software engineering; software development methodologies; traditional software development methodology; agile methodologies; waterfall model; Scrum
• Language: croatian
• URN:NBN: urn:nbn:hr:148:570686
• Study programme: Title: Business Economics; Study programme type: university; Study level: graduate; Academic / professional title: magistar/magistra ekonomije (magistar/magistra ekonomije)
• Type of resource: Text
• File origin: Born digital
• Access conditions: Open access
• Created on: 2020-05-31 17:18:04