{"id":837,"date":"2018-03-06T11:05:53","date_gmt":"2018-03-06T10:05:53","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=837"},"modified":"2018-03-27T08:25:15","modified_gmt":"2018-03-27T07:25:15","slug":"jak-na-skalovani-scrumu-pro-vice-tymu-idealni-je-less-large-scale-scrum","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/jak-na-skalovani-scrumu-pro-vice-tymu-idealni-je-less-large-scale-scrum\/","title":{"rendered":"Jak na\u00a0\u0161k\u00e1lov\u00e1n\u00ed Scrumu pro v\u00edce t\u00fdm\u016f?\u00a0Ide\u00e1ln\u00ed je LeSS Large-Scale Scrum"},"content":{"rendered":"

Kdy\u017e zav\u00e1d\u00edte \u010di ve firm\u011b pou\u017e\u00edv\u00e1te Scrum, \u010dasem se dostanete do situace, kdy pot\u0159ebujete aplikovat Scrum na n\u011bco v\u011bt\u0161\u00edho, a nechat spolupracovat v\u00edce t\u00fdm\u016f. Obecn\u011b to nen\u00ed nic slo\u017eit\u00e9ho, ale abyste se v\u00a0tom neztratili, je vhodn\u00e9 si trochu pomoct n\u011bjak\u00fdm frameworkem. U men\u0161\u00ed produktov\u00e9 firmy je to po\u0159\u00e1d relativn\u011b snadn\u00e9. Pou\u017eijete Scrum ve v\u011bt\u0161\u00edm, tedy Large-Scale Scrum (LeSS)<\/a>.<\/p>\n

\"Large<\/a><\/p>\n

LeSS je jednoduch\u00fd framework, kter\u00fd stav\u00ed na principech Scrumu a d\u00e1le je pou\u017e\u00edv\u00e1 na v\u00edce t\u00fdm\u016f. Tedy v\u00a0kostce m\u00e1te, jednoho Product Ownera, jeden Product Backlog, jeden produkt, kter\u00fd prezentujete z\u00e1kazn\u00edk\u016fm, ale v\u00edce t\u00fdm\u016f, kte\u0159\u00ed ho spole\u010dn\u011b dod\u00e1vaj\u00ed. T\u00fdmy jsou stejn\u011b jako v\u00a0klasick\u00e9m Scrumu stabiln\u00ed, self-organized, a cross-functional \u2013 tedy ka\u017ed\u00fd t\u00fdm dok\u00e1\u017ee vz\u00edt libovolnou polo\u017eku z\u00a0Backlogu a dokon\u010dit j\u00ed. Mus\u00ed tedy m\u00edt v\u0161echny kompetence, kter\u00e9 jsou pot\u0159eba aby mohli dodat end-to-end hodnotu z\u00e1kazn\u00edkovi podle Definition of Done<\/a> nap\u0159. DB, backend, frontend, dokumentace, UX, architektura, automatick\u00e9 testy, u\u017eivatelsk\u00e1 dokumentace apod.). Takhle jednoduch\u00fd koncept plat\u00ed pro prost\u0159ed\u00ed do osmi spolupracuj\u00edc\u00edch cross-functional t\u00fdm\u016f.<\/p>\n

\"Product<\/a>
\nPokud jste velk\u00e1 korporace (banka, poji\u0161\u0165ovna, nebo prost\u011b jen velk\u00e1 IT firma \u010di firma s\u00a0velk\u00fdm IT odd\u011blen\u00edm), principi\u00e1ln\u011b je to stejn\u00e9. Jen implementace je v\u00fdrazn\u011b komplexn\u011bj\u0161\u00ed a zm\u011bna n\u00e1ro\u010dn\u011bj\u0161\u00ed. V\u00a0takov\u00e9m p\u0159\u00edpad\u011b u\u017e si nevysta\u010d\u00edte s\u00a0jednoduch\u00fdm LeSS frameworkem, ale mus\u00edte pou\u017e\u00edt takzvan\u00fd LeSS Huge \u2013 tedy Large-Scale Scrum pro obrovsk\u00e1 prost\u0159ed\u00ed. Po\u0159\u00e1d m\u00e1te stabiln\u00ed, self-organized, a cross-functional t\u00fdmy, kter\u00e9 spole\u010dn\u011b dod\u00e1vaj\u00ed jeden produkt. Je dobr\u00e9 si uv\u011bdomit \u017ee produkt nen\u00ed projekt. Projekt je jen jednou polo\u017ekou Product Backlogu. V\u00edce si o tom m\u016f\u017eete p\u0159e\u010d\u00edst tady<\/a>. Produkt je tedy daleko dlouhodob\u011bj\u0161\u00ed a umo\u017e\u0148uje postavit stabiln\u011bj\u0161\u00ed t\u00fdmov\u00e9 prost\u0159ed\u00ed.<\/p>\n

