{"id":373,"date":"2011-12-11T12:56:17","date_gmt":"2011-12-11T11:56:17","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=373"},"modified":"2011-12-11T12:56:17","modified_gmt":"2011-12-11T11:56:17","slug":"kdo-pise-user-story-a-kdo-tasky","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/kdo-pise-user-story-a-kdo-tasky\/","title":{"rendered":"Kdo p\u00ed\u0161e User Story? A kdo tasky?"},"content":{"rendered":"<p>A jako pokra\u010dov\u00e1n\u00ed v m\u00e9m miniseri\u00e1lu o agiln\u00edch metod\u00e1ch, Scrum procesu a konkr\u00e9tn\u011b User Stories je odpov\u011b\u010f na ot\u00e1zku kdo p\u00ed\u0161e User Story?<\/p>\n<p>Tak jako obvykle, navrhnout User Story m\u016f\u017ee kdokoliv. Libovoln\u00fd \u010dlen t\u00fdmu, v\u00fdvoj\u00e1\u0159, tester. Nicm\u00e9n\u011b Scrum zav\u00e1d\u00ed roli Product Ownera, kter\u00fd je za cel\u00fd backlog a User Story v n\u011bm zodpov\u011bdn\u00fd. A proto je Product Owner ten, kdo User Story nakonec do backlogu akceptuje, a p\u0159i\u0159ad\u00ed j\u00ed v z\u00e1vislosti na business value prioritu. Product Owner je tedy ve Scrumu \u010dasto ten, co User Story definuje, n\u00e1sledn\u011b je ale diskutuje jak s produktov\u00fdm t\u00fdmem tak se Scrum t\u00fdmem kter\u00fd jednotliv\u00e9 User Story ohodnocuje.<\/p>\n<p>A kdy se maj\u00ed jednotliv\u00e9 User Story rozd\u011blit na tasky\/\u00falohy? Idealn\u011b b\u011bhem planningu, maxim\u00e1ln\u011b prvn\u00ed den Sprintu. Kdy\u017e to ud\u011bl\u00e1te pozd\u011bji \u010di v\u016fbec, riskujete, \u017ee v\u011bt\u0161ina \u010dlen\u016f t\u00fdmu nebude v\u011bd\u011bt, z \u010deho se jednotliv\u00e9 User Story sest\u00e1vaj\u00ed, co n\u00e1m jako t\u00fdmu je\u0161t\u011b chyb\u00ed dokon\u010dit a jak jsme daleko.<\/p>\n<p>Co je task? Task neboli \u00faloha je n\u011bjak\u00e1 jednotlivost, kter\u00e1 se mus\u00ed ud\u011blat, aby User Story p\u0159in\u00e1\u0161ela o\u010dek\u00e1vanou hodnotu. Tedy pro User Story &#8220;<em>jako mana\u017eer, chci m\u00edt evidenci zam\u011bstnanc\u016f, abych m\u011bl rychl\u00fd p\u0159ehled o v\u0161ech lidech ve firm\u011b i detailu konkr\u00e9tn\u00edch pracovn\u00edk\u016f<\/em>.&#8221; to m\u016f\u017ee b\u00fdt nap\u0159. zalo\u017een\u00ed tabulky a \u010d\u00edseln\u00edk\u016f, zobrazen\u00ed dat z db na obrazovku v browsu, filtrace, zobrazen\u00ed jedn\u00e9 detailn\u00ed polo\u017eky zam\u011bstnance, grafick\u00fd design obrazovek, test. Ka\u017ed\u00e1 \u00faloha by nem\u011bla b\u00fdt del\u0161\u00ed, ne\u017e \u0159ekn\u011bme dva dny a krat\u0161\u00ed ne\u017e p\u016fl den u\u017e je mo\u017en\u00e1 zbyte\u010dn\u00fd detail, nicm\u00e9n\u011b m\u016f\u017ee m\u00edt smysl si i takovou \u00falohu zaznamenat, abychom na ni nezapomn\u011bli. V pr\u016fm\u011bru by ka\u017ed\u00e1 \u00faloha m\u011bla b\u00fdt tak asi na den pr\u00e1ce, co\u017e n\u00e1m pak usnad\u0148uje denn\u00ed standup meeting, kde je pak snaz\u0161\u00ed definovat, co opravdu dokon\u010d\u00edme. <\/p>\n<p>Na za\u010d\u00e1tku jsme psala, \u017ee za User Story je zodpov\u011bdn\u00fd Product Owner, potom za rozpad t\u011bchto User Story na tasky \/ \u00falohy je naopak zodpov\u011bdn\u00fd t\u00fdm a jsou tu jen pro intern\u00ed pot\u0159eby t\u00fdmu. Aby v\u0161ichni v\u011bd\u011bli jak daleko je\u0161t\u011b jsou od c\u00edle a to i bez slo\u017eit\u00e9ho ohodnocov\u00e1n\u00ed jednotliv\u00fdch \u00faloh a kreslen\u00ed Sprint Burndownu. V\u0161e je pak na prvn\u00ed pohled vid\u011bt z tabule &#8211; Scrum Boardu.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A jako pokra\u010dov\u00e1n\u00ed v m\u00e9m miniseri\u00e1lu o agiln\u00edch metod\u00e1ch, Scrum procesu a konkr\u00e9tn\u011b User Stories je odpov\u011b\u010f na ot\u00e1zku kdo p\u00ed\u0161e User Story? Tak jako obvykle, navrhnout User Story m\u016f\u017ee kdokoliv. Libovoln\u00fd \u010dlen t\u00fdmu, v\u00fdvoj\u00e1\u0159, tester. Nicm\u00e9n\u011b Scrum zav\u00e1d\u00ed roli Product Ownera, kter\u00fd je za cel\u00fd backlog a User Story v n\u011bm zodpov\u011bdn\u00fd. A proto &hellip; <a href=\"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/kdo-pise-user-story-a-kdo-tasky\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Kdo p\u00ed\u0161e User Story? A kdo tasky?&#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":[15,57,7,10,82],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/373"}],"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=373"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/373\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=373"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=373"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=373"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}