{"id":1310,"date":"2026-07-13T09:42:27","date_gmt":"2026-07-13T07:42:27","guid":{"rendered":"https:\/\/agilebrothers.cz\/blog\/?p=1310"},"modified":"2026-07-13T16:13:35","modified_gmt":"2026-07-13T14:13:35","slug":"requirement-feature-story-hierarchie-jira","status":"publish","type":"post","link":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/","title":{"rendered":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira"},"content":{"rendered":"\n\n<p class=\"wp-block-paragraph\">Na prvn\u00ed pohled vypadalo v\u0161echno spr\u00e1vn\u011b. V Jira existoval Requirement, pod n\u00edm Feature a pod n\u00ed n\u011bkolik Stories. Polo\u017eky byly propojen\u00e9, m\u011bly p\u0159i\u0159azen\u00e9 vlastn\u00edky a zobrazovaly se ve spr\u00e1vn\u00fdch reportech.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159esto t\u00fdm b\u011bhem refinementu nedok\u00e1zal odpov\u011bd\u011bt na n\u011bkolik z\u00e1kladn\u00edch ot\u00e1zek:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Jak\u00fd probl\u00e9m z\u00e1kazn\u00edka vlastn\u011b \u0159e\u0161\u00edme?<\/li>\n<li>Co u\u017e bylo schv\u00e1leno a o \u010dem se st\u00e1le diskutuje?<\/li>\n<li>Je navr\u017een\u00e9 \u0159e\u0161en\u00ed povinnou sou\u010d\u00e1st\u00ed po\u017eadavku, nebo pouze jednou z mo\u017enost\u00ed?<\/li>\n<li>Co p\u0159esn\u011b m\u00e1 t\u00fdm dodat jako prvn\u00ed pou\u017eiteln\u00fd v\u00fdsledek?<\/li>\n<li>Podle \u010deho pozn\u00e1me, \u017ee byla Feature \u00fasp\u011b\u0161n\u011b dokon\u010dena?<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Kdy\u017e jsme otev\u0159eli jednotliv\u00e9 polo\u017eky, uk\u00e1zalo se, \u017ee Requirement, Feature i Stories obsahuj\u00ed z velk\u00e9 \u010d\u00e1sti stejn\u00fd text. Informace se mezi \u00farovn\u011bmi p\u0159edev\u0161\u00edm kop\u00edrovaly. Nevznikalo nov\u00e9 porozum\u011bn\u00ed ani nov\u00e9 rozhodnut\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Organizace m\u011bla spr\u00e1vn\u011b nakreslenou hierarchii. Nem\u011bla v\u0161ak funk\u010dn\u00ed syst\u00e9m, kter\u00fd by p\u0159ev\u00e1d\u011bl pot\u0159ebu stakeholdera do konkr\u00e9tn\u00edho v\u00fdsledku a n\u00e1sledn\u011b do pr\u00e1ce t\u00fdmu.<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Requirement, Feature a Story nemaj\u00ed b\u00fdt jen t\u0159i r\u016fzn\u00e9 velikosti ticketu. Ka\u017ed\u00e1 \u00farove\u0148 m\u00e1 slou\u017eit jin\u00e9mu rozhodnut\u00ed.<\/p><\/blockquote>\n\n\n\n\n<h2 class=\"wp-block-heading\">Requirement, Feature a Story nejsou jen velk\u00e1, st\u0159edn\u00ed a mal\u00e1 polo\u017eka<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">\u010cast\u00e1 definice hierarchie zn\u00ed p\u0159ibli\u017en\u011b takto:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Requirement je velk\u00fd po\u017eadavek.<\/li>\n<li>Feature je men\u0161\u00ed \u010d\u00e1st po\u017eadavku.<\/li>\n<li>Story je mal\u00fd \u00fakol pro t\u00fdm.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takov\u00e9 vysv\u011btlen\u00ed je jednoduch\u00e9, ale pro praktick\u00e9 \u0159\u00edzen\u00ed pr\u00e1ce nesta\u010d\u00ed. Velikost toti\u017e nen\u00ed hlavn\u00edm rozd\u00edlem mezi jednotliv\u00fdmi \u00farovn\u011bmi.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pom\u011brn\u011b mal\u00fd po\u017eadavek m\u016f\u017ee b\u00fdt realizov\u00e1n jednou Story. Jin\u00fd Requirement m\u016f\u017ee v\u00e9st k n\u011bkolika Features pro v\u00edce produktov\u00fdch oblast\u00ed. N\u011bkter\u00e1 Feature bude vy\u017eadovat deset Stories, jin\u00e1 dv\u011b. A Story nemus\u00ed b\u00fdt mal\u00e1 proto, \u017ee stoj\u00ed nejn\u00ed\u017ee v Jira. Mal\u00e1 m\u00e1 b\u00fdt proto, aby ji t\u00fdm dok\u00e1zal v kr\u00e1tk\u00e9m \u010dase dokon\u010dit a ov\u011b\u0159it.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">U\u017eite\u010dn\u011bj\u0161\u00ed je proto definovat jednotliv\u00e9 \u00farovn\u011b podle ot\u00e1zky, kterou maj\u00ed zodpov\u011bd\u011bt:<\/p>\n\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>\u00darove\u0148<\/th><th>Hlavn\u00ed ot\u00e1zka<\/th><th>Typick\u00fd v\u00fdsledek<\/th><\/tr><\/thead><tbody><tr><td><strong>Requirement<\/strong><\/td><td>Co pot\u0159ebujeme zm\u011bnit a pro\u010d?<\/td><td>Objasn\u011bn\u00e1 pot\u0159eba<\/td><\/tr><tr><td><strong>Feature<\/strong><\/td><td>Jak\u00fd ucelen\u00fd v\u00fdsledek se rozhodneme dodat?<\/td><td>Rozhodnut\u00fd rozsah dod\u00e1vky<\/td><\/tr><tr><td><strong>Story<\/strong><\/td><td>Jak\u00fd mal\u00fd a ov\u011b\u0159iteln\u00fd inkrement t\u00fdm dokon\u010d\u00ed?<\/td><td>Implementovateln\u00e1 polo\u017eka t\u00fdmov\u00e9ho backlogu<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nejde o univerz\u00e1ln\u00ed definici, kterou mus\u00ed ka\u017ed\u00e1 firma p\u0159evz\u00edt. Organizace m\u016f\u017ee pou\u017e\u00edvat jin\u00e9 n\u00e1zvy: Initiative, Epic, Capability, Feature, Enabler, Story nebo Product Backlog Item. Podstatn\u00e9 je, aby jednotliv\u00e9 \u00farovn\u011b p\u0159edstavovaly r\u016fzn\u00e9 druhy rozhodnut\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Podobn\u00fd princip popisujeme tak\u00e9 v \u010dl\u00e1nku <a href=\"https:\/\/agilebrothers.cz\/blog\/tri-urovne-rizeni-prace-bez-frameworku-investice-%E2%86%92-doruceni-%E2%86%92-inkrement\/\">T\u0159i \u00farovn\u011b \u0159\u00edzen\u00ed pr\u00e1ce bez frameworku: investice \u2192 doru\u010den\u00ed \u2192 inkrement<\/a>. Jakmile se do jednoho backlogu prom\u00edchaj\u00ed investi\u010dn\u00ed, doru\u010dovac\u00ed a t\u00fdmov\u00e1 rozhodnut\u00ed, leadership za\u010dne \u0159e\u0161it p\u0159\u00edli\u0161 velk\u00fd detail a t\u00fdmy naopak ztr\u00e1cej\u00ed pot\u0159ebn\u00fd kontext.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Requirement: co pot\u0159ebujeme zm\u011bnit a pro\u010d<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Requirement m\u00e1 zachytit pot\u0159ebu, nikoliv p\u0159edem nadiktovat kompletn\u00ed \u0159e\u0161en\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dob\u0159e objasn\u011bn\u00fd Requirement by m\u011bl typicky vysv\u011btlit:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>koho se pot\u0159eba t\u00fdk\u00e1,<\/li>\n<li>jak\u00e1 je sou\u010dasn\u00e1 situace,<\/li>\n<li>co se m\u00e1 zm\u011bnit,<\/li>\n<li>pro\u010d je zm\u011bna d\u016fle\u017eit\u00e1,<\/li>\n<li>jak\u00fd v\u00fdsledek stakeholder o\u010dek\u00e1v\u00e1,<\/li>\n<li>jak\u00e1 omezen\u00ed mus\u00edme respektovat,<\/li>\n<li>kter\u00e9 ot\u00e1zky zat\u00edm z\u016fst\u00e1vaj\u00ed otev\u0159en\u00e9.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159edstavme si nap\u0159\u00edklad po\u017eadavek:<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>P\u0159idejte na hlavn\u00ed str\u00e1nku tla\u010d\u00edtko \u201eZm\u011bnit adresu\u201c a po\u0161lete zadan\u00e9 \u00fadaje do syst\u00e9mu X.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Form\u00e1ln\u011b jde o po\u017eadavek. Ve skute\u010dnosti v\u0161ak obsahuje ji\u017e navr\u017een\u00e9 u\u017eivatelsk\u00e9 rozhran\u00ed, um\u00edst\u011bn\u00ed prvku i technickou integraci. Nen\u00ed jasn\u00e9, jak\u00fd probl\u00e9m m\u00e1 zm\u011bna vy\u0159e\u0161it.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159i rozhovoru se stakeholderem m\u016f\u017eeme zjistit, \u017ee skute\u010dn\u00e1 pot\u0159eba zn\u00ed jinak:<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Z\u00e1kazn\u00edci mus\u00ed p\u0159i zm\u011bn\u011b doru\u010dovac\u00ed adresy volat na podporu. Chceme umo\u017enit samoobslu\u017enou zm\u011bnu adresy a sn\u00ed\u017eit po\u010det souvisej\u00edc\u00edch kontakt\u016f z\u00e1kaznick\u00e9ho centra.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Tato formulace ponech\u00e1v\u00e1 prostor pro hled\u00e1n\u00ed vhodn\u00e9ho \u0159e\u0161en\u00ed. Sou\u010dasn\u011b vysv\u011btluje o\u010dek\u00e1van\u00fd v\u00fdsledek. Tla\u010d\u00edtko i syst\u00e9m X mohou b\u00fdt sou\u010d\u00e1st\u00ed \u0159e\u0161en\u00ed, ale nejsou automaticky nedotknutelnou sou\u010d\u00e1st\u00ed p\u016fvodn\u00ed pot\u0159eby.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Requirement nemus\u00ed v\u017edy vytvo\u0159it Feature<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Hierarchie by nem\u011bla fungovat jako povinn\u00e1 v\u00fdrobn\u00ed linka, kterou mus\u00ed proj\u00edt ka\u017ed\u00fd ticket.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Po objasn\u011bn\u00ed Requirementu m\u016f\u017ee nastat n\u011bkolik r\u016fzn\u00fdch situac\u00ed:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>po\u017eadavek ned\u00e1v\u00e1 dostate\u010dnou hodnotu a nebude realizov\u00e1n,<\/li>\n<li>je duplicitn\u00ed a slou\u010d\u00ed se s jin\u00fdm po\u017eadavkem,<\/li>\n<li>vy\u0159e\u0161\u00ed jej ji\u017e existuj\u00edc\u00ed Feature,<\/li>\n<li>jde o malou zm\u011bnu, kter\u00e1 m\u016f\u017ee p\u0159ej\u00edt p\u0159\u00edmo do Story,<\/li>\n<li>jde o v\u011bt\u0161\u00ed v\u00fdsledek, pro kter\u00fd vznikne jedna nebo v\u00edce Features,<\/li>\n<li>nejprve pot\u0159ebujeme discovery, technick\u00e9 posouzen\u00ed nebo experiment.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud je pravidlem, \u017ee ka\u017ed\u00fd Requirement mus\u00ed automaticky vytvo\u0159it Feature a ka\u017ed\u00e1 Feature mus\u00ed obsahovat n\u011bkolik Stories, organizace si nevytv\u00e1\u0159\u00ed transparentnost. Vytv\u00e1\u0159\u00ed si povinn\u00e9 administrativn\u00ed mezikroky.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Feature: jak\u00fd ucelen\u00fd v\u00fdsledek se rozhodneme dodat<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature p\u0159edstavuje rozhodnut\u00ed o dod\u00e1vce. Pot\u0159eba u\u017e byla dostate\u010dn\u011b pochopena a nyn\u00ed ur\u010dujeme, jak\u00fd konkr\u00e9tn\u00ed v\u00fdsledek m\u00e1 produkt nebo \u0159e\u0161en\u00ed nab\u00eddnout.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">V na\u0161em p\u0159\u00edkladu m\u016f\u017ee Feature zn\u00edt nap\u0159\u00edklad takto:<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Z\u00e1kazn\u00edk m\u016f\u017ee v z\u00e1kaznick\u00e9m port\u00e1lu bezpe\u010dn\u011b zm\u011bnit doru\u010dovac\u00ed adresu bez kontaktov\u00e1n\u00ed podpory.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takto formulovan\u00e1 Feature popisuje ucelenou schopnost. Je\u0161t\u011b nep\u0159edepisuje ka\u017ed\u00fd technick\u00fd krok, ale vytv\u00e1\u0159\u00ed dostate\u010dn\u011b konkr\u00e9tn\u00ed r\u00e1mec pro prioritizaci, rozd\u011blen\u00ed pr\u00e1ce a ov\u011b\u0159en\u00ed v\u00fdsledku.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature by m\u011bla typicky objasnit:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>komu m\u00e1 v\u00fdsledek pomoci,<\/li>\n<li>jak\u00e9 chov\u00e1n\u00ed nebo schopnost se zm\u011bn\u00ed,<\/li>\n<li>co je sou\u010d\u00e1st\u00ed rozsahu a co u\u017e ne,<\/li>\n<li>jak\u00fdm zp\u016fsobem v\u00fdsledek ov\u011b\u0159\u00edme,<\/li>\n<li>jak\u00e1 rizika a z\u00e1vislosti zn\u00e1me,<\/li>\n<li>jak lze dod\u00e1vku rozd\u011blit do men\u0161\u00edch inkrement\u016f.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jako u\u017eite\u010dnou inspiraci lze vyu\u017e\u00edt tak\u00e9 <a href=\"https:\/\/framework.scaledagile.com\/features-and-capabilities\">pojet\u00ed Features ve Scaled Agile Frameworku<\/a>. SAFe pracuje s Feature jako s polo\u017ekou ART Backlogu, kter\u00e1 p\u0159in\u00e1\u0161\u00ed hodnotu a m\u00e1 b\u00fdt realizovateln\u00e1 v r\u00e1mci jednoho PI. Nen\u00ed nutn\u00e9 toto pravidlo mechanicky p\u0159evz\u00edt, ale nut\u00ed n\u00e1s uva\u017eovat o Feature jako o v\u00fdsledku s omezen\u00fdm \u010dasov\u00fdm horizontem, nikoliv jako o dlouhodob\u00e9m kontejneru na libovoln\u00e9 mno\u017estv\u00ed pr\u00e1ce.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Feature nen\u00ed ob\u00e1lka na nesouvisej\u00edc\u00ed Stories<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">V mnoha organizac\u00edch vznikaj\u00ed takzvan\u00e9 container Features. Nemaj\u00ed vlastn\u00ed z\u00e1kaznick\u00fd ani business v\u00fdsledek. Existuj\u00ed p\u0159edev\u0161\u00edm proto, aby se t\u00fdmov\u00e9 Stories zobrazily v programov\u00e9m reportu nebo aby ka\u017ed\u00e1 Story m\u011bla povinn\u00e9ho rodi\u010de.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Typick\u00e9 n\u00e1zvy mohou vypadat nap\u0159\u00edklad takto:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Frontend pr\u00e1ce pro PI 3,<\/li>\n<li>Backend improvements,<\/li>\n<li>Technick\u00e9 zm\u011bny t\u00fdmu A,<\/li>\n<li>Implementace po\u017eadavk\u016f trhu,<\/li>\n<li>Ostatn\u00ed zm\u011bny z\u00e1kaznick\u00e9ho port\u00e1lu.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takov\u00e1 polo\u017eka m\u016f\u017ee b\u00fdt z technick\u00fdch nebo reportingov\u00fdch d\u016fvod\u016f do\u010dasn\u011b pot\u0159ebn\u00e1. Nem\u011bla by se ale zam\u011b\u0148ovat za skute\u010dnou Feature. Ze samotn\u00e9ho n\u00e1zvu ani obsahu toti\u017e nelze poznat, jak\u00fd v\u00fdsledek se m\u00e1 zm\u011bnit pro z\u00e1kazn\u00edka nebo organizaci.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Story: jak\u00fd ov\u011b\u0159iteln\u00fd inkrement t\u00fdm dokon\u010d\u00ed<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Story je jednotka t\u00fdmov\u00e9 spolupr\u00e1ce a dod\u00e1vky. M\u00e1 b\u00fdt dostate\u010dn\u011b mal\u00e1, aby ji t\u00fdm dok\u00e1zal v kr\u00e1tk\u00e9m \u010dase dokon\u010dit, a dostate\u010dn\u011b smyslupln\u00e1, aby \u0161el jej\u00ed v\u00fdsledek ov\u011b\u0159it.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature se samoobslu\u017enou zm\u011bnou adresy m\u016f\u017eeme rozd\u011blit nap\u0159\u00edklad na tyto Stories:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>z\u00e1kazn\u00edk vid\u00ed svou aktu\u00e1ln\u00ed doru\u010dovac\u00ed adresu,<\/li>\n<li>z\u00e1kazn\u00edk zad\u00e1 a nech\u00e1 ov\u011b\u0159it novou adresu,<\/li>\n<li>z\u00e1kazn\u00edk zm\u011bnu bezpe\u010dn\u011b potvrd\u00ed,<\/li>\n<li>z\u00e1kazn\u00edk obdr\u017e\u00ed potvrzen\u00ed o proveden\u00e9 zm\u011bn\u011b,<\/li>\n<li>pracovn\u00edk podpory vid\u00ed auditn\u00ed stopu zm\u011bny.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Ka\u017ed\u00e1 polo\u017eka p\u0159edstavuje pozorovatelnou \u010d\u00e1st chov\u00e1n\u00ed syst\u00e9mu. Naproti tomu n\u00e1sleduj\u00edc\u00ed rozpad by byl v\u00fdrazn\u011b problemati\u010dt\u011bj\u0161\u00ed:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Story pro anal\u00fdzu,<\/li>\n<li>Story pro n\u00e1vrh datab\u00e1ze,<\/li>\n<li>Story pro frontend,<\/li>\n<li>Story pro backend,<\/li>\n<li>Story pro testov\u00e1n\u00ed.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takov\u00e9 polo\u017eky mohou b\u00fdt u\u017eite\u010dn\u00e9 jako \u00fakoly uvnit\u0159 t\u00fdmu, ale jednotliv\u011b nep\u0159edstavuj\u00ed dokon\u010den\u00fd inkrement. Hodnota vznikne a\u017e ve chv\u00edli, kdy jsou hotov\u00e9 v\u0161echny. Rozpracovanost roste a ka\u017ed\u00e1 specializace optimalizuje svou \u010d\u00e1st, zat\u00edmco skute\u010dn\u00fd v\u00fdsledek st\u00e1le \u010dek\u00e1.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Scrum mimochodem nep\u0159edepisuje povinnou hierarchii Requirement\u2013Feature\u2013Story. <a href=\"https:\/\/scrumguides.org\/scrum-guide.html\">Scrum Guide<\/a> pracuje obecn\u011b s polo\u017ekami Product Backlogu a jejich pr\u016fb\u011b\u017en\u00fdm zp\u0159es\u0148ov\u00e1n\u00edm. User Story je u\u017eite\u010dn\u00e1 technika, nikoliv povinn\u00fd objekt Scrumu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Stejn\u011b tak by Story nem\u011bla b\u00fdt pova\u017eov\u00e1na za p\u0159ipravenou jen proto, \u017ee m\u00e1 vypln\u011bn\u00e1 povinn\u00e1 pole nebo p\u0159id\u011blen\u00fd odhad. Jak ukazujeme v \u010dl\u00e1nku <a href=\"https:\/\/agilebrothers.cz\/blog\/kdyz-odhad-neni-skutecny-odhad-proc-tymovy-souhlas-nestaci\/\">Kdy\u017e odhad nen\u00ed skute\u010dn\u00fd odhad<\/a>, \u010d\u00edslo m\u016f\u017ee vzniknout i bez skute\u010dn\u00e9ho t\u00fdmov\u00e9ho porozum\u011bn\u00ed. Odhad pak pouze zakr\u00fdv\u00e1 neodhalen\u00e9 ot\u00e1zky, z\u00e1vislosti a rizika.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Pro\u010d spr\u00e1vn\u00e1 hierarchie v Jira probl\u00e9m nevy\u0159e\u0161\u00ed<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jira um\u00ed ulo\u017eit typy polo\u017eek, jejich pole, workflow a vz\u00e1jemn\u00e9 vazby. Umo\u017e\u0148uje tak\u00e9 konfigurovat hierarchii nad standardn\u00edmi work items. Technick\u00e1 konfigurace ale sama neur\u010d\u00ed, jak\u00e1 rozhodnut\u00ed maj\u00ed lid\u00e9 na jednotliv\u00fdch \u00farovn\u00edch d\u011blat. P\u0159ehled z\u00e1kladn\u00edch mo\u017enost\u00ed nab\u00edz\u00ed dokumentace Atlassianu k <a href=\"https:\/\/support.atlassian.com\/jira-cloud-administration\/docs\/what-are-issue-types\/\">typ\u016fm pr\u00e1ce v Jira<\/a>.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud organizace nem\u00e1 dohodnut\u00fd obsah a smysl jednotliv\u00fdch \u00farovn\u00ed, Jira pouze p\u0159esn\u011b zaznamen\u00e1 nejasnost, kter\u00e1 existuje mimo ni.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Chyb\u00ed pravidla pro p\u0159echod mezi \u00farovn\u011bmi<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nejd\u016fle\u017eit\u011bj\u0161\u00ed nen\u00ed jen obsah jednotliv\u00fdch ticket\u016f. D\u016fle\u017eit\u00e9 je, co se m\u00e1 st\u00e1t p\u0159i p\u0159echodu z jedn\u00e9 \u00farovn\u011b na druhou.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159echod z Requirementu do Feature by m\u011bl znamenat nap\u0159\u00edklad to, \u017ee:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>pot\u0159eba byla objasn\u011bna se stakeholdery,<\/li>\n<li>rozum\u00edme o\u010dek\u00e1van\u00e9mu v\u00fdsledku,<\/li>\n<li>bylo rozhodnuto, \u017ee m\u00e1 smysl hledat nebo p\u0159ipravit \u0159e\u0161en\u00ed,<\/li>\n<li>vznikl prvn\u00ed smyslupln\u00fd rozsah dod\u00e1vky,<\/li>\n<li>n\u011bkdo p\u0159evzal odpov\u011bdnost za dal\u0161\u00ed refinement.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159echod z Feature do Stories by m\u011bl p\u0159idat dal\u0161\u00ed rozhodnut\u00ed:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>jak v\u00fdsledek rozd\u011bl\u00edme na men\u0161\u00ed inkrementy,<\/li>\n<li>kter\u00fd inkrement pot\u0159ebujeme jako prvn\u00ed,<\/li>\n<li>co dok\u00e1\u017ee realizovat jeden t\u00fdm,<\/li>\n<li>jak budeme v\u00fdsledek ov\u011b\u0159ovat,<\/li>\n<li>kter\u00e9 nejistoty mus\u00edme odstranit p\u0159ed zah\u00e1jen\u00edm pr\u00e1ce.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud p\u0159echod pouze vytvo\u0159\u00ed nov\u00fd ticket a zkop\u00edruje do n\u011bj popis rodi\u010de, \u017e\u00e1dn\u00fd skute\u010dn\u00fd refinement se neodehr\u00e1l.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Chyb\u00ed cadence a rozhodovac\u00ed f\u00f3rum<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Workflow se stavy Open, In Specification, Ready nebo Implementation nevytvo\u0159\u00ed samo o sob\u011b tok pr\u00e1ce. Mus\u00ed b\u00fdt jasn\u00e9, kdo a kdy m\u00e1 s jednotliv\u00fdmi polo\u017ekami pracovat.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Ka\u017ed\u00e1 \u00farove\u0148 obvykle pot\u0159ebuje jinou cadence:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>intake a clarification pro nov\u00e9 Requirements,<\/li>\n<li>produktovou nebo programovou prioritizaci pro Features,<\/li>\n<li>pr\u016fb\u011b\u017en\u00fd refinement pro rozd\u011blen\u00ed Features,<\/li>\n<li>t\u00fdmov\u00fd refinement a pull do realizace pro Stories.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">U\u017eite\u010dnou inspiraci nab\u00edz\u00ed <a href=\"https:\/\/kanbanguides.org\/open-guide-to-kanban\/\">Open Guide to Kanban<\/a>, kter\u00fd zd\u016fraz\u0148uje pot\u0159ebu definovat workflow, aktivn\u011b \u0159\u00eddit polo\u017eky a vytv\u00e1\u0159et explicitn\u00ed pravidla jejich toku. Nejde p\u0159itom o to, zda t\u00fdm pou\u017e\u00edv\u00e1 Scrum, Kanban nebo \u0161k\u00e1lovan\u00fd framework. Bez explicitn\u00edch pravidel se tok pr\u00e1ce spol\u00e9h\u00e1 p\u0159edev\u0161\u00edm na individu\u00e1ln\u00ed interpretaci.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Chyb\u00ed p\u0159\u00edm\u00e1 komunikace mezi lidmi<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dal\u0161\u00edm probl\u00e9mem b\u00fdv\u00e1 \u0159et\u011bzec p\u0159ed\u00e1v\u00e1n\u00ed informac\u00ed:<\/p>\n\n\n\n\n<ol class=\"wp-block-list\">\n<li>Stakeholder vysv\u011btl\u00ed pot\u0159ebu business analytikovi.<\/li>\n<li>Analytik ji zap\u00ed\u0161e do Requirementu.<\/li>\n<li>Product Owner z Requirementu p\u0159iprav\u00ed Feature.<\/li>\n<li>Feature se rozpadne na Stories.<\/li>\n<li>V\u00fdvoj\u00e1\u0159 dostane Story, ale k p\u016fvodn\u00edmu stakeholderovi se u\u017e nedostane.<\/li>\n<\/ol>\n\n\n\n\n<p class=\"wp-block-paragraph\">Business analytik i Product Owner mohou v tomto procesu odv\u00e9st v\u00fdbornou pr\u00e1ci. P\u0159esto p\u0159i ka\u017ed\u00e9m p\u0159ed\u00e1n\u00ed \u010d\u00e1st kontextu zmiz\u00ed a \u010d\u00e1st interpretace se p\u0159id\u00e1. Hierarchie pak za\u010dne fungovat jako telefonn\u00ed hra.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dob\u0159e nastaven\u00fd proces neobch\u00e1z\u00ed analytiky ani produktov\u00e9 role. Umo\u017e\u0148uje ale p\u0159\u00edm\u00e9 dovysv\u011btlen\u00ed tam, kde je pot\u0159eba produktov\u00fd, technick\u00fd nebo dom\u00e9nov\u00fd detail. Ticket nenahrazuje rozhovor. M\u00e1 pomoci zachovat jeho v\u00fdsledek.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Pozor na rozpad podle komponent a organiza\u010dn\u00edch sil<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Hierarchie pr\u00e1ce \u010dasto za\u010dne nev\u011bdomky kop\u00edrovat organiza\u010dn\u00ed nebo technickou strukturu firmy.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jeden z\u00e1kaznick\u00fd v\u00fdsledek se rozd\u011bl\u00ed nap\u0159\u00edklad na:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>frontendovou Feature,<\/li>\n<li>backendovou Feature,<\/li>\n<li>integra\u010dn\u00ed Feature,<\/li>\n<li>testovac\u00ed Feature.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Ka\u017ed\u00e1 polo\u017eka m\u00e1 vlastn\u00ed t\u00fdm, vlastn\u00ed pl\u00e1n a vlastn\u00ed status. \u017d\u00e1dn\u00e1 z nich ale samostatn\u011b nep\u0159in\u00e1\u0161\u00ed pou\u017eiteln\u00fd v\u00fdsledek. V\u0161echny mus\u00ed b\u00fdt dokon\u010deny, aby mohl z\u00e1kazn\u00edk zm\u011bnit svou adresu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Lep\u0161\u00ed je hledat vertik\u00e1ln\u00ed inkrementy, nap\u0159\u00edklad:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>z\u00e1kazn\u00edk m\u016f\u017ee zm\u011bnit adresu u jednoduch\u00e9ho typu objedn\u00e1vky,<\/li>\n<li>zm\u011bnu lze pou\u017e\u00edt tak\u00e9 u rozpracovan\u00e9 objedn\u00e1vky,<\/li>\n<li>syst\u00e9m zvl\u00e1dne regulovan\u00e9 nebo jinak omezen\u00e9 p\u0159\u00edpady,<\/li>\n<li>podpora m\u00e1 k dispozici audit a mo\u017enost asistovan\u00e9ho \u0159e\u0161en\u00ed.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Technick\u00e9 komponenty samoz\u0159ejm\u011b nezmiz\u00ed. T\u00fdmy na nich st\u00e1le mus\u00ed spolupracovat. Rozpad backlogu ale z\u016fst\u00e1v\u00e1 orientovan\u00fd na postupn\u011b pou\u017eiteln\u00e9 v\u00fdsledky, nikoliv na vyt\u00ed\u017een\u00ed jednotliv\u00fdch specializac\u00ed.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">P\u011bt test\u016f funk\u010dn\u00ed hierarchie<\/h2>\n\n\n\n\n<h3 class=\"wp-block-heading\">1. Ka\u017ed\u00e1 \u00farove\u0148 m\u00e1 vlastn\u00ed \u00fa\u010del<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Lid\u00e9 dok\u00e1\u017eou jednou v\u011btou vysv\u011btlit, pro\u010d existuje Requirement, pro\u010d Feature a pro\u010d Story. Odpov\u011b\u010f nen\u00ed jen \u201eproto\u017ee je to povinn\u00e9 v Jira\u201c.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">2. P\u0159echod p\u0159id\u00e1v\u00e1 nov\u00e9 rozhodnut\u00ed<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Text se pouze nekop\u00edruje. P\u0159echodem mezi \u00farovn\u011bmi vznik\u00e1 nov\u00e9 porozum\u011bn\u00ed, rozhodnut\u00ed o investici, rozsahu, priorit\u011b nebo zp\u016fsobu dod\u00e1n\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">3. Ne ka\u017ed\u00e1 zm\u011bna mus\u00ed proj\u00edt celou hierarchi\u00ed<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Mal\u00e1 a dob\u0159e pochopen\u00e1 zm\u011bna m\u016f\u017ee p\u0159ej\u00edt p\u0159\u00edmo z po\u017eadavku do t\u00fdmov\u00e9ho backlogu. Nejasn\u00e1 zm\u011bna m\u016f\u017ee nejprve pot\u0159ebovat experiment. Hierarchie podporuje rozhodov\u00e1n\u00ed, nikoliv povinn\u00e9 zakl\u00e1d\u00e1n\u00ed ticket\u016f.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">4. Polo\u017eky p\u0159edstavuj\u00ed dokon\u010diteln\u00e9 v\u00fdsledky<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature se nezav\u00edr\u00e1 jen proto, \u017ee skon\u010dilo PI nebo byly uzav\u0159eny v\u0161echny technick\u00e9 \u00fakoly. Story nen\u00ed hotov\u00e1, pokud chyb\u00ed testov\u00e1n\u00ed nebo integrace pot\u0159ebn\u00e1 pro jej\u00ed ov\u011b\u0159en\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">5. Vazby pom\u00e1haj\u00ed odpov\u00eddat na d\u016fle\u017eit\u00e9 ot\u00e1zky<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Z hierarchie dok\u00e1\u017eeme zjistit:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>pro\u010d konkr\u00e9tn\u00ed Story realizujeme,<\/li>\n<li>kter\u00fd po\u017eadavek \u0159e\u0161\u00ed,<\/li>\n<li>jak\u00fd v\u00fdsledek u\u017e byl skute\u010dn\u011b dod\u00e1n,<\/li>\n<li>kter\u00e9 Requirements st\u00e1le \u010dekaj\u00ed na rozhodnut\u00ed,<\/li>\n<li>kter\u00e9 Features jsou p\u0159\u00edli\u0161 velk\u00e9 nebo dlouho rozpracovan\u00e9.<\/li>\n<\/ul>\n\n\n\n\n<h2 class=\"wp-block-heading\">Typick\u00e9 chyby<\/h2>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Stejn\u00fd obsah na v\u0161ech \u00farovn\u00edch.<\/strong> Requirement, Feature i Story obsahuj\u00ed zkop\u00edrovan\u00fd text, ale nep\u0159id\u00e1vaj\u00ed nov\u00e9 rozhodnut\u00ed.<\/li>\n<li><strong>Definice zalo\u017een\u00e1 pouze na velikosti.<\/strong> Lid\u00e9 rozli\u0161uj\u00ed polo\u017eky podle Story Points nebo odhadovan\u00e9 d\u00e9lky, nikoliv podle jejich \u00fa\u010delu.<\/li>\n<li><strong>Povinn\u00fd pr\u016fchod celou hierarchi\u00ed.<\/strong> I drobn\u00e1 zm\u011bna pot\u0159ebuje Requirement, Feature a n\u011bkolik Stories.<\/li>\n<li><strong>Requirement jako hotov\u00e9 \u0159e\u0161en\u00ed.<\/strong> Stakeholder p\u0159edep\u00ed\u0161e obrazovku, komponentu i technickou integraci je\u0161t\u011b p\u0159ed spole\u010dn\u00fdm pochopen\u00edm probl\u00e9mu.<\/li>\n<li><strong>Feature jako reportingov\u00fd kontejner.<\/strong> Polo\u017eka nepopisuje v\u00fdsledek, pouze sdru\u017euje pr\u00e1ci t\u00fdmu nebo obdob\u00ed.<\/li>\n<li><strong>Rozpad podle komponent.<\/strong> Frontend, backend a testov\u00e1n\u00ed maj\u00ed vlastn\u00ed polo\u017eky, ale pou\u017eiteln\u00fd v\u00fdsledek vznikne a\u017e po dokon\u010den\u00ed v\u0161ech.<\/li>\n<li><strong>Stories vznikaj\u00ed p\u0159\u00edli\u0161 pozd\u011b.<\/strong> Velk\u00e1 Feature se za\u010dne d\u011blit a\u017e t\u011bsn\u011b p\u0159ed pl\u00e1nov\u00e1n\u00edm, kdy u\u017e nen\u00ed \u010das odhalit z\u00e1vislosti a nejistoty.<\/li>\n<li><strong>Povinn\u00e1 pole se zam\u011b\u0148uj\u00ed za p\u0159ipravenost.<\/strong> Ticket je ozna\u010den jako Ready, proto\u017ee obsahuje odhad, acceptance criteria a vlastn\u00edka, p\u0159esto mu t\u00fdm nerozum\u00ed.<\/li>\n<li><strong>Analytik funguje jako jedin\u00fd komunika\u010dn\u00ed most.<\/strong> V\u00fdvoj\u00e1\u0159i nemaj\u00ed mo\u017enost dovyjasnit odborn\u00fd nebo technick\u00fd detail p\u0159\u00edmo se stakeholderem.<\/li>\n<li><strong>Hierarchie kop\u00edruje organiza\u010dn\u00ed strukturu.<\/strong> Ka\u017ed\u00fd t\u00fdm, syst\u00e9m nebo dodavatel pot\u0159ebuje vlastn\u00ed Feature bez ohledu na z\u00e1kaznick\u00fd v\u00fdsledek.<\/li>\n<li><strong>Rodi\u010d se zav\u00edr\u00e1 podle statusu potomk\u016f.<\/strong> Nikdo neov\u011b\u0159uje, zda bylo skute\u010dn\u011b dosa\u017eeno o\u010dek\u00e1van\u00e9ho v\u00fdsledku.<\/li>\n<li><strong>Jeden model se vnucuje v\u0161em typ\u016fm pr\u00e1ce.<\/strong> Stejnou hierarchi\u00ed mus\u00ed proch\u00e1zet produktov\u00e1 zm\u011bna, produk\u010dn\u00ed chyba, technick\u00fd dluh i drobn\u00fd regulatorn\u00ed po\u017eadavek.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159\u00edli\u0161 velk\u00e9 nebo nejasn\u00e9 Stories se n\u00e1sledn\u011b prom\u00edtaj\u00ed tak\u00e9 do pl\u00e1nov\u00e1n\u00ed. T\u00fdm sice pr\u00e1ci p\u0159ijme, ale b\u011bhem realizace objevuje dal\u0161\u00ed rozsah, technick\u00e9 komplikace nebo chyb\u011bj\u00edc\u00ed rozhodnut\u00ed. V\u00fdsledkem b\u00fdv\u00e1 spillover a p\u0159epln\u011bn\u00fd sprint. V\u00edce se t\u00e9to souvislosti v\u011bnujeme v \u010dl\u00e1nku <a href=\"https:\/\/agilebrothers.cz\/blog\/sprint-overcommitment-proc-tym-nestiha-plan-i-kdyz-pracuje-naplno\/\">Sprint overcommitment: pro\u010d t\u00fdm nest\u00edh\u00e1 pl\u00e1n, i kdy\u017e pracuje naplno<\/a>.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Jak za\u010d\u00edt v praxi<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nedoporu\u010duji za\u010d\u00ednat vytvo\u0159en\u00edm nov\u00e9 sm\u011brnice ani p\u0159ekreslen\u00edm cel\u00e9ho Jira workflow. Za\u010dn\u011bte nad skute\u010dnou prac\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">1. Vyberte p\u011bt konkr\u00e9tn\u00edch dod\u00e1vek<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Ide\u00e1ln\u00ed je vz\u00edt:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>jednu malou zm\u011bnu,<\/li>\n<li>jednu v\u011bt\u0161\u00ed dod\u00e1vku,<\/li>\n<li>jeden nejasn\u00fd po\u017eadavek,<\/li>\n<li>jeden po\u017eadavek zasahuj\u00edc\u00ed v\u00edce t\u00fdm\u016f,<\/li>\n<li>jeden p\u0159\u00edpad, kter\u00fd se v\u00fdrazn\u011b zpozdil nebo nedopadl podle o\u010dek\u00e1v\u00e1n\u00ed.<\/li>\n<\/ul>\n\n\n\n\n<h3 class=\"wp-block-heading\">2. Zrekonstruujte skute\u010dn\u00fd tok rozhodnut\u00ed<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">U ka\u017ed\u00e9ho p\u0159\u00edpadu si polo\u017ete ot\u00e1zky:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Kdy a od koho p\u0159i\u0161la p\u016fvodn\u00ed pot\u0159eba?<\/li>\n<li>Kdo objasnil, co se m\u00e1 zm\u011bnit?<\/li>\n<li>Kdo rozhodl, jak\u00fd v\u00fdsledek se skute\u010dn\u011b dod\u00e1?<\/li>\n<li>Kdy byl zapojen v\u00fdvojov\u00fd t\u00fdm?<\/li>\n<li>Kdy se objevily technick\u00e9 a produktov\u00e9 nejistoty?<\/li>\n<li>Kde se \u010dekalo na rozhodnut\u00ed nebo informace?<\/li>\n<li>Kter\u00fd ticket v Jira p\u0159edstavoval kter\u00e9 rozhodnut\u00ed?<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Velmi \u010dasto zjist\u00edte, \u017ee nejv\u011bt\u0161\u00ed prodleva nevznikla p\u0159i programov\u00e1n\u00ed. Vznikla mezi p\u0159ijet\u00edm po\u017eadavku, rozhodnut\u00edm o jeho priorit\u011b a okam\u017eikem, kdy se j\u00edm t\u00fdm za\u010dal skute\u010dn\u011b zab\u00fdvat.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">3. Popi\u0161te \u00fa\u010del ka\u017ed\u00e9 \u00farovn\u011b jednou v\u011btou<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nap\u0159\u00edklad:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Requirement<\/strong> popisuje objasn\u011bnou pot\u0159ebu, o jej\u00edm\u017e dal\u0161\u00edm zpracov\u00e1n\u00ed m\u00e1me rozhodnout.<\/li>\n<li><strong>Feature<\/strong> popisuje prioritizovan\u00fd a ucelen\u00fd v\u00fdsledek ur\u010den\u00fd k dod\u00e1n\u00ed.<\/li>\n<li><strong>Story<\/strong> popisuje ov\u011b\u0159iteln\u00fd inkrement, kter\u00fd m\u016f\u017ee dokon\u010dit jeden t\u00fdm.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud nedok\u00e1\u017eete rozd\u00edl vysv\u011btlit bez slov \u201ev\u011bt\u0161\u00ed\u201c a \u201emen\u0161\u00ed\u201c, je \u00fa\u010del jednotliv\u00fdch \u00farovn\u00ed pravd\u011bpodobn\u011b st\u00e1le nejasn\u00fd.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">4. Vytvo\u0159te jednoduchou policy card<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pro ka\u017edou \u00farove\u0148 si na jednu str\u00e1nku napi\u0161te:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>\u00fa\u010del polo\u017eky,<\/li>\n<li>kdo ji m\u016f\u017ee vytvo\u0159it,<\/li>\n<li>kdo ji vlastn\u00ed,<\/li>\n<li>jak\u00e9 minimum informac\u00ed pot\u0159ebuje,<\/li>\n<li>kdo rozhoduje o priorit\u011b,<\/li>\n<li>jak\u00e9 podm\u00ednky plat\u00ed pro dal\u0161\u00ed posun,<\/li>\n<li>jak se polo\u017eka rozd\u011bluje,<\/li>\n<li>podle \u010deho se pova\u017euje za dokon\u010denou.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nen\u00ed nutn\u00e9 okam\u017eit\u011b m\u011bnit Jira. Nejprve ov\u011b\u0159te, \u017ee pravidl\u016fm lid\u00e9 rozum\u011bj\u00ed a dok\u00e1\u017eou je pou\u017e\u00edvat na skute\u010dn\u00fdch p\u0159\u00edkladech.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">5. Otestujte jedno pravidlo po dobu \u010dty\u0159 t\u00fddn\u016f<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Prvn\u00edm experimentem m\u016f\u017ee b\u00fdt nap\u0159\u00edklad n\u00e1sleduj\u00edc\u00ed dohoda:<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Ka\u017ed\u00e1 nov\u00e1 Feature mus\u00ed popsat o\u010dek\u00e1vanou zm\u011bnu pro u\u017eivatele nebo business, hranici rozsahu a zp\u016fsob ov\u011b\u0159en\u00ed. Feature nesm\u00ed vzniknout pouze jako ob\u00e1lka na Stories.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Po \u010dty\u0159ech t\u00fddnech vyhodno\u0165te:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>zda t\u00fdmy dost\u00e1vaj\u00ed v\u00edce pot\u0159ebn\u00e9ho kontextu,<\/li>\n<li>zda se Features da\u0159\u00ed rozd\u011blovat d\u0159\u00edve,<\/li>\n<li>zda ubylo kop\u00edrov\u00e1n\u00ed textu,<\/li>\n<li>zda se rychleji odhaluj\u00ed z\u00e1vislosti,<\/li>\n<li>zda je jasn\u011bj\u0161\u00ed, kdo m\u00e1 u\u010dinit dal\u0161\u00ed rozhodnut\u00ed.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Teprve potom m\u00e1 smysl upravovat workflow, povinn\u00e1 pole nebo automatizace.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Kdy u\u017e probl\u00e9m nen\u00ed jen v backlogu<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">N\u011bkdy se p\u0159i pr\u00e1ci s hierarchi\u00ed uk\u00e1\u017ee, \u017ee skute\u010dn\u00fd probl\u00e9m le\u017e\u00ed v\u00fd\u0161e:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>stakeholde\u0159i nedok\u00e1\u017eou rozhodovat o priorit\u00e1ch,<\/li>\n<li>t\u00fdmy dost\u00e1vaj\u00ed p\u0159\u00edli\u0161 mnoho paraleln\u00edch po\u017eadavk\u016f,<\/li>\n<li>nen\u00ed jasn\u00e9, kdo vlastn\u00ed produktov\u00fd v\u00fdsledek,<\/li>\n<li>programov\u00e1 \u00farove\u0148 pouze sb\u00edr\u00e1 statusy, ale ne\u0159\u00edd\u00ed tok pr\u00e1ce,<\/li>\n<li>strategie se nep\u0159ekl\u00e1d\u00e1 do konkr\u00e9tn\u00edch rozhodnut\u00ed o kapacit\u011b,<\/li>\n<li>ka\u017ed\u00fd t\u00fdm pou\u017e\u00edv\u00e1 jin\u00fd v\u00fdznam stejn\u00fdch pojm\u016f.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">V takov\u00e9 situaci dal\u0161\u00ed \u00faprava Jira obvykle nesta\u010d\u00ed. Je pot\u0159eba pod\u00edvat se na \u0161ir\u0161\u00ed zp\u016fsob \u0159\u00edzen\u00ed pr\u00e1ce, rozhodovac\u00ed pravomoci a propojen\u00ed mezi businessem a delivery.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud si nejste jist\u00ed, kde p\u0159esn\u011b se pr\u00e1ce zadrh\u00e1v\u00e1, m\u016f\u017ee pomoci kr\u00e1tk\u00e9 zmapov\u00e1n\u00ed reality v r\u00e1mci <a href=\"https:\/\/ab.jakub-drbohlav.cz\/produkty\/agile-reality-check\/\">Agile Reality Checku<\/a>. Pro organizace, kter\u00e9 pot\u0159ebuj\u00ed propojit strategick\u00e9 priority s programov\u00fdmi a t\u00fdmov\u00fdmi backlogy, je bli\u017e\u0161\u00ed slu\u017eba <a href=\"https:\/\/ab.jakub-drbohlav.cz\/produkty\/strategy-to-execution\/\">Strategy-to-Execution<\/a>. P\u0159i nastavov\u00e1n\u00ed spolupr\u00e1ce v\u00edce t\u00fdm\u016f a spole\u010dn\u00e9ho programov\u00e9ho backlogu m\u016f\u017ee b\u00fdt relevantn\u00ed tak\u00e9 <a href=\"https:\/\/ab.jakub-drbohlav.cz\/produkty\/art-launch-pi-planning-bootcamp\/\">ART \/ Tribe Launch &amp; PI Planning<\/a>.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nejde p\u0159itom o zaveden\u00ed dal\u0161\u00edch typ\u016f ticket\u016f. C\u00edlem je nastavit minim\u00e1ln\u00ed funk\u010dn\u00ed model, ve kter\u00e9m lid\u00e9 v\u011bd\u00ed, jak\u00e9 rozhodnut\u00ed maj\u00ed ud\u011blat, jak\u00e9 informace k n\u011bmu pot\u0159ebuj\u00ed a jak se v\u00fdsledek p\u0159ekl\u00e1d\u00e1 do pr\u00e1ce t\u00fdm\u016f.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Z\u00e1v\u011br: nejd\u0159\u00edv model rozhodov\u00e1n\u00ed, potom konfigurace Jira<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Requirement, Feature a Story mohou vytvo\u0159it u\u017eite\u010dn\u00fd most mezi stakeholdery, produktov\u00fdm \u0159\u00edzen\u00edm a v\u00fdvojov\u00fdmi t\u00fdmy. Samotn\u00e9 propojen\u00ed ticket\u016f v\u0161ak tento most nevytvo\u0159\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Funk\u010dn\u00ed hierarchie pot\u0159ebuje:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>jasn\u00fd \u00fa\u010del ka\u017ed\u00e9 \u00farovn\u011b,<\/li>\n<li>rozd\u00edln\u00e9 ot\u00e1zky a rozhodnut\u00ed,<\/li>\n<li>vlastn\u00edky a rozhodovac\u00ed pravomoci,<\/li>\n<li>pravidla p\u0159echodu mezi \u00farovn\u011bmi,<\/li>\n<li>pravideln\u00fd refinement a prioritizaci,<\/li>\n<li>p\u0159\u00edmou komunikaci mezi lidmi,<\/li>\n<li>mo\u017enost zjednodu\u0161it cestu pro malou nebo specifickou pr\u00e1ci.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jira m\u00e1 tento model podporovat a zviditel\u0148ovat. Nem\u016f\u017ee ho za organizaci vymyslet.<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Ne\u017e do Jira p\u0159id\u00e1te dal\u0161\u00ed \u00farove\u0148, zkuste nejprve popsat, jak\u00e9 nov\u00e9 rozhodnut\u00ed m\u00e1 tato \u00farove\u0148 umo\u017enit. Pokud \u017e\u00e1dn\u00e9 nenajdete, pravd\u011bpodobn\u011b nepot\u0159ebujete dal\u0161\u00ed typ ticketu.<\/p><\/blockquote>\n\n\n\n\n<hr class=\"wp-block-separator has-alpha-channel-opacity\"\/>\n\n\n\n\n<h3 class=\"wp-block-heading\">Chcete si pravidla jednotliv\u00fdch \u00farovn\u00ed navrhnout sami?<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">V <a href=\"https:\/\/academy.agilebrothers.cz\/zdroje\/\">Agile Brothers Academy<\/a> postupn\u011b zve\u0159ej\u0148ujeme praktick\u00e9 \u0161ablony, toolkity a tah\u00e1ky pro pr\u00e1ci s backlogem, tokem pr\u00e1ce a t\u00fdmov\u00fdm zlep\u0161ov\u00e1n\u00edm. Mohou v\u00e1m pomoci p\u0159ipravit prvn\u00ed n\u00e1vrh pravidel bez zav\u00e1d\u011bn\u00ed dal\u0161\u00ed slo\u017eit\u00e9 metodiky.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud je probl\u00e9m \u0161ir\u0161\u00ed a r\u016fzn\u00e9 \u010d\u00e1sti organizace si pod stejn\u00fdmi pojmy p\u0159edstavuj\u00ed n\u011bco jin\u00e9ho, m\u016f\u017eeme se spole\u010dn\u011b pod\u00edvat na n\u011bkolik skute\u010dn\u00fdch Requirements, Features a Stories a naj\u00edt m\u00edsto, kde se tok rozhodnut\u00ed rozpad\u00e1. N\u011bkdy sta\u010d\u00ed n\u011bkolik jasn\u00fdch pravidel. Jindy se uk\u00e1\u017ee, \u017ee je pot\u0159eba upravit zp\u016fsob prioritizace nebo spolupr\u00e1ce mezi t\u00fdmy.<\/p>\n\n","protected":false},"excerpt":{"rendered":"<p>Mnoho organizac\u00ed m\u00e1 v Jira pe\u010dliv\u011b vytvo\u0159enou hierarchii Requirement, Feature a Story. P\u0159esto se po\u017eadavky ztr\u00e1cej\u00ed, t\u00fdmy dost\u00e1vaj\u00ed nejasn\u00e1 zad\u00e1n\u00ed a stejn\u00fd text se kop\u00edruje mezi n\u011bkolika tickety. Probl\u00e9m toti\u017e obvykle nen\u00ed v konfiguraci Jira, ale v tom, \u017ee jednotliv\u00e9 \u00farovn\u011b nemaj\u00ed jasn\u00fd \u00fa\u010del, vlastn\u00edka ani pravidla rozhodov\u00e1n\u00ed.<\/p>\n","protected":false},"author":4,"featured_media":1311,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[101,103,111],"tags":[224,219,220,218,217,223,216,221,225,222],"class_list":["post-1310","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-flow-a-predvidatelnost","category-operating-model","category-transformation-playbook","tag-backlog","tag-backlog-refinement","tag-business-analyza","tag-feature","tag-jira","tag-product-management","tag-requirement","tag-rizeni-pozadavku","tag-safe","tag-user-story"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v27.5 (Yoast SEO v27.5) - https:\/\/yoast.com\/product\/yoast-seo-premium-wordpress\/ -->\n<title>Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira - Blog Agile Brothers<\/title>\n<meta name=\"description\" content=\"Requirement, Feature a Story nejsou jen t\u0159i velikosti ticketu. Zjist\u011bte, jak nastavit jejich \u00fa\u010del, odpov\u011bdnosti a pravidla toku pr\u00e1ce v Jira.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/\" \/>\n<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira\" \/>\n<meta property=\"og:description\" content=\"%\" \/>\n<meta property=\"og:url\" content=\"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog Agile Brothers\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-13T07:42:27+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-13T14:13:35+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png\" \/>\n\t<meta property=\"og:image:width\" content=\"1672\" \/>\n\t<meta property=\"og:image:height\" content=\"941\" \/>\n\t<meta property=\"og:image:type\" content=\"image\/png\" \/>\n<meta name=\"author\" content=\"Milan Drbohlav\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:label1\" content=\"Napsal(a)\" \/>\n\t<meta name=\"twitter:data1\" content=\"Milan Drbohlav\" \/>\n\t<meta name=\"twitter:label2\" content=\"Odhadovan\u00e1 doba \u010dten\u00ed\" \/>\n\t<meta name=\"twitter:data2\" content=\"15 minut\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\\\/\\\/schema.org\",\"@graph\":[{\"@type\":\"Article\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/\"},\"author\":{\"name\":\"Milan Drbohlav\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#\\\/schema\\\/person\\\/8820a946316ac68645371e2a16fa77cb\"},\"headline\":\"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira\",\"datePublished\":\"2026-07-13T07:42:27+00:00\",\"dateModified\":\"2026-07-13T14:13:35+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/\"},\"wordCount\":3807,\"publisher\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/RequirementFeatureStory.png\",\"keywords\":[\"backlog\",\"backlog refinement\",\"business anal\u00fdza\",\"Feature\",\"Jira\",\"product management\",\"Requirement\",\"\u0159\u00edzen\u00ed po\u017eadavk\u016f\",\"SAFe\",\"User Story\"],\"articleSection\":[\"Flow &amp; P\u0159edv\u00eddatelnost\",\"Operating model\",\"Transformation playbook\"],\"inLanguage\":\"cs\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/\",\"name\":\"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira - Blog Agile Brothers\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/RequirementFeatureStory.png\",\"datePublished\":\"2026-07-13T07:42:27+00:00\",\"dateModified\":\"2026-07-13T14:13:35+00:00\",\"description\":\"Requirement, Feature a Story nejsou jen t\u0159i velikosti ticketu. Zjist\u011bte, jak nastavit jejich \u00fa\u010del, odpov\u011bdnosti a pravidla toku pr\u00e1ce v Jira.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#breadcrumb\"},\"inLanguage\":\"cs\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"cs\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#primaryimage\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/RequirementFeatureStory.png\",\"contentUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/RequirementFeatureStory.png\",\"width\":1672,\"height\":941,\"caption\":\"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/requirement-feature-story-hierarchie-jira\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Dom\u016f\",\"item\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#website\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/\",\"name\":\"Blog Agile Brothers\",\"description\":\"\",\"publisher\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#organization\"},\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"cs\"},{\"@type\":\"Organization\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#organization\",\"name\":\"Agile Brothers s.r.o.\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/\",\"logo\":{\"@type\":\"ImageObject\",\"inLanguage\":\"cs\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/logo-agilebrothers-bez-webu.svg\",\"contentUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/02\\\/logo-agilebrothers-bez-webu.svg\",\"width\":1,\"height\":1,\"caption\":\"Agile Brothers s.r.o.\"},\"image\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#\\\/schema\\\/logo\\\/image\\\/\"},\"sameAs\":[\"https:\\\/\\\/www.linkedin.com\\\/company\\\/agilebrothers\"]},{\"@type\":\"Person\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#\\\/schema\\\/person\\\/8820a946316ac68645371e2a16fa77cb\",\"name\":\"Milan Drbohlav\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"cs\",\"@id\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g\",\"url\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g\",\"contentUrl\":\"https:\\\/\\\/secure.gravatar.com\\\/avatar\\\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g\",\"caption\":\"Milan Drbohlav\"},\"description\":\"Partner, Senior Consultant\",\"sameAs\":[\"https:\\\/\\\/milan-drbohlav.cz\\\/\"],\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/author\\\/milan\\\/\"}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira - Blog Agile Brothers","description":"Requirement, Feature a Story nejsou jen t\u0159i velikosti ticketu. Zjist\u011bte, jak nastavit jejich \u00fa\u010del, odpov\u011bdnosti a pravidla toku pr\u00e1ce v Jira.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/","og_locale":"cs_CZ","og_type":"article","og_title":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira","og_description":"%","og_url":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/","og_site_name":"Blog Agile Brothers","article_published_time":"2026-07-13T07:42:27+00:00","article_modified_time":"2026-07-13T14:13:35+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png","type":"image\/png"}],"author":"Milan Drbohlav","twitter_card":"summary_large_image","twitter_misc":{"Napsal(a)":"Milan Drbohlav","Odhadovan\u00e1 doba \u010dten\u00ed":"15 minut"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"Article","@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#article","isPartOf":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/"},"author":{"name":"Milan Drbohlav","@id":"https:\/\/agilebrothers.cz\/blog\/#\/schema\/person\/8820a946316ac68645371e2a16fa77cb"},"headline":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira","datePublished":"2026-07-13T07:42:27+00:00","dateModified":"2026-07-13T14:13:35+00:00","mainEntityOfPage":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/"},"wordCount":3807,"publisher":{"@id":"https:\/\/agilebrothers.cz\/blog\/#organization"},"image":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#primaryimage"},"thumbnailUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png","keywords":["backlog","backlog refinement","business anal\u00fdza","Feature","Jira","product management","Requirement","\u0159\u00edzen\u00ed po\u017eadavk\u016f","SAFe","User Story"],"articleSection":["Flow &amp; P\u0159edv\u00eddatelnost","Operating model","Transformation playbook"],"inLanguage":"cs"},{"@type":"WebPage","@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/","url":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/","name":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira - Blog Agile Brothers","isPartOf":{"@id":"https:\/\/agilebrothers.cz\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#primaryimage"},"image":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#primaryimage"},"thumbnailUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png","datePublished":"2026-07-13T07:42:27+00:00","dateModified":"2026-07-13T14:13:35+00:00","description":"Requirement, Feature a Story nejsou jen t\u0159i velikosti ticketu. Zjist\u011bte, jak nastavit jejich \u00fa\u010del, odpov\u011bdnosti a pravidla toku pr\u00e1ce v Jira.","breadcrumb":{"@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#breadcrumb"},"inLanguage":"cs","potentialAction":[{"@type":"ReadAction","target":["https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/"]}]},{"@type":"ImageObject","inLanguage":"cs","@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#primaryimage","url":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png","contentUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/RequirementFeatureStory.png","width":1672,"height":941,"caption":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira"},{"@type":"BreadcrumbList","@id":"https:\/\/agilebrothers.cz\/blog\/requirement-feature-story-hierarchie-jira\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Dom\u016f","item":"https:\/\/agilebrothers.cz\/blog\/"},{"@type":"ListItem","position":2,"name":"Requirement, Feature, Story: pro\u010d nesta\u010d\u00ed m\u00edt hierarchii v Jira"}]},{"@type":"WebSite","@id":"https:\/\/agilebrothers.cz\/blog\/#website","url":"https:\/\/agilebrothers.cz\/blog\/","name":"Blog Agile Brothers","description":"","publisher":{"@id":"https:\/\/agilebrothers.cz\/blog\/#organization"},"potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/agilebrothers.cz\/blog\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"cs"},{"@type":"Organization","@id":"https:\/\/agilebrothers.cz\/blog\/#organization","name":"Agile Brothers s.r.o.","url":"https:\/\/agilebrothers.cz\/blog\/","logo":{"@type":"ImageObject","inLanguage":"cs","@id":"https:\/\/agilebrothers.cz\/blog\/#\/schema\/logo\/image\/","url":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/02\/logo-agilebrothers-bez-webu.svg","contentUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/02\/logo-agilebrothers-bez-webu.svg","width":1,"height":1,"caption":"Agile Brothers s.r.o."},"image":{"@id":"https:\/\/agilebrothers.cz\/blog\/#\/schema\/logo\/image\/"},"sameAs":["https:\/\/www.linkedin.com\/company\/agilebrothers"]},{"@type":"Person","@id":"https:\/\/agilebrothers.cz\/blog\/#\/schema\/person\/8820a946316ac68645371e2a16fa77cb","name":"Milan Drbohlav","image":{"@type":"ImageObject","inLanguage":"cs","@id":"https:\/\/secure.gravatar.com\/avatar\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g","url":"https:\/\/secure.gravatar.com\/avatar\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g","contentUrl":"https:\/\/secure.gravatar.com\/avatar\/78bf0d13cb04b48dce84016585d1d5ab2ecc97e98ee027f56d3fe9808ba65d01?s=96&d=mm&r=g","caption":"Milan Drbohlav"},"description":"Partner, Senior Consultant","sameAs":["https:\/\/milan-drbohlav.cz\/"],"url":"https:\/\/agilebrothers.cz\/blog\/author\/milan\/"}]}},"_links":{"self":[{"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts\/1310","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/comments?post=1310"}],"version-history":[{"count":1,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts\/1310\/revisions"}],"predecessor-version":[{"id":1312,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts\/1310\/revisions\/1312"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/media\/1311"}],"wp:attachment":[{"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/media?parent=1310"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/categories?post=1310"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/tags?post=1310"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}