\"Large<\/a>LeSS Huge nen\u00ed a\u017e tak odli\u0161n\u00fd od klasick\u00e9ho Large-Scale Scrumu. Co je ale v\u00a0LeSS Huge slo\u017eit\u011bj\u0161\u00ed je struktura Product Backlogu. Zbytek z\u016fst\u00e1v\u00e1 stejn\u00fd. P\u0159ekvapiv\u011b jednoduch\u00e9, \u017ee? Abychom si zachovali takzvan\u00fd tah na branku, st\u00e1le chceme m\u00edt jednoho Product Ownera a jeden Backlog. To ale u\u017e nen\u00ed tak snadn\u00e9, a tak\u00a0vznik\u00e1 podp\u016frn\u00e1 struktura takzvan\u00fdch Area Product Owner\u016f, kte\u0159\u00ed pom\u00e1haj\u00ed v\u00fd\u0161e zm\u00edn\u011bn\u00e9mu Product Ownerovi s\u00a0prioritizac\u00ed. Arey nejsou fixn\u00ed, ale dynamicky se m\u011bn\u00ed podle pot\u0159eb businessu \u2013 ostatn\u011b st\u00e1le plat\u00ed, \u017ee t\u00fdmy jsou cross-functional, tak\u017ee mohou vz\u00edt z\u00a0Backlogu jakoukoli polo\u017eku a napl\u00e1novat ji do Sprintu. Co neum\u00ed, u\u010d\u00ed se. Obvykle ale nemus\u00ed um\u011bt v\u0161e a v\u011bnuj\u00ed se n\u011bjak\u00e9 oblasti (Area). Nezapome\u0148te ale, \u017ee oblast nen\u00ed komponenta a t\u00fdmy dod\u00e1vaj\u00ed v\u017edy end-to-end funkcionalitu. Product Backlog je st\u00e1le jeden, a tak m\u00e1me po\u0159\u00e1d focus na ty pro firmu businessov\u011b nejd\u016fle\u017eit\u011bj\u0161\u00ed v\u011bci.<\/p>\n

Je to jednoduch\u00e9, a hlavn\u011b to funguje. Ale stejn\u011b jako Scrum, ani Large-Scale Scrum tedy LeSS<\/a> nen\u00ed \u017e\u00e1dn\u00e1 z\u00e1zra\u010dn\u00e1 pilulka. Aby zafungoval vy\u017eaduje zm\u011bnu my\u0161len\u00ed, p\u0159\u00edstupu a mindsetu. Ale na to jste si v\u00a0Agiln\u00edm sv\u011bt\u011b jist\u011b zvykli. \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"

Kdy\u017e zav\u00e1d\u00edte \u010di ve firm\u011b pou\u017e\u00edv\u00e1te Scrum, \u010dasem se dostanete do situace, kdy pot\u0159ebujete aplikovat Scrum na n\u011bco v\u011bt\u0161\u00edho, a nechat spolupracovat v\u00edce t\u00fdm\u016f. Obecn\u011b to nen\u00ed nic slo\u017eit\u00e9ho, ale abyste se v\u00a0tom neztratili, je vhodn\u00e9 si trochu pomoct n\u011bjak\u00fdm frameworkem. U men\u0161\u00ed produktov\u00e9 firmy je to po\u0159\u00e1d relativn\u011b snadn\u00e9. Pou\u017eijete Scrum ve v\u011bt\u0161\u00edm, tedy … Continue reading “Jak na\u00a0\u0161k\u00e1lov\u00e1n\u00ed Scrumu pro v\u00edce t\u00fdm\u016f?\u00a0Ide\u00e1ln\u00ed je LeSS Large-Scale Scrum”<\/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,216,149,139,126,7],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/837"}],"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=837"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/837\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=837"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=837"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=837"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}