{"id":97853,"date":"2020-10-22T14:42:44","date_gmt":"2020-10-22T12:42:44","guid":{"rendered":"https:\/\/prohoster.info\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte"},"modified":"2020-11-18T00:58:50","modified_gmt":"2020-11-17T22:58:50","slug":"organizacziya-rabochego-proczessa-v-komande-na-it-proekte","status":"publish","type":"post","link":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte","title":{"rendered":"Organiz\u00e1cia pracovn\u00e9ho procesu v t\u00edme na IT projekte","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Ahojte priatelia. \u010casto, najm\u00e4 v outsourcingu, vid\u00edm t\u00fa ist\u00fa situ\u00e1ciu. Nedostatok jasn\u00e9ho pracovn\u00e9ho procesu v t\u00edmoch na r\u00f4znych projektoch.<\/p>\n<p>Najd\u00f4le\u017eitej\u0161ie je, \u017ee program\u00e1tori nerozumej\u00fa, ako komunikova\u0165 so z\u00e1kazn\u00edkom a medzi sebou. Ako vybudova\u0165 nepretr\u017eit\u00fd proces v\u00fdvoja kvalitn\u00e9ho produktu. Ako si napl\u00e1nova\u0165 svoj pracovn\u00fd de\u0148 a sprinty.<\/p>\n<p>A to v\u0161etko vy\u00fasti do zme\u0161kan\u00fdch term\u00ednov, nad\u010dasov, neust\u00e1lych sporov, kto je vinn\u00edk, a nespokojnosti z\u00e1kazn\u00edkov \u2014 kam a ako v\u0161etko smeruje. Pomerne \u010dasto to vedie k zmene program\u00e1torov, alebo cel\u00fdch t\u00edmov. Ztr\u00e1te z\u00e1kazn\u00edka, zhor\u0161eniu reput\u00e1cie a tak \u010falej.<\/p>\n<p>V istom \u010dase som sa dostal na tak\u00fd projekt, kde sa v\u0161etky tieto nepr\u00edjemnosti vyskytovali. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nNikto nechcel prevzia\u0165 zodpovednos\u0165 za projekt (ve\u013ek\u00fd servisn\u00fd trhovisko), fluktu\u00e1cia bola dramatick\u00e1, z\u00e1kazn\u00edk jednoducho ni\u010dil a hneval sa. CEO sa k mne nejako pribl\u00ed\u017eil a povedal, \u017ee m\u00e1\u0161 potrebn\u00e9 sk\u00fasenosti, tak ti d\u00e1vam vo\u013en\u00fa ruku. Zober si projekt a ak sa ti to nepodar\u00ed, projekt zavrieme a v\u0161etk\u00fdch vyhod\u00edme. Ak to vyjde, bude to skvel\u00e9, potom ho vedz a rozv\u00edjaj tak, ako pova\u017euje\u0161 za potrebn\u00e9. Nakoniec som sa stal t\u00edmov\u00fdm l\u00eddrom na projekte a v\u0161etko sa ulo\u017eilo na moje plecia.<\/p>\n<p>Prv\u00e9, \u010do som urobil, bolo vyvin\u00fa\u0165 pracovn\u00fd proces od nuly, ktor\u00fd v tom \u010dase zodpovedal m\u00f4jmu poh\u013eadu, a nap\u00edsal som popis pr\u00e1ce pre t\u00edm. Zav\u00e1dza\u0165 ho nebolo jednoduch\u00e9. Ale niekde v priebehu mesiaca sa v\u0161etko usadilo, v\u00fdvoj\u00e1ri a klient si zvykli a v\u0161etko u\u017e prebiehalo pokojne a pohodlne. Aby som t\u00edmu uk\u00e1zal, \u017ee to nie je len \"b\u00farka v poh\u00e1ri\", ale skuto\u010dn\u00e9 rie\u0161enie situ\u00e1cie, vzal som na seba maxim\u00e1lny objem povinnost\u00ed, aby som odstr\u00e1nil nepr\u00edjemn\u00fa rutinu z t\u00edmu. <\/p>\n<p>U\u017e uplynulo p\u00e4\u0165n\u00e1s\u0165 mesiacov a projekt sa vyv\u00edja bez nad\u010dasov, bez \u201epotkan\u00edch pretekov\u201c a r\u00f4znych stresov. Niekto zo starej t\u00edmu nechcel takto pracova\u0165 a odi\u0161iel, niekomu in\u00e9mu sa naopak ve\u013emi zap\u00e1\u010dilo, \u017ee sa objavili transparentn\u00e9 pravidl\u00e1. Ale nakoniec v\u0161etci, kto s\u00fa v t\u00edme, s\u00fa ve\u013emi motivovan\u00ed a \u00faplne poznaj\u00fa obrovsk\u00fd projekt, vr\u00e1tane front-endu a back-endu, vr\u00e1tane k\u00f3dovej b\u00e1zy a celej podnikovej logiky. U\u017e to dospelo do toho, \u017ee nie sme len \u201evesl\u00e1ri\u201c, ale sami vym\u00fd\u0161\u013eame mnoh\u00e9 obchodn\u00e9 procesy a nov\u00e9 funkcie, ktor\u00e9 sa podniku p\u00e1\u010dia.<\/p>\n<p>V\u010faka tak\u00e9muto pr\u00edstupu z na\u0161ej strany sa z\u00e1kazn\u00edk rozhodol objedna\u0165 od na\u0161ej spolo\u010dnosti \u010fal\u0161\u00ed marketplace, \u010do n\u00e1s nem\u00f4\u017ee ako te\u0161i\u0165.<\/p>\n<p>Ke\u010f\u017ee na mojom projekte to funguje, mo\u017eno to pom\u00f4\u017ee aj niekomu in\u00e9mu. Tak\u017ee samotn\u00fd proces, ktor\u00fd n\u00e1m pomohol zachr\u00e1ni\u0165 projekt:<\/p>\n<p>Proces pr\u00e1ce t\u00edmu na projekte \"M\u00f4j ob\u013e\u00faben\u00fd projekt\"<\/p>\n<p>a) Intern\u00fd t\u00edmov\u00fd proces (medzi v\u00fdvoj\u00e1rmi)<\/p>\n<ul>\n<li>V\u0161etky \u00falohy s\u00fa vytvoren\u00e9 v syst\u00e9me Jira<\/li>\n<li>Ka\u017ed\u00e1 \u00faloha by mala by\u0165 maxim\u00e1lne pop\u00edsan\u00e1 a vykon\u00e1va\u0165 striktne jeden \u00fakon<\/li>\n<li>Ak\u00e1ko\u013evek funkcia, ak je dostato\u010dne zlo\u017eit\u00e1, sa rozdel\u00ed na mno\u017estvo drobn\u00fdch \u00faloh<\/li>\n<li>T\u00edm pracuje na funkci\u00e1ch ako na jednej \u00falohe. Najprv rob\u00edme v\u0161etci spolu jednu funkciu, odovzd\u00e1vame ju na testovanie a potom prech\u00e1dzame na \u010fal\u0161iu.<\/li>\n<li>Ka\u017ed\u00e1 \u00faloha je ozna\u010den\u00e1, \u010di patr\u00ed do back-endu alebo front-endu<\/li>\n<li>Existuj\u00fa typy \u00faloh a bugov. Je potrebn\u00e9 ich spr\u00e1vne ozna\u010di\u0165.<\/li>\n<li>Po splnen\u00ed \u00falohy sa preklad\u00e1 do stavu rev\u00edzie k\u00f3du (z\u00e1rove\u0148 sa vytv\u00e1ra pull request na kolegu)<\/li>\n<li>Ten, kto \u00falohu vykon\u00e1val, hne\u010f sleduje svoj \u010das pre t\u00fato \u00falohu<\/li>\n<li>Po kontrole k\u00f3du je PR schv\u00e1len\u00fd a potom ten, kto \u00falohu vykon\u00e1val, ju samostatne zl\u00fa\u010di do hlavnej vetvy, po \u010dom zmen\u00ed jej stav na pripraven\u00fa na nasadenie na dev <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/sk\/server\/\"   title=\"server\" data-wpil-keyword-link=\"linked\">server<\/a>.<\/li>\n<li>V\u0161etky \u00falohy pripraven\u00e9 na nasadenie na dev server nasadzuje t\u00edmov\u00fd lead (jeho zodpovednos\u0165), niekedy aj \u010dlen t\u00edmu, ak je nie\u010do urgentn\u00e9. Po nasaden\u00ed sa v\u0161etky \u00falohy s pr\u00edpravou na nasadenie na dev prekladaj\u00fa do stavu \u2014 pripraven\u00e9 na testovanie na dev<\/li>\n<li>V\u0161etky \u00falohy testuje z\u00e1kazn\u00edk<\/li>\n<li>Ke\u010f z\u00e1kazn\u00edk otestoval \u00falohu na dev, prevedie ju do stavu pripraven\u00e9ho na nasadenie na produkciu<\/li>\n<li>Pre nasadenie na produkciu m\u00e1me samostatn\u00fa vetvu, do ktorej zl\u00fa\u010dime hlavn\u00fa vetvu iba pred nasaden\u00edm<\/li>\n<li>Ak po\u010das testovania z\u00e1kazn\u00edk n\u00e1jde chyby, vr\u00e1ti \u00falohu na \u00fapravy a nastav\u00ed jej stav na vr\u00e1ten\u00e1 na \u00fapravu. T\u00fdmto sp\u00f4sobom oddel\u00edme nov\u00e9 \u00falohy od t\u00fdch, ktor\u00e9 nepre\u0161li testovan\u00edm.<\/li>\n<li>Nakoniec v\u0161etky \u00falohy prech\u00e1dzaj\u00fa cestou od vytvorenia po dokon\u010denie: To Do \u2192 In Development \u2192 Code Review \u2192 Ready deploy to dev \u2192 QA on dev \u2192 (Return to dev) \u2192 Ready deploy to prod \u2192 QA on prod \u2192 Done.<\/li>\n<li>Ka\u017ed\u00fd v\u00fdvoj\u00e1r testuje svoj k\u00f3d samostatne, vr\u00e1tane toho, ako pou\u017e\u00edvate\u013e webu. Nie je povolen\u00e9 zl\u00fa\u010di\u0165 vetvu s hlavnou, pokia\u013e nie je presne zn\u00e1me, \u017ee k\u00f3d funguje.<\/li>\n<li>Ka\u017ed\u00e1 \u00faloha m\u00e1 priority. Priority ur\u010duje bu\u010f z\u00e1kazn\u00edk, alebo t\u00edmov\u00fd l\u00edder.<\/li>\n<li>V\u00fdvoj\u00e1ri sa najprv zaoberaj\u00fa prioritn\u00fdmi \u00falohami.<\/li>\n<li>V\u00fdvoj\u00e1ri m\u00f4\u017eu prira\u010fova\u0165 \u00falohy navz\u00e1jom, ak boli n\u00e1jden\u00e9 r\u00f4zne chyby v syst\u00e9me alebo ak sa jedna \u00faloha sklad\u00e1 z pr\u00e1ce viacer\u00fdch odborn\u00edkov.<\/li>\n<li>V\u0161etky \u00falohy, ktor\u00e9 vytvor\u00ed z\u00e1kazn\u00edk, putuj\u00fa k t\u00edmov\u00e9mu l\u00eddrovi, ktor\u00fd ich vyhodnocuje, a bu\u010f \u017eiada z\u00e1kazn\u00edka o \u00fapravy alebo ich prira\u010fuje niektor\u00e9mu z \u010dlenov t\u00edmu.<\/li>\n<li>V\u0161etky \u00falohy, ktor\u00e9 s\u00fa pripraven\u00e9 na nasadenie na dev alebo prod, putuj\u00fa tie\u017e k t\u00edmov\u00e9mu l\u00eddrovi, ktor\u00fd s\u00e1m rozhoduje, kedy a ako vykona\u0165 nasadenie. Po ka\u017edom nasaden\u00ed mus\u00ed t\u00edmov\u00fd l\u00edder (alebo \u010dlen t\u00edmu) informova\u0165 z\u00e1kazn\u00edka o tom. A tie\u017e zmeni\u0165 stavy pre \u00falohy na pripraven\u00e9 na testovanie na dev\/prod.<\/li>\n<li>Ka\u017ed\u00fd de\u0148 o tej istej hodine (u n\u00e1s je to o 12.00) kon\u00e1me m\u00edting medzi v\u0161etk\u00fdmi \u010dlenmi t\u00edmu.<\/li>\n<li>Ka\u017ed\u00fd na m\u00edtingu pod\u00e1va spr\u00e1vy, vr\u00e1tane t\u00edmov\u00e9ho l\u00eddra, o tom, \u010do robil v\u010dera, \u010do pl\u00e1nuje robi\u0165 dnes. \u010co nefunguje a pre\u010do. Takto je cel\u00e1 t\u00edm informovan\u00fd o tom, kto \u010do rob\u00ed a v akom \u0161t\u00e1diu je projekt. Toto n\u00e1m umo\u017e\u0148uje predpoveda\u0165 a prisp\u00f4sobova\u0165, ak je to potrebn\u00e9, na\u0161e odhady a term\u00edny.<\/li>\n<li>Na m\u00edtingu t\u00edmov\u00fd l\u00edder tie\u017e oznamuje v\u0161etky zmeny v projekte a \u00farove\u0148 aktu\u00e1lnych ch\u00fdb, ktor\u00e9 neboli n\u00e1jden\u00e9 z\u00e1kazn\u00edkom. V\u0161etky chyby sa preberaj\u00fa a prira\u010fuj\u00fa ka\u017ed\u00e9mu \u010dlenovi t\u00edmu na ich vyrie\u0161enie.<\/li>\n<li>Na m\u00edtingu t\u00edmov\u00fd l\u00edder prira\u010fuje ka\u017ed\u00e9mu \u00falohy, pri\u010dom zoh\u013ead\u0148uje aktu\u00e1lne za\u0165a\u017eenie v\u00fdvoj\u00e1rov, \u00farove\u0148 ich profesion\u00e1lneho vzdelania, a taktie\u017e bl\u00edzkos\u0165 danej \u00falohy k tomu, \u010domu sa v\u00fdvoj\u00e1r pr\u00e1ve venuje.<\/li>\n<li>Na stretnut\u00ed t\u00edmov\u00fd l\u00edder formuluje celkov\u00fa strat\u00e9giu architekt\u00fary a obchodnej logiky. Potom to cel\u00e1 t\u00edm diskutuje a rozhodne o potrebn\u00fdch \u00faprav\u00e1ch alebo prijat\u00ed tejto strat\u00e9gie.<\/li>\n<li>Ka\u017ed\u00fd v\u00fdvoj\u00e1r p\u00ed\u0161e k\u00f3d a vytv\u00e1ra algoritmy samostatne v r\u00e1mci jednotnej architekt\u00fary a obchodnej logiky. Ka\u017ed\u00fd m\u00f4\u017ee vyjadri\u0165 svoju predstavu o implement\u00e1cii, ale nikto nie je n\u00faten\u00fd robi\u0165 to len tak alebo inak. Ka\u017ed\u00e9 rozhodnutie je zd\u00f4vodnen\u00e9. Ak existuje lep\u0161ie rie\u0161enie, ale teraz na\u0148 nie je \u010das, vytvor\u00ed sa \u00faloha v Jire na bud\u00face prepracovanie ur\u010ditej \u010dasti k\u00f3du.<\/li>\n<li>Ke\u010f v\u00fdvoj\u00e1r prevezme \u00falohu, prepo\u0161le ju do stavu v\u00fdvoja. Cel\u00e1 komunik\u00e1cia oh\u013eadom objasnenia \u00falohy le\u017e\u00ed na pleciach v\u00fdvoj\u00e1ra. Technick\u00e9 ot\u00e1zky m\u00f4\u017ee kl\u00e1s\u0165 t\u00edmov\u00e9mu l\u00eddrovi alebo kolegom.<\/li>\n<li>Ak v\u00fdvoj\u00e1rovi nie je jasn\u00e1 podstata \u00falohy a z\u00e1kazn\u00edk ju nedok\u00e1\u017ee zrozumite\u013ene vysvetli\u0165, prejde k \u010fal\u0161ej \u00falohe. Aktu\u00e1lnu \u00falohu preber\u00e1 t\u00edmov\u00fd l\u00edder a s\u00e1m ju diskutuje so z\u00e1kazn\u00edkom.<\/li>\n<li>Ka\u017ed\u00fd de\u0148 by mal v\u00fdvoj\u00e1r v chate z\u00e1kazn\u00edka p\u00edsa\u0165 o tom, na ak\u00fdch \u00faloh\u00e1ch pracoval v\u010dera a na ak\u00fdch \u00faloh\u00e1ch bude pracova\u0165 dnes.<\/li>\n<li>Pracovn\u00fd proces prebieha pod\u013ea Scrum metodol\u00f3gie. V\u0161etko je rozdelen\u00e9 do sprintov. Ka\u017ed\u00fd sprin\u0165 trv\u00e1 dva t\u00fd\u017edne.<\/li>\n<li>Sprinty vytv\u00e1ra, nap\u013a\u0148a a uzatv\u00e1ra t\u00edmov\u00fd l\u00edder.<\/li>\n<li>Ak m\u00e1 projekt pr\u00edsne term\u00edny, sna\u017e\u00edme sa odhadn\u00fa\u0165 v\u0161etky \u00falohy. A zozbierame ich do sprintu. Ak sa z\u00e1kazn\u00edk pok\u00fasi prida\u0165 \u010fal\u0161ie \u00falohy do sprintu, stanov\u00edme priority a niektor\u00e9 in\u00e9 \u00falohy presunieme na \u010fal\u0161\u00ed sprin\u0165.<\/li>\n<\/ul>\n<p>\nb) Proces pr\u00e1ce so z\u00e1kazn\u00edkom<\/p>\n<ul>\n<li>Ka\u017ed\u00fd v\u00fdvoj\u00e1r m\u00f4\u017ee a mal by komunikova\u0165 so z\u00e1kazn\u00edkom.<\/li>\n<li>Nem\u00f4\u017eeme umo\u017eni\u0165 z\u00e1kazn\u00edkovi vnucova\u0165 svoje pravidl\u00e1. Je potrebn\u00e9 v zdvorilej a priate\u013eskej forme da\u0165 z\u00e1kazn\u00edkovi jasne najavo, \u017ee sme odborn\u00edci vo svojom obore, a len my by sme mali organizova\u0165 pracovn\u00e9 procesy a zap\u00e1ja\u0165 do nich z\u00e1kazn\u00edka.<\/li>\n<li>Ide\u00e1lne je pred za\u010dat\u00edm implement\u00e1cie ak\u00e9hoko\u013evek funk\u010dn\u00e9ho prvku vytvori\u0165 blokov\u00fa sch\u00e9mu cel\u00e9ho logick\u00e9ho procesu pre funkciu (workflow). A posla\u0165 ju na schv\u00e1lenie z\u00e1kazn\u00edkovi. To sa t\u00fdka iba zlo\u017eit\u00fdch a \u0165a\u017eko zrozumite\u013en\u00fdch funkci\u00ed, ako napr\u00edklad platobn\u00fd syst\u00e9m, syst\u00e9m upozornen\u00ed at\u010f. To umo\u017en\u00ed presnej\u0161ie pochopenie, \u010do z\u00e1kazn\u00edk skuto\u010dne potrebuje, uchova\u0165 dokument\u00e1ciu k funkcii a tie\u017e ochr\u00e1ni\u0165 seba pred t\u00fdm, \u017ee z\u00e1kazn\u00edk v bud\u00facnosti povie, \u017ee sme urobili nie\u010do in\u00e9, ako si prial.<\/li>\n<li>V\u0161etky diagramy\/blokov\u00e9 sch\u00e9my\/logiky at\u010f. uchov\u00e1vame v Confluence\/Jira, kde \u017eiadame z\u00e1kazn\u00edka, aby v koment\u00e1roch potvrdil spr\u00e1vnos\u0165 bud\u00facej implement\u00e1cie.<\/li>\n<li>Sna\u017e\u00edme sa neza\u0165a\u017eova\u0165 z\u00e1kazn\u00edka technick\u00fdmi podrobnos\u0165ami. Ak potrebujeme pochopi\u0165, ako si z\u00e1kazn\u00edk \u017eel\u00e1, nakresl\u00edme primit\u00edvne algoritmy vo forme blokovej sch\u00e9my, ktor\u00e9 z\u00e1kazn\u00edk m\u00f4\u017ee pochopi\u0165 a s\u00e1m v\u0161etko opravi\u0165\/doplni\u0165.<\/li>\n<li>Ak z\u00e1kazn\u00edk n\u00e1jde v projekte chybu, ve\u013emi podrobne ho \u017eiadame, aby ju op\u00edsal v Jira. Ak\u00e9 okolnosti sa udiali, kedy, ak\u00fa postupnos\u0165 akci\u00ed vykon\u00e1val z\u00e1kazn\u00edk pri testovan\u00ed. \u017diadame ho, aby pripojil screenshoty.<\/li>\n<li>Sna\u017e\u00edme sa ka\u017ed\u00fd de\u0148, maxim\u00e1lne ka\u017ed\u00fd druh\u00fd de\u0148, robi\u0165 nasadenie na dev server. Z\u00e1kazn\u00edk potom za\u010dne testova\u0165 funk\u010dnos\u0165 a projekt nestoja. To tie\u017e sl\u00fa\u017ei ako ukazovate\u013e pre z\u00e1kazn\u00edka, \u017ee projekt je v plnej v\u00fdvoji a nikto mu nepredklad\u00e1 rozpr\u00e1vky.<\/li>\n<li>Ve\u013eakr\u00e1t sa st\u00e1va, \u017ee z\u00e1kazn\u00edk \u00faplne nerozumie, \u010do vlastne potrebuje. Preto\u017ee zaklad\u00e1 nov\u00fd podnik s e\u0161te nepreveren\u00fdmi procesmi. Preto sa ve\u013emi \u010dasto st\u00e1va situ\u00e1cia, \u017ee vyhadzujeme cel\u00e9 kusy k\u00f3du a prer\u00e1bame logiku aplik\u00e1cie. Z toho vypl\u00fdva, \u017ee nie je nutn\u00e9 pokr\u00fdva\u0165 v\u0161etko testami. Je zmyslupln\u00e9 pokry\u0165 testami iba kriticky d\u00f4le\u017eit\u00fa funk\u010dnos\u0165 a to s v\u00fdhradami.<\/li>\n<li>S\u00fa situ\u00e1cie, ke\u010f t\u00edm zist\u00ed, \u017ee sa nezmest\u00edme do term\u00ednov. Vtedy vykon\u00e1me r\u00fdchly audit \u00faloh a ihne\u010f informujeme z\u00e1kazn\u00edka. Ako rie\u0161enie situ\u00e1cie navrhujeme uv\u00e1dzan\u00ed do prev\u00e1dzky d\u00f4le\u017eitej a kritickej funk\u010dnosti v term\u00edne, a ostatn\u00e9 necha\u0165 na post-release.<\/li>\n<li>Ak objedn\u00e1vate\u013e za\u010dne vym\u00fd\u0161\u013ea\u0165 r\u00f4zne \u00falohy z hlavy, za\u010dne fantaz\u00edrova\u0165 a vysvet\u013eova\u0165 prstami, tak ho \u017eiadame, aby n\u00e1m poskytol n\u00e1vrh str\u00e1nky a tok so logikou, ktor\u00e1 by mala \u00faplne pop\u00edsa\u0165 spr\u00e1vanie cel\u00e9ho n\u00e1vrhu a jeho prvkov.<\/li>\n<li>Predt\u00fdm ako preberieme ak\u00fako\u013evek \u00falohu, mus\u00edme sa uisti\u0165, \u017ee t\u00e1to funkcia bola zahrnut\u00e1 v podmienkach na\u0161ej zmluvy. Ak je to nov\u00e1 funkcia, ktor\u00e1 presahuje na\u0161e p\u00f4vodn\u00e9 dohody, mus\u00edme ju nevyhnutne odhadn\u00fa\u0165 ((priemern\u00fd \u010das vykonania + 30%) x 2) a uvies\u0165 objedn\u00e1vate\u013eovi, \u017ee na \u0148u potrebujeme to\u013eko \u010dasu, plus term\u00edn sa posunie o \u010das odhadu vyn\u00e1soben\u00fd dvoma. Ak \u00falohu urob\u00edme r\u00fdchlej\u0161ie \u2013 skvele, v\u0161etci z toho len z\u00edskaj\u00fa. Ak nie, sme kryt\u00ed.<\/li>\n<\/ul>\n<p>\nb) \u010co neprij\u00edmame v t\u00edme:<\/p>\n<ul>\n<li>Nezodpovednos\u0165, nes\u00fastredenie, zab\u00fadanie<\/li>\n<li>\u201eKrmienie ra\u0148ajkami\u201c. Ak nem\u00f4\u017ee\u0161 splni\u0165 \u00falohu, nevie\u0161 ako, o tom je potrebn\u00e9 okam\u017eite informova\u0165 t\u00edmov\u00e9ho l\u00eddra, a nie \u010daka\u0165 do poslednej chv\u00edle.<\/li>\n<li>Chv\u00e1stanie a chv\u00e1lenie od \u010dloveka, ktor\u00fd e\u0161te nepreuk\u00e1zal svoje schopnosti a profesionalitu. Ak to preuk\u00e1zal, bere sa to v r\u00e1mci slu\u0161nosti \ud83d\ude42<\/li>\n<li>Podvod v ak\u00fdchko\u013evek jeho prejavoch. Ak \u00faloha nie je splnen\u00e1, nie je potrebn\u00e9 meni\u0165 jej stav na splnen\u00fd a p\u00edsa\u0165 v chate klientovi, \u017ee je pripraven\u00e1. Pokazil sa po\u010d\u00edta\u010d, syst\u00e9m spadol, pes roztrhal notebook \u2013 toto je neprijate\u013en\u00e9. Ak sa stane skuto\u010dn\u00e1 neo\u010dak\u00e1van\u00e1 udalos\u0165, t\u00edmov\u00fd l\u00edder by mal by\u0165 okam\u017eite informovan\u00fd.<\/li>\n<li>Ke\u010f je \u0161pecialista st\u00e1le offline a je \u0165a\u017ek\u00e9 sa k nemu dosta\u0165 v pracovnom \u010dase.<\/li>\n<li>Toxickos\u0165 v t\u00edme nie je prijate\u013en\u00e1! Ak sa niekto s nie\u010d\u00edm nes\u00fahlas\u00ed, v\u0161etci sa spolo\u010dne zhroma\u017edia na meetingu a to prediskutuj\u00fa a rozhodn\u00fa.<\/li>\n<\/ul>\n<p>A e\u0161te nieko\u013eko ot\u00e1zok\/tez\u00ed, ktor\u00e9 ob\u010das kladiem svojmu objedn\u00e1vate\u013eovi, aby odstr\u00e1nil v\u0161etky nedorozumenia:<\/p>\n<ol>\n<li>Ak\u00e9 s\u00fa va\u0161e krit\u00e9ri\u00e1 kvality?<\/li>\n<li>Ako ur\u010dujete, \u010di s\u00fa v projekte probl\u00e9my, alebo nie?<\/li>\n<li>Poru\u0161ovan\u00edm v\u0161etk\u00fdch na\u0161ich odpor\u00fa\u010dan\u00ed a r\u00e1d na zmenu\/zlep\u0161enie syst\u00e9mu nesiete v\u0161etky rizik\u00e1 iba vy.<\/li>\n<li>Ak\u00e9ko\u013evek majoritn\u00e9 zmeny projektu (napr\u00edklad ak\u00e9ko\u013evek extra toky) m\u00f4\u017eu vies\u0165 k mo\u017en\u00e9mu vzniku ch\u00fdb (ktor\u00e9 budeme, samozrejme, opravova\u0165).<\/li>\n<li>Nemo\u017eno v priebehu p\u00e1r min\u00fat pochopi\u0165, ak\u00fd probl\u00e9m sa na projekte vyskytol, a u\u017e v\u00f4bec ho hne\u010f opravi\u0165.<\/li>\n<li>Pracujeme pod\u013ea konkr\u00e9tneho produktov\u00e9ho toku (\u00dalohy v Jira \u2014 V\u00fdvoj \u2014 Testovanie \u2014 Nasadenie). To znamen\u00e1, \u017ee nem\u00f4\u017eeme reagova\u0165 na cel\u00fd pr\u00fad \u017eiadost\u00ed a s\u0165a\u017enost\u00ed v chate.<\/li>\n<li>Program\u00e1tori s\u00fa program\u00e1tori a nie profesion\u00e1lni testeri, a nem\u00f4\u017eu zabezpe\u010di\u0165 primeran\u00fa kvalitu testovania projektu.<\/li>\n<li>Zodpovednos\u0165 za kone\u010dn\u00e9 testovanie a prijatie \u00faloh na produkcii le\u017e\u00ed plne na v\u00e1s.<\/li>\n<li>Ak sme u\u017e vzali \u00falohu do pr\u00e1ce, nem\u00f4\u017eeme sa ihne\u010f prepn\u00fa\u0165 na in\u00e9, k\u00fdm nedokon\u010d\u00edme aktu\u00e1lnu (inak to vedie k e\u0161te v\u00e4\u010d\u0161\u00edm chyb\u00e1m a predl\u017euje \u010das v\u00fdvoja).<\/li>\n<li>\u013dud\u00ed v t\u00edme je menej (z d\u00f4vodu dovoleniek alebo chor\u00f4b), a pr\u00e1ce je viac, a fyzicky nest\u00edhame reagova\u0165 na v\u0161etko, \u010do si prajete.<\/li>\n<li>\u017diados\u0165 z va\u0161ej strany o nasadenie na produkciu bez otestovan\u00fdch \u00faloh na dev sa t\u00fdka iba va\u0161ich riz\u00edk a nie v\u00fdvoj\u00e1rov.<\/li>\n<li>Ke\u010f stanov\u00edte nejasn\u00e9 \u00falohy bez spr\u00e1vneho toku, bez dizajnov\u00fdch makiet, vy\u017eaduje to od n\u00e1s ove\u013ea v\u00e4\u010d\u0161ie \u00fasilie a dlh\u0161ie lehoty realiz\u00e1cie, preto\u017ee namiesto v\u00e1s mus\u00edme vykon\u00e1va\u0165 dodato\u010dn\u00fa pr\u00e1cu.<\/li>\n<li>Ak\u00e9ko\u013evek \u00falohy t\u00fdkaj\u00face sa ch\u00fdb bez podrobn\u00e9ho popisu ich vzniku a sn\u00edmok obrazovky n\u00e1m ned\u00e1vaj\u00fa mo\u017enos\u0165 pochopi\u0165, \u010do sa pokazilo a ako simulova\u0165 t\u00fato chybu.<\/li>\n<li>Projekt si vy\u017eaduje neust\u00e1lu pr\u00e1cu a zlep\u0161ovanie na zv\u00fd\u0161enie v\u00fdkonnosti a bezpe\u010dnosti. Preto t\u00edm venuje \u010das t\u00fdmto vylep\u0161eniam.<\/li>\n<li>Z d\u00f4vodu toho, \u017ee m\u00e1me prepracovan\u00e9 hodiny (urgentn\u00e9 opravy), mus\u00edme ich kompenzova\u0165 v in\u00e9 dni.<\/li>\n<\/ol>\n<p>\nZvy\u010dajne klient okam\u017eite ch\u00e1pe, \u017ee v\u00fdvoj softv\u00e9ru nie je tak jednoduch\u00fd, a jedn\u00e9ho priania rozhodne nesta\u010d\u00ed.<\/p>\n<p>Celkovo je to v\u0161etko. Za sc\u00e9nou zost\u00e1va mno\u017estvo rokovan\u00ed a po\u010diato\u010dn\u00e9 ladenie v\u0161etk\u00fdch procesov, ale nakoniec sa v\u0161etko zlep\u0161ilo. M\u00f4\u017eem poveda\u0165, \u017ee tento proces sa pre n\u00e1s stal akousi \u201estriebornou gu\u013eou\u201c. Nov\u00ed \u013eudia, ktor\u00ed pri\u0161li do projektu, sa mohli u\u017e od prv\u00e9ho d\u0148a zapoji\u0165 do pr\u00e1ce, preto\u017ee v\u0161etky procesy s\u00fa pop\u00edsan\u00e9 a dokument\u00e1cia a architekt\u00fara vo forme diagramov okam\u017eite poskytovali predstavu o tom, \u010d\u00edm sa tu v\u0161etci zaober\u00e1me. <\/p>\n<p><i>P. S. Chcem objasni\u0165, \u017ee na na\u0161ej strane nie je projektov\u00fd mana\u017e\u00e9r. Ten je na strane z\u00e1kazn\u00edka. Nie je technick\u00fd. Projekt je eur\u00f3psky. V\u0161etka komunik\u00e1cia je len v angli\u010dtine.<\/i><\/p>\n<p>V\u0161etk\u00fdm prajem ve\u013ea \u0161\u0165astia na projektoch. Nenechajte sa vyhorie\u0165 a sna\u017ete sa zlep\u0161ova\u0165 svoje procesy.<\/p>\n<p>Zdrojov\u00fd k\u00f3d je v mojom <noindex><a rel=\"nofollow\" href=\"https:\/\/cleverman.org\/post\/organizaciya-rabochego-processa-v-komande-na-it-proekte\">blogu<\/a><\/noindex>.<br \/>\n<br \/>Zdroj: <a content=\"nofollow\" rel=\"nofollow\" href=\"https:\/\/habr.com\/ru\/post\/524460\/\">habr.com<\/a> <\/p>","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"excerpt":{"rendered":"<p>\u041f\u0440\u0438\u0432\u0435\u0442 \u0434\u0440\u0443\u0437\u044c\u044f. \u0421\u043f\u043b\u043e\u0448\u044c \u0438 \u0440\u044f\u0434\u043e\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432 \u0430\u0443\u0442\u0441\u043e\u0440\u0441\u0435, \u044f \u0432\u0438\u0436\u0443 \u043e\u0434\u043d\u0443 \u0438 \u0442\u0443 \u0436\u0435 \u043a\u0430\u0440\u0442\u0438\u043d\u0443. \u041e\u0442\u0441\u0443\u0442\u0441\u0442\u0432\u0438\u0435 \u0447\u0435\u0442\u043a\u043e\u0433\u043e \u0440\u0430\u0431\u043e\u0447\u0435\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0432 \u043a\u043e\u043c\u0430\u043d\u0434\u0430\u0445 \u043d\u0430 \u0440\u0430\u0437\u043b\u0438\u0447\u043d\u044b\u0445 \u043f\u0440\u043e\u0435\u043a\u0442\u0430\u0445. \u0421\u0430\u043c\u043e\u0435 \u0433\u043b\u0430\u0432\u043d\u043e\u0435 \u2014 \u044d\u0442\u043e \u0442\u043e, \u0447\u0442\u043e \u043f\u0440\u043e\u0433\u0440\u0430\u043c\u043c\u0438\u0441\u0442\u044b \u043d\u0435 \u043f\u043e\u043d\u0438\u043c\u0430\u044e\u0442, \u043a\u0430\u043a \u043d\u0443\u0436\u043d\u043e \u043a\u043e\u043c\u043c\u0443\u043d\u0438\u0446\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0441 \u0437\u0430\u043a\u0430\u0437\u0447\u0438\u043a\u043e\u043c \u0438 \u0434\u0440\u0443\u0433 \u0441 \u0434\u0440\u0443\u0433\u043e\u043c. \u041a\u0430\u043a \u043f\u043e\u0441\u0442\u0440\u043e\u0438\u0442\u044c \u043d\u0435\u043f\u0440\u0435\u0440\u044b\u0432\u043d\u044b\u0439 \u043f\u0440\u043e\u0446\u0435\u0441\u0441 \u0440\u0430\u0437\u0440\u0430\u0431\u043e\u0442\u043a\u0438 \u043a\u0430\u0447\u0435\u0441\u0442\u0432\u0435\u043d\u043d\u043e\u0433\u043e \u043f\u0440\u043e\u0434\u0443\u043a\u0442\u0430. \u041a\u0430\u043a \u0441\u043f\u043b\u0430\u043d\u0438\u0440\u043e\u0432\u0430\u0442\u044c \u0441\u0432\u043e\u0439 \u0440\u0430\u0431\u043e\u0447\u0438\u0439 \u0434\u0435\u043d\u044c \u0438 [&hellip;]<\/p>\n","protected":false,"gt_translate_keys":[{"key":"rendered","format":"html"}]},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[688],"tags":[],"class_list":["post-97853","post","type-post","status-publish","format-standard","hentry","category-administrirovanie"],"aioseo_notices":[],"aioseo_head":"\n\t\t<!-- All in One SEO 5.0.3 - aioseo.com -->\n\t<meta name=\"description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442 \u0434\u0440\u0443\u0437\u044c\u044f. \u0421\u043f\u043b\u043e\u0448\u044c \u0438 \u0440\u044f\u0434\u043e\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432 \u0430\u0443\u0442\u0441\u043e\u0440\u0441\u0435, \u044f \u0432\u0438\u0436\u0443 \u043e\u0434\u043d\u0443 \u0438 \u0442\u0443 \u0436\u0435 \u043a\u0430\u0440\u0442\u0438\u043d\u0443.\" \/>\n\t<meta name=\"robots\" content=\"max-image-preview:large\" \/>\n\t<meta name=\"author\" content=\"Yuri Gagarin\"\/>\n\t<link rel=\"canonical\" href=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte\" \/>\n\t\t<meta name=\"generator\" content=\"All in One SEO (AIOSEO) 5.0.3\" \/>\n\t\t<meta property=\"og:locale\" content=\"sk_SK\" \/>\n\t\t<meta property=\"og:site_name\" content=\"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b\" \/>\n\t\t<meta property=\"og:type\" content=\"article\" \/>\n\t\t<meta property=\"og:title\" content=\"\ud83e\udd47\u041e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f \u0440\u0430\u0431\u043e\u0447\u0435\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0432 \u043a\u043e\u043c\u0430\u043d\u0434\u0435 \u043d\u0430 IT-\u043f\u0440\u043e\u0435\u043a\u0442\u0435 | ProHoster\" \/>\n\t\t<meta property=\"og:description\" content=\"\u041f\u0440\u0438\u0432\u0435\u0442 \u0434\u0440\u0443\u0437\u044c\u044f. \u0421\u043f\u043b\u043e\u0448\u044c \u0438 \u0440\u044f\u0434\u043e\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432 \u0430\u0443\u0442\u0441\u043e\u0440\u0441\u0435, \u044f \u0432\u0438\u0436\u0443 \u043e\u0434\u043d\u0443 \u0438 \u0442\u0443 \u0436\u0435 \u043a\u0430\u0440\u0442\u0438\u043d\u0443.\" \/>\n\t\t<meta property=\"og:url\" content=\"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte\" \/>\n\t\t<meta property=\"og:image\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:secure_url\" content=\"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg\" \/>\n\t\t<meta property=\"og:image:width\" content=\"350\" \/>\n\t\t<meta property=\"og:image:height\" content=\"350\" \/>\n\t\t<meta property=\"article:published_time\" content=\"2020-10-22T12:42:44+00:00\" \/>\n\t\t<meta property=\"article:modified_time\" content=\"2020-11-17T22:58:50+00:00\" \/>\n\t\t<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<meta property=\"article:author\" content=\"https:\/\/www.facebook.com\/prohoster\" \/>\n\t\t<!-- All in One SEO -->\n\n","aioseo_head_json":{"title":"\ud83e\udd47Organiz\u00e1cia pracovn\u00e9ho procesu v t\u00edme na IT projekte | ProHoster","description":"Ahojte priatelia. \u010casto, najm\u00e4 v outsourcingu, vid\u00edm st\u00e1le t\u00fa ist\u00fa situ\u00e1ciu.","canonical_url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"sk_SK","og:site_name":"ProHoster | \u041a\u0443\u043f\u0438\u0442\u044c \u043d\u0430\u0434\u0435\u0436\u043d\u044b\u0439 \u0445\u043e\u0441\u0442\u0438\u043d\u0433 \u0434\u043b\u044f \u0441\u0430\u0439\u0442\u043e\u0432 \u0441 \u0437\u0430\u0449\u0438\u0442\u043e\u0439 \u043e\u0442 DDoS, VPS VDS \u0441\u0435\u0440\u0432\u0435\u0440\u044b","og:type":"article","og:title":"\ud83e\udd47\u041e\u0440\u0433\u0430\u043d\u0438\u0437\u0430\u0446\u0438\u044f \u0440\u0430\u0431\u043e\u0447\u0435\u0433\u043e \u043f\u0440\u043e\u0446\u0435\u0441\u0441\u0430 \u0432 \u043a\u043e\u043c\u0430\u043d\u0434\u0435 \u043d\u0430 IT-\u043f\u0440\u043e\u0435\u043a\u0442\u0435 | ProHoster","og:description":"\u041f\u0440\u0438\u0432\u0435\u0442 \u0434\u0440\u0443\u0437\u044c\u044f. \u0421\u043f\u043b\u043e\u0448\u044c \u0438 \u0440\u044f\u0434\u043e\u043c, \u043e\u0441\u043e\u0431\u0435\u043d\u043d\u043e \u0432 \u0430\u0443\u0442\u0441\u043e\u0440\u0441\u0435, \u044f \u0432\u0438\u0436\u0443 \u043e\u0434\u043d\u0443 \u0438 \u0442\u0443 \u0436\u0435 \u043a\u0430\u0440\u0442\u0438\u043d\u0443.","og:url":"https:\/\/prohoster.info\/sk\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte","og:image":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:secure_url":"https:\/\/prohoster.info\/wp-content\/uploads\/2021\/11\/logo-350.jpg","og:image:width":350,"og:image:height":350,"article:published_time":"2020-10-22T12:42:44+00:00","article:modified_time":"2020-11-17T22:58:50+00:00","article:publisher":"https:\/\/www.facebook.com\/prohoster","article:author":"https:\/\/www.facebook.com\/prohoster"},"aioseo_meta_data":{"post_id":"97853","title":null,"description":null,"keywords":null,"keyphrases":null,"primary_term":null,"canonical_url":null,"og_title":null,"og_description":null,"og_object_type":"default","og_image_type":"default","og_image_url":null,"og_image_width":null,"og_image_height":null,"og_image_custom_url":null,"og_image_custom_fields":null,"og_video":null,"og_custom_url":null,"og_article_section":null,"og_article_tags":null,"twitter_use_og":false,"twitter_card":"default","twitter_image_type":"default","twitter_image_url":null,"twitter_image_custom_url":null,"twitter_image_custom_fields":null,"twitter_title":null,"twitter_description":null,"schema":{"blockGraphs":[],"customGraphs":[],"default":{"data":{"Article":[],"Course":[],"Dataset":[],"FAQPage":[],"Movie":[],"Person":[],"Product":[],"ProductReview":[],"Car":[],"Recipe":[],"Service":[],"SoftwareApplication":[],"WebPage":[]},"graphName":"","isEnabled":true},"graphs":[]},"schema_type":null,"schema_type_options":null,"pillar_content":false,"robots_default":true,"robots_noindex":false,"robots_noarchive":false,"robots_nosnippet":false,"robots_nofollow":false,"robots_noimageindex":false,"robots_noodp":false,"robots_notranslate":false,"robots_max_snippet":null,"robots_max_videopreview":null,"robots_max_imagepreview":"large","priority":null,"frequency":null,"local_seo":null,"seo_analyzer_scan_date":null,"breadcrumb_settings":null,"limit_modified_date":false,"reviewed_by":null,"ai":null,"created":"2021-02-28 10:11:34","updated":"2022-10-03 07:12:20","focus_keyword":null,"additional_keywords":null,"truseo_locale":null},"gt_translate_keys":[{"key":"link","format":"url"}],"_links":{"self":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/97853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/comments?post=97853"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/97853\/revisions"}],"predecessor-version":[{"id":172897,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/posts\/97853\/revisions\/172897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/media?parent=97853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/categories?post=97853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/sk\/wp-json\/wp\/v2\/tags?post=97853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}