Search

V diplomskem delu sta opisana tradicionalni in agilni projektni management, ter primerjava obeh načinov projektnega vodenja. V teoretičnem delu je poleg nekaterih glavnih metod, ki se jih uporablja v projektnem management opisana tudi primerjava in uporaba agilnih in tradicionalnih metod. Namen diplomskega dela je prepoznati prednosti in slabosti različnih metod projektnega managementa, ki se uporabljajo pri tradicionalnem in agilnem projektnem vodenju in kombinacij (t. i. hibridni modeli) teh metod. Pri teoretičnem primeru je obravnavan primer aktivnosti na gradbišču, kjer je primerjana uporaba sočasnega inženiringa, ki je metoda tradicionalnega managementa, ter metode Scrum, ki spada pod metode agilnega projektnega managementa. Cilj diplomskega dela je opisen in grafičen prikaz razlik pri uporabi različnih metod vodenja projektov, ter prednosti in slabosti določenih načinov vodenja. The thesis describes traditional and agile project management, as well as a comparison of both methods of project management. In addition to some of the main methods used in project management, the theoretical part also describes the comparison and use of agile and traditional methods. The purpose of the thesis is to identify the advantages and disadvantages of various project management methods used in traditional and agile project management and combinations (so-called hybrid models) of these methods. In the theoretical example, an example of activities on a construction site is discussed, where the use of concurrent engineering, which is a traditional management method, and the Scrum method, which belongs to the methods of agile project management, are compared. The aim of the thesis is a descriptive and graphic presentation of the differences in the use of different project management methods, as well as the advantages and disadvantages of certain management methods.

Spremembe pri izvajanju projektov so neizogibne, zato je pomembno, da so organizacije sposobne njihove izvedbe. Za organizacije je izvajanje sprememb lahko zahtevno in tvegano, ključno pa je to, da te v njih vidijo priložnosti. Če je obvladovanje neuspešno, to predstavlja resno tveganje, ki lahko prispeva k neuspehu projekta. Spremembe se smatrajo kot razvojna nujnost, zato podjetje brez spreminjanja na dolgi rok ne preživi. V zaključni nalogi obravnavamo teoretična izhodišča obvladovanja sprememb, v praktičnem delu pa je natančneje prikazano obvladovanje sprememb pri projektu zamenjave strehe. Predstavili smo potrebna orodja za lažji nadzor in izvedbo sprememb ter ugotovili, da je metoda obvladovanja sprememb z uporabo sočasnega inženiringa najprimernejša za izvedbo gradbenih projektov. Changes in the implementation of projects are inevitable, so it is important that organizations are able to implement them. Implementing change can be challenging and risky for an organization, but the key is to perceive it as an opportunity. Failure in management poses a significant risk that could result in the project's failure. Changes are considered a developmental necessity, therefore a company cannot survive in the long run without changes. In the final assignment, we discuss the theoretical background of change management, while in the practical part, change management in the roof replacement project is shown more precisely. We presented the necessary tools for easier control and implementation of changes and concluded that the change management method of concurrent engineering is the most suitable for construction projects.

Razvoj programske potpore za ugradbene računalne sustave usko je povezan sa sklopovljem na kojem se programska potpora izvodi. Razvoj vođen testiranjem (engl. Test Driven Development, TDD) već se dugo koristi u praksi kao uspješno dokazana metodologija razvoja programske potpore u raznim domenama, ali još uvijek nije zastupljen u razvoju programske potpore za ugradbene računalne sustave. U ovom radu prikazane su mogućnosti i prednosti korištenja TDD pristupa razvoju programske potpore za ugradbene računalne sustave. Opisani su agilni načini razvoja programske potpore, paradigma razvoja upravljanog testiranjem, osnovni pojmovi vezani uz TDD pristup (mikrociklus, refaktoriranje, mock objekti) te su navedeni prednosti i nedostaci TDD paradigme. Posebna pažnja posvećena je opisu mogućnosti radnog okvira CppUTest te njegovom načinu korištenja za razvoj programske potpore za ugradbena računala. Prikazan je primjer korištenja TDD paradigme za razvoj upravljačkih programa za dva odabrana integrirana sklopa (MCP23008 i CAP1293). Embedded software development cycle is closely coupled with the hardware as a target execution environment. Test-driven development (Test Driven Development, TDD) has been used for a long time as a successfully proven methodology for software development in various domains but it is still not present as a widely used approach in embedded software development workflow. This paper describes the possibilities and advantages of using TDD approach for embedded software development. The paper describes agile methods of software development, test-driven development paradigm, basic terms related to the TDD approach (microcycle, refactoring, mock objects), and the advantages and disadvantages of the TDD paradigm. Particular focus was on description of the CppUTest framework and its use for embedded software development. An example of using the TDD paradigm for device driver development was demonstrated for two selected integrated circuits (MCP23008 and CAP1293).

Namen diplomskega dela je pripraviti situacijski pristop k agilnemu razvoju programske opreme za specifičen tip podjetja. V prvem delu je predstavljena zgodovina vodenja projektov in razvoj procesnih metod ter opis pogosto uporabljenih agilnih modelov razvoja programske opreme. Drugi del se posveti opredelitvi situacijskega pristopa -- od načina ocenjevanja posameznih potencialnih elementov pristopa, zastavitev vprašanj glede na literaturo in sami sestavi ankete. Sledi poglavje, ki opiše uporabo pristopa na specifičnem podjetju. Začne se z predstavitvijo podjetja in analizo rezultatov empirične raziskave. Osrednji del raziskave predstavlja izvedba fokusnih delavnic, sam izbor elementov metode razvoja programske opreme in razlago razlogov za njihovo izbiro. Nadaljuje se s seznamom izbranih elementov metode in povratno informacijo vodstva. Diplomsko delo se zaključi s sklepnimi ugotovitvami in možnim prihodnjim delom na tem področju. The purpose of the thesis is to prepare a situational approach to agile software development for a specific type of company. The first part describes the history of project management and the development of process methods, as well as a description of commonly used agile software development models. The second part focuses on the definition of the situational approach - from the evaluation of individual potential elements of the approach and forming questions based on the literature to the composition of the survey. The following is a section that describes how to apply the approach to a specific company. It begins with a presentation of the company and analysis of the results of empirical research. The central part of the research is the implementation of focus workshops, the selection of elements of the software development method and the explanation of the reasons for their choice. It continues with a list of selected method elements and management feedback. The diploma thesis concludes with final thoughts and possible further work in this field.

Postizanje agilnosti u poduzeću je cilj većine poslovanja jer agilne metodologije govore o tome da su promjene poželjne i konstantne. Stoga je agilnost cilj mnogih organizacija koje se žele održati na tržištu, jer se agilne organizacije brže prilagođavaju zahtjevima dionika i tržišnim prilikama, što omogućuje smanjenje vremena razvoja novih procesa i povećanje fleksibilnosti postojećih. Agilni se razvoj softvera odnosi na set načela i principa za razvoj softvera unutar kojih se specificiraju rješenja i ona se razvijaju kroz zajednički pothvat samoorganizirajućih međufunkcionalnih timova. Prema istraživanjima, većina organizacija koja koristi ove metode doseže lakše svoje ciljeve i uspješnije provodi projekte unutar budžeta, pa ne čudi da su se tijekom vremena razvile određene najbolje prakse i obrasci korištenja upravo tih metoda. S obzirom na funkcije i čimbenike koji karakteriziraju agilne metode razvoja softvera te je metode moguće primijeniti u vođenju projekata u mnogim tvrtkama, među ostalim i telekomunikacijskim. Stoga se u radu analiziraju primjene metoda agilnih razvoja sektora u projektima koje vode telekomunikacijske tvrtke na području Republike Hrvatske. Achieving agility in the company is the goal of most businesses because agile methodologies show that change is desirable and constant. Therefore, agility is the goal of many organizations that want to survive in the market because agile organizations adapt more quickly to stakeholder requirements and market opportunities, which allows to reduce the development time of new processes and increase the flexibility of existing ones. Agile software development refers to a set of principles and principles for software development within which solutions are specified and are being developed through a joint venture of self-organizing cross-functional teams. According to research, most organizations that use these methods achieve their goals and projects more easily, within budget, so it is not surprising that over time, certain best practices and patterns of using these methods have developed. Given the functions and factors that characterize agile methods of software development, these methods can be applied in project management in many companies, including telecommunications. Therefore, this thesis analyzes the application of agile development methods of the sector in projects led by telecommunications companies in the Republic of Croatia.

