Kdy\u017e to \u0159eknu jednou v\u011btou, Scrum je iterativn\u00ed a inkrement\u00e1ln\u00ed styl pr\u00e1ce, zam\u011b\u0159en\u00fd na t\u00fdmovou spolupr\u00e1ci a maximalizaci business hodnoty. Nic slo\u017eit\u00e9ho. To ale neznamen\u00e1 \u017ee ho organizace hned napoprv\u00e9 implementuj\u00ed spr\u00e1vn\u011b. Scrum toti\u017e m\u011bn\u00ed pom\u011brn\u011b hodn\u011b za\u017eit\u00fdch v\u011bc\u00ed. Tentokr\u00e1t bych se cht\u011bla pod\u00edvat na eventy. A jen tak mimochodem, ne\u0159\u00edk\u00e1me jim ani \u201cceremonie\u201c (kter\u00e9 t\u00fdmy d\u011blaj\u00ed jen tak naoko, proto\u017ee Scrum \u0159\u00edk\u00e1 \u017ee se to mus\u00ed), ani \u201cmeetingy\u201c kter\u00e9 n\u011bkdo pro t\u00fdm mus\u00ed zorganizovat. Event je bli\u017e\u0161\u00ed slovu \u201chappening\u201c. Tedy n\u011b\u010demu, co se d\u011bje skoro by se dalo \u0159\u00edct samo od sebe, proto\u017ee v\u0161ichni cht\u011bj\u00ed, aby se to d\u011blo. Nikde se nic nemus\u00ed pl\u00e1novat, v\u0161ichni v\u011bd\u00ed, kde a kdy event je a \u00fa\u010dastn\u00ed se, proto\u017ee jim to p\u0159ipad\u00e1 u\u017eite\u010dn\u00e9 a smyslupln\u00e9.<\/p>\n
Event\u016f je ve Scrumu p\u011bt a se d\u011bj\u00ed pravideln\u011b. Maj\u00ed sice definovanou maxim\u00e1ln\u00ed d\u00e9lku, ale je dobr\u00e9 v\u011bd\u011bt \u017ee pro krat\u0161\u00ed Sprinty eventy trvaj\u00ed v\u00fdznamn\u011b krat\u0161\u00ed dobu. D\u016fle\u017eit\u00e1 je hlavn\u011b pravidelnost. T\u00edm, \u017ee se d\u011bj\u00ed pravideln\u011b, pom\u00e1haj\u00ed t\u00fdmu ale i z\u00e1kazn\u00edk\u016fm si na iterativn\u00ed styl pr\u00e1ce zvyknout a l\u00e9pe pl\u00e1novat, p\u0159ipravovat se, a v\u011bd\u011bt co se d\u011bje.<\/p>\n
Asi nej\u010dast\u011bj\u0161\u00ed probl\u00e9m je, \u017ee se t\u00fdmy sna\u017e\u00ed aplikovat Scrum na jednotlivce m\u00edsto na t\u00fdm a \u017ee v Product Backlogu maj\u00ed nahodil\u00e9 t\u00e1sky, nikoliv polo\u017eky backlogu definuj\u00edc\u00ed business hodnotu. V takov\u00e9m prost\u0159ed\u00ed v\u011bt\u0161ina event\u016f nefunguje, proto\u017ee jsou zalo\u017een\u00e9 na t\u00fdmov\u00e9 spolupr\u00e1ci a dod\u00e1v\u00e1n\u00ed hodnoty. Ze Sprint Planningu se stane alokace pr\u00e1ce pro jednotlivce, z Daily Scrumu se st\u00e1v\u00e1 micromanagersk\u00fd otravn\u00fd meeting, Sprint Review ukazujeme jen tak sami sob\u011b, proto\u017ee drobn\u00e9 \u010dinnosti vlastn\u011b nikoho nezaj\u00edmaj\u00ed, a na Retrospektiv\u011b si post\u011b\u017eujeme, jak n\u00e1m ten Scrum nefunguje. Nic, co byste cht\u011bli za\u017e\u00edt. A nem\u00e1 ani moc cenu nutit jednotlivce Scrum eventy vykon\u00e1vat, dokud m\u00edsto skupiny jednotlivc\u016f nem\u00e1te t\u00fdm a dokud v Product Backlogu nem\u00e1te opravdov\u00e9 polo\u017eky backlogu zam\u011b\u0159en\u00e9 na hodnotu. V moment\u011b, kdy se tyto dv\u011b v\u011bci sprav\u00ed, d\u011bj\u00ed se eventy vlastn\u011b samy od sebe, proto\u017ee t\u00fdmu pom\u00e1haj\u00ed se l\u00e9pe zorganizovat a dosahovat v\u011bt\u0161\u00ed hodnoty pro z\u00e1kazn\u00edka.<\/p>\n
Kdy\u017e budete m\u00edt t\u00fdm a relevantn\u00ed Product Backlog, zb\u00fdv\u00e1 u\u017e jen vysv\u011btlit k \u010demu jednotliv\u00e9 Scrum eventy jsou a jak by m\u011bly vypadat. A na to se pod\u00edv\u00e1me v n\u00e1sleduj\u00edc\u00edch p\u0159\u00edsp\u011bvc\u00edch: Sprint, Sprint Planning, Daily Scrum, Sprint Review, Retrospektiva<\/a>.<\/p>\n","protected":false},"excerpt":{"rendered":" Kdy\u017e to \u0159eknu jednou v\u011btou, Scrum je iterativn\u00ed a inkrement\u00e1ln\u00ed styl pr\u00e1ce, zam\u011b\u0159en\u00fd na t\u00fdmovou spolupr\u00e1ci a maximalizaci business hodnoty. Nic slo\u017eit\u00e9ho. To ale neznamen\u00e1 \u017ee ho organizace hned napoprv\u00e9 implementuj\u00ed spr\u00e1vn\u011b. Scrum toti\u017e m\u011bn\u00ed pom\u011brn\u011b hodn\u011b za\u017eit\u00fdch v\u011bc\u00ed. Tentokr\u00e1t bych se cht\u011bla pod\u00edvat na eventy. A jen tak mimochodem, ne\u0159\u00edk\u00e1me jim ani \u201cceremonie\u201c (kter\u00e9 … Continue reading “Jak na Scrum Eventy”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[11,12],"tags":[272,199,284,135,130,54,7,293,153,164],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/1174"}],"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=1174"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/1174\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=1174"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=1174"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=1174"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}