Jak se posledn\u00ed dobou pohybuji ve v\u011bt\u0161\u00edch firm\u00e1ch, setk\u00e1v\u00e1m se \u010dasto s n\u00e1zorem, \u017ee Scrum je jen pro mal\u00e9 firmy. Tak se poj\u010fme pod\u00edvat, co se t\u00edm v re\u00e1lu mysl\u00ed. V korpor\u00e1tech se \u010dasto objevuje pojem \u201cide\u00e1ln\u00ed Scrum\u201c, \u010d\u00edm\u017e je m\u00edn\u011bno prost\u0159ed\u00ed kde je jeden t\u00fdm, jeden Scrum Master, jeden Product Owner a \u017e\u00e1dn\u00e9 z\u00e1vislosti. V\u0161ichni pln\u011b alokovan\u00ed, pracuj\u00ed na n\u011b\u010dem, co ide\u00e1ln\u011b vytv\u00e1\u0159\u00edme od nuly a co s ni\u010d\u00edm dal\u0161\u00edm nesouvis\u00ed. Takov\u00e9 jednoduch\u00e9. A druh\u00fdm dechem dod\u00e1vaj\u00ed, \u017ee to my v na\u0161\u00ed organizaci nem\u00e1me, my m\u00e1me ty velk\u00e9 integra\u010dn\u00ed projekty a na n\u00e1s se agiln\u00ed metody nehod\u00ed. No ostatn\u011b ka\u017ed\u00fd d\u016fvod se hod\u00ed, kdy\u017e se chceme br\u00e1nit zm\u011bn\u011b. Za\u010d\u00ednala jsem se u\u010dit Scrum ve velk\u00e9 korporaci, kter\u00e1 m\u011bla n\u011bkolik diviz\u00ed, IT v \u0159\u00e1du jednotek tis\u00edc\u016f, outsourcing\/offshoring a distribuovan\u00e9 t\u00fdmy. A vid\u011bla, co se stalo po transformaci na agile a Scrum. V\u00fdrazn\u00fd n\u00e1r\u016fst efektivity, kvality, zastupitelnosti. A to v\u0161e ve velice komplexn\u00edm prost\u0159ed\u00ed mnoha souvisej\u00edc\u00edch produkt\u016f a specifick\u00fdch technologi\u00ed napojen\u00fdch na vlastn\u00ed HW. Nebyly to \u017e\u00e1dn\u00e9 mal\u00e9 internetov\u00e9 projekt\u00edky. Proto tomuto argumentu \u010desk\u00fdch firem moc nerozum\u00edm.<\/p>\n
Ale poj\u010fme se pod\u00edvat, pro\u010d by v prost\u0159ed\u00ed velk\u00e9 korporace mohl b\u00fdt Scrum a agiln\u00ed metody prosp\u011b\u0161n\u00e9. Takov\u00e9hle velk\u00e9 firmy \u010dasto dokonverguj\u00ed k zaj\u00edmav\u00e9 organiza\u010dn\u00ed struktu\u0159e. Maj\u00ed odd\u011blen\u00e9 IT a business. Moc spolu nemluv\u00ed, moc se nemaj\u00ed r\u00e1di. Business d\u00e1v\u00e1 velice voln\u011b definovan\u00e9 po\u017eadavky \u2013 slovy IT nev\u00ed, co chce \u2013 a to IT m\u00e1 na jejich \u0159e\u0161en\u00ed m\u00e1lo kapacit a nest\u00edh\u00e1. V\u0161echno je pozd\u011b. A je\u0161t\u011b \u010dasto dod\u00e1 n\u011bco jin\u00e9ho. Takov\u00e9 firmy se sna\u017e\u00ed tuto nefunk\u010dnost r\u016fzn\u011b h\u00e1zet jeden na druh\u00e9ho. Ti co se na to dok\u00e1\u017e\u00ed d\u00edvat s nadhledem, \u010dasto \u0159\u00edkaj\u00ed \u201cM\u00e1me velk\u00fd probl\u00e9m v IT, kter\u00fd ale nele\u017e\u00ed v IT.<\/em>\u201c<\/p>\n Jak je business hodn\u011b daleko a nem\u00e1 obvykle p\u0159\u00edli\u0161 motivaci se do projekt\u016f zapojovat, tak se t\u00fdmy obklop\u00ed arm\u00e1dou business analytik\u016f, kte\u0159\u00ed se sna\u017e\u00ed po\u017eadavky businessu dodefinovat a interpretovat IT sv\u011btu tak, aby pro n\u011b byly srozumiteln\u00e9. A proto\u017ee oni za \u00fasp\u011b\u0161nost projektu nenesou \u017e\u00e1dnou zodpov\u011bdnost, tak po\u017eadavky nijak neo\u0159ez\u00e1vaj\u00ed, ba pr\u00e1v\u011b naopak. Oni jen pln\u00ed p\u0159\u00e1n\u00ed businessu. A rozm\u00fd\u0161l\u00ed, jak by se takov\u00e1 v\u011bc mohla chovat. A tak IT roste a roste a p\u0159ekvapiv\u011b po\u0159\u00e1d nest\u00edh\u00e1 tu spoustu po\u017eadavk\u016f businessu zpracov\u00e1vat. A kdyby mohlo, sed\u00ed ve v\u0161ech budov\u00e1ch a kancel\u00e1\u0159\u00edch po cel\u00e9m m\u011bst\u011b.<\/p>\n Agiln\u00ed metody a Scrum proces se sna\u017e\u00ed organizovat t\u00fdmy po produktech, ne po technologi\u00edch. Z\u00e1kladn\u00ed v\u00fdhodou potom je, \u017ee to co se d\u011bl\u00e1, nen\u00ed rozhodov\u00e1no IT nebo analytiky, ale businessem kter\u00fd u ka\u017ed\u00e9 funkcionality zva\u017euje, jestli se jim vyplat\u00ed do n\u00ed investovat energii t\u00fdmu\/pen\u00edze. U ka\u017ed\u00e9 funkcionality se zamysl\u00ed nad t\u00edm jak\u00fd m\u00e1 o\u010dek\u00e1van\u00fd p\u0159\u00ednos a jakou \u201cpokutu\u201c bychom ev. platili za jej\u00ed absenci a jestli n\u00e1m to cel\u00e9 stoj\u00ed za to. Na to se hod\u00ed koncept User Stories<\/a> (ur\u010dit\u011b si vzpomenete na zkratku INVEST<\/a> kter\u00e1 je v tomto kontextu docela v\u00fdsti\u017en\u00e1). Tohle je tedy krom\u011b lep\u0161\u00ed komunikace mezi IT a businessem, vy\u0161\u0161\u00ed motivac\u00ed a vy\u0161\u0161\u00ed zastupitelnost\u00ed asi hlavn\u00edm d\u016fvodem pro vyzkou\u0161en\u00ed agiln\u00edho p\u0159\u00edstupu. \u0158\u00edk\u00e1 se, \u017ee firmy, kter\u00e9 takto \u0159\u00edd\u00ed svoj\u00ed funkcionalitu, mohou u\u0161et\u0159it a\u017e 80% effortu. Ur\u010dit\u011b to neplat\u00ed plo\u0161n\u011b, ale pod\u00edvejte se kolem sebe. Kolik funkcionality se opravdu pou\u017eije a vyplat\u00ed? Kolik toho v\u0161eho na \u010dem pracujete, by \u0161lo zjednodu\u0161it, kdybychom rozum\u011bli tomu, pro\u010d to v\u016fbec d\u011bl\u00e1me. A co by \u0161lo v kone\u010dn\u00e9m d\u016fsledku \u00fapln\u011b nahradit\u2026<\/p>\n \u0158ekn\u011bme tedy, \u017ee jste mi uv\u011b\u0159ili, \u017ee by to mohlo m\u00edt smysl. Co d\u00e1l? Jak zformovat stabiln\u00ed t\u00fdm v prost\u0159ed\u00ed stovky integrovan\u00fdch syst\u00e9m\u016f, kde se IT skl\u00e1d\u00e1 z mnoha isolovan\u00fdch \u00fazk\u00fdch specialist\u016f a syst\u00e9my tvo\u0159\u00ed chobotnici vz\u00e1jemn\u011b prov\u00e1zan\u00fdch funkcionalit s mno\u017estv\u00edm legacy k\u00f3du, kter\u00e9mu ji\u017e nikdo nerozum\u00ed? Kupodivu to jde sn\u00e1ze ne\u017e byste si mysleli. V re\u00e1lu obvykle dojdete k tomu, \u017ee t\u00edm, \u017ee se za\u010dnete na syst\u00e9my d\u00edvat z pohledu businessu, ud\u011bl\u00e1te v podstat\u011b vertik\u00e1ln\u00ed strukturu proti sou\u010dasn\u00e9 horizont\u00e1ln\u00ed. Je to jin\u00fd pohled. N\u011bkter\u00e9 produkty spoj\u00edte, jin\u00e9 rozd\u011bl\u00edte, ale ve fin\u00e1le se v\u017edy p\u0159ijde na to, \u017ee syst\u00e9m jde relativn\u011b snadno roz\u0159ezat na funk\u010dn\u00ed logick\u00e9 produkty, kde je mo\u017en\u00e9 stanovit Product Ownera, kter\u00fd m\u00e1 zodpov\u011bdnost za n\u00e1vratnost a \u00fasp\u011b\u0161nost produktu. Nen\u00ed na to s\u00e1m, pom\u00e1haj\u00ed mu ostatn\u00ed kolegov\u00e9 z businessu, business analytici a IT architekti jako doposud, ale je tu n\u011bkdo, kdo je stabiln\u011b zodpov\u011bdn\u00fd za produktovou linii. D\u011bl\u00e1 jen to co m\u00e1 smysl. Co se vyplat\u00ed v dlouhodob\u00e9m horizontu. To je prvn\u00ed \u010d\u00e1st \u00fakolu. Druh\u00e1 \u010d\u00e1st sest\u00e1v\u00e1 z definov\u00e1n\u00ed stabiln\u00edch Scrum t\u00fdm\u016f. I to nen\u00ed tak slo\u017eit\u00e9, jak by se mohlo zd\u00e1t. T\u00fdm mus\u00edm obsahovat znalosti kl\u00ed\u010dov\u00fdch technologi\u00ed, syst\u00e9m\u016f a architektury. Ale kdy\u017e to zkus\u00edte, zjist\u00edte, \u017ee va\u0161e sou\u010dasn\u00e1 chobotnice slo\u017een\u00e1 z nenahraditeln\u00fdch a nezastupiteln\u00fdch \u010d\u00e1ste\u010dek jde obvykle rozd\u011blit na t\u00fdmy o cca 7-10 lidech, kter\u00e9 jsou schopny v\u011bt\u0161inu pr\u00e1ce na nov\u011b definovan\u00e9m produktu ud\u011blat sami. Co zbyde, si bu\u010f objednaj\u00ed zvenku, nebo se nau\u010d\u00ed. V\u011bt\u0161\u00ed produkty budou implementovat skupiny 1-4 stabiln\u00edch t\u00fdm\u016f, men\u0161\u00ed projekty se daj\u00ed sdru\u017eit pod jednoho Product Ownera, kter\u00fd m\u00e1 jeden takov\u00fd t\u00fdm. Zn\u00ed to jako utopie, ale zkuste to. Zat\u00edm jsem nepotkala firmu, ve kter\u00e9 by to ne\u0161lo.<\/p>\n Co je na tom nejt\u011b\u017e\u0161\u00ed? Uv\u011b\u0159it, \u017ee i v takto slo\u017eit\u00e9 a komplexn\u00ed firm\u011b je to mo\u017en\u00e9. Uv\u011b\u0159it, \u017ee by n\u00e1m takov\u00e1 zm\u011bna mohla v\u00fdrazn\u011b pomoct. Za\u010d\u00edt budovat kulturu zodpov\u011bdnosti, pos\u00edlit d\u016fv\u011bru, a podpo\u0159it transparentn\u00ed komunikaci v r\u00e1mci cel\u00e9ho syst\u00e9mu. Zn\u00ed to jako fr\u00e1ze, ale funguje to. Je to t\u011b\u017ek\u00e1 a zdlouhav\u00e9 pr\u00e1ce. P\u0159\u00edjemn\u00e9 je, \u017ee jakmile za\u010dnete, va\u0161e snaha velice rychle p\u0159inese sv\u00e9 ovoce a lidem se po prvotn\u00ed vln\u011b odporu nov\u00fd proces zal\u00edb\u00ed. V ten moment za\u010dne b\u00fdt va\u0161e snaha o zm\u011bnu naka\u017eliv\u00e1 a vy m\u00e1te o kousek pr\u00e1ce m\u00ed\u0148.<\/p>\n","protected":false},"excerpt":{"rendered":" Jak se posledn\u00ed dobou pohybuji ve v\u011bt\u0161\u00edch firm\u00e1ch, setk\u00e1v\u00e1m se \u010dasto s n\u00e1zorem, \u017ee Scrum je jen pro mal\u00e9 firmy. Tak se poj\u010fme pod\u00edvat, co se t\u00edm v re\u00e1lu mysl\u00ed. V korpor\u00e1tech se \u010dasto objevuje pojem \u201cide\u00e1ln\u00ed Scrum\u201c, \u010d\u00edm\u017e je m\u00edn\u011bno prost\u0159ed\u00ed kde je jeden t\u00fdm, jeden Scrum Master, jeden Product Owner a \u017e\u00e1dn\u00e9 z\u00e1vislosti. … Continue reading “Je Scrum jen pro male firmy?”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[272,95,273,57,7,82],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/410"}],"collection":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/comments?post=410"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/410\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=410"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=410"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=410"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}