{"id":872,"date":"2018-07-18T15:18:04","date_gmt":"2018-07-18T14:18:04","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=872"},"modified":"2018-07-21T01:50:42","modified_gmt":"2018-07-21T00:50:42","slug":"nejcastejsi-nepochopeni-scrumu","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/nejcastejsi-nepochopeni-scrumu\/","title":{"rendered":"Nej\u010dast\u011bj\u0161\u00ed nepochopen\u00ed Scrumu"},"content":{"rendered":"<p>Scrum je velmi jednoduch\u00fd framework. Bohu\u017eel ale nen\u00ed v\u016fbec snadn\u00fd aplikovat. Je to velk\u00e1 zm\u011bna my\u0161len\u00ed, p\u0159\u00edstupu, hodnot. Kdy\u017e se p\u016fjdete do b\u011b\u017en\u00e9 firmy pod\u00edvat, tohle asi budou nej\u010dast\u011bj\u0161\u00ed nedorozum\u011bn\u00ed, a nepochopen\u00ed, na kter\u00e9 naraz\u00edte:<\/p>\n<p><a href=\"http:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15.png\"><img loading=\"lazy\" class=\"alignnone wp-image-870\" src=\"http:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15-300x225.png\" alt=\"Scrum\" width=\"450\" height=\"338\" srcset=\"https:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15-300x225.png 300w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15-1024x768.png 1024w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15-900x675.png 900w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2018\/06\/2017-10-21-10.07.15.png 2048w\" sizes=\"(max-width: 450px) 85vw, 450px\" \/><\/a><\/p>\n<h3>Daily Scrum jako status meeting<\/h3>\n<p>Daily Scrum alias Standup meeting je tak trivi\u00e1ln\u00ed v\u011bc, \u017ee by jeden \u0159ekl \u017ee se snad ani ned\u00e1 zkazit. Chyba l\u00e1vky. 80% firem ho bere jako status meeting, kde ka\u017ed\u00fd jednotlivec referuje (managerovi, ScrumMasterovi, nebo ostatn\u00edm \u010dlen\u016fm t\u00fdmu) co d\u011blal. A kosmetick\u00e9 zm\u011bny ScrumGuidu, kter\u00e9 se sna\u017e\u00ed vysv\u011btlit, \u017ee je to cel\u00e9 o synchronizaci t\u00fdmu, jejich diskusi, jak dos\u00e1hnou c\u00edle Sprintu (Sprint Goal), z\u016fst\u00e1vaj\u00ed bez pov\u0161imnut\u00ed. Kde jinde bychom ty l\u00edn\u00e9 v\u00fdvoj\u00e1\u0159e kontrolovali a \u0159\u00eddili, v\u017edy\u0165 jinak nebudou nic d\u011blat.<\/p>\n<p>\u201cC\u00edlem Daily Scrumu je synchronizace \u010dlen\u016f t\u00fdmu a jejich dohoda, jak budou d\u00e1le pracovat na dos\u00e1hnut\u00ed c\u00edle Sprintu, tedy Sprint Goalu.\u201c<\/p>\n<h3>Sprint Backlog se nesm\u00ed m\u011bnit, je kl\u00ed\u010dov\u00fd<\/h3>\n<p>Kdy\u017e u\u017e jsem zm\u00ednila Sprint Goal, poj\u010fme u n\u011bj z\u016fstat. V\u011bt\u0161ina firem \u017e\u00e1dn\u00e9 Sprint Goaly nepou\u017e\u00edv\u00e1. Vysta\u010d\u00ed si se Sprint Backlogem, kter\u00fd nav\u00edc myln\u011b vn\u00edm\u00e1 jako nem\u011bnnou specifikaci, kter\u00e1 do detailu popisuje, co p\u0159esn\u011b m\u00e1 t\u00fdm (rozum\u011bj \u2018coding monkeys\u2018) naimplementovat. Sprint Backlog je ale jen r\u00e1mcovou dohodou, jak chceme dos\u00e1hnout c\u00edle Sprintu. Kl\u00ed\u010dov\u00fdm artefaktem je Sprint Goal, kter\u00fd definuje, \u010deho z pohledu business value chceme dos\u00e1hnout. Ten by se m\u011bnit nem\u011bl, proto\u017ee to je to do \u010deho v\u00a0r\u00e1mci Sprintu investujete. Sprint Backlog se naopak v\u00a0z\u00e1vislosti na situaci a dohod\u011b t\u00fdmu klidn\u011b m\u011bnit m\u016f\u017ee. V\u00a0podstat\u011b s\u00a0t\u00edm, jak se ve Scrumu za\u010dal Sprint Goal v\u00edce pou\u017e\u00edvat, p\u0159estal b\u00fdt Sprint Backlog t\u00e9m\u011b\u0159 pot\u0159eba, nato\u017e aby byl nem\u011bnn\u00fd.<\/p>\n<p><em>\u201cSprint Goal definuje smysl Sprintu, \u010deho chceme z\u00a0pohledu business value dos\u00e1hnout. Sprint Backlog n\u00e1m pouze pom\u00e1h\u00e1 ud\u011blat dohodu \u2018jak\u2019 toho chceme dos\u00e1hnout. \u201c<\/em><\/p>\n<h3>Sprint Review je o akceptaci<\/h3>\n<p>A do t\u0159etice v\u0161eho dobr\u00e9ho, nebo sp\u00ed\u0161 zl\u00e9ho :), takov\u00e9 b\u011b\u017en\u00e9 Sprint Review alias Demo velmi \u010dasto skon\u010d\u00ed jako prezentace technick\u00fdch sc\u00e9n\u00e1\u0159\u016f Product Ownerovi. Pro\u010d prezentujeme n\u011bco n\u011bkomu, kdo m\u011bl b\u00fdt celou dobu p\u0159itom, je mi z\u00e1hadou. N\u011bkde prezentujeme Product Ownerovi proto, \u017ee nikoho jin\u00e9ho technick\u00e9 sc\u00e9n\u00e1\u0159e nezaj\u00edmaj\u00ed, jinde proto\u017ee se boj\u00edme \u010dleny t\u00fdmu komukoli uk\u00e1zat, aby neud\u011blali ostudu, jinde ani Product Owner nechod\u00ed a d\u011bl\u00e1me to jen proto\u017ee Scrum. Sprint Review je kl\u00ed\u010dov\u00fdm prvkem Scrumu, proto\u017ee pr\u00e1v\u011b tady z\u00edsk\u00e1v\u00e1me zp\u011btnou vazbu na doru\u010den\u00fd Sprint Goal, tedy funk\u010dn\u00ed inkrement produktu, nebo jinak \u0159e\u010deno dodanou business hodnotu. Jdeme spr\u00e1vn\u00fdm sm\u011brem? Je tohle opravdu business hodnota? Dos\u00e1hli jsme o\u010dek\u00e1van\u00e9ho impactu? To jsou ot\u00e1zky, kter\u00e9 je dobr\u00e9 si v\u00a0r\u00e1mci Sprint Review polo\u017eit.<\/p>\n<p><em>\u201cC\u00edlem Sprint Review je z\u00edskat zp\u011btnou vazbu od z\u00e1kazn\u00edk\u016f, stakeholder\u016f, u\u017eivatel\u016f abyste se na jej\u00edm z\u00e1klad\u011b mohli adaptovat. Je to kl\u00ed\u010dov\u00fdm prvkem a by v\u00e1m fungoval proncip Inspect and Adapt.\u201c<\/em><\/p>\n<p>&nbsp;<\/p>\n<p>Jestli jste se ve v\u00fd\u0161e zm\u00edn\u011bn\u00fdch p\u0159\u00edkladech nepoznali, dobr\u00e1 zpr\u00e1va. Asi jste se u\u017e vymanili z\u00a0podru\u010d\u00ed \u2018Technick\u00e9ho Scrumu\u2019, nebo \u2019Dark Scrumu\u2019 a jste o krok bl\u00ed\u017ee zm\u011bn\u011b mindsetu. Jen tak d\u00e1l \ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Scrum je velmi jednoduch\u00fd framework. Bohu\u017eel ale nen\u00ed v\u016fbec snadn\u00fd aplikovat. Je to velk\u00e1 zm\u011bna my\u0161len\u00ed, p\u0159\u00edstupu, hodnot. Kdy\u017e se p\u016fjdete do b\u011b\u017en\u00e9 firmy pod\u00edvat, tohle asi budou nej\u010dast\u011bj\u0161\u00ed nedorozum\u011bn\u00ed, a nepochopen\u00ed, na kter\u00e9 naraz\u00edte: Daily Scrum jako status meeting Daily Scrum alias Standup meeting je tak trivi\u00e1ln\u00ed v\u011bc, \u017ee by jeden \u0159ekl \u017ee se &hellip; <a href=\"https:\/\/soch.cz\/blog\/management\/agile\/nejcastejsi-nepochopeni-scrumu\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Nej\u010dast\u011bj\u0161\u00ed nepochopen\u00ed Scrumu&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[272,13,199,168,78,7,228,227],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/872"}],"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=872"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/872\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=872"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=872"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=872"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}