{"id":1248,"date":"2013-07-24T14:44:19","date_gmt":"2013-07-24T12:44:19","guid":{"rendered":"http:\/\/agile.sk\/?p=1248"},"modified":"2014-12-16T21:02:37","modified_gmt":"2014-12-16T20:02:37","slug":"agilne-kontrakty","status":"publish","type":"post","link":"https:\/\/agile.sk\/?p=1248","title":{"rendered":"Agiln\u00e9 kontrakty"},"content":{"rendered":"<p>Tento \u010dl\u00e1nok je venovan\u00fd obchodn\u00edkom, \u0161\u00e9fom firiem, pr\u00e1vnikom a business developerom &#8211; \u013eudom ktor\u00ed tvoria a s\u00fa zodpovedn\u00ed za kontrakty pre agiln\u00e9 softv\u00e9rov\u00e9 t\u00edmy. Popisuje typy kontraktov pre agiln\u00e9 projekty, ich v\u00fdhody a nev\u00fdhody.<\/p>\n<p>Kontrakt pre agiln\u00fd projekt by mal rie\u0161i\u0165 podobn\u00e9 t\u00e9my a probl\u00e9my ako kontrakt pre tradi\u010dn\u00fd model v\u00fdvoja softv\u00e9ru: cena, term\u00edny, rozsah dod\u00e1vky, z\u00e1ruka,\u00a0odstra\u0148ovanie\u00a0ch\u00fdb\u00a0a pod. K\u013e\u00fa\u010dov\u00fd rozdiel je pochopenie ako prebieha dodanie v\u00fdsledn\u00e9ho produktu v agilnom projekte. \u013dudia, ktor\u00ed uzatv\u00e1raj\u00fa kontrakt, musia rozumie\u0165 agiln\u00fdm princ\u00edpom. Dod\u00e1vky produktu v iter\u00e1ci\u00e1ch a skor\u00e1 kolabor\u00e1cia medzi z\u00e1kazn\u00edkom a dod\u00e1vate\u013eom pom\u00e1ha zni\u017eova\u0165 rizik\u00e1 projektu. Kontrakt pre agiln\u00e9 projekty by mal by\u0165 zalo\u017een\u00fd na transparentnosti a d\u00f4vere. A tak ako sa vyv\u00fdja vz\u0165ah medzi z\u00e1kazn\u00edkom a dod\u00e1vate\u013eom, tak sa mus\u00ed\u00a0vyv\u00edja\u0165\u00a0aj kontrakt &#8211; presne v zmysle princ\u00edpu:\u00a0 &#8220;Customer collaboration over contract negotiation&#8221;, <a href=\"http:\/\/agilemanifesto.org\">http:\/\/agilemanifesto.org<\/a>.<\/p>\n<p>Je to zmena myslenia? \u00c1no &#8211; prioritou pre v\u0161etk\u00fdch je \u00faspe\u0161n\u00e1 realiz\u00e1cia projektu, nie &#8220;pr\u00e1vnicky bezchybn\u00fd&#8221; kontrakt, ktor\u00fd nevedie k \u00faspe\u0161n\u00e9mu dokon\u010deniu projektu.<\/p>\n<p>Ako vyzer\u00e1 &#8220;tradi\u010dn\u00fd&#8221; kontrakt? Kop\u00edruje tradi\u010dn\u00fd model v\u00fdvoja softv\u00e9ru:<\/p>\n<ul>\n<li>zmluva\u00a0obsahuje ve\u013emi detailn\u00fa \u0161pecifik\u00e1cia po\u017eiadaviek,<\/li>\n<li>term\u00edn dodania produktu je ve\u013emi vzdialen\u00fd, nezriedka rok a viac,<\/li>\n<li>feedback od z\u00e1kazn\u00edka je poskytnut\u00fd neskoro, niekedy a\u017e po fin\u00e1lnej dod\u00e1vke produktu,<\/li>\n<li>platba dod\u00e1vate\u013eovi je za fin\u00e1lnu dod\u00e1vku produktu,<\/li>\n<li>probl\u00e9my ak projekt je nie je dokon\u010den\u00fd do konca s kompletnou funkcionalitou,<\/li>\n<li>rozsiahla klauzula o rizik\u00e1ch, testovan\u00ed, z\u00e1ruke, n\u00e1hrade \u0161kody a odstra\u0148ovan\u00ed ch\u00fdb,<\/li>\n<li>je pou\u017eit\u00e1 pr\u00e1vnick\u00e1 terminol\u00f3gia, samotn\u00e9 koncipovanie a ods\u00fahlasenie zmluvy trv\u00e1 dlh\u00fd \u010das.<\/li>\n<\/ul>\n<p>Kontrakt pre agiln\u00e9 softv\u00e9rov\u00e9 t\u00edmy je ak\u00fdmsi protip\u00f3lom predch\u00e1dzaj\u00facich bodov, ide\u00e1lne len definuje framework pre agiln\u00fd \u0161t\u00fdl vedenia projektu. V\u010faka funguj\u00facemu produktu, ktor\u00fd m\u00e1me k dispoz\u00edcii na konci ka\u017edej iter\u00e1cie a skor\u00e9mu feedbacku od z\u00e1kazn\u00edka, m\u00f4\u017eeme zmeni\u0165 poh\u013ead na kontrakt a rizik\u00e1 s\u00favisiace s projektom.<\/p>\n<h3>Fixed Price<\/h3>\n<p>Fixed Price kontrakt je najjednoduch\u0161\u00ed typ kontraktu. Fixn\u00e1 je cena, obsah a aj \u010das dod\u00e1vky softv\u00e9ru. Z\u00e1kazn\u00edk plat\u00ed dod\u00e1vate\u013eovi ur\u010dit\u00fa \u010diastku z celkovej dohodnutej sumy zvy\u010dajne na konci ka\u017edej iter\u00e1cie.<\/p>\n<p>Tento typ kontraktu m\u00f4\u017ee fungova\u0165 ak funguje d\u00f4vera medzi z\u00e1kazn\u00edkom a dod\u00e1vate\u013eom a ak z\u00e1kazn\u00edk dost\u00e1va na konci ka\u017edej iter\u00e1cie po\u017eadovan\u00fd softv\u00e9r. Dod\u00e1vate\u013e m\u00f4\u017ee akceptova\u0165 zmeny v p\u00f4vodne dohodnut\u00fdch po\u017eiadavk\u00e1ch, pokia\u013e je zachovan\u00e1 komplexita a zlo\u017eitos\u0165. Potom sa z\u00e1kazn\u00edk nemus\u00ed s\u00fastredi\u0165 na samotn\u00fd kontrakt, ale kooperuje s dod\u00e1vate\u013eom a ak t\u00e1to spolupr\u00e1ca naozaj funguje &#8211; v\u0161etko je v najlep\u0161om poriadku.<\/p>\n<p>Fixed Price kontrakt v\u0161ak \u010dasto vedie k situ\u00e1cii kedy z\u00e1kazn\u00edk nedostane \u010do p\u00f4vodne chcel alebo dod\u00e1vate\u013e je v strate. M\u00f4\u017ee sa tie\u017e sta\u0165, \u017ee dod\u00e1vate\u013e, v snahe doda\u0165 \u010do s\u013e\u00fabil v r\u00e1mci fixnej ceny, zni\u017euje kvalitu dod\u00e1vky &#8211; chybov\u00fd k\u00f3d, ch\u00fdba dohodnut\u00e1 funkcionalita alebo testy. To vedie k e\u0161te va\u010d\u0161\u00edm celkov\u00fdm n\u00e1kladom vzh\u013eadom na opravu a n\u00e1sledn\u00fa \u00fadr\u017ebu.<\/p>\n<p>Najv\u00e4\u010d\u0161ie riziko pri Fixed Price kontraktoch je na strane dod\u00e1vate\u013ea. Dod\u00e1vate\u013e si m\u00f4\u017ee toto riziko premietn\u00fa\u0165 do svoj\u00edch odhadov n\u00e1kladov a akceptova\u0165 treb\u00e1rs menej user stories pre dann\u00fa iter\u00e1ciu. Toto v\u0161ak bude vies\u0165 k strate transparentnosti, d\u00f4very a ku snahe dod\u00e1vate\u013ea hra\u0165 na v\u00e4\u010d\u0161\u00ed zisk.<\/p>\n<h3>T&amp;M<\/h3>\n<p>T&amp;M &#8211; \u010cas a materi\u00e1l je typ kontraktu kedy z\u00e1kazn\u00edk plat\u00ed dod\u00e1vate\u013eovi za vopred dohodnut\u00fa hodinov\u00fa sadzbu a za pou\u017eit\u00fd materi\u00e1l ako napr. licencie alebo HW.<\/p>\n<p>Tento typ kontraktu je vhodn\u00fd pre agiln\u00e9 projekty. Je jednoduch\u00fd, jasn\u00fd a podpruje agilitu. Typick\u00e1 dilema z\u00e1kazn\u00edka je kedy bude ukon\u010den\u00fd projekt, \u010di neuviazne v nikdy sa nekon\u010diacich platb\u00e1ch dod\u00e1vate\u013eovi a \u010di dost\u00e1va primeran\u00fa hodnotu za svoje peniaze. Tieto obavy s\u00fa eliminovan\u00e9 ka\u017ed\u00fa iter\u00e1ciu prostredn\u00edctvom:<\/p>\n<ul>\n<li>jasnej inform\u00e1cie o r\u00fdchlosti softv\u00e9rov\u00e9ho t\u00edmu &#8211;\u00a0 meranej pomocou implementovan\u00fdch user stories alebo user features,<\/li>\n<li>vysokej miere transparetnosti a<\/li>\n<li>mo\u017enosti ukon\u010di\u0165 kontrakt na konci hociktorej iter\u00e1cie.<\/li>\n<\/ul>\n<p>T&amp;M kontrakt vy\u017eaduje vysok\u00fd stupe\u0148 d\u00f4very na oboch stran\u00e1ch a to tak ako pri ka\u017edom inom vz\u0165ahu medzi \u013eudmi nefunguje okam\u017eite ale vyv\u00fdja sa. Je fajn za\u010da\u0165\u00a0 budova\u0165 tento vz\u0165ah prostredn\u00edctvom Fixed Price kontraktu a postupne prejs\u0165 na T&amp;M typ kontraktu.<\/p>\n<h3>Target Cost<\/h3>\n<p>Target Cost kontrakt je v\u00fdsledkom spolo\u010dnej zodpovednosti oboch st\u00e1n: z\u00e1kazn\u00edka aj dod\u00e1vate\u013ea. Kontrakt je \u010dasto dokonca komunikovan\u00fd v\u0161etk\u00fdm zamestnancom a t\u00ed maj\u00fa z\u00e1ujem kolaborova\u0165, efekt\u00edve rie\u0161i\u0165 probl\u00e9my a tak dosahova\u0165 spolo\u010dn\u00e9 ciele.<\/p>\n<p>Tento typ kontraktu pou\u017e\u00edva napr. Toyota s cie\u013eom dosiahnu\u0165 dlhodob\u00fd vz\u0165ah s dod\u00e1vate\u013emi zalo\u017een\u00fd na d\u00f4vere a vz\u00e1jomnej podpore.\u00a0 Samotn\u00fd kontrakt prebieha v dvoch f\u00e1zach:<\/p>\n<ol>\n<li>Inci\u00e1lna f\u00e1za &#8211; z\u00e1kazn\u00edk a dod\u00e1vate\u013e spolo\u010dne identifikuj\u00fa, analyzuj\u00fa a odhaduj\u00fa v\u0161etky po\u017eiadavky projektu a n\u00e1klady mo\u017en\u00fdch zmien po\u010das trvania projektu. Z tohto sa vypo\u010d\u00edtaju pl\u00e1novan\u00e9 n\u00e1klady. N\u00e1sledne sa ur\u010d\u00ed cie\u013eov\u00fd profit (napr. 15% z p\u00e1novan\u00fdch n\u00e1kladov). V\u0161etky tieto detaily s\u00fa zdie\u013ean\u00e9 z\u00e1kazn\u00edkovi.<\/li>\n<li>Vykonanie projektu &#8211; po\u010das ktorej s\u00fa kalkulovan\u00e9 skuto\u010dn\u00e9 n\u00e1klady na vykonanie napr. \u010das programovania, \u010das str\u00e1ven\u00fd na meetingoch, HW. Tieto inform\u00e1cie s\u00fa zdie\u013ean\u00e9 z\u00e1kazn\u00edkovi, najlep\u0161ie online.<\/li>\n<\/ol>\n<p>Teraz pr\u00edde najzauj\u00edm\u00fd aspekt tohto typu kontraktu. V pr\u00edpade rozdielu medzi pl\u00e1novan\u00fdmi a skuto\u010dn\u00fdmi n\u00e1kladmi je vyrovnanie vypo\u010d\u00edtane tak, \u017ee sa zdie\u013eaj\u00fa n\u00e1klady alebo profit medzi z\u00e1kazn\u00edkom a dod\u00e1vate\u013eom. Napr:<\/p>\n<p style=\"text-align: center\">Vyrovnanie rozdielu = (Skuto\u010dn\u00e9 n\u00e1klady &#8211; Pl\u00e1novan\u00e9 n\u00e1klady) * Kon\u0161tanta zdie\u013eania<\/p>\n<p style=\"text-align: center\">Platba dod\u00e1vate\u013eovi = Skuto\u010dn\u00e9 n\u00e1klady + Cie\u013eov\u00fd profit + Vyrovnanie rozdielu<\/p>\n<p>Ako je vidie\u0165 vyrovnanie rozdielu m\u00f4\u017ee by\u0165 kladn\u00e9 alebo z\u00e1porn\u00e9. Ak skutpo\u010dn\u00e9 n\u00e1klady s\u00fa vy\u0161sie ako pl\u00e1novan\u00e9, z\u00e1kazn\u00edk aj dod\u00e1vate\u013e spolo\u010dne zdie\u013eaju tieto n\u00e1klady. Ak skuto\u010dn\u00e9 n\u00e1klady s\u00fa ni\u017e\u015bie, obaja zdie\u013eaj\u00fa aj tento profit. V\u00fdsledkom tohto cel\u00e9ho potom je to, \u017ee obe strany kontraktu sa sna\u017eia redukova\u0165 n\u00e1klady.<\/p>\n<h3>Profit Sharing<\/h3>\n<p>Profit Sharing typ kontraktu je zalo\u017een\u00fd na spolo\u010dnom joint venture z\u00e1kazn\u00edka a dod\u00e1vate\u013ea. Z\u00e1kazn\u00edk poskytuje peniaze na rozvoj dod\u00e1vate\u013eovi a obidne strany prosperuj\u00fa a zdie\u013eaj\u00fa pr\u00edjmy v pr\u00edpade zisku. Tento model je zlo\u017eitej\u0161\u00ed na realiz\u00e1ciu a m\u00e1 ur\u010dit\u00e9 nev\u00fdhody z toho vypl\u00fdvaj\u00face.<\/p>\n<h3>Progressive<\/h3>\n<p>Progressive kontrakt predstavuje framework pre spolupr\u00e1cu medzi dod\u00e1vate\u013eom a z\u00e1kazn\u00edkom. Popisuje vz\u0165ah medzi oboma stranami, ale nie priamo obsah dod\u00e1vky alebo cenu. Samotn\u00fd kontrakt sa tvor\u00ed pre ka\u017ed\u00fa iter\u00e1ciu a typicky sa vyv\u00fdja cez Fixed Price kontrakt, T&amp;M kontrakt a\u017e k Target Cost kontraktu. V\u00fdhodou je zna\u010dn\u00e1 flexibilita. Nev\u00fdhodou to, \u017ee pre ka\u017ed\u00fa iter\u00e1ciu mus\u00edme vytvori\u0165 nov\u00fd kontrakt.<\/p>\n<p>&nbsp;<\/p>\n<p>Na z\u00e1ver len zhrniem vz\u0165ah rizika medzi dod\u00e1vate\u013eom a z\u00e1kazn\u00edkom pri r\u00f4znych typoch kontraktov:<\/p>\n<ul>\n<li>Fixed Price kontrakt &#8211; riziko je na strane dod\u00e1vate\u013ea,<\/li>\n<li>T&amp;M kontrakt &#8211; riziko je na strane na z\u00e1kazn\u00edka,<\/li>\n<li>Target Cost a Profit Share kontrakt &#8211; riziko sa zdie\u013ea medzi obe strany.<\/li>\n<\/ul>\n<p style=\"text-align: center\"><a href=\"http:\/\/agile.sk\/wp-content\/uploads\/2013\/07\/RizikaKontraktu.jpg\"><img loading=\"lazy\" decoding=\"async\" class=\"size-full wp-image-1268 aligncenter\" title=\"Rizik\u00e1 kontraktov\" alt=\"RizikaKontraktu\" src=\"http:\/\/agile.sk\/wp-content\/uploads\/2013\/07\/RizikaKontraktu.jpg\" width=\"661\" height=\"314\" \/><\/a><\/p>\n<p style=\"text-align: right\"><a href=\"https:\/\/www.linkedin.com\/pub\/jan-majoros\/2\/990\/30b\" target=\"_blank\">J\u00e1n Majoro\u0161<\/a><\/p>\n\n<!-- Facebook Like Button v1.9.6 BEGIN [http:\/\/blog.bottomlessinc.com] -->\n<iframe src=\"http:\/\/www.facebook.com\/plugins\/like.php?href=https%3A%2F%2Fagile.sk%2F%3Fp%3D1248&amp;layout=standard&amp;show_faces=false&amp;width=450&amp;action=like&amp;colorscheme=light\" scrolling=\"no\" frameborder=\"0\" allowTransparency=\"true\" style=\"border:none; overflow:hidden; width:450px; height: 30px; align: left; margin: 20px 0px 2px 0px\"><\/iframe>\n<!-- Facebook Like Button END -->\n","protected":false},"excerpt":{"rendered":"<p>Tento \u010dl\u00e1nok je venovan\u00fd obchodn\u00edkom, \u0161\u00e9fom firiem, pr\u00e1vnikom a business developerom &#8211; \u013eudom ktor\u00ed tvoria a s\u00fa zodpovedn\u00ed za kontrakty pre agiln\u00e9 softv\u00e9rov\u00e9 t\u00edmy. Popisuje typy kontraktov pre agiln\u00e9 projekty, ich v\u00fdhody a nev\u00fdhody. Kontrakt pre agiln\u00fd projekt by mal rie\u0161i\u0165 podobn\u00e9 t\u00e9my a probl\u00e9my ako kontrakt pre tradi\u010dn\u00fd model v\u00fdvoja softv\u00e9ru: cena, term\u00edny, rozsah [&hellip;]<\/p>\n","protected":false},"author":7,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[8],"tags":[11,39,32],"_links":{"self":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/1248"}],"collection":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/users\/7"}],"replies":[{"embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=1248"}],"version-history":[{"count":32,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/1248\/revisions"}],"predecessor-version":[{"id":54054,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/1248\/revisions\/54054"}],"wp:attachment":[{"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=1248"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=1248"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=1248"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}