Ovaj završni rad temelji se na agilnim metodama za upravljanje projektima. Razlog samih agilnih metoda kao odabrane tematike jest pretpostavka kako su agilne metode u IT projektima bolji odabir od onih tradicionalnih. U prvom dijelu rada prezentiran je pojam projekta i samog upravljanja projektima kao i metode koje se koriste za isto. Prezentirane su općenite značajke tradicionalnih i agilnih metoda uz pobliže objašnjenje onih najzastupljenijih u praksi. Objašnjenje istih temelji se na fazama projekta, promatranju timova, uključenosti naručitelja/korisnika te sklonosti promjenama. U drugom dijelu rada predstavljena je primjena tradicionalnih i agilnih metoda na primjeru iz prakse. Na temelju pretpostavki vezanih za agilne i tradicionalne metode, provedena su dva strukturirana intervjua vezana za primjenu navedenih metoda u poduzećima čiji su rezultati služili za kalibraciju anketnog upitnika i prilagodbu pitanja kojima je provedeno glavno istraživanje. Glavno istraživanje provedeno je na uzorku od 16 osoba koje su voditelji projekata ili članovi projektnih timova, a imaju iskustvo u radu uz primjenu tradicionalnih i agilnih metoda. Navedeno istraživanje kao i strukturirani intervjui, rezultirali su informacijama koje su validne za krajnji rezultat ovog rada, što je usporedba metoda, njihovih značajka te potvrđivanje ili negiranje početne pretpostavke kako su agilne metode u prednosti nad onim tradicionalnima.

Prispevki, zbrani v zborniku že 24. strokovne konference Sodobne informacijske tehnologije in storitve, naslavljajo izjemno aktualne izzive, s katerimi se informatiki, programski inženirji, računalničarji, podatkovni znanstveniki, arhitekti, razvijalci ter upravljalci informacijskih rešitev in storitev srečujemo pri svojem vsakdanjem delu. Avtorji predstavljajo inovativne rešitve in skozi konkretne projekte pridobljene izkušnje s/z: vpeljavo tehnologij strojnega učenja in obogatene inteligence, uporabo tehnologij in platform veriženja blokov, razvojem šibko sklopljenih mikrostoritev, popolno virtualizacijo in izkoriščanjem porazdeljenih infrastruktur, zagotavljanjem kibernetske varnosti, zaupnosti in zasebnosti, skaliranjem agilnih metod v porazdeljenih projektnih skupinah, vpeljavo agilnih pristopov v sklopu avtomatiziranih in neprekinjenih procesov razvoja, testiranja, integracije in dostave, posodobitvijo in nadgradnjo obstoječih informacijskih sistemov, razvojem uporabniško prijaznih spletnih in mobilnih rešitev in uvajanjem sodobnih programskih jezikov in razvojnih okolij. The papers in the proceedings of the 24th Professional Conference on Advanced Information Technology and Services address the extremely topical challenges that we (IS/IT experts, Software Engineers, Computer Scientists, Data Scientists, software and solution architects, developers, IT managers, etc.) encounter in our daily work. The authors present the innovative solutions and rich experience gained by conducting real-life projects: Applying Augmented Intelligence and Machine Learning technologies, Using Blockchain technologies and platforms, Developing loosely coupled micro-services, Providing full virtualization and exploitation of distributed infrastructures, Ensuring cybersecurity, confidentiality and privacy, Applying large-scale agile methods in distributed teams, Introducing agile approaches that enable the rapid and efficient software development via automated processes, and continuous testing, integration, delivery & deployment Updating and upgrading existing Information Systems, Incorporating advanced programming languages and development environments, Developing user-friendly web and mobile solutions & services.

The thesis touches on the agile manifesto, followed by a description of Scrum, where Roles, Ceremonies, Artifacts, and Sprints are described. In addition to Scrum, the thesis describes Extreme Programming, Kanban, and Lean. The last part of the chapter contains an analysis of the pros and cons of agile methods in software development. The thesis concludes with a review of survey results. S hitrim razvojem računalnikov in računalniške programske opreme se je pojavila močna potreba po nastanku novih metod vodenja razvojnih timov. Tako so se razvili novi procesni modeli. Ker pa vsi procesni modeli niso primerni za vsako vrsto razvoja programske opreme, smo v sklopu diplomske naloge raziskali prednosti in slabosti določenih metod. Zaključno delo predstavi tematiko agilnega pristopa pri razvoju programske opreme. V uvodu dela so predstavljeni koncepti razvoja programske opreme, zakaj potrebujemo različne metode ter kratek opis zgradbe diplomske naloge. Uvodu sledi glavni del, v katerem je opisana tradicionalna metoda – Slapovni model. Predstavljeni so razlogi za razvoj metodologij, koraki razvoja in nadgradnje. Prav tako so opisane pomanjkljivosti, ki so bile povod za razvoj agilnih metodologij. Ker so se v tradicionalnih metodah pojavili problemi zaradi neprilagodljivosti spremembam, so bile predlagane alternativne metode, ki so opisane v tretjem poglavju. Podana je razlaga agilnih metod ter opis agilnega manifesta - smernice, na katerih temeljijo agilni pristopi. Temu sledi opis metodologije Scrum. Opisani so problemi, ki jih poskušamo rešiti z uvedbo Scrum metode, ter posledice po uvedbi metode. Predstavljen je procesni model Scrum-a. V podrobnosti so opisane Scrum vloge, Scrum postopki ter Scrum Artefakti. Scrum vloge so: Product owner, Scrum Master ter razvojna ekipa. Za vsako vlogo so opisane naloge, ki jih mora ta oseba opravljati. Pod Scrum postopke spadajo načrtovanje šprinta, revizija šprinta, retrospektiva šprinta, dnevni sestanki in sam šprint. Pri Scrum artefaktih pa sta opisana Product backlog in Sprint backlog. Na koncu tega poglavja je opisan postopek šprinta. Postopek je opisan v več delih. Najprej je opisana priprava na šprint, kjer so opisane uporabniške zgodbe. Temu sledi opis poteka šprinta. Poleg Scruma, na katerem je največ poudarka, so opisane tudi metode Ekstremno programiranje, Kanban ter Lean. Agilne metode uporablja vedno več uspešnih podjetij zaradi česar se postavlja vprašanje, zakaj so metode agilnega pristopa prevzele vodilno vlogo pri razvoju programske opreme. Zato so, v zadnjem delu poglavja, analizirane prednosti in slabosti agilnih metod, kjer primerjamo različne vidike metod. Sklicujemo se na podatke iz 12th State of Agile survey, ki vsako leto prireja dogodke ter sledi trendom popularnosti agilnih metod. Opisano je kdaj so agilne metode primerne, kakšne so njihove prednosti in kakšne so njihove slabosti. Na koncu so predstavljeni še rezultati ankete, ki smo jo poslali različnim računalniškim podjetjem. Posvetili smo se predvsem popularnosti agilnih metod, njihovim karakteristikam ter prednostim in slabostim različnih metodologij.

Programsko inženjerstvo je primjena sustavnog, discipliniranog i mjerljivog pristupa razvoju, uporabi i održavanju programske opreme. Kako bi se uspješno izvodila, potrebno je slijediti provjerene metode i alate. Agilne su metode najuspješnije i najviše korištene metode za izradu programske podrške u najutjecajnijim svjetskim kompanijama. Istražene su i objašnjene najkorištenije agilne metode te njihovi ključni elementi. Predstavljene su skupine alata za njihovu podršku, te su analizirani oni alati koji se najviše koriste u svijetu. Među studentima Fakulteta elektrotehnike i računarstva te hrvatskim IT kompanijama je provedeno istraživanje s ciljem otkrivanja zastupljenosti agilnih metoda na fakultetu te u profesionalnim okruženjima. Potom su sa studentima izvedene vježbe u kojima se testiralo njihovo znanje i zainteresiranost za korištenjem agilnih metoda na studentskim projektima. Na temelju rezultata istraživanja je izrađen nacrt predmeta koji bi studentima približio agilne metode te im pružio praktično znanje koje bi im bilo korisno za budući rad, kako na fakultetu, tako i u profesionalnom životu. Software engineering is the application of a systematic, disciplined, quantifiable approach to the design, development, operation, and maintenance of software. In order to be successful, it is necessary to follow proven methods and tools. Agile methods are the most successful and most used software development methods among the most influential companies in the world. The most widely used agile methods and their key elements are explored and explained. Groups of supporting tools for their use are presented and the most widely used tools were analyzed. Research was conducted among the students of the Faculty of Electrical Engineering and Computing and Croatian IT companies with the aim of discovering the presence of agile methods at the faculty and in professional environments. The students then participated in exercises that tested their knowledge and interest in using agile methods in student projects. Based on the results of the research, a draft of a course was developed. The aim of the course is to bring agile methods closer to students and provide them with practical knowledge that would be useful for future work, both at faculty and later in their professional life.

