{"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\/cs\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte","title":{"rendered":"Organizace pracovn\u00edho procesu v t\u00fdmu na IT projektu.","gt_translate_keys":[{"key":"rendered","format":"text"}]},"content":{"rendered":"<p>Ahoj p\u0159\u00e1tel\u00e9. \u010casto, zejm\u00e9na v outsourcingu, vid\u00edm stejn\u00fd obraz. Chyb\u011bj\u00edc\u00ed jasn\u00fd pracovn\u00ed proces v t\u00fdmech na r\u016fzn\u00fdch projektech.<\/p>\n<p>Nejd\u016fle\u017eit\u011bj\u0161\u00ed je, \u017ee program\u00e1to\u0159i nerozum\u00ed, jak komunikovat se z\u00e1kazn\u00edkem a mezi sebou. Jak vybudovat nep\u0159etr\u017eit\u00fd proces v\u00fdvoje kvalitn\u00edho produktu. Jak si napl\u00e1novat sv\u016fj pracovn\u00ed den a sprinty.<\/p>\n<p>A to v\u0161echno nakonec vy\u00fastit ve zpo\u017ed\u011bn\u00e9 deadliny, p\u0159es\u010dasy, neust\u00e1l\u00e9 h\u00e1dky o to, kdo je za co zodpov\u011bdn\u00fd, a nespokojenost z\u00e1kazn\u00edk\u016f \u2014 jak\u00fdm sm\u011brem se v\u0161e ub\u00edr\u00e1. Pom\u011brn\u011b \u010dasto to vede ke st\u0159\u00edd\u00e1n\u00ed program\u00e1tor\u016f, nebo i cel\u00fdch t\u00fdm\u016f. Ztr\u00e1t\u011b z\u00e1kazn\u00edka, zhor\u0161en\u00ed pov\u011bsti a tak d\u00e1le.<\/p>\n<p>Kdysi jsem se dostal na takov\u00fd projekt, kde byly v\u0161echny tyto probl\u00e9my. <br \/>\n<noindex><a rel=\"nofollow\" name=\"habracut\"><\/a><\/noindex><br \/>\nNikdo necht\u011bl p\u0159evz\u00edt odpov\u011bdnost za projekt (velk\u00fd servisn\u00ed marketplace), fluktuace byla stra\u0161n\u00e1, z\u00e1kazn\u00edk neust\u00e1le zu\u0159il. \u0158editel mi jednou p\u0159i\u0161el a \u0159ekl, \u017ee m\u00e1\u0161 pot\u0159ebn\u00e9 zku\u0161enosti, tak tady m\u00e1\u0161 projekt. Kdy\u017e to pokaz\u00ed\u0161, projekt zav\u0159eme a v\u0161echny vyhod\u00edme. Pokud to vyjde, bude to skv\u011bl\u00e9, pak ho \u0159\u00edd\u00ed\u0161 a rozv\u00edj\u00ed\u0161, jak uzn\u00e1\u0161 za vhodn\u00e9. Nakonec jsem se stal vedouc\u00edm t\u00fdmu na projektu a v\u0161echno le\u017eelo na m\u00fdch bedrech.<\/p>\n<p>Prvn\u00ed, co jsem ud\u011blal, bylo, \u017ee jsem vyvinul pracovn\u00ed proces od nuly, kter\u00fd v t\u00e9 dob\u011b odpov\u00eddal m\u00e9mu vid\u011bn\u00ed, a napsal jsem popis pr\u00e1ce pro t\u00fdm. Implementace nebyla snadn\u00e1. Ale b\u011bhem asi m\u011bs\u00edce se v\u0161echno usadilo, v\u00fdvoj\u00e1\u0159i a klient si zvykli a v\u0161echno za\u010dalo plynout klidn\u011b a pohodln\u011b. Abych uk\u00e1zal t\u00fdmu, \u017ee to nen\u00ed jen \"bou\u0159e ve sklenici vody\", ale skute\u010dn\u00e9 v\u00fdchodisko ze situace, vzal jsem na sebe maxim\u00e1ln\u00ed objem povinnost\u00ed a uvolnil t\u00fdm od nep\u0159\u00edjemn\u00e9 rutiny. <\/p>\n<p>U\u017e ub\u011bhlo jeden a p\u016fl roku a projekt se vyv\u00edj\u00ed bez p\u0159es\u010das\u016f, bez \"krys\u00edch z\u00e1vod\u016f\" a r\u016fzn\u00fdch stres\u016f. N\u011bkdo ve star\u00e9m t\u00fdmu necht\u011bl takto pracovat a ode\u0161el, n\u011bkdo naopak byl r\u00e1d, \u017ee se objevila jasn\u00e1 pravidla. Ale nakonec v\u0161ichni, kdo jsou v t\u00fdmu, jsou velmi motivov\u00e1ni a znaj\u00ed obrovsk\u00fd projekt dokonale, zahrnuj\u00edc\u00ed jak frontend, tak backend. V\u010detn\u011b k\u00f3dov\u00e9 z\u00e1kladny a cel\u00e9 obchodn\u00ed logiky. U\u017e jsme dosp\u011bli a\u017e k tomu, \u017ee nejsme jen \"vesla\u0159i\", ale sami vym\u00fd\u0161l\u00edme mnoh\u00e9 obchodn\u00ed procesy a nov\u00e9 funkce, kter\u00e9 se byznysu l\u00edb\u00ed.<\/p>\n<p>D\u00edky na\u0161emu p\u0159\u00edstupu se z\u00e1kazn\u00edk rozhodl objednat u na\u0161\u00ed spole\u010dnosti dal\u0161\u00ed tr\u017ei\u0161t\u011b, co\u017e n\u00e1s velmi pot\u011b\u0161ilo.<\/p>\n<p>Proto\u017ee to u m\u00e9ho projektu funguje, m\u016f\u017ee to b\u00fdt u\u017eite\u010dn\u00e9 i n\u011bkomu jin\u00e9mu. Tak\u017ee tady je proces, kter\u00fd n\u00e1m pomohl zachr\u00e1nit projekt:<\/p>\n<p>Pracovn\u00ed proces t\u00fdmu na projektu \u201eM\u016fj obl\u00edben\u00fd projekt\u201c<\/p>\n<p>a) Intern\u00ed t\u00fdmov\u00fd proces (mezi v\u00fdvoj\u00e1\u0159i)<\/p>\n<ul>\n<li>V\u0161echny \u00fakoly jsou vytv\u00e1\u0159eny v syst\u00e9mu Jira<\/li>\n<li>Ka\u017ed\u00fd \u00fakol by m\u011bl b\u00fdt co nejl\u00e9pe pops\u00e1n a m\u011bl by vykon\u00e1vat striktn\u011b jednu \u010dinnost<\/li>\n<li>Ka\u017ed\u00e1 funkce, pokud je dostate\u010dn\u011b slo\u017eit\u00e1, se rozd\u011bluje na mnoho mal\u00fdch \u00fakol\u016f<\/li>\n<li>T\u00fdm pracuje na funkc\u00edch jako na jednom \u00fakolu. Nejprve spole\u010dn\u011b vytvo\u0159\u00edme jednu funkci, p\u0159ed\u00e1me ji k testov\u00e1n\u00ed, a pak se zam\u011b\u0159\u00edme na dal\u0161\u00ed.<\/li>\n<li>Ka\u017ed\u00fd \u00fakol je ozna\u010den, zda pat\u0159\u00ed k backendu nebo frontendu<\/li>\n<li>Existuj\u00ed typy \u00fakol\u016f a chyb. Je nutn\u00e9 je spr\u00e1vn\u011b uv\u00e1d\u011bt.<\/li>\n<li>Po dokon\u010den\u00ed \u00fakolu je p\u0159eveden do stavu recenze k\u00f3du (p\u0159itom se vytv\u00e1\u0159\u00ed pull request pro kolegu)<\/li>\n<li>Osoba, kter\u00e1 \u00fakol vykon\u00e1vala, hned sleduje sv\u016fj \u010das pro tento \u00fakol<\/li>\n<li>Po kontrole k\u00f3du je PR schv\u00e1len a pak ten, kdo \u00fakol vykon\u00e1val, s\u00e1m provede jeho slou\u010den\u00ed do hlavn\u00ed v\u011btve, a pot\u00e9 zm\u011bn\u00ed jeho stav na p\u0159ipraveno k nasazen\u00ed na dev <a class=\"wpil_keyword_link\" href=\"https:\/\/prohoster.info\/cs\/server\/\"   title=\"server\" data-wpil-keyword-link=\"linked\">server<\/a>.<\/li>\n<li>V\u0161echny \u00fakoly p\u0159ipraven\u00e9 k nasazen\u00ed na dev server jsou nasazov\u00e1ny t\u00fdmov\u00fdm l\u00eddrem (jeho odpov\u011bdnost), ob\u010das \u010dlenem t\u00fdmu, pokud je n\u011bco nal\u00e9hav\u00e9ho. Po nasazen\u00ed jsou v\u0161echny \u00fakoly s p\u0159ipraveno k nasazen\u00ed na dev p\u0159evedeny do stavu \u2013 p\u0159ipraveno k testov\u00e1n\u00ed na devu<\/li>\n<li>V\u0161echny \u00fakoly testuje z\u00e1kazn\u00edk<\/li>\n<li>Kdy\u017e z\u00e1kazn\u00edk otestuje \u00fakol na devu, p\u0159evede jej do stavu p\u0159ipraveno k nasazen\u00ed na produkci<\/li>\n<li>Pro nasazen\u00ed na produkci m\u00e1me odd\u011blenou v\u011btev, do kter\u00e9 slu\u010dujeme hlavn\u00ed v\u011btev pouze p\u0159ed nasazen\u00edm<\/li>\n<li>Pokud z\u00e1kazn\u00edk b\u011bhem testov\u00e1n\u00ed najde chyby, vr\u00e1t\u00ed \u00fakol k dopracov\u00e1n\u00ed, p\u0159i\u010dem\u017e mu nastav\u00ed stav vr\u00e1ceno k dopracov\u00e1n\u00ed. T\u00edm odd\u011blujeme nov\u00e9 \u00fakoly od t\u011bch, kter\u00e9 nepro\u0161ly testov\u00e1n\u00edm<\/li>\n<li>Nakonec v\u0161echny \u00fakoly projdou cestu od vytvo\u0159en\u00ed po dokon\u010den\u00ed: 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\u00e1\u0159 testuje sv\u016fj k\u00f3d samostatn\u011b, v\u010detn\u011b testov\u00e1n\u00ed jako u\u017eivatel webu. Slou\u010den\u00ed v\u011btve s hlavn\u00ed je zak\u00e1z\u00e1no, dokud nen\u00ed zn\u00e1mo, \u017ee k\u00f3d funguje.<\/li>\n<li>Ka\u017ed\u00e9mu \u00fakolu jsou p\u0159i\u0159azeny priority. Tyto priority stanovuje bu\u010f zadavatel, nebo t\u00fdmov\u00fd vedouc\u00ed.<\/li>\n<li>V\u00fdvoj\u00e1\u0159i nejprve pln\u00ed \u00fakoly s nejvy\u0161\u0161\u00edmi prioritami.<\/li>\n<li>V\u00fdvoj\u00e1\u0159i si mohou p\u0159i\u0159azovat \u00fakoly navz\u00e1jem, pokud byly nalezeny r\u016fzn\u00e9 chyby v syst\u00e9mu, nebo pokud je jeden \u00fakol rozd\u011blen mezi n\u011bkolik specialist\u016f.<\/li>\n<li>V\u0161echny \u00fakoly, kter\u00e9 vytvo\u0159\u00ed zadavatel, se dost\u00e1vaj\u00ed k t\u00fdmov\u00e9mu vedouc\u00edmu, kter\u00fd je posoud\u00ed a bu\u010f po\u017e\u00e1d\u00e1 zadavatele o \u00fapravy, nebo je p\u0159id\u011bl\u00ed jednomu z \u010dlen\u016f t\u00fdmu.<\/li>\n<li>V\u0161echny \u00fakoly, kter\u00e9 jsou p\u0159ipraveny k nasazen\u00ed na dev nebo prod, se tak\u00e9 dost\u00e1vaj\u00ed k t\u00fdmov\u00e9mu vedouc\u00edmu, kter\u00fd samostatn\u011b ur\u010duje, kdy a jak prov\u00e9st nasazen\u00ed. Po ka\u017ed\u00e9m nasazen\u00ed mus\u00ed t\u00fdmov\u00fd vedouc\u00ed (nebo \u010dlen t\u00fdmu) informovat zadavatele o tom, a tak\u00e9 zm\u011bnit statusy \u00fakol\u016f na p\u0159ipraven\u00e9 k testov\u00e1n\u00ed na dev\/prod.<\/li>\n<li>Ka\u017ed\u00fd den ve stejnou dobu (u n\u00e1s v 12:00) kon\u00e1me sch\u016fzku v\u0161ech \u010dlen\u016f t\u00fdmu.<\/li>\n<li>Na sch\u016fzce se k reportov\u00e1n\u00ed zapojuj\u00ed v\u0161ichni, v\u010detn\u011b t\u00fdmov\u00e9ho vedouc\u00edho, a oznamuj\u00ed, co d\u011blali v\u010dera, co pl\u00e1nuj\u00ed na dnes, co se neda\u0159\u00ed a pro\u010d. T\u00edmto zp\u016fsobem m\u00e1 cel\u00fd t\u00fdm p\u0159ehled o tom, \u010d\u00edm se kdo zab\u00fdv\u00e1 a v jak\u00e9 f\u00e1zi se projekt nach\u00e1z\u00ed. To n\u00e1m umo\u017e\u0148uje progn\u00f3zovat a, pokud je to pot\u0159eba, upravit na\u0161e odhady a term\u00edny.<\/li>\n<li>Na sch\u016fzce t\u00fdmov\u00fd vedouc\u00ed tak\u00e9 oznamuje v\u0161echny zm\u011bny v projektu a \u00farove\u0148 aktu\u00e1ln\u00edch chyb, kter\u00e9 nebyly nalezeny zadavatelem. V\u0161echny chyby se prob\u00edraj\u00ed a p\u0159i\u0159azuj\u00ed ka\u017ed\u00e9mu \u010dlenu t\u00fdmu k vy\u0159e\u0161en\u00ed.<\/li>\n<li>Na sch\u016fzce t\u00fdmov\u00fd vedouc\u00ed p\u0159i\u0159azuje ka\u017ed\u00e9mu \u00fakoly, berouc v \u00favahu aktu\u00e1ln\u00ed vyt\u00ed\u017eenost v\u00fdvoj\u00e1\u0159\u016f, \u00farove\u0148 jejich odborn\u00e9 p\u0159ipravenosti a tak\u00e9 p\u0159ihl\u00ed\u017e\u00ed k bl\u00edzkosti dan\u00e9ho \u00fakolu k tomu, \u010demu se v\u00fdvoj\u00e1\u0159 aktu\u00e1ln\u011b v\u011bnuje.<\/li>\n<li>Na sch\u016fzce t\u00fdmov\u00fd vedouc\u00ed vypracov\u00e1v\u00e1 celkovou strategii architektury a obchodn\u00ed logiky. Pot\u00e9 to cel\u00fd t\u00fdm diskutuje a p\u0159ij\u00edm\u00e1 rozhodnut\u00ed o proveden\u00ed \u00faprav nebo p\u0159ijet\u00ed t\u00e9to strategie.<\/li>\n<li>Ka\u017ed\u00fd v\u00fdvoj\u00e1\u0159 p\u00ed\u0161e k\u00f3d a vytv\u00e1\u0159\u00ed algoritmy s\u00e1m v r\u00e1mci jedn\u00e9 architektury a obchodn\u00ed logiky. Ka\u017ed\u00fd m\u016f\u017ee vyj\u00e1d\u0159it svou vizi realizace, ale nikdo nen\u00ed nucen to d\u011blat jen tak, nebo jinak. Ka\u017ed\u00e9 rozhodnut\u00ed m\u00e1 sv\u00e9 zd\u016fvodn\u011bn\u00ed. Pokud existuje lep\u0161\u00ed \u0159e\u0161en\u00ed, ale nyn\u00ed na n\u011bj nen\u00ed \u010das, vytvo\u0159\u00ed se \u00fakol v JIRA na budouc\u00ed refaktoring ur\u010dit\u00e9 \u010d\u00e1sti k\u00f3du.<\/li>\n<li>Kdy\u017e v\u00fdvoj\u00e1\u0159 p\u0159evezme \u00fakol, p\u0159evede ho do stavu v\u00fdvoje. Ve\u0161ker\u00e1 komunikace ohledn\u011b up\u0159esn\u011bn\u00ed \u00fakolu s klientem le\u017e\u00ed na bedrech v\u00fdvoj\u00e1\u0159e. Technick\u00e9 dotazy lze sm\u011b\u0159ovat k t\u00fdmov\u00e9mu vedouc\u00edmu nebo koleg\u016fm.<\/li>\n<li>Pokud v\u00fdvoj\u00e1\u0159 nerozum\u00ed podstat\u011b \u00fakolu a klient jej nedok\u00e1zal srozumiteln\u011b vysv\u011btlit, p\u0159ech\u00e1z\u00ed k dal\u0161\u00ed \u00faloze. Sou\u010dasn\u00fd \u00fakol p\u0159evezme t\u00fdmov\u00fd vedouc\u00ed a s klientem jej s\u00e1m projedn\u00e1v\u00e1.<\/li>\n<li>Ka\u017ed\u00fd den by m\u011bl v\u00fdvoj\u00e1\u0159 v chatu s klientem ps\u00e1t o \u00fakolech, na nich\u017e pracoval v\u010dera, a na kter\u00fdch bude pracovat dnes.<\/li>\n<li>Pracovn\u00ed proces prob\u00edh\u00e1 podle scrumu. V\u0161echno je rozd\u011bleno do sprint\u016f. Ka\u017ed\u00fd sprint trv\u00e1 dva t\u00fddny.<\/li>\n<li>Sprinty vytv\u00e1\u0159\u00ed, napl\u0148uje a uzav\u00edr\u00e1 t\u00fdmov\u00fd vedouc\u00ed.<\/li>\n<li>Pokud projekt m\u00e1 p\u0159\u00edsn\u00e9 term\u00edny, sna\u017e\u00edme se odhadnout v\u0161echny \u00fakoly a sestavit z nich sprint. Pokud se klient sna\u017e\u00ed do sprintu p\u0159idat dal\u0161\u00ed \u00fakoly, stanovujeme priority a n\u011bkter\u00e9 \u00fakoly p\u0159esouv\u00e1me na dal\u0161\u00ed sprint.<\/li>\n<\/ul>\n<p>\nb) Proces pr\u00e1ce s klientem<\/p>\n<ul>\n<li>Ka\u017ed\u00fd v\u00fdvoj\u00e1\u0159 m\u016f\u017ee a m\u011bl by komunikovat s klientem.<\/li>\n<li>Nen\u00ed mo\u017en\u00e9 klientovi dovolovat vnucovat sv\u00e1 pravidla hry. Je nutn\u00e9 v zdvo\u0159il\u00e9 a p\u0159\u00e1telsk\u00e9 form\u011b d\u00e1t klientovi najevo, \u017ee jsme odborn\u00edci ve sv\u00e9m oboru, a jen my bychom m\u011bli \u0159\u00eddit pracovn\u00ed procesy a zapojovat do nich klienta.<\/li>\n<li>Je nutn\u00e9, ide\u00e1ln\u011b p\u0159ed zah\u00e1jen\u00edm realizace jak\u00e9hokoliv funk\u010dn\u00edho prvku, vytvo\u0159it blokov\u00e9 sch\u00e9ma cel\u00e9ho logick\u00e9ho procesu pro funkci (workflow). A poslat ho ke schv\u00e1len\u00ed klientovi. To se t\u00fdk\u00e1 pouze slo\u017eit\u00e9ho a ne z\u0159ejm\u00e9ho funk\u010dn\u00edho prvku, nap\u0159\u00edklad platebn\u00edho syst\u00e9mu, syst\u00e9mu notifikac\u00ed atd. To umo\u017en\u00ed l\u00e9pe pochopit, co p\u0159esn\u011b klient pot\u0159ebuje, zachovat dokumentaci k funkci, a tak\u00e9 se chr\u00e1nit p\u0159ed t\u00edm, \u017ee klient m\u016f\u017ee v budoucnu \u0159\u00edct, \u017ee jsme ud\u011blali n\u011bco jin\u00e9ho, ne\u017e co \u017e\u00e1dal.<\/li>\n<li>V\u0161echny diagramy\/flowcharty\/logiku atd. ukl\u00e1d\u00e1me do Confluence\/Jira, kde \u017e\u00e1d\u00e1me z\u00e1kazn\u00edka, aby v koment\u00e1\u0159\u00edch potvrdil spr\u00e1vnost budouc\u00ed implementace.<\/li>\n<li>Sna\u017e\u00edme se nezat\u011b\u017eovat z\u00e1kazn\u00edka technick\u00fdmi detaily. Pokud pot\u0159ebujeme pochopit, co p\u0159esn\u011b z\u00e1kazn\u00edk chce, nakresl\u00edme primitivn\u00ed algoritmy ve form\u011b flowchartu, kter\u00e9 m\u016f\u017ee z\u00e1kazn\u00edk pochopit a p\u0159\u00edpadn\u011b opravit\/doklepat s\u00e1m.<\/li>\n<li>Pokud z\u00e1kazn\u00edk najde chybu v projektu, \u017e\u00e1d\u00e1me ho, aby ji co nejpodrobn\u011bji popsal v Jira. Za jak\u00fdch okolnost\u00ed k n\u00ed do\u0161lo, kdy, jak\u00fd sled akc\u00ed z\u00e1kazn\u00edk prov\u00e1d\u011bl p\u0159i testov\u00e1n\u00ed. \u017d\u00e1d\u00e1me o p\u0159ipojen\u00ed screenshot\u016f.<\/li>\n<li>Sna\u017e\u00edme se ka\u017ed\u00fd den, maxim\u00e1ln\u011b ka\u017ed\u00e9 dva dny prov\u00e1d\u011bt nasazen\u00ed na v\u00fdvojov\u00fd server. Z\u00e1kazn\u00edk pak za\u010d\u00edn\u00e1 testovat funk\u010dnost a projekt nez\u016fst\u00e1v\u00e1 ne\u010dinn\u00fd. To je z\u00e1rove\u0148 zna\u010dkou pro z\u00e1kazn\u00edka, \u017ee projekt je v pln\u00e9m v\u00fdvoji a nikdo mu nevypr\u00e1v\u00ed poh\u00e1dky.<\/li>\n<li>Velmi \u010dasto se st\u00e1v\u00e1, \u017ee z\u00e1kazn\u00edk \u00fapln\u011b nerozum\u00ed, co vlastn\u011b pot\u0159ebuje. Vytv\u00e1\u0159\u00ed nov\u00fd byznys s je\u0161t\u011b nefunguj\u00edc\u00edmi procesy. Proto se \u010dasto st\u00e1v\u00e1, \u017ee vyhazujeme cel\u00e9 kusy k\u00f3du do ko\u0161e a p\u0159epracov\u00e1v\u00e1me logiku aplikace. Z toho vypl\u00fdv\u00e1, \u017ee nen\u00ed nutn\u00e9 pokr\u00fdvat testy v\u0161e. Smysl m\u00e1 pokr\u00fdvat testy pouze kriticky d\u016fle\u017eitou funk\u010dnost a to s v\u00fdhradami.<\/li>\n<li>N\u011bkdy se st\u00e1v\u00e1, \u017ee t\u00fdm ch\u00e1pe, \u017ee se nevejdeme do term\u00edn\u016f. Pot\u00e9 provedeme rychl\u00fd audit \u00fakol\u016f a ihned o tom informujeme z\u00e1kazn\u00edka. Jako v\u00fdchodisko z situace nab\u00edz\u00edme spu\u0161t\u011bn\u00ed d\u016fle\u017eit\u00e9 a kritick\u00e9 funk\u010dnosti v term\u00ednu a zbytek nechat na post-release.<\/li>\n<li>Pokud z\u00e1kazn\u00edk za\u010dne vym\u00fd\u0161let r\u016fzn\u00e9 \u00fakoly z hlavy, za\u010dne fantaz\u00edrovat a vysv\u011btlovat to na prstech, \u017e\u00e1d\u00e1me ho, aby n\u00e1m poskytl maketu str\u00e1nky a flow s logikou, kter\u00e1 by m\u011bla \u00fapln\u011b popsat chov\u00e1n\u00ed cel\u00e9 makety a jej\u00edch prvk\u016f.<\/li>\n<li>Ne\u017e se pust\u00edme do jak\u00e9hokoli \u00fakolu, mus\u00edme se ujistit, \u017ee tato funkce byla sou\u010d\u00e1st\u00ed podm\u00ednek na\u0161\u00ed smlouvy. Pokud jde o novou funkci, kter\u00e1 p\u0159ekra\u010duje na\u0161e p\u016fvodn\u00ed dohody, mus\u00edme ji ur\u010dit\u011b odhadnout ((p\u0159ibli\u017en\u00e1 doba proveden\u00ed + 30%) x 2) a informovat z\u00e1kazn\u00edka, \u017ee na ni budeme pot\u0159ebovat tolik a tolik \u010dasu, nav\u00edc se term\u00edn posune o dobu odhadu vyn\u00e1sobenou dv\u011bma. Pokud \u00fakol dokon\u010d\u00edme rychleji \u2014 skv\u011bl\u00e9, v\u0161ichni z toho budou m\u00edt prosp\u011bch. Pokud ne, m\u00e1me rezervu.<\/li>\n<\/ul>\n<p>\nv) Co v t\u00fdmu nep\u0159ij\u00edm\u00e1me:<\/p>\n<ul>\n<li>Nezodpov\u011bdnost, nepo\u0159\u00e1dnost, zapomn\u011btlivost<\/li>\n<li>Odm\u00edt\u00e1n\u00ed odpov\u011bdnosti. Pokud nem\u016f\u017eete \u00fakol splnit, nebo nev\u00edte jak, mus\u00edte okam\u017eit\u011b informovat t\u00fdmov\u00e9ho l\u00eddra, a ne \u010dekat na posledn\u00ed chv\u00edli.<\/li>\n<li>Chluben\u00edm se od osoby, kter\u00e1 je\u0161t\u011b nedok\u00e1zala sv\u00e9 schopnosti a profesionalitu skutky. Pokud to prok\u00e1zala, je to v r\u00e1mci slu\u0161nosti p\u0159ijateln\u00e9 \ud83d\ude42<\/li>\n<li>Podvod v jak\u00e9koli podob\u011b. Pokud \u00fakol nen\u00ed spln\u011bn, nen\u00ed vhodn\u00e9 m\u011bnit jeho stav na spln\u011bn\u00fd a ps\u00e1t v chatu z\u00e1kazn\u00edka, \u017ee je hotov\u00fd. Po\u010d\u00edta\u010d se rozbil, syst\u00e9m selhal, pes rozcupoval notebook \u2014 to v\u0161echno je nep\u0159ijateln\u00e9. Pokud dojde k re\u00e1ln\u00e9 mimo\u0159\u00e1dn\u00e9 situaci, mus\u00ed b\u00fdt t\u00fdmov\u00fd l\u00eddr okam\u017eit\u011b informov\u00e1n.<\/li>\n<li>Kdy\u017e je specialista neust\u00e1le offline a t\u011b\u017eko ho kontaktovat b\u011bhem pracovn\u00ed doby.<\/li>\n<li>Toxi\u010dnost v t\u00fdmu nen\u00ed povolena! Pokud s n\u011b\u010d\u00edm n\u011bkdo nesouhlas\u00ed, v\u0161ichni se sejdou na sch\u016fzce a toto t\u00e9ma prodiskutuj\u00ed a vy\u0159e\u0161\u00ed.<\/li>\n<\/ul>\n<p>A tak\u00e9 n\u011bkolik ot\u00e1zek\/thes\u00ed, kter\u00e9 ob\u010das pokl\u00e1d\u00e1m sv\u00e9mu z\u00e1kazn\u00edkovi, abych odstranil v\u0161echna nedorozum\u011bn\u00ed:<\/p>\n<ol>\n<li>Jak\u00e9 m\u00e1te krit\u00e9ria kvality?<\/li>\n<li>Jak ur\u010dujete, zda projekt m\u00e1 nebo nem\u00e1 probl\u00e9my?<\/li>\n<li>Pokud nedodr\u017eujete v\u0161echna na\u0161e doporu\u010den\u00ed a rady ohledn\u011b zm\u011bn\/vylep\u0161en\u00ed syst\u00e9mu, ve\u0161ker\u00e9 riziko nese jen vy.<\/li>\n<li>Jak\u00e9koli majoritn\u00ed zm\u011bny v projektu (nap\u0159\u00edklad r\u016fzn\u00e9 extra toky) mohou v\u00e9st k mo\u017en\u00e9mu vzniku chyb (kter\u00e9 samoz\u0159ejm\u011b budeme opravovat).<\/li>\n<li>Nen\u00ed mo\u017en\u00e9 b\u011bhem n\u011bkolika minut pochopit, jak\u00fd probl\u00e9m se na projektu objevil, a u\u017e v\u016fbec ne hned jej opravit.<\/li>\n<li>Pracujeme podle konkr\u00e9tn\u00edho produktu flow (\u00dakoly v JIRA \u2014 V\u00fdvoj \u2014 Testov\u00e1n\u00ed \u2014 Nasazen\u00ed). To znamen\u00e1, \u017ee nem\u016f\u017eeme reagovat na cel\u00fd proud \u017e\u00e1dost\u00ed a st\u00ed\u017enost\u00ed v chatu.<\/li>\n<li>Program\u00e1to\u0159i jsou program\u00e1to\u0159i, nikoli profesion\u00e1ln\u00ed testovac\u00ed in\u017een\u00fd\u0159i, a nemohou zajistit odpov\u00eddaj\u00edc\u00ed kvalitu testov\u00e1n\u00ed projektu.<\/li>\n<li>Odpov\u011bdnost za kone\u010dn\u00e9 testov\u00e1n\u00ed a p\u0159evzet\u00ed \u00fakol\u016f do produkce le\u017e\u00ed pln\u011b na v\u00e1s.<\/li>\n<li>Pokud jsme ji\u017e vzali \u00fakol do pr\u00e1ce, nem\u016f\u017eeme se hned p\u0159epnout na jin\u00e9, dokud nedokon\u010d\u00edme aktu\u00e1ln\u00ed (jinak to vede k je\u0161t\u011b v\u011bt\u0161\u00edm chyb\u00e1m a prodlou\u017een\u00ed doby v\u00fdvoje).<\/li>\n<li>Lid\u00e9 v t\u00fdmu se zmen\u0161ili (kv\u016fli dovolen\u00fdm nebo nemocem), ale pr\u00e1ce je v\u00edce, a fyzicky nem\u016f\u017eeme reagovat na v\u0161e, co pot\u0159ebujete.<\/li>\n<li>Va\u0161e \u017e\u00e1dost o nasazen\u00ed do produkce bez otestovan\u00fdch \u00fakol\u016f na develu je pouze va\u0161e riziko, nikoli riziko v\u00fdvoj\u00e1\u0159\u016f.<\/li>\n<li>Kdy\u017e zad\u00e1te nejasn\u00e9 \u00fakoly, bez spr\u00e1vn\u00e9ho workflow a n\u00e1vrh\u016f, vy\u017eaduje to od n\u00e1s mnohem v\u00edce \u00fasil\u00ed a \u010dasu na realizaci, proto\u017ee nam\u00edsto v\u00e1s mus\u00edme vykonat dal\u0161\u00ed objem pr\u00e1ce.<\/li>\n<li>Jak\u00e9koli \u00fakoly t\u00fdkaj\u00edc\u00ed se chyb, bez podrobn\u00e9ho popisu jejich vzniku a screenshot\u016f, n\u00e1m ned\u00e1vaj\u00ed mo\u017enost pochopit, co se pokazilo, a jak tuto chybu simulovat.<\/li>\n<li>Projekt vy\u017eaduje neust\u00e1l\u00e9 \u00fapravy a zlep\u0161en\u00ed pro zv\u00fd\u0161en\u00ed v\u00fdkonu a bezpe\u010dnosti. Proto t\u00fdm tr\u00e1v\u00ed \u010d\u00e1st sv\u00e9ho \u010dasu na t\u011bchto vylep\u0161en\u00edch.<\/li>\n<li>Vzhledem k tomu, \u017ee m\u00e1me ob\u010das p\u0159es\u010dasy (nal\u00e9hav\u00e9 opravy), mus\u00edme je kompenzovat v jin\u00e9 dny.<\/li>\n<\/ol>\n<p>\nObvykle z\u00e1kazn\u00edk okam\u017eit\u011b ch\u00e1pe, \u017ee v\u00fdvoj softwaru nen\u00ed tak jednoduch\u00fd a jedno p\u0159\u00e1n\u00ed zde zcela jist\u011b nesta\u010d\u00ed.<\/p>\n<p>To je v\u0161e. Za sc\u00e9nou z\u016fst\u00e1v\u00e1 \u0159ada jedn\u00e1n\u00ed a po\u010d\u00e1te\u010dn\u00ed lad\u011bn\u00ed v\u0161ech proces\u016f, ale nakonec se v\u0161echno zlep\u0161ilo. Mohu \u0159\u00edci, \u017ee tento proces se stal pro n\u00e1s jakousi 'st\u0159\u00edbrnou kulkou'. Nov\u00ed lid\u00e9, kte\u0159\u00ed se p\u0159i\u0161li do projektu zapojit, mohli za\u010d\u00edt pracovat hned od prvn\u00edho dne, proto\u017ee v\u0161echny procesy byly pops\u00e1ny a dokumentace a architektura ve form\u011b diagram\u016f d\u00e1valy okam\u017eit\u00fd p\u0159ehled o tom, co v\u0161echno d\u011bl\u00e1me. <\/p>\n<p><i>P. S. Chci up\u0159esnit, \u017ee na na\u0161\u00ed stran\u011b nen\u00ed projektov\u00fd mana\u017eer. Je na stran\u011b z\u00e1kazn\u00edka. Nen\u00ed to technik. Projekt je evropsk\u00fd. Cel\u00e1 komunikace prob\u00edh\u00e1 pouze v angli\u010dtin\u011b.<\/i><\/p>\n<p>V\u0161em p\u0159eji hodn\u011b \u0161t\u011bst\u00ed v projektech. Nevyho\u0159\u00edvejte a sna\u017ete se zlep\u0161ovat sv\u00e9 procesy.<\/p>\n<p>Zdrojov\u00fd k\u00f3d m\u00e1m v sob\u011b. <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\/cs\/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=\"cs_CZ\" \/>\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\/cs\/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\udd47 Organizace pracovn\u00edho procesu v t\u00fdmu na IT projektu | ProHoster","description":"Ahoj p\u0159\u00e1tel\u00e9. \u010casto, zejm\u00e9na v outsourcingu, vid\u00edm st\u00e1le tot\u00e9\u017e.","canonical_url":"https:\/\/prohoster.info\/cs\/blog\/administrirovanie\/organizacziya-rabochego-proczessa-v-komande-na-it-proekte","robots":"max-image-preview:large","keywords":"","webmasterTools":{"miscellaneous":""},"schema":null,"og:locale":"cs_CZ","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\/cs\/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\/cs\/wp-json\/wp\/v2\/posts\/97853","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/comments?post=97853"}],"version-history":[{"count":1,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/97853\/revisions"}],"predecessor-version":[{"id":172897,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/posts\/97853\/revisions\/172897"}],"wp:attachment":[{"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/media?parent=97853"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/categories?post=97853"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/prohoster.info\/cs\/wp-json\/wp\/v2\/tags?post=97853"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}