Jedn\u00edm z\u00a0\u010dast\u00fdch dotaz\u016f, kter\u00e9 dost\u00e1v\u00e1m, je jak \u0159e\u0161it ve Scrumu chyby. Je lep\u0161\u00ed m\u00edt separ\u00e1tn\u00ed t\u00fdm na chyby a separ\u00e1tn\u00ed t\u00fdm na nov\u00fd development, nebo cross-functional t\u00fdmy co pracuj\u00ed na tom, co je zrovna pot\u0159eba, tedy chyb\u00e1ch i nov\u00fdch funkcionalit\u00e1ch. Odpov\u011b\u010f je snadn\u00e1. Scrum optimalizuje business value. Definuje proto t\u00fdmy jako cross-functional, kter\u00e9 dok\u00e1\u017e\u00ed ud\u011blat jakoukoli zm\u011bnu produktu, co p\u0159in\u00e1\u0161\u00ed business value. Tedy chceme t\u00fdm (t\u00fdmy) co pracuj\u00ed na tom, co je zrovna v\u00a0produktu pot\u0159eba. A\u0165 u\u017e je to chyba, nebo nov\u00e1 feature.<\/p>\n
Prvn\u00ed, co je t\u0159eba si uv\u011bdomit je, \u017ee chyba je zase jen zm\u011bna funkcionality, tak\u017ee nen\u00ed sebemen\u0161\u00ed d\u016fvod, pro\u010d by chyby nemohly j\u00edt do Backlogu jako jak\u00e9koli jin\u00e9 v\u011bci, kter\u00e9 chcete ve va\u0161em produktu zm\u011bnit. Jsou to prost\u011b oby\u010dejn\u00e9 polo\u017eky Backlogu, kter\u00e9 by m\u011bl Product Owner prioritizovat podle business value. Kdy\u017e d\u00e1m p\u0159\u00edklad, p\u0159edstavte si, \u017ee m\u00e1te hru, kde si hr\u00e1\u010di m\u016f\u017eou nastavovat vlastn\u00ed avatary. A jedn\u00edm z\u00a0mo\u017en\u00fdch nastaven\u00ed je i barva vlas\u016f. A co \u010dert necht\u011bl, poka\u017ed\u00e9 kdy\u017e se odhl\u00e1s\u00edte, v\u00e1\u0161 avatar barvu vlas\u016f ztrat\u00ed a je zase blond. Otrava, \u017ee? Jasn\u00e1 chyba, \u0159ekli byste. Tak\u017ee ji mus\u00edme d\u00e1t do Backlogu a opravit. Dokonce na to klidn\u011b m\u016f\u017eete pou\u017e\u00edt form\u00e1t User Story a napsat:<\/p>\n
Jako hr\u00e1\u010d, <\/em><\/p>\n chci, aby si m\u016fj avatar pamatoval barvu vlas\u016f, <\/em><\/p>\n abych ji nemusel nastavovat poka\u017ed\u00e9 znova. <\/em><\/p>\n Kdy\u017e to ud\u011bl\u00e1te, stane se zaj\u00edmav\u00e1 v\u011bc. Z\u00a0n\u011b\u010deho co se mus\u00ed opravit, se stane n\u011bco, co m\u00e1 business value (abych ji nemusel nastavovat poka\u017ed\u00e9 znova) a lze prioritizovat relativn\u011b vzhledem k\u00a0ostatn\u00edm polo\u017ek\u00e1m Product Backlogu. V\u00a0tomto konkr\u00e9tn\u00edm p\u0159\u00edpad\u011b n\u00e1s to donut\u00ed zjistit, kolik hr\u00e1\u010d\u016f tuto funkcionalitu s\u00a0chybou kdy pou\u017eilo, ale hlavn\u011b kolika z\u00a0nich vadilo, \u017ee se p\u0159es noc stali blond. A kdy\u017e zjist\u00edte, \u017ee existuje jedin\u00fd hr\u00e1\u010d, kter\u00e9mu vad\u00ed, \u017ee nem\u00e1 barevn\u00e9 vlasy, tak mo\u017en\u00e1 polo\u017eka do Backlogu bude \u00fapln\u011b jin\u00e1 a bude naopak znamenat odstran\u011bn\u00ed funkcionality jako takov\u00e9.<\/p>\n Co kdy\u017e ale chyba nen\u00ed takhle ned\u016fle\u017eit\u00e1, ale je kritick\u00e1? Stoj\u00ed v\u00e1m produkce, u\u017eivatel\u00e9 nem\u016f\u017eou produkt pou\u017e\u00edvat? No tak ji opravte. \u017de v\u00e1m to naru\u0161uje Sprint? Je to v\u00fdjime\u010dn\u00e1 situace, a v\u00fdjimky se d\u011bj\u00ed. Kdy\u017e cel\u00fd t\u00fdm onemocn\u00ed, taky to berete jako v\u00fdjimku a moc to ne\u0159e\u0161\u00edte. Je t\u0159eba si uv\u011bdomit, na co klademe d\u016fraz. V\u00a0tradi\u010dn\u00edm sv\u011bt\u011b waterfallu bylo hlavn\u00ed chybu co nejrychleji opravit. T\u00edm jsme probl\u00e9m pova\u017eovali za vy\u0159e\u0161en\u00fd. V\u00a0Agiln\u00edm sv\u011bt\u011b ji oprav\u00edme, a klidn\u011b i hned jestli je tak kritick\u00e1, \u017ee nepo\u010dk\u00e1 do dal\u0161\u00edho Sprintu. Pak si odpo\u010dineme, a zamysl\u00edme se, co ud\u011bl\u00e1me p\u0159\u00ed\u0161t\u011b pro to, aby se n\u00e1m to u\u017e nestalo. Najdeme rootcause, zm\u011bn\u00edme sv\u00e9 procesy, refactorujeme, prost\u011b ud\u011bl\u00e1me cokoli, aby se takov\u00e9hle kritick\u00e9 chyby neobjevovaly, a ty, kter\u00e9 n\u00e1m p\u0159eci jen ute\u010dou, jsme mohli v\u00a0pohod\u011b pova\u017eovat za v\u00fdjimky. Proto\u017ee v\u00fdjime\u010dn\u00e9 v\u011bci se d\u011bj\u00ed v\u00fdjime\u010dn\u011b, moc n\u00e1m nevad\u00ed. Dok\u00e1\u017eeme se z\u00a0toho ot\u0159epat. Stejn\u011b jako kdy\u017e cel\u00fd t\u00fdm onemocn\u00ed. Naopak obvykl\u00e9 v\u011bci se d\u011bj\u00ed obvykle a mohou b\u00fdt p\u011bkn\u011b vy\u010derp\u00e1vaj\u00edc\u00ed.<\/p>\n","protected":false},"excerpt":{"rendered":" Jedn\u00edm z\u00a0\u010dast\u00fdch dotaz\u016f, kter\u00e9 dost\u00e1v\u00e1m, je jak \u0159e\u0161it ve Scrumu chyby. Je lep\u0161\u00ed m\u00edt separ\u00e1tn\u00ed t\u00fdm na chyby a separ\u00e1tn\u00ed t\u00fdm na nov\u00fd development, nebo cross-functional t\u00fdmy co pracuj\u00ed na tom, co je zrovna pot\u0159eba, tedy chyb\u00e1ch i nov\u00fdch funkcionalit\u00e1ch. Odpov\u011b\u010f je snadn\u00e1. Scrum optimalizuje business value. Definuje proto t\u00fdmy jako cross-functional, kter\u00e9 dok\u00e1\u017e\u00ed ud\u011blat … Continue reading “Jak \u0159e\u0161it chyby ve Scrumu?”<\/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,174,175,7,16],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/729"}],"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=729"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/729\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=729"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=729"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=729"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}