Radom se teorijski razrađuju informacijski sustavi i razvoj informacijskih sustava s fokusom na agilne metode. Pronalaze se zajedničke karakteristike agilnih metoda kroz tablične prikaze kako bi se kroz istraživanje utvrdila mogućnost izvršenja komparativne analize s ciljem omogućavanja odabira metode razvoja. Upućuje se na prednosti i nedostatke te statističke pokazatelje o uspješnosti primjene metoda radi ukazivanja na potencijalna očekivanja ishoda primjene odabrane/odabranih metoda. The thesis is a theoretical consideration of the field of information systems and information systems development with focus on agile methods. It presents agile methods' common properties and features through data tables research in order to establish the possibility of conducting a comparative analysis aimed at facilitating the selection of a development method. It points out the distinctive individual method advantages and disadvantages and statistical indicators of method application success in order to establish the potential outcome expectation of chosen method application.

Agilne metodologije razvoja programskog proizvoda nastale su kao odgovor tradicionalnim metodama razvoja, primjenjujući specifične razvojne postupke koji se fokusiraju na brzi razvoj programskog proizvoda, uz zadržanu kvalitetu. Praksa pokazuje da tradicionalne i agilne metode ne moraju nužno biti isključive, te da postoji veliko i neistraženo područje gdje se ta dva pristupa mogu međusobno kombinirati i nadopunjavati. Ovaj rad provodi analizu razvojne metodologije ekstremnog programiranja. Istražuje mogućnosti primjene razvojnih postupaka definiranih unutar te metode za primjer specifične projektne okoline i s naglaskom na programski proizvod. Posebna pažnja je posvećena testiranju, mogućnostima poboljšanja programskog koda i integraciji programskih pomagala. Istraživanje je provedeno na razvojnom programskom projektu javne elektroničke usluge. Agile methods of software development have developed as response to the more traditional development methods, applying specific development procedures which focus on rapid software development while containing the quality. Praxis shows that traditional and agile methods need not be exclusive and that there is a vast and unexplored area where those two approaches can be combined. In this work was conducted the analysis of Extreme Programming development method. The possibility of application of development techniques defined whitin the method as an example of specific project encircling with an emphasis to the software are explored. Special attention was given to the testing, possibility of enhancements of program code and the integration of program tools. The research was undertaken on the example of public e-service development project.

Unatoč relativno kratkoj povijesti razvoja, softversko inženjerstvo do danas se razvija sve dinamičnije i intenzivnije. Sukladno tome, ističe se istinskom kompleksnošću, ali i značajem u suvremeno doba. Smatra se kako ono daje izravnu podršku suvremenom društvu i međunarodnoj ekonomiji. Generalno se može pojmiti kao znanstveno područje u svezi razvoja i upravljanja softverima to jest programskim rješenjima. Kada je riječ o razvoju softvera, zapravo se misli na fazni proces njegova životnog ciklusa. Svaka faza pri tome je jasno određena, a podrška provedbi ovoga procesa dolazi od integriranog, normatiziranog i standardiziranog kombiniranja metoda, tehnika i tehnologija. Agilne metode javljaju se kao odgovor na pritiske suvremenoga doba i nedostataka klasičnih metoda programiranja. One otklanjaju vodeće nedostatke sekvencijksih, tradicionalno orijentiranih metoda. Pri tome, ističu se većom fleksibilnošću, kvalitetom i orijentaciji prema korisnicima. U praksi donose veću učinkovitost i efikasnost. Despite a relatively short history of development, software engineering today is becoming increasingly dynamic and intensive. Accordingly, it is emphasized by the true complexity, but also by its significance in the contemporary time. It is considered to be a direct support to the modern society and the international economy. It can be generally considered as a scientific area for software development and management, that is, software solutions. Software development actually consideres thephases of its life cycle process. Each phase is clearly defined and has to be supportedwith the implementation of integrated, normatized and standraded combination of methods, techniques and technologies. Agile methods appear as a response to contemporary pressures and the disadvantages of the classical programming methods. They eliminate the main disadvantages of sequential, traditionally-oriented methods. In this regard, greater flexibility, quality and customer orientation are emphasized. In practice they bring greater efficiency and quality for customers.

V diplomskem delu je predstavljena vpeljava agilnih in vitkih metod v proces podjetja, ki je nekatere prakse uporabljalo že prej, vendar nedosledno. Za uspešno vpeljavo je bilo najprej potrebno preučiti značilnosti agilnega in vitkega pristopa s poudarkom na Scrumu in Kanbanu. Upoštevajoč značilnosti projekta se je izkazalo, da bi bila najprimernejša kombinacija obeh - Scrumban. Na podlagi tega je bil izdelan načrt vpeljave, s točno opredelitvijo uporabljenih metod, izbranih pravil in predvidenega poteka dela. Po vpeljavi je bila opravljena analiza uspešnosti, kjer je uspešnost ocenjena s pomočjo grafov in spremljanja doslednosti uporabe izbranih praks. Rezultati meritev so pokazali, da je bila vpeljava uspešna in posledično dostava projektnega izdelka hitrejša. This Bachelor’s thesis introduces the implementation of agile and lean methods into the company process, which used some practices previously, but inconsistently. For successful implementation, the characteristics of agile and lean approach, with an emphasis on Scrum and Kanban, had to be considered first. Considering the characteristics of the project, it became apparent that the combination of both would be best – Scrumban. Based on this, an implementation plan with an exact characterization of methods used, selected rules and estimated work course was formed. After the implementation, a performance analysis was carried out, which assessed the success rate with the help of graphs and monitoring the consistency of using specific practices. The results proved that the implementation was successful and, consequently, the project product delivery was faster.

U današnje vrijeme Scrum metodologija predstavlja moderan pristup razvoja, ne samo informacijskih programskih rješenja već bilo kakvih kompleksnih proizvoda. Koristeći pravila, uloge i tehnike dokumentiranja koju metodologija zahtjeva, te pravilnim korištenjem svega što Scrum nudi svaka se radna okolina može preinačiti u jednu samoorganizirajuću skupinu odnosno tim koji u vrlo kratkom roku pokazuje iznimnu produktivnost. Srž metodologije leži u timskom radu koji se prilagođava okolini stvarajući što veću učinkovitost, smanjujući nedostakte i rizike. Scrum Metodologija se pokazala vrlo učinkovitom u izvršavanju devnih zadataka i dugoročnih projekata unutar radne okoline Sistem administratora i što je najbitnije od svega značajno je povećala produktivnost njihovog rada. Today Scrum methodology represents a modern way in developing new products, not only in software development, but in any type of production. Using Scrum rules, roles and documentation techniques which this methodology requires, every working environment can replace a group of individuals with a well performing self-organised team in a short period of time. The key of this methodology is the teamwork which adapts to a variety of incoming requests delivering high quality products in the most efficient way and in the same time reducing deficiencies and risks. The Scrum Methodology proved to be very effective in perfomring daily tasks and long term projects in a team of System Administrators and, which is most important, significantly increased the productivity of their work.

