![\"\"](\"http:\/\/soch.cz\/blog\/wp-content\/uploads\/2013\/05\/sprintburndown1.png\" "\\"sprintburndown1\\"")
<\/a><\/p>\nMo\u017en\u00e1 nam\u00edtnete, \u017ee v\u00e1\u0161 t\u00fdm p\u0159eci jen n\u011bco v pr\u016fb\u011bhu dokon\u010d\u00ed, pak situace vypad\u00e1 asi tak takto\u2026 ale to v re\u00e1lu na v\u011bci nic nem\u011bn\u00ed. Nezb\u00fdv\u00e1 ne\u017e si dr\u017eet palce. Nic o v\u00fdsledku n\u00e1m takov\u00fd graf ne\u0159\u00edk\u00e1. Jen ukazuje na fakt, \u017ee nic nev\u00edme.<\/p>\n
A n\u011bkde tady se rod\u00ed my\u0161lenka implementovan\u00e1 mnoha n\u00e1stroji, \u017ee je pro Burndown graf t\u0159eba trackovat jednotliv\u00e9 \u00falohy. A abychom m\u011bli p\u0159ehled, za\u010dneme je ohodnocovat v \u010dase. Ale pozor, nen\u00ed \u010das p\u0159esn\u011b to, \u010deho jsme se v r\u00e1mci agiln\u00edch p\u0159\u00edstup\u016f sna\u017eili zbavit? Na co pak ohodnocujeme v bodech, kdy\u017e t\u00fdm vz\u00e1p\u011bt\u00ed vrac\u00edme do sv\u011bta man-days a hodin? Odhl\u00e9dneme-li od toho, \u017ee zalo\u017eit \u00falohu v syst\u00e9mu stoj\u00ed nemal\u00fd \u010das t\u00fdmu, kter\u00fd se \u010dlenov\u00e9 t\u00fdmu sna\u017e\u00ed minimalizovat tak, \u017ee zakl\u00e1daj\u00ed relativn\u011b velk\u00e9 \u00falohy, aby je pak nemuseli m\u011bnit, nebo dokonce zahodit. A tyto pak odhaduj\u00ed v hodin\u00e1ch a sv\u00e9 odhady kolik \u010dasu zb\u00fdv\u00e1, ka\u017ed\u00fd den m\u011bn\u00ed. A p\u0159ekvapiv\u011b, jsme na tom obvykle je\u0161t\u011b h\u016f\u0159, ne\u017e bez takov\u00fdch odhad\u016f. V\u011bt\u0161inu \u010dasu si mysl\u00edme, \u017ee je v\u0161echno v pohod\u011b, a ejhle, ono nebylo. M\u016f\u017ee za to mnoho faktor\u016f, psychologie a optimismus v\u00fdvoj\u00e1\u0159\u016f \u010di tester\u016f je jedn\u00edm z nich. U\u017e je to p\u0159eci skoro hotov\u00e9.<\/p>\n No a te\u010f u\u017e zb\u00fdv\u00e1 jen jeden krok \u2013 tedy m\u00edsto n\u011bjak\u00fdch odhad\u016f prost\u011b jen m\u011b\u0159it \u010das, kter\u00fd jsme na dan\u00fdch User Stories str\u00e1vili, a ten v grafu zobrazit. A sv\u011bte div se, dostaneme ka\u017ed\u00fd Sprint kr\u00e1snou line\u00e1rn\u00ed k\u0159ivku, kolik \u201chodnoty\u201c t\u00fdm ka\u017ed\u00fd den vyprodukoval. O tom, kdy to bude hotov\u00e9, takov\u00fd graf ne\u0159\u00edk\u00e1 nic, ale zato p\u011bkn\u011b vypad\u00e1, d\u00e1 se hezky reportovat a t\u00fdm m\u016f\u017ee v\u0161em dok\u00e1zat, \u017ee poctiv\u011b pracoval. Sl\u00edbila jsem vysv\u011btlen\u00ed, pro\u010d je Sprint Burndown zbyte\u010dn\u00fdm overheadem a co d\u011blat nam\u00edsto n\u011bj. Tedy za\u010dn\u011bme t\u00edm, co by m\u011blo b\u00fdt c\u00edlem – a tedy poznat, jestli t\u00fdm je\u0161t\u011b stihne dokon\u010dit User Stories, ke kter\u00fdm se v r\u00e1mci Sprintu zav\u00e1zal. Tedy v\u0161echno, co je ve Sprint Backlogu. A to co nejjednodu\u0161\u0161\u00ed cestou. Bez zbyte\u010dn\u00fdch v\u011bc\u00ed. … Continue reading “Pro\u010d je Sprint Burndown omyl”<\/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,13,14,19,273,33,7,60,98,10,82],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/439"}],"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=439"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/439\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=439"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=439"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=439"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}<\/a><\/p>\n<\/a><\/p>\n
\nTak\u017ee co s t\u00edm? Daleko snaz\u0161\u00ed metodou jak zjistit, jestli je\u0161t\u011b stihneme dan\u00e9 User Story dokon\u010dit, je ud\u011blat dobrou a p\u0159ehlednou Scrum tabuli. T\u0159i sloupce – backlog, in progress, done. P\u0159ehledn\u011b ozna\u010dit, kdo na \u010dem pracuje, a co je je\u0161t\u011b t\u0159eba dokon\u010dit. Dodr\u017eovat best practice tak, \u017ee limitujeme work in progress, tedy rozpracovanou pr\u00e1ci, sna\u017e\u00edme se v\u011bci rychle dokon\u010dovat a aby to bylo p\u011bkn\u011b vid\u011bt, rozpadnout User Stories na jednotliv\u00e9 \u010dinnosti o velikosti cca jeden den. P\u0159idat l\u00edstek s taskem trv\u00e1 n\u011bkolik vte\u0159in, zahozen\u00ed je\u0161t\u011b m\u00e9n\u011b. Je to snadn\u00e9, rychl\u00e9, efektivn\u00ed. I n\u00e1hodn\u00fd kolemjdouc\u00ed koutkem oka z takov\u00e9 tabule vid\u00ed, v jak\u00e9m je to stavu. A to se m\u016f\u017ee hodit. U\u0161et\u0159\u00edte si kup\u0159\u00edkladu otravn\u00e9 ot\u00e1zky Product Ownera, jestli to stihnete, ale hlavn\u011b, budete sami v\u011bd\u011bt, na \u010dem opravdu jste. A abych v\u00e1s nenechala bez n\u00e1vodu, o tabuli, jak ji pou\u017e\u00edvat, a jak m\u00e1 vypadat, nap\u00ed\u0161u zase p\u0159\u00ed\u0161t\u011b.<\/p>\n","protected":false},"excerpt":{"rendered":"