{"id":659,"date":"2016-01-08T08:43:37","date_gmt":"2016-01-08T07:43:37","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=659"},"modified":"2018-02-07T15:34:28","modified_gmt":"2018-02-07T14:34:28","slug":"scaling-agile-and-scrum","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/scaling-agile-and-scrum\/","title":{"rendered":"Scaling Agile and Scrum"},"content":{"rendered":"

Posledn\u00ed dobou se vyrojila spousta r\u016fzn\u00fdch metod jak \u0161k\u00e1lovat Scrum a Agile proces na prost\u0159ed\u00ed velk\u00fdch produkt\u016f. Tak\u017ee ne\u017e se chyt\u00edte do s\u00edt\u011b r\u016fzn\u00fdch klasicky sm\u00fd\u0161lej\u00edc\u00edch organizac\u00ed, kter\u00e9 ve Scalingu kone\u010dn\u011b na\u0161ly cestu jak naoko aplikovat Scrum,\u00a0ale\u00a0praktiky nemuset m\u011bnit, tak se zkuste pod\u00edvat na zcela Agiln\u00ed p\u0159\u00edstup jak na to.<\/p>\n

\"\"<\/a>Nen\u00ed na tom nic a\u017e tak slo\u017eit\u00e9ho. \u00a0Jen mus\u00edte rozum\u011bt tomu, co je opravdu Scrum. Nen\u00ed to toti\u017e proces jak \u0159\u00eddit v\u00fdvoj, ani n\u011bco kv\u016fli \u010demu m\u00e1me Backlog a Standupy, ale p\u0159\u00edstup, filosofie a kultura. Obecn\u011b se tomu \u0159\u00edk\u00e1 empirick\u00fd proces. Tedy velice voln\u011b definovan\u00e1 pravidla hry. Ka\u017ed\u00e1 takov\u00e1 Scrum hra m\u00e1 sv\u00e9 h\u0159i\u0161t\u011b s\u00a0pevn\u011b dan\u00fdmi mantinely a p\u00e1r pravidly jak hr\u00e1t. Jinak by to byl chaos. Ale u\u017e ne\u0159\u00edk\u00e1, co p\u0159esn\u011b v\u00a0kter\u00e9 situaci mus\u00edte ud\u011blat. K\u00a0tomu jsou definovan\u00e9 best practices. A Scaling Scrum je \u010dasto uk\u00e1zkou, jak k\u00a0tomuto probl\u00e9mu lze p\u0159istoupit neagiln\u011b a nescrumov\u011b – tedy kolem Scrum t\u00fdm\u016f vytvo\u0159it slo\u017eit\u00e9 byrokratick\u00e9 struktury nov\u00fdch rol\u00ed, proces\u016f, \u00a0meeting\u016f, pojm\u016f.\u00a0 Viz obr\u00e1zek, kde ta b\u00edl\u00e1 plocha je to, co je p\u016fvodn\u00ed Scrum.<\/p>\n

Opa\u010dn\u00fd p\u0159\u00edstup zvolil Bas a Craig s\u00a0frameworkem LeSS. Stejn\u011b tak, jako kdy\u017e Ken kdysi d\u00e1vno definoval Scrum a m\u011bl mo\u017enost si zvolit, kter\u00e9 praktiky budou sou\u010d\u00e1st\u00ed Scrumu a kter\u00e9 ne, volil sp\u00ed\u0161e m\u00e9n\u011b ne\u017e v\u00edce. A proto\u017ee Scrum je n\u011bco, co se st\u00e1le vyv\u00edj\u00ed, je dnes na rozd\u00edl od za\u010d\u00e1tku ned\u00edlnou sou\u010d\u00e1st\u00ed Scrumu Retrospektiva, ale nap\u0159\u00edklad story pointy, User Stories and Scrum Board jsou jen doporu\u010den\u00e9 praktiky. Proto je Scrum tak \u00fasp\u011b\u0161n\u00fd. Je toti\u017e aplikovateln\u00fd \u00fapln\u011b kdekoliv. Kdy\u017e se vr\u00e1t\u00edm k\u00a0LeSS Large-Scale Scrum frameworku, tak p\u0159esn\u011b to je hlavn\u00ed filosofi\u00ed LeSS \u2013 \u2018Do more with LeSS\u2018.<\/p>\n

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

Co se tedy podle LeSS mus\u00ed zm\u011bnit proti jednoduch\u00e9mu obr\u00e1zku, kde m\u00e1me jen jeden Scrum t\u00fdm? Na prvn\u00ed pohled nic z\u00e1sadn\u00edho. Po\u0159\u00e1d m\u00e1me jeden stejn\u00fd Sprint, jeden \u2018potentional shipable product increment\u2018, jeden k\u00f3d a continuous integration. Po\u0159\u00e1d m\u00e1me cross-functional t\u00fdmy kter\u00e9 dok\u00e1\u017eou jako t\u00fdm samostatn\u011b dokon\u010dit jakoukoli polo\u017eku z\u00a0Product Backlogu. T\u00fdmy si d\u011blaj\u00ed sv\u00e9 vlastn\u00ed Standupy a Retrospektivy. Po\u0159\u00e1d m\u00e1me v\u0161ichni jeden c\u00edl, dodat hodnotu z\u00e1kazn\u00edkovi. A tak pro jeden produkt m\u00e1me jeden Product Backlog a jednoho Product Ownera \u2013 a nemus\u00edte se b\u00e1t, zvl\u00e1dne to. On toti\u017e Product Owner nikdy nepracuje s\u00e1m a i na tom jednoduch\u00e9m 1-1 obr\u00e1zku m\u00e1 spoustu pomocn\u00edk\u016f.<\/p>\n

Tak\u017ee v\u00a0podstat\u011b jedin\u00e9, co se zm\u011bnilo je, \u017ee na \u00farovni development t\u00fdm\u016f se zaj\u00edm\u00e1me co d\u011blaj\u00ed ostatn\u00ed t\u00fdmy, jednotliv\u00ed \u010dlenov\u00e9 spolu \u0159e\u0161\u00ed z\u00e1vislosti. Ne co se t\u00fd\u010de businessu, proto\u017ee polo\u017eky Backlogu jsou nez\u00e1visl\u00e9, ale z\u00e1vislosti v\u00a0k\u00f3du, dan\u00e9 konkr\u00e9tn\u00edm \u0159e\u0161en\u00edm dan\u00e9 Story. D\u00e1le obvykle pos\u00edl\u00e1me z\u00e1stupce t\u00fdm\u016f, aby chodili jako pozorovatel\u00e9 na Standup ostatn\u00edch t\u00fdm\u016f a identifikovali tak v\u010das p\u0159\u00edpadn\u00e9 n\u00e1vaznosti a rizika. Na \u00farovni produktu u\u017e nen\u00ed jen na Product Ownerovi, aby p\u0159ed Sprintem vybral priority pro p\u0159\u00ed\u0161t\u00ed Sprint, ale obvykle se takov\u00e9ho v\u00fdb\u011bru z\u00fa\u010dastn\u00ed i z\u00e1stupci t\u00fdm\u016f, aby zohlednili jejich r\u016fzn\u00e9 zku\u0161enosti. Nakonec je tu je\u0161t\u011b jeden nov\u00fd meeting \u2013 Overall Retrospective \u2013 jej\u00edm\u017e c\u00edlem je ud\u011blat retrospektivu na t\u00e9ma jak n\u00e1m jde spolupr\u00e1ce. A jak se asi d\u00e1 o\u010dek\u00e1vat, jsou tam ScrumMaste\u0159i, Product Owner, a z\u00e1stupci t\u00fdm\u016f a kon\u00e1 se v\u017edy po skon\u010den\u00ed Sprintu.<\/p>\n

Nic slo\u017eit\u00e9ho. A jestli to funguje? Ale jist\u011b. Prvn\u00ed implementace Scrumu, ve kter\u00e9 jsem se ocitla je\u0161t\u011b jako v\u00fdvoj\u00e1\u0159, byla p\u0159esn\u011b takov\u00e1. T\u0159i t\u00fdmy, jeden produkt. \u010casem jsem byla ScrumMasterem n\u011bkolika t\u00fdm\u016f pr\u00e1v\u011b v\u00a0takov\u00e9m uspo\u0159\u00e1d\u00e1n\u00ed, tentokr\u00e1t pro \u0161est t\u00fdm\u016f. A jako Agiln\u00ed coach jsem takov\u00e9 uspo\u0159\u00e1d\u00e1n\u00ed pom\u00e1hala implementovat v\u00a0mnoha r\u016fzn\u00fdch firm\u00e1ch. Tak\u017ee ano, funguje to, je to snadn\u00e9, je to Agiln\u00ed, a p\u0159in\u00e1\u0161\u00ed to v\u00fdsledky. Jestli jsem v\u00e1s nep\u0159esv\u011bd\u010dila, m\u016f\u017eete se pod\u00edvat na n\u011bkterou z\u00a0LeSS case studies<\/a> nebo na detailn\u00ed popis LeSS Large-Scale Scrum Frameworku<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":"

Posledn\u00ed dobou se vyrojila spousta r\u016fzn\u00fdch metod jak \u0161k\u00e1lovat Scrum a Agile proces na prost\u0159ed\u00ed velk\u00fdch produkt\u016f. Tak\u017ee ne\u017e se chyt\u00edte do s\u00edt\u011b r\u016fzn\u00fdch klasicky sm\u00fd\u0161lej\u00edc\u00edch organizac\u00ed, kter\u00e9 ve Scalingu kone\u010dn\u011b na\u0161ly cestu jak naoko aplikovat Scrum,\u00a0ale\u00a0praktiky nemuset m\u011bnit, tak se zkuste pod\u00edvat na zcela Agiln\u00ed p\u0159\u00edstup jak na to. Nen\u00ed na tom nic a\u017e … Continue reading “Scaling Agile and 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":[12],"tags":[272,216,149,139,126,7],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/659"}],"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=659"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/659\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=659"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=659"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=659"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}