The increasing use of agile methods for software development creates the need for these methods to become part of the education of future computer and information science engineers. On the other hand, teaching these methods gives us an opportunity to verify individual agile concepts and their effectiveness. For that reason, project work is an appropriate and frequently used form of teaching that enables students to get acquainted with agile methods and, at the same time, provides case studies for evaluating individual agile concepts. We describe our approach to teaching the Scrum agile method, within the software technology course, in cooperation with a software development company. Students were taught through work on a real project for which a list of requirements was submitted by the company. A co-worker of this company participated throughout the teaching period playing the role of customer's representative. During their work, students consistently used the Scrum method and at the end of each iteration they evaluated their experience by means of a questionnaire. In the article, the Scrum method is presented first, then a description of work on the project is given and finally the results of the survey are described. Vse večja uporaba agilnih metodologij za razvoj programske opreme zahteva, da učenje teh metodologij postane sestavni del izobraževanja bodočih inženirjev računalništva in informatike. Po drugi strani pa je možno skozi poučevanje teh metodologij preveriti tudi posamezne agilne koncepte in poiskati natančnejše odgovore na vprašanja o njihovi učinkovitosti. Zato se kot najprimernejša oblika poučevanja pogosto uporablja delo na projektih, ki omogočajo, da študenti v praksi spoznajo značilnosti agilnega pristopa, obenem pa služijo kot študije primera za ovrednotenje posameznih agilnih konceptov. V članku opisujemo, kako smo v sklopu predmeta Tehnologija programske opreme izpeljali učenje agilne metode Scrum v sodelovanju s podjetjem za razvoj programske opreme. Učenje je potekalo ob delu na realnem projektu, za katerega je seznam zahtev posredovalo podjetje, sodelavec tega podjetja pa je ves čas sodeloval s študenti kot predstavnik naročnika. Študenti so pri svojem delu dosledno uporabljali metodo Scrum in na koncu vsake iteracije s pomočjo ankete ocenili svoje izkušnje. V članku je najprej na kratko predstavljena metoda Scrum, nato sledi opis poteka dela na projektu, na koncu pa so predstavljeni rezultati ankete.

The purpose of the master thesis is to research and determine how to successfully manage a project using agile methodology Scrum. Scrum methodology will be used to improve the functionality of existing internally developed software solutions. Scrum, being an agile methodology, is an alternative approach to the traditional waterfall methodology, and is typically used in software development. Agile methodologies help teams respond to a project’s unpredictability by using incremental, iterative way of work known as sprints. The first part of the master’s thesis presents a problem, defines goals and methods used, and the necessary tools required to achieve the objectives. The following part of the thesis presents the foundations of agile methodologies and describes the used methodology – Scrum - in detail. In the practical part, the thesis presents the existing software solution and opportunities for its improvement. We use Scrum for upgrading existing application, including all the attributes of the mentioned methodology, from team design to artifacts and events. The thesis also presents a renewed application in detail. In conclusion, by using the SWOT analysis we observe suitability for use of the Scrum methodology in the case of renewal of application and propose further changes to improve the application. Vse organizacije – ne glede na to ali so poslovne, vladne ali neprofitne – morajo biti sposobne ustvariti svojo vrednost z grajenjem, prilagajanjem ali vsaj s pomočjo programske opreme. Brez programske opreme je zmožnost za doseganje zastavljenih ciljev na poslovnem področju izjemno omejena, če ne celo nemogoča. Kljub potrebi je bil razvoj programske opreme v preteklosti nezanesljiv in drag proces, sam podvig pa nagnjen k napakam. Navedene težave so pripeljale do različnih načinov pristopa k razvoju programske opreme: od tradicionalne metode slapu (ang. Waterfall method) do novejših agilnih metod. Agilno vodenje projektov je sodobnejši pristop k oblikovanju in uresničitvi programske opreme, hkrati pa zagotavlja razvoj programske opreme, ki ima največjo vrednost za kupca. Agilne metodologije pomagajo razvijalcem pri reševanju nepredvidljivih situacij z uporabo inkrementalnega, iterativnega dela in empiričnih povratnih informacij. Inkrementalni model pomeni, da se programska oprema razvija v posamičnih, hitrih ciklih. Takšen razvoj izdelkov zagotavlja, da je potencialno uporabna verzija delujočega izdelka vedno na voljo. Rezultat so majhne izdaje, kjer vsaka izdaja postopoma nadgrajuje oz. razširja funkcionalnost izdelka. Vsaka razširitev je temeljito testirana, kako bi se ohranila in zagotovila kakovost programske opreme. Testiranje je integrirano v celotnem življenjskem ciklu produkta, kar omogoča redne preglede delovanja le-tega. Testiranje lastniku omogoča identifikacijo potrebnih modifikacij, razvojni skupini pa zgodnji vpogled v kakovost programske opreme. Da bi bili uspešni pri opravljanju dela, se morajo strokovnjaki najprej naučiti načel in odnosov, na katerih temelji agilni razvoj. Izkušeni inženirji programske opreme so se zbrali leta 2001, da bi ugotovili, kaj imajo določene lahke metode skupnega. Na tem sestanku so prvič uporabili naziv »agilne metode,« nekateri izmed njih pa so kasneje ustanovili neprofitno organizacijo »The Agile Alliance«, katere namen je bil promoviranje agilnega razvoja. Ustvarjalci te zveze so ustvarili tudi manifest, ki predpisuje temeljne principe in postopke, ki bi jih morali upoštevati uporabniki agilnih metodologij. Manifest opisuje štiri ključne vrednote, ki so danes enako pomembne, kot so bile takrat: • Posamezniki in interakcije pred procesi in orodji. • Delujoča programska oprema pred vseobsežno dokumentacijo. • Sodelovanje s stranko pred pogodbenimi pogajanji. • Odziv na spremembe pred strogim sledenjem načrtom.

Razvoj softvera vođen testiranjem se krenuo koristiti radi želje programera da se u programu implementiraju samo potrebne metode i kako bi im testovi na vrijeme otkrili da li trenutna verzija programa radi ono što treba. Najčešće se ovaj način razvoja softvera koristi u manjim projektima, ali zbog sve veće popularnosti kreće se sve više koristiti u većim projektima.Razvoj softvera vođen testiranjem se sastoji od tri faze. Prva faza se sastoji od pisanja testova za metode koje još nisu implementirane. U drugoj fazi pišemo metode koje će proći napisane testove. U trećoj fazi se brinemo o kvaliteti koda, jednostavnosti održavanja i jednostavnosti čitanje koda. Kako se razvoj softvera vođen testiranjem krenuo sve više koristiti tako su se zamijetili određeni obrasci koji se najčešće pojavljuju. Obrasci se pojavljuju u sve tri faze razvoja softvera. Iako su neki očiti, preporučeno je poznavanje svih obrazaca prije početka korištenja ovog načina razvoja softvera. Njihovo poznavanje će umanjiti vrijeme potrebno za implementiranje metoda i smanjit će broj pogrešaka. Kod razvoja softvera vođenog testiranjem bitno je koristiti programski jezik koji ima aplikacijski okvir za testiranje dijelova. To nije presudan uvjet ali on olakšava razvoj softvera. Aplikacijski okviri sadrže mnogo korisnih metoda koje će poslužiti programeru. Usage of test-driven development was started because programmers wanted to implement only the necessary methods in their programmes and so the tests could reveal if the current version of the program is working as expected. This method is commonly used in smaller projects, but because of the increasing popularity it is getting more and more used in bigger projects. Test-driven development has three phases. The first (red) phase consists of writing tests for methods that are not yet implemented. In the second (green) phase we write methods that will pass the written tests. In the third (refactor) phase we are concerned about code quality, code maintenance and code reading simplicity. As test-driven development was more and more used, programmers started to notice patterns. Patterns occur in all three phases in software development. Although some are simple it is recommended to learn all of the patterns before using this type of software development. Pattern recognition will decrease time needed for method implementation al will decrease the number of errors. In test-driven development it is important to use a programming language that has a unit test framework. This is not a crucial requirement but it simplifies software development. Frameworks have a lot of useful methods that will be at disposal to the programmer.

