{"id":270,"date":"2009-02-01T21:23:10","date_gmt":"2009-02-01T19:23:10","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=270"},"modified":"2009-02-01T21:23:10","modified_gmt":"2009-02-01T19:23:10","slug":"scrum-v-extremnich-podminkach","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/scrum-v-extremnich-podminkach\/","title":{"rendered":"Scrum v extr\u00e9mn\u00edch podm\u00ednk\u00e1ch"},"content":{"rendered":"<p>Vra\u0165me se k ot\u00e1zce pro jak velk\u00fd t\u00fdm a v jak\u00fdch podm\u00ednk\u00e1ch lze Scrum proces pou\u017e\u00edt. R\u00e1da bych se pod\u011blila o svou posledn\u00ed zku\u0161enost se zav\u00e1d\u011bn\u00edm Scrum procesu v t\u00e9 nejminim\u00e1ln\u011bj\u0161\u00ed p\u0159edstaviteln\u00e9 podob\u011b. Jak si poradit s kr\u00e1tk\u00fdmi projekty v \u0159\u00e1du n\u011bkolika dn\u00ed a t\u00fdmu o velikosti jednoho \u010dlov\u011bka? Prvn\u00ed intuitivn\u00ed odpov\u011b\u010f je, \u017ee na Scrum m\u016f\u017eete zapomenout. V\u0161echny projekty by vlastn\u011b byly hotovy v r\u00e1mci jednoho Sprintu, a tedy by to asi nem\u011blo moc smysl. Jak ale za\u0159\u00eddit abychom v\u017edy p\u0159esn\u011b v\u011bd\u011bli, kde jsme a mohli rychle reagovat na t\u0159eba i drobn\u00e9 zpo\u017ed\u011bn\u00ed a probl\u00e9my? Zvl\u00e1\u0161\u0165 kdy\u017e zpo\u017ed\u011bn\u00ed jeden den u\u017e m\u016f\u017ee b\u00fdt pro \u00fasp\u011bch projektu kritick\u00e9. <\/p>\n<p>\u0158e\u0161en\u00ed je nasnad\u011b. Nic n\u00e1m vlastn\u011b nebr\u00e1n\u00ed Scrum proces pou\u017e\u00edt, jen se mus\u00ed vhodn\u011b upravit d\u00e9lka Sprintu. Prvn\u00edm \u00fakolem bylo vytvo\u0159en\u00ed Backlogu. Jednotliv\u00e9 \u00falohy, ohodnoceny body, byly rozd\u011bleny na celky v \u0159\u00e1du p\u00e1r hodin. D\u00e9lku Sprintu jsme nastavili na p\u016fl dne. V takto kr\u00e1tce nastaven\u00e9m Sprint cyklu u\u017e se nic neschov\u00e1. \u017d\u00e1dn\u00fd del\u0161\u00ed ob\u011bd, rann\u00ed k\u00e1va, ani probl\u00e9m se \u0161patn\u00fdm ohodnocen\u00edm \u00faloh. Nic. Ale na druhou stranu, alespo\u0148 m\u00e1te informace o tom, \u017ee projekt z\u00edtra nebude, ji\u017e dnes v poledne. A tedy m\u016f\u017eete zareagovat. Vy\u017e\u00e1dat si pomoc kolegy, zavolat z\u00e1kazn\u00edkovi a domluvit si pozd\u011bj\u0161\u00ed dod\u00e1n\u00ed. Po\u0159\u00e1d lep\u0161\u00ed ne\u017e volat zp\u011btn\u011b \u017ee jste to zase nestihli.<\/p>\n<p>Tak\u017ee jak to vypad\u00e1 v praxi. Ka\u017ed\u00fd p\u00e1tek se ud\u011bl\u00e1 pl\u00e1n na n\u00e1sleduj\u00edc\u00ed t\u00fdden. V kalend\u00e1\u0159i rezervace \u010dasu na jednotliv\u00e9 projekty. Pro v\u0161echny t\u00fdmy (i kdy\u017e t\u00fdm o jednom \u010dlov\u011bku moc t\u00fdmem nen\u00ed). Ka\u017ed\u00fd p\u016flden se potom updatuj\u00ed Burndowny jednotliv\u00fdch projekt\u016f, a p\u0159\u00edpadn\u011b kalend\u00e1\u0159, abychom v\u011bd\u011bli, pro\u010d se pl\u00e1n zm\u011bnil. Docela hodn\u011b drsn\u00e9. Ale hlavn\u011b, funguje to naprosto skv\u011ble. Vzhledem k rychlosti v\u00fdroby produktu, je to ale asi jedin\u00e1 mo\u017enost. Scrum meeting asi sta\u010d\u00ed jednou denn\u011b, na prodiskutov\u00e1n\u00ed progresu a pl\u00e1nu na n\u00e1sleduj\u00edc\u00ed den. <\/p>\n<p>Je\u0161t\u011b jedna v\u011bc. P\u0159esunuli jsme Burndowny na GoogleDocs, na zm\u011bnu m\u00e1me nastaven\u00e9 automatick\u00e9 emaily a tak sta\u010d\u00ed jen sledovat na mailu co se d\u011bje. <\/p>\n","protected":false},"excerpt":{"rendered":"<p>Vra\u0165me se k ot\u00e1zce pro jak velk\u00fd t\u00fdm a v jak\u00fdch podm\u00ednk\u00e1ch lze Scrum proces pou\u017e\u00edt. R\u00e1da bych se pod\u011blila o svou posledn\u00ed zku\u0161enost se zav\u00e1d\u011bn\u00edm Scrum procesu v t\u00e9 nejminim\u00e1ln\u011bj\u0161\u00ed p\u0159edstaviteln\u00e9 podob\u011b. Jak si poradit s kr\u00e1tk\u00fdmi projekty v \u0159\u00e1du n\u011bkolika dn\u00ed a t\u00fdmu o velikosti jednoho \u010dlov\u011bka? Prvn\u00ed intuitivn\u00ed odpov\u011b\u010f je, \u017ee na &hellip; <a href=\"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/scrum-v-extremnich-podminkach\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Scrum v extr\u00e9mn\u00edch podm\u00ednk\u00e1ch&#8221;<\/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":[13,14,273,7],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/270"}],"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=270"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/270\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=270"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=270"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=270"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}