Specifikace v\u00a0takov\u00e9m tom klasick\u00e9m slova smyslu je mrtv\u00e1. Agiln\u00ed prost\u0159ed\u00ed se daleko v\u00edce zaj\u00edm\u00e1 o to co je to minimum, kter\u00e9 mus\u00edme implementovat abychom dodali maximum business value, ne\u017e co v\u0161echno mus\u00edme naimplementovat abychom se do n\u011bjak\u00e9 t\u00e9 business hodnoty trefili. Jak \u0159\u00edkal jeden m\u016fj zn\u00e1m\u00fd ScrumMaster, klasick\u00e9 organizace \u010dasto se zav\u00e1zan\u00fdma o\u010dima st\u0159\u00edl\u00ed na kachny. A proto\u017ee st\u0159\u00edl\u00ed hodn\u011b, ob\u010das n\u011bjakou tref\u00ed. Agiln\u00ed organizace pochopily, \u017ee m\u00e9n\u011b je n\u011bkdy v\u00edce, a p\u0159estali tr\u00e1vit hodiny \u010dasu specifikac\u00ed toho co v\u0161echno bychom taky mohli ud\u011blat. Na m\u00edsto toho se v\u00a0r\u00e1mci Inspect and Adapt principu a \u010dast\u00e9 zp\u011btn\u00e9 vazby sna\u017e\u00ed pochopit co p\u0159in\u00e1\u0161\u00ed nejvy\u0161\u0161\u00ed business hodnotu a na tu se soust\u0159ed\u00ed. Ano, je to zm\u011bna, a bude to t\u011b\u017ek\u00e9, ale o tom Agile pr\u00e1v\u011b je.<\/p>\n
\u010cast\u00fdm nepochopen\u00edm je \u017ee organizace maj\u00ed pocit, \u017ee v\u00a0r\u00e1mci UserStory mus\u00ed ps\u00e1t detailn\u00ed popis, jak danou pot\u0159ebu adresovat nap\u0159\u00edklad formou Akcepta\u010dn\u00edch krit\u00e9ri\u00ed. To ale v\u016fbec nepat\u0159\u00ed do UserStory. Ta by m\u011bla pouze definovat pot\u0159ebu konkr\u00e9tn\u00edho u\u017eivatele\/persony,\u00a0\u2018jak\u2019ji budeme \u0159e\u0161it je na dohod\u011b t\u00fdmu v\u00a0r\u00e1mci Sprintu. Ano, pre-rekvizitou je pochopen\u00ed toho co d\u011bl\u00e1me cel\u00fdm t\u00fdmem, tedy dobr\u00fd Product Owner a Backlog Refinement. Jinak v\u00e1m ale Scrum ani Agile fungovat nebude. Agile i Scrum je customer centric, business driven. Tak\u017ee zapome\u0148te na specifikaci, zkuste se zc\u00edtit do z\u00e1kazn\u00edk\u016f a pochopte jejich pot\u0159eby. Jen tak dos\u00e1hnete lep\u0161\u00edch v\u00fdsledk\u016f.<\/p>\n
Dal\u0161\u00ed v\u011bc\u00ed, kter\u00e1 se d\u0159\u00edve \u010di pozd\u011bji octne na smeti\u0161ti d\u011bjin, jsou projekty. Stejn\u011b jako role project managera. Ale o tom t\u0159eba zase p\u0159\u00ed\u0161t\u011b. Projekt je toti\u017e jen kontejner, v\u00a0jeho\u017e r\u00e1mci \u0159\u00edd\u00edme a zpracov\u00e1v\u00e1me pr\u00e1ci v\u00a0klasick\u00e9m sv\u011bt\u011b. V agiln\u00edm sv\u011bt\u011b n\u00e1m stejnou slu\u017ebu d\u011bl\u00e1 Product Backlog, jeho polo\u017eky a kr\u00e1tk\u00e9 Sprinty\/iterace se zp\u011btnou vazbou. Product Backlog je nav\u00edc daleko l\u00e9pe optimalizovan\u00fd na vysokou adaptivnost syst\u00e9mu, reakce na zm\u011bny a obecn\u011b pr\u00e1ci v\u00a0komplexn\u00edm prost\u0159ed\u00ed. A tak d\u016fle\u017eitost sv\u011bta produkt\u016f postupn\u011b uvad\u00e1. \u017de jste projektov\u00fdmi managery? Ur\u010dit\u011b se pro v\u00e1s najde uplatn\u011bn\u00ed. Project manage\u0159i se nej\u010dast\u011bji st\u00e1vaj\u00ed stakeholdery, kte\u0159\u00ed pom\u00e1haj\u00ed t\u00fdm\u016fm pochopit kontext z\u00e1kazn\u00edk\u016f, \u010dast\u00e1 b\u00fdv\u00e1 i zm\u011bna na Product Ownera, v\u00fdjime\u010dn\u011b ScrumMastera. V\u011bt\u0161inou plat\u00ed, \u017ee kdy\u017e jste byli pot\u0159eba v\u00a0p\u0159edchoz\u00ed neagiln\u00ed struktu\u0159e, budete pot\u0159eba i v\u00a0t\u00e9 nov\u00e9. Jen va\u0161e role a pr\u00e1ce se zm\u011bn\u00ed. Ale to plat\u00ed nejen pro projektov\u00e9 managery, ale i developery, testery, analytiky, a managery. V\u00a0agiln\u00edm sv\u011bt\u011b je v\u0161echno jinak a jednoduch\u00fd mapping neexistuje. Agile je zm\u011bna mindsetu, a ta za\u010d\u00edn\u00e1 ve va\u0161\u00ed hlav\u011b.\u00a0\ud83d\ude42<\/p>\n","protected":false},"excerpt":{"rendered":"
Specifikace Specifikace v\u00a0takov\u00e9m tom klasick\u00e9m slova smyslu je mrtv\u00e1. Agiln\u00ed prost\u0159ed\u00ed se daleko v\u00edce zaj\u00edm\u00e1 o to co je to minimum, kter\u00e9 mus\u00edme implementovat abychom dodali maximum business value, ne\u017e co v\u0161echno mus\u00edme naimplementovat abychom se do n\u011bjak\u00e9 t\u00e9 business hodnoty trefili. Jak \u0159\u00edkal jeden m\u016fj zn\u00e1m\u00fd ScrumMaster, klasick\u00e9 organizace \u010dasto se zav\u00e1zan\u00fdma o\u010dima st\u0159\u00edl\u00ed … Continue reading “Na kter\u00e9 v\u011bci m\u016f\u017eete v\u00a0Agiln\u00edm prost\u0159ed\u00ed zapomenout”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[226,272,225,94,7,153,16,103,160],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/865"}],"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=865"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/865\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=865"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=865"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=865"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}