Scrum je agilna metoda razvoja programske opreme, s katero lahko podjetja razvijajo izdelke hitreje ter bolj učinkovito. Zaradi inkrementalnega in iterativnega razvoja ter velike angažiranosti stranke lahko projekt napreduje bolje, lažje pa je tudi implementirati spremembe, ki bi si jih stranka morda želela. V tem diplomskem delu je bil opravljen pregled obstoječe znanstvene literature na temo metode Scrum v razvoju programske opreme, pregled pa je prinesel odgovore na tri zastavljena raziskovalna vprašanja: kakšne vrste raziskav metode Scrum obravnavajo članki v znanstveni literaturi, kakšne so pridobitve in izzivi ob uporabi metode Scrum ter kaj predlagajo dosedanje raziskave metode Scrum za najlažjo uveljavitev metode pri delu. Opravljena je bila tudi primerjava ugotovitev pregleda literature z lastnimi izkušnjami dela na projektu pri predmetu Tehnologija programske opreme. Scrum is an agile method for software engineering, used by companies to develop products faster and more efficiently. Because the customer is more engaged in the process and the development is incremental and iterative projects progress better, it is also easier to implement any changes in functionality the customer might want. In this thesis a review of existing scientific literature regarding the method Scrum in software engineering has been made. The review brought forth answers to three previously set research questions: which types of research of the method Scrum are present in the scientific literature, what are the advantages and challenges in working with Scrum, and what does previous research suggest for the easiest implementation of the method at work. A comparison of results of this review and our own experiences with working on a project in Software engineering class has been made.

Magistrsko delo opisuje platformski pristop razvoja programske opreme pametnih merilnikov. V uvodnem poglavju delo opredeli osnovne značilnosti platformskega pristopa in osnovna platformska sredstva. Platformski pristop temelji na krovnem kaskadnem procesu razvoja izdelka. V razvojni fazi izdelka je uporabljen V razvojni model, ki omogoča hkraten razvoj in testiranje izdelka oziroma programske opreme. Lastni razvojni proces programske opreme temelji na konceptu agilnih metod in modelirno usmerjenemu razvoju. Proces sledi iterativnemu in inkrementalnemu izboljševanju programske opreme. Strežnik TFS je uporabljen za infrastrukturno podporo vodenju lastnega razvojnega procesa. Orodje IBM Rational Rhapsody je uporabljeno za razvoj arhitekture, podrobno načrtovanje programskih sklopov in njihovo implementacijo. Arhitektura pametnega merilnika temelji na domenski zasnovi posameznih modulov. Vsaka domena predstavlja samostojen sklop pametnega merilnika. Samostojno izvajanje domene je omogočeno preko testnega ogrodja CUnit. Različne domene družimo v štiri (4) glavne pakete, ki tvorijo jedro vsakega izdelka. Le-tega je moč poljubno konfigurirati, kar omogoča lažje vodenje večih različic izdelka. V delu so prav tako opisani različni vzorci reševanja problemov v programski opremi. Za načrtovanje arhitekture in ostalih programskih sklopov je uporabljen jezik UML. Celotno načrtovanje poteka z modelirnim orodjem IBM Rational Rhapsody. Razlogi za izbiro modelirno usmerjenega pristopa so utemeljeni z analizo SWOT. Orodje IBM Rational Rhapsody je bilo izbrano na podlagi primerjave večih tovrstnih orodij. V zadnjem delu je podana primerjava s klasičnim razvojem programske opreme. This master's thesis describes the platform approach for smart meters' firmware development. In the introductory section of the thesis the basic features of the platform approach and common platform assets are defined. Platform approach is based on the cardinal cascade product development process. In the development phase of the product, V development model is used, which enables concurrent development and testing of smart meters' firmware. Firmware development process is based on principles of agile methods and model driven development. Delivered firmware follows an iterative and incremental paradigm of small improvements over sprints. TFS server is used for infrastructural support of smart meters' development process. IBM Rational Rhapsody is used to develop the overall architecture, detailed design and implementation of identified domains. The architecture of smart meters is based on domain design pattern. Each domain represents independent functional set of the smart meter. Standalone domain execution is performed through the test harness called CUnit. Different domains are grouped into four (4) top level packages that represent each product. The latter can be freely configured, enabling easier variant and version management of different products. This thesis also describes different design patterns in order to solve – in a standardized manner - challenges presented in the firmware. For architectural and detailed design of components UML is used. The modelling is completely done in IBM Rational Rhapsody tool. Reasons for choosing model driven approach is justified by the SWOT analysis. IBM Rational Rhapsody tool has been selected based on a comparison of several modelling tools. The last section is dedicated to a comparison between a conventional firmware development and described one

