SCRUM SELF ORGANIZATIONAL AND HIGHLY FUNCTIONAL TEAMS

Ovaj zavröni rad u osnovi dokumentira znanja koja su steöena tokom prethodnih 20 godina primjenjujuéi Scrum kao najkoriöteniji model agilnog mena&menta. Scrum je procesni okvir koji se koristi za upravljanje razvojem proizvoda i drugim radom znanja. Scrum je empirijski po tome 5to timovima pnüa naöin da uspostave hipotezu o tome kako oni misle da neäto funkcionira, isprobaju ga, razmisle o iskustvu i naprave odgovarajuée prilagodbe. To jest, kada se okvir pravilno koristi. Scrum je strukturiran na naéin koji omoguéuje timovima da ugrade prakse iz drugih okvira gdje imaju smisla za kontekst tima. Uloge u Scrumu, artefakti, dogadanja i pravila su nepromjenjivi i iako se mogu primijeniti samo dijelovi, rezultat nije Scrum. Scrum postoji samo kao cjelina i funkcionira dobro kao okru%enje za druge tehnike, metodologije i prakse. Scrum je najprikladniji u sluöaju kada viäefunkcionalni tim radi u okru±enju razvoja proizvoda gdje postoji netrivijalna koliéina posla koja se moie podijeliti na viöe od jedne iteracije od 2 do 4 tjedna.This final paper basically documents the knowledge gained over the past 20 years using Scrum as the most used model of agile management. Scrum is a process framework used to manage product development and other Imowledge work. Scrum is empirical in that it provides a means for teams to establish a hypothesis of how they think something works, try it out, reflect on the experience, and make the appropriate adjustments. That is, when the framework is used properly. Scrum is sfructured in a way that allows teams to incorporate practices from other frameworks where they make sense for the team's context. Scrum roles, artifacts, events and rules are immutable and although only parts can be applied, the result is not Scrum. Scrum exists only as a whole and ftnctions well as an environment for other techniques, methodologies and practices. Scrum is best suited in the case where a cross functional team is working in a product development setting where there is a non trivial amount of work that lends itself to being split into more than one 2 — 4 week iteration