Delež neuspešnih projektov razvoja informacijskih sistemov ostaja razmeroma visok kljub naraščajočim vlaganjem v informacijske sisteme in njihovemu velikem pomenu za sodobne organizacije. Eden izmed kritičnih razlogov za tako visok delež neuspešnih projektov razvoja informacijskih sistemov je odpor do sprememb. Organizacije so se z odporom do sprememb soočale že pred pojavom prvih računalnikov, saj je to naravna reakcija ljudi na spremembe. S pojavom računalnikov in vpeljevanjem informacijskih tehnologij v organizacije je odpor postal še bolj problematičen in opazen, saj so spremembe v organizacijah zaradi hitro razvijajoče se tehnologije vse pogostejše. Danes, po več desetletjih od prvih vpeljav informacijske tehnologije v organizacije in preučevanja odpora do sprememb, predstavlja odpor do sprememb še vedno trd oreh, saj se pojavlja praktično pri vseh projektih razvoja informacijskih sistemov. Na področju razvoja informacijskih sistemov je bil odpor uporabnikov preučevan iz različnih zornih kotov in zanj so bile predlagane teoretične razlage ter kontrolni seznami. Obvladovanje odpora je kljub temu relativno nezrelo in slabo raziskano. Že samo razumevanje odpora s strani managementa naj bi bilo dovolj za njegovo uspešno obvladovanje, odpor pa se tipično obvladuje skupaj z ostalimi tehničnimi in organizacijskimi tveganji projektov razvoja informacijskih sistemov. Tega problema smo se v disertaciji lotili na več načinov. Najprej smo opredelili koncept odpora deležnikov. V raziskavah informacijskih sistemov široko uveljavljeni koncept odpor uporabnikov je namreč zavajajoč, saj do odpora ne prihaja zgolj pri končnih uporabnikih razvitega informacijskega sistema, temveč pri vseh projektnih deležnikih. Nato smo razvili teoretični model organizacijskih tveganj, ki trdi, da so organizacijska tveganja bistveno kompleksnejša od tehničnih. Za učinkovito obvladovanje organizacijskih tveganj je tako potrebno identificirati ne-trivialne temeljne vzroke, saj sicer obstaja možnost, da se ukrepi za obvladovanje organizacijskih tveganj nanašajo zgolj na simptome namesto na njihove temeljne vzroke. Skladno s teoretičnim modelom organizacijskih tveganj smo razvili dvofazni model obvladovanja odpora s fokusnimi skupinami. Raznolike teoretične razlage in kontrolne sezname iz literature na področju raziskav informacijskih sistemov smo konsolidirali ter razvili nov kontrolni seznam virov odpora. Tudi raziskave s področij uspeha informacijskih sistemov in uspeha projektov smo konsolidirali ter razvili nov model uspeha projektov razvoja informacijskih sistemov. Predlagani kontrolni seznam in predlagani model uspeha projektov razvoja informacijskih sistemov se uporabljata v prvi fazi predlaganega modela obvladovanja odpora s fokusnimi skupinami. Predlagani teoretični model organizacijskih tveganj in predlagani model obvladovanja odpora s fokusnimi skupinami sta bila evalvirana v študiji primera na projektu razvoja informacijskega sistema za proces kreditov v Banki BB (ime banke je fiktivno zaradi zagotavljanja anonimnosti). Z aplikacijo teoretičnega modela organizacijskih tveganj na odpor deležnikov smo v študiji primera potrdili, da imajo lahko organizacijska tveganja ne-trivialne temeljne vzroke, kar pomeni, da obstoječi pristopi obvladovanja tveganj v projektih razvoja informacijskih sistemov temeljijo na pomanjkljivi teoriji organizacijskih tveganj. V študiji primera smo tudi pokazali, da predlagani model obvladovanja odpora s fokusnimi skupinami nadgrajuje obstoječe pristope za obvladovanje organizacijskih tveganj in omogoča pridobivanje poglobljenih informacij, ki managementu omogočajo pripravo ustreznih ukrepov za obvladovanje odpora. Prestop iz tradicionalnih k agilnim metodam pomeni večjo fleksibilnost ter vključenost končnih uporabnikov v razvoj informacijskih sistemov in raziskave kažejo izboljšanje uspeha projektov razvoja informacijskih sistemov. Agilne metode so bile prvotno namenjene manjšim projektom razvoja programske opreme, a se zanimanje za njihovo uporabo pri večjih projektih razvoja v zadnjih letih naglo povečuje. Kljub temu je to področje še relativno nezrelo in delež uspešnih večjih projektov ostaja majhen. Obstoječi modeli za vrednotenje tradicionalnih metod se opirajo predvsem na njihove tehnične aspekte, redki modeli pa upoštevajo poleg njih tudi socialne. Kljub temu je vrednotenje tradicionalnih metod omejeno na razvojno organizacijo. Agilne metode znižujejo pomen formalne opredeljenosti metodologije razvoja, kar pomeni večjo prilagodljivost agilnih metod. Ta fleksibilnost hkrati pomeni tudi pogosto implicitno vrednotenje metodologije razvoja, saj le redke agilne metode to aktivnost tudi formalno opredeljujejo (npr. retrospektiva sprinta pri Scrumu). Vrednotenje agilnih metod je tako prepuščeno naključju oz. sposobnosti projektne ekipe. Zaradi poudarjenega sodelovanja z naročniškimi organizacijami lahko vrednotenje agilnih metod preseže meje razvojne organizacije in jih vrednoti tudi glede na dejavnike v naročniških organizacijah. Namen vrednotenja tradicionalnih in agilnih metod je optimizacija procesa razvoja informacijskih sistemov. Da bi vrednotenje metodologij razvoja premaknili še bolj k naročniškim organizacijam in njegov namen razširili tudi na obvladovanje odpora, smo v tej disertaciji najprej razvili meta-model sodelovanja razvojnih in naročniških organizacij pri razvoju informacijskih sistemov. Nato smo opredelili koncept stičnih elementov, t.j. elementov agilnih metod in lastnosti informacijskega sistema, s katerimi prihajajo v stik projektni deležniki v naročniških organizacijah. Nazadnje smo z aplikacijo teorij agentov sprememb in mnenjskih voditeljev razvili meta-model vpliva metodologij razvoja informacijskih sistemov na odpor deležnikov. Na tej podlagi smo razvili nov model za vrednotenje stičnih elementov. S predlaganim modelom je možno izboljševanje tistih delov metodologije razvoja, ki lahko vplivajo na odpor deležnikov v naročniških organizacijah. Predlagani model vrednotenja stičnih elementov je bil evalviran v študiji primera na projektu razvoja zdravstvenega informacijskega sistema Think!Med na Marandu (razvojna organizacija) in Pediatrični kliniki Univerzitetnega kliničnega centra Ljubljana (naročniška organizacija). V študiji primera smo pokazali, da predlagani model vrednotenja stičnih elementov omogoča pridobivanje poglobljenih informacij, ki razvojnim organizacijam omogoča pripravo ukrepov za izboljšanje tistih delov metodologije razvoja, ki lahko vplivajo na odpor deležnikov. Model obvladovanja odpora s fokusnimi skupinami in model vrednotenja stičnih elementov sta bila razvita za uporabo v posameznih projektih razvoja informacijskih sistemov. Zaradi napredka informacijske tehnologije v sodobnih organizacijah le redko najdemo primere izoliranih projektov razvoja informacijskih sistemov, saj so projekti razvoja informacijskih sistemov praktično ves čas v teku. V tej disertaciji smo se lotili te potrebe po kontinuiranemu obvladovanju odpora z razvojem procesa obvladovanja odpora. Predlagani proces je mogoče vključiti tako v procese naročniških kot tudi razvojnih organizacij. Kot del predlaganega procesa je mogoče vključiti model obvladovanja odpora s fokusnimi skupinami, ki je primernejši za naročniške organizacije, in model vrednotenja stičnih elementov, ki je primernejši za razvojne organizacije. The rate of failed information systems development projects remains high despite increasing investments into information systems and their major importance for contemporary organizations. Resistance to change is one of the critical reasons for such high failure rates. Organizations faced resistance to change long before the emergence of first computers as it is a natural reaction to change. With the emergence of computers and introduction of information technology to organizations, resistance to change became more problematic and visible as changes became much more frequent due to the fast development of technology. Today, after several decades since first introduction of information systems to organizations and related research resistance to change still stays a hard nut to crack and is present in most information systems development projects. User resistance has been studied from different perspectives in information systems research and several theoretical explanations and checklists were proposed. Despite this, resistance management stays relatively immature and poorly researched. The sheer understanding of resistance should be enough for successful management, while resistance is typically managed together with other technical and organizational information systems development project risks. In this dissertation we addressed this problem in several ways. First, we defined the concept of stakeholder resistance. The term user resistance which is broadly used in information systems research is misleading. Users of the information system are not the only ones who can resist the change. All project stakeholders can resist it. Next, we developed a theoretical model of organizational risks which posits that organizational risks are by far more complex than technical risks. It is necessary to identify non-trivial root causes of organizational risks in order to manage them effectively otherwise risk measures could address only the symptoms instead of root causes. In accordance with the theoretical model of organizational risks, we developed a two-phased focus groups resistance management model. We consolidated diverse theoretical explanations and resistance checklists in the area of information systems research into a novel resistance checklist. We also consolidated research on information systems and project success and developed a novel information systems development project success model. Both, the proposed resistance checklist and the information systems development project success model, are used in the first phase of the proposed focus groups resistance management model. A case study was conducted in a loan process information system development project in Bank BB (fictional name due to anonymity) in order to evaluate the proposed theoretical model of organizational risks and focus groups resistance management model. In the case study, we confirmed that organizational risks can have non-trivial root causes by applying the theoretical model of organizational risks to the context of stakeholder resistance. These results indicate that existing risk management approaches are based on inadequate organizational risk theory. We also showed that the proposed focus groups resistance management model upgrades existing organizational risks management approaches and provides in-depth information that enables managers to develop appropriate resistance handling measures. The crossing from traditional to agile methods means bigger flexibility and involvement of end users in the development of information systems and research shows better information systems development project success rates. Agile methods were primarily intended for small software development projects but there is an increase of interest for their use in large information systems development projects. However, this area remains relatively immature and the success rates of large projects remain low. Existing traditional method evaluation models address mainly their technical aspects with few models also considering certain social aspects. Nevertheless, the evaluation of traditional methods stays limited to the development organization. Agile methods lower the importance of formal definition of development methodologies which means greater flexibility of agile methods. This flexibility also means typically implicit evaluation of the development methodology as only few agile methods define this activity formally (e.g., sprint retrospective in Scrum). The evaluation of agile methods is thus left to coincidences and the abilities of the project team. The evaluation of agile methods can exceed the boundaries of development organizations due to emphasized collaboration with customer organizations therefore evaluating them according to factors stemming from customer organizations. The purpose of both traditional and agile method evaluation is the optimization of the information systems development process. To approach the customer organizations even more broaden the purpose of development methodology evaluation to encompass resistance management, we first develop a meta-model of cooperation between development and customer organizations in information systems development. Next, we defined the concept of interaction elements as agile method elements and information system characteristics that stakeholders in customer organization interact with. Finally, we applied the change agent and opinion leader theory in order to develop a meta-model of information systems development methodology influence on stakeholder resistance. Based on this, we developed a novel interaction elements evaluation model. The proposed model enables improvement of those development methodology parts that can influence stakeholder resistance in customer organizations. A case study was conducted in Think!Med medical information system development project in Marand (development organization) and Division of Paediatrics of University Medical Center Ljubljana (customer organization) in order to evaluate the proposed interaction elements evaluation model. The case study showed that the proposed model provides in-depth information that enable development organizations to develop measures to improve those parts of information systems development methodology that can influence stakeholder resistance in customer organizations. Both the proposed focus groups resistance management model and the proposed interaction elements evaluation model are intended to be used in single information systems development projects. However, in contemporary organizations it is almost impossible to find isolated information systems development projects because they are practically constantly present. In this dissertation we addressed this need for continuous resistance management by developing a resistance management process. The proposed process can be integrated into existing processes of both customer and development organizations. The proposed focus groups resistance management model and the proposed interaction elements evaluation model can be both included in the proposed resistance management process. The first model is more appropriate for customer organizations and the latter for development organizations.

V diplomski nalogi je prikazan postopek razvoja finančno-računovodske aplikacije za manjše podjetje po metodi Scrum. Najprej so predstavljene glavne karakteristike agilnih metod, sledi predstavitev metode Scrum s poudarkom na agilnem planiranju s pomočjo uporabniških zgodb. Nato je opisan podroben potek razvoja aplikacije po metodi Scrum in uporabljena spletna orodja. Na koncu je prikazano še delovanje aplikacije. Njene glavne funkcionalnosti lahko razdelimo v štiri skupine – obdelava podatkov o uporabnikih, vodenje projektov, prejetih računov in izdanih računov. Aplikacija je zasnovana za upravljanje s strani administratorja ali pa uporabnika. Prvi ima omogočene vse funkcionalnosti, uporabnik pa ima le opcijo urejanja projektov in osebnih podatkov. The thesis presents the development of a financial accountancy application for small enterprises using Scrum method. Firstly, the thesis introduces the main characteristics of agile methods, followed by a presentation of Scrum method with the emphasis on agile planning by means of user stories. Secondly, a detailed procedure of application development with the Scrum method and online tools is depicted. Finally, the thesis highlights the application's functionalities. The main functions of the application can be divided into four categories: user data processing, project management, overview of received and issued invoices. The application is designed to be operated by an administrator or user. The former can make use of all four functions, while the latter has only the option of editing projects and personal data.

Diplomsko delo obravnava uvajanje agilne metode razvoja Scrum v razvoj spletnega portala za zdravo prehrano. Začetno poglavje je namenjeno seznanitvi z agilnimi metodami. Bolj podrobno je opisna agilna metoda Scrum. V naslednjem poglavju se diplomsko delo osredotoči na predstavitev konkretnega projekta prenove spletnega portala, kjer je najprej predstavljeno poslanstvo in funkcija portala. Sledi opis nosilne platforme portala Magento in nekaterih orodij in storitev, ki so bile uporabljene pri razvoju: sistem za nadzor verzij Git in storitev Bitbucket. Osrednje poglavje diplomskega dela je namenjeno postopku uvajanja agilne metode Scrum v razvoj portala. V tem poglavju je opisan postopek vzpostavitve začetnega seznama zahtev, načrtovanje posameznih iteracij, merjenje napredka s pomočjo metrik, ki jih predlaga Scrum in načrtovanje rokov in izdaj. Zaključni del je namenjen analizi pridobljenih izkušnje in predlogom, kako bi lahko uvajanje Scruma še izboljšali. The thesis deals with the introduction of Scrum agile development method in the development of a web portal for a healthy diet. The initial chapter is an introduction to the agile methods More specifically described is agile method: Scrum. In the next chapter, the thesis focuses on a renovation project of a web portal where it firstly presents the mission and function of the portal. Following is a description of the supporting platform Magento and some tools and services that were used during development of the portal: Git and Bitbucket service. The central section of the thesis is aimed at the process of introducing Scrum agile method in the development of the portal. This section describes the process of setting up an initial Product Backlog, the planning of iterations (Sprints), measuring progress using metrics proposed by Scrum and planning deadlines and releases. The final part is devoted to the analysis of lessons learned and proposals of how to introduce Scrum even better.

Pojem agilnosti ter z njim povezane metode razvoja programske opreme so dandanes že tako razširjene, da verjetno skorajda ni IT strokovnjaka, ki ne bi vsaj slišal za katero izmed njih. Obstaja namreč mnogo metod, ki se predstavljajo kot agilne. V diplomskem delu tako opisujemo kaj pravzaprav je agilnost in kaj so tisti ključni faktorji, ki neko metodo naredijo agilno, opisujemo po kakšnih vrednotah in načelih pravzaprav delujejo agilne metode ter kaj so tiste ključne razlike med njimi in vsemi ostalimi, tradicionalnimi metodami. V nadaljevanju raziskujemo kako agilne metode dojemajo tisti, ki delujejo po njihovih načelih, ter kako jih dojemajo naročniki, ki aktivno sodelujejo v procesih razvoja. V diplomskem delu predstavljamo še pomembnejše agilne metode razvoja programske opreme, podajamo njihova osnovna načela in priporočila ter opisujemo kritične dejavnike uspeha na področju agilnega razvoja programske opreme. Podrobno opisujemo metodo Scrum ter opravljamo raziskavo njenih vplivov tako na IT podjetja kot tudi na njihove zaposlene doma in po svetu. V zaključku diplomskega dela podajamo rezultate opravljene raziskave. Concept of agility in IS development methods are so widespread these days, that there is probably no one left in the IT bussiness sector, that hasn't at least heard of agile methodology until now. Namely because curently exist many methods that declare themselves as agile. In this diploma work we describe what exactly agility is and what those crucial factors are, that make one method agile and the other not, we also describe with what values and principles agile methods actually work and what those crucial differences between agile methods and other, traditional methods are. After that we are exploring how agile methods are perceived by those who live and work by their principles and how they are perceived by clients or customers that actively cooperate in the development processes. We are also presenting important agile software developments methods, interpret their core values and principles and describe critical success factors in agile software development areas. Furthermore we describe the Scrum method in detail and perform global research on how the implementation of Scrum method affect IT organizations and people working within. In conclusion we interpret the results of our reseach.

Diplomsko delo obravnava tematiko agilnega razvoja programske opreme. V sklopu dela so najprej opisane tradicionalne in agilne metode s poudarkom na metodologiji Scrum. Nato sledita dve osrednji poglavji.Prvo izmed njiju opisujeuporabometodologije Scrum na realnem projektu implementacije rezervacij športne dvorane, v sklopu katerega smo podrobneje opredelili zahteve, oblikovali uporabniške zgodbe, izvedli njihovo ocenjevanje po metodah planning poker in team estimation game ter se nenazadnje dotaknili tudi uporabljenih tehnologij. Drugo pa obsega analizo točnosti ocen zahtevnosti posameznih uporabniških zgodb, v kateri primerjamo čas, ocenjen po metodah planning poker in team estimation game, z dejansko porabljenim časom. V zaključnem delu je podan še pregled težav, s katerimi smo se srečali med implementacijo in predlogi za njihovo rešitev. The thesis deals with the agile software development. In thesis we first describe traditional and agile methodologies for software development with emphasis on Scrum methodology. Then two main chapters follow. First of them describes how to use Scrum methodology on a real project for reservation of sport hall. In accordance with the Scum guidelines user stories were formed and estimated. Estimation was made by using planning poker and team estimation game methods. Within chapter used technology for implementing application is described. In the second chapter we analyse accuracy of all estimations based on methods planning poker, team estimation game and actual spent time for implementing user stories. At the end we review the problems and their solutions, which were encountered during implementation.

Raziskava obravnava prilagoditev agilne metode za integracijo EDMS v obstoječi informacijski sistem. Problemsko stanje, ki ga v konkretnem poslovnem sistemu zaznavajo, je pomanjkanje definirane metodologije za integracijo EDMS, povprečna prekoračitev planiranih projektnih rokov od 20 % do 50 %, oteženo sledenje sprememb projekta, pomanjkanje testiranja in nedefinirano določanje prioritet zahtevam. Podan je pregled strokovne literature o agilnih metodah, EDMS, BPMN. Ugotovljeno je, da dokumentacija za prilagoditev agilne metode pri integraciji EDMS rešitve ne obstaja. Analizirani so konkretni primeri procesa integracije EDMS v obravnavani organizaciji in uporabljen je BPMN kot orodje za modeliranje poslovnega procesa. Anketirali smo 3 tipe uporabnikov EDMS: končne uporabnike, skrbnike EDMS in končne uporabnike, ki so hkrati skrbniki EDMS. Statatistika izvedene ankete je prikazala, da se naročniki v več kot polovici primerov strinjajo z vrednotami agilnega razvoja in da je naročniku delujoča programska oprema skoraj tako pomembna kot popolna dokumentacija. Uvedba EDMS rešitve je na začetku pri uporabnikih povzročila nezadovoljstvo, vendar bi uporabniki kljub temu storitve in produkte EDMS rešitve priporočali tudi drugim. Večinsko so mnenja, da se ne bi vrnili v stanje pred implementacijo EDMS rešitve. Najpomembnejši predlogi izboljšav integracije so uvedba dnevnih sestankov, seznama zahtev, seznama zahtev iteracije, table aktivnosti ter določitev prioritet zahtevam. Zelo pomembna bi bila tudi uporaba krajših razvojnih ciklov in večja vključenost naročnika pri integraciji EDMS. Predvideni učinki predlogov so: a)povečana sposobnost upravljanja spreminjajočih prioritet zahtev in produktivnost, b) izboljšana sledljivost projekta, morala skupine in kakovost programske opreme, c) zmanjšano tveganje zakasnitve ali neuspeha projekta in d) večje zadovoljstvo naročnikov ob enakih virih. In this research we adapt agile methods for the integration of EDMS in existing information systems. Problem situation, which is in this particular business system perceived are a lack of defined methodology for the integration, the average overrun of planned project deadlines from 20 % to 50 %, difficulty in tracking design changes, lack of testing and undefined prioritizing requests. A review of the scientific literature on agile methods, EDMS and BPMN is presented. It was found that the specific literature on the adaptation of agile methods in the integration of EDMS solution does not exist. Concrete examples of the integration process of EDMS in this business are analysed. BPMN was used as a tool for business process modeling. We surveyed three types of EDMS users: end users, responsible owners of EDMS and end users, who are also responsible owners of EDMS. Survey showed that clients in more than half of the cases agree with the values of agile development and that to client operating software is almost as important as the complete documentation. Introduction of EDMS solutions caused user dissatisfaction at the beginning, but users would nevertheless recommend services and EDMS products to others. The majority have opinion that they would not return to the situation prior to the implementation of EDMS. The most important suggestions on integration improvements are introduction of daily stand-up meetings, product backlogs, sprint backlogs, task boards and requirement prioritization. It would be particular important to use shorter development cycles and deeper client involvement in the integration. Expected impacts of these improvements include: a) increased management capabilities for changing priorities and productivity, b) improved project traceability, group morale, and software quality, c) reduced risk of project overrun or project failure and d) increased customer satisfaction while using equal resources.

Agilne metode razvoja programske opreme so fleksibilne metode primerne predvsem za manjše razvojne skupine, ki se morajo hitro prilagajati spremembam. Pogosto se navajajo kot alternativa bolj togim klasičnim metodam. Preverjali smo možnost vpeljave agilnih metod na primeru podjetja, ki sedaj za razvoj programske opreme ne uporablja nobene formalno definirane metode. Predvsem smo z intervjujem z razvijalci ugotavljali njihovo pripravljenost na spremembe. Ugotovili smo, da so v splošnem sicer pripravljeni na spremembe, vendar ne na hitre spremembe. Vpeljavo agilnih metod smo obravnavali kot možno rešitev za dosego dveh ciljev v povezavi z razvojem, ki si jih je zadalo podjetje. Ugotovili smo, da nobena od obravnavanih metodologij ni v celoti primerna za podjetje, so pa primerni posamezni deli metodologij. Zato smo pripravili predlog lastne metodologije, ki pretežno temelji na lastnostih obravnavanih agilnih metod. Poleg tega smo pripravili tudi predlog programa za spremljanje razvoja programske opreme. Agile software development methods are flexible methods suitable primarily for small development teams who need to adapt to changes quickly. Often, they are regarded as alternative to more rigid classical methods. We examined the possibility to adopt agile methods in case of a small software development company that currently uses no formal method in its development process. We interviewed the developers to determine their willingness to accept change in the development process. We found that they are generally prepared to accept changes but only if they are implemented gradually. We examined possibility of using agile methods to achieve the development goals set by company management. We determined that none of examined methods is entirely suitable for the company, but certain parts of the methods are. Based on the conclusion of our investigation and considering the limitations set by the management, we prepared a proposal for a methodology composed of parts of the examined agile methods. We also prepared the requirements for a program to support and control the software development process in the company.

Obrađene su metodologije vođenja složenih informatičkih projekata. Poseban osvrt je na agilne metode, odnosno kanban metodu. Opisana je primjena navedene metode na vođenje projekta: Informacijski sustav za elektroničko upravljanje dokumentacijom Splitsko dalmatinske županije.

Tema ovog diplomskog rada je primjena metode agilnog razvoja softvera Scrum u razvoju velikih telekomunikacijskih sustava. U okviru diplomskog rada provedena je analiza i usporedba postojećeg iterativno-inkrementalnog modela razvoja koji se primjenjuje u razvojno-istraživačkom centru tvrtke i agilnog modela razvoja koji je odnedavno u upotrebi. U okviru diplomskog rada razvijena je skripta za automatizaciju provjere kvalitete softvera u suradnji s tvrtkom Ericsson Nikola Tesla. Skripta je razvijena za potrebe Scrum tima s kojim je ostvarena suradnja u trajanju jedne iteracije. Također je opisan proizvod na kojem radi tim, te način rada i profil tima. Razvijena skripta je testirana na jednom softverskom modulu u okviru sustava MSS. Testiranjem je potvrđeno da skripta poboljšava učinkovitost i brzinu procesa testiranja.

V diplomskem delu obravnavamo planiranje projektov po metodologiji ekstremnega programiranja. Predstavimo razloge za nastanek agilnih metodologij, pozitiven vpliv agilnosti na uspešnost projektov, na kratko predstavimo metodologijo ekstremnega programiranja, nadalje pa sledi še podroben prikaz njene prakse igre planiranja. Prikazane so tudi nekatere omejitve te prakse in zanje možne rešitve ter prilagoditve. Na primeru podjetja FJA Oda Team d.o.o je podrobno predstavljen prilagojen proces igre planiranja, kjer primerjamo predstavljeno teorijo s praktično izvedbo igre planiranja. Prikažemo tudi analizo veščine napovedovanja truda v omenjenem podjetju. This paper discusses planning projects using extreme programming methodology. It presents the causes for the emergence of agile methodologies, the positive impact of agility on the success of projects, and a brief presentation of extreme programming methodology, followed by a detailed view on its planning practice named the planning game. Some limitations of this practice are pointed out, for which some possible solutions and adjustments to overcome them are provided. A study was made of FJA Oda Team d.o.o. software company's modified form of the planning game, where a comparison is made between presented theory and applied practice. In addition, the paper presents an analysis of the company's technique of estimating effort.

V diplomski nalogi smo se najprej posvetili pravilni izbiri metodologije za razvoj programske opreme. V nadaljevanju smo opisali principe agilne metodologije in se podrobneje posvetili metodi Scrum, ki smo jo tudi natančneje preučili. Izbrali smo tri različna orodja, ki podpirajo metodologijo Scrum in jih natančneje opisali ter jih med seboj primerjali. Na podlagi ugotovitev smo naredili načrt za lastno orodje. At the beginning, the diploma thesis deals with the appropriate choice of methodology for software development. Next are a description of the Agile methodologies principles and a detailed description of the Scrum method. Three various tools which support the Scrum method are chosen, described and compared in detail. Based on the observations, a plan for our own tool is presented.

Vrijeme do plasiranja na tržište i nedovoljno početno saznanje o potrebama dva su značajna problema po kojima se organiziranje potreba kod projekata razvijanja softvera za tržište razlikuje od projekata za softver po narudžbi. Ti se problemi mogu riješiti primjenom agilnih metodologija razvoja softvera kad se radi o tržišno orijentiranom softveru budući da Agilne metode naglašavaju dinamički pristup organiziranju potreba usko povezan s iterativnim ciklusom isporuke. U ovom radu, dinamički pristup Agilnih metoda definiranju potreba koristi se za uspješnu implementaciju složenog tržišno orijentiranog softverskog projekta., Time-to-market and insufficient initial requirements are two significant challenges that make managing requirements for market-driven software projects different from custom-made software projects. These challenges can be resolved by using agile software development methodologies for market-driven software development as agile methods put emphasis on a dynamic approach for requirement engineering which works closely with an iterative release cycle. In this study, dynamic requirement engineering approach of Agile methods was used for the successful implementation of market-driven complex software project.