{"id":1325,"date":"2026-07-13T12:46:43","date_gmt":"2026-07-13T10:46:43","guid":{"rendered":"https:\/\/agilebrothers.cz\/blog\/?p=1325"},"modified":"2026-07-13T16:11:45","modified_gmt":"2026-07-13T14:11:45","slug":"container-feature-nefunkcni-backlog","status":"publish","type":"post","link":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/","title":{"rendered":"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog"},"content":{"rendered":"\n\n<p class=\"wp-block-paragraph\">Na prvn\u00ed pohled vypadala Feature docela zdrav\u011b. M\u011bla vlastn\u00edka, stav In Progress, n\u011bkolik t\u00fdmov\u00fdch Stories a dokonce i p\u0159i\u0159azenou Business Value. Jmenovala se \u201eTechnical Improvements \u2013 PI 4\u201c.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Kdy\u017e jsme ji ale b\u011bhem kontroly backlogu otev\u0159eli, na\u0161li jsme pod n\u00ed aktualizaci knihovny, zm\u011bnu logov\u00e1n\u00ed, \u00fapravu jednoho formul\u00e1\u0159e, nov\u00fd monitoring, po\u017eadavek lok\u00e1ln\u00edho trhu a opravu integra\u010dn\u00edho rozhran\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Polo\u017eil jsem jednoduchou ot\u00e1zku: \u201eCo bude po dokon\u010den\u00ed t\u00e9to Feature jinak pro z\u00e1kazn\u00edka nebo pro organizaci?\u201c<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nikdo nedok\u00e1zal odpov\u011bd\u011bt. Jedin\u00e9, co m\u011bly polo\u017eky spole\u010dn\u00e9, byl t\u00fdm, kter\u00fd je m\u011bl realizovat.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pr\u00e1v\u011b v podobn\u00fdch situac\u00edch vznikaj\u00ed takzvan\u00e9 Container Features. Ne v\u017edy jsou chybou. Mohou b\u00fdt pragmatickou pom\u016fckou pro agregaci drobn\u00e9, technick\u00e9 nebo provozn\u00ed pr\u00e1ce. Stejn\u011b snadno se z nich ale stane backlogov\u00fd odpadkov\u00fd ko\u0161: m\u00edsto, kam se ukl\u00e1daj\u00ed polo\u017eky, o jejich\u017e \u00fa\u010delu, hodnot\u011b a priorit\u011b se organizaci nechce rozhodovat.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Co je Container Feature<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature nen\u00ed obecn\u011b standardizovan\u00fd agiln\u00ed pojem s jednou z\u00e1vaznou definic\u00ed. V praxi se t\u00edmto ozna\u010den\u00edm obvykle mysl\u00ed nad\u0159azen\u00e1 backlogov\u00e1 polo\u017eka, kter\u00e1 vznikla p\u0159edev\u0161\u00edm proto, aby seskupila n\u011bkolik Stories.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Na rozd\u00edl od b\u011b\u017en\u00e9 Feature v\u0161ak tyto Stories nevytv\u00e1\u0159ej\u00ed jeden ucelen\u00fd v\u00fdsledek. Spojuje je nap\u0159\u00edklad:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>stejn\u00fd t\u00fdm,<\/li>\n<li>stejn\u00e1 technick\u00e1 komponenta,<\/li>\n<li>stejn\u00fd typ pr\u00e1ce,<\/li>\n<li>stejn\u00fd kvart\u00e1l nebo PI,<\/li>\n<li>stejn\u00fd zdroj po\u017eadavk\u016f,<\/li>\n<li>nebo pouze povinnost m\u00edt v n\u00e1stroji vypln\u011bn\u00e9ho rodi\u010de.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pracovn\u00ed definice tedy m\u016f\u017ee zn\u00edt n\u00e1sledovn\u011b:<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Container Feature je nad\u0159azen\u00e1 backlogov\u00e1 polo\u017eka vytvo\u0159en\u00e1 p\u0159edev\u0161\u00edm pro seskupen\u00ed Stories, nikoliv pro \u0159\u00edzen\u00ed jednoho ucelen\u00e9ho z\u00e1kaznick\u00e9ho, provozn\u00edho nebo business v\u00fdsledku.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Samotn\u00e1 hierarchie p\u0159itom je\u0161t\u011b nezaru\u010duje, \u017ee backlog d\u00e1v\u00e1 smysl. T\u00e9to ot\u00e1zce se podrobn\u011bji v\u011bnujeme tak\u00e9 v \u010dl\u00e1nku o tom, pro\u010d je pot\u0159eba rozli\u0161ovat r\u016fzn\u00e9 \u00farovn\u011b \u0159\u00edzen\u00ed pr\u00e1ce. <a href=\"https:\/\/agilebrothers.cz\/blog\/tri-urovne-rizeni-prace-bez-frameworku-investice-%E2%86%92-doruceni-%E2%86%92-inkrement\/\">Investi\u010dn\u00ed, doru\u010dovac\u00ed a t\u00fdmov\u00e1 \u00farove\u0148 p\u0159edstavuj\u00ed r\u016fzn\u00e9 typy rozhodnut\u00ed<\/a>, nikoliv pouze r\u016fzn\u011b velk\u00e9 tickety.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Jak se li\u0161\u00ed od skute\u010dn\u00e9 Feature<\/h3>\n\n\n\n\n<figure class=\"wp-block-table\"><table><thead><tr><th>Ot\u00e1zka<\/th><th>Skute\u010dn\u00e1 Feature<\/th><th>Container Feature<\/th><\/tr><\/thead><tbody><tr><td>Co spojuje jej\u00ed Stories?<\/td><td>Jeden rozpoznateln\u00fd v\u00fdsledek<\/td><td>T\u00fdm, obdob\u00ed, technologie nebo typ pr\u00e1ce<\/td><\/tr><tr><td>Jak se prioritizuje?<\/td><td>Podle hodnoty a nal\u00e9havosti v\u00fdsledku<\/td><td>\u010casto mus\u00ed b\u00fdt prioritizov\u00e1na ka\u017ed\u00e1 Story zvl\u00e1\u0161\u0165<\/td><\/tr><tr><td>Kdy je dokon\u010den\u00e1?<\/td><td>Po dosa\u017een\u00ed definovan\u00e9ho v\u00fdsledku<\/td><td>Po skon\u010den\u00ed obdob\u00ed nebo ve chv\u00edli, kdy u\u017e se nep\u0159id\u00e1v\u00e1 dal\u0161\u00ed pr\u00e1ce<\/td><\/tr><tr><td>M\u00e1 jasnou hranici?<\/td><td>M\u011bla by m\u00edt<\/td><td>\u010casto se pr\u016fb\u011b\u017en\u011b roz\u0161i\u0159uje<\/td><\/tr><tr><td>Lze ov\u011b\u0159it p\u0159\u00ednos?<\/td><td>Ano, alespo\u0148 pomoc\u00ed hypot\u00e9zy a d\u016fkaz\u016f<\/td><td>Obvykle pouze na \u00farovni jednotliv\u00fdch Stories<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nap\u0159\u00edklad <a href=\"https:\/\/framework.scaledagile.com\/features-and-capabilities\">Scaled Agile Framework popisuje Feature<\/a> jako funkcionalitu, kter\u00e1 napl\u0148uje pot\u0159ebu stakeholdera, p\u0159in\u00e1\u0161\u00ed hodnotu a je mo\u017en\u00e9 ji dokon\u010dit v r\u00e1mci jednoho PI. Nen\u00ed to jedin\u00e1 pou\u017eiteln\u00e1 definice Feature, ale poskytuje dobr\u00fd kontroln\u00ed bod: existuje zde konkr\u00e9tn\u00ed pot\u0159eba, rozpoznateln\u00fd v\u00fdsledek a \u010dasov\u00e1 hranice.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Scrum naproti tomu \u017e\u00e1dnou povinnou hierarchii Epic\u2013Feature\u2013Story nep\u0159edepisuje. Ofici\u00e1ln\u00ed <a href=\"https:\/\/scrumguides.org\/\">Scrum Guide<\/a> pracuje obecn\u011b s polo\u017ekami Product Backlogu. Povinnost, aby ka\u017ed\u00e1 Story m\u011bla rodi\u010dovskou Feature, tedy obvykle nevych\u00e1z\u00ed ze Scrumu. Vych\u00e1z\u00ed z konkr\u00e9tn\u00edho organiza\u010dn\u00edho nebo n\u00e1strojov\u00e9ho nastaven\u00ed.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Pro\u010d Container Features vznikaj\u00ed<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Features obvykle nevznikaj\u00ed proto, \u017ee by n\u011bkdo cht\u011bl z\u00e1m\u011brn\u011b po\u0161kodit backlog. \u010cast\u011bji jde o pragmatickou reakci na re\u00e1ln\u00fd probl\u00e9m.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">N\u00e1stroj vy\u017eaduje rodi\u010dovskou polo\u017eku<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jira, Azure DevOps nebo firemn\u00ed reporting mohou b\u00fdt nakonfigurovan\u00e9 tak, \u017ee ka\u017ed\u00e1 Story mus\u00ed pat\u0159it pod Feature. Kdy\u017e p\u0159irozen\u00e1 Feature neexistuje, lid\u00e9 vytvo\u0159\u00ed n\u00e1hradn\u00edho rodi\u010de.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Drobn\u00e9 polo\u017eky jsou p\u0159\u00edli\u0161 mal\u00e9 na samostatnou Feature<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">T\u00fdm pr\u016fb\u011b\u017en\u011b \u0159e\u0161\u00ed men\u0161\u00ed zm\u011bny, kter\u00e9 samostatn\u011b nedosahuj\u00ed \u00farovn\u011b programov\u00e9 Feature. M\u016f\u017ee j\u00edt o drobn\u00e9 po\u017eadavky lok\u00e1ln\u00edch trh\u016f, \u00fadr\u017ebu, aktualizace knihoven, mal\u00e9 regulatorn\u00ed zm\u011bny nebo technick\u00e1 zlep\u0161en\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Leadership chce vid\u011bt celou spot\u0159ebu kapacity<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Programov\u00fd backlog ukazuje strategick\u00e9 Features, ale \u010d\u00e1st kapacity miz\u00ed v supportu, maintenance nebo technick\u00e9 pr\u00e1ci. Container Feature m\u016f\u017ee tuto pr\u00e1ci zviditelnit.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Organizace chce rezervovat \u010d\u00e1st kapacity<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nap\u0159\u00edklad deset procent kapacity na technick\u00fd dluh nebo bezpe\u010dnostn\u00ed aktualizace. Container Feature pak funguje jako pl\u00e1novac\u00ed ob\u00e1lka.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">T\u00fdm nem\u00e1 jin\u00fd vstupn\u00ed kan\u00e1l<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Do ji\u017e schv\u00e1len\u00e9 Container Feature lze \u010dasto vlo\u017eit novou Story sn\u00e1ze ne\u017e vytvo\u0159it novou Feature, obh\u00e1jit jej\u00ed hodnotu a dostat ji do programov\u00e9 prioritizace. Pr\u00e1v\u011b zde se z praktick\u00e9 pom\u016fcky za\u010d\u00edn\u00e1 st\u00e1vat probl\u00e9m.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Kdy m\u016f\u017ee Container Feature skute\u010dn\u011b pom\u00e1hat<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Odm\u00edtnout v\u0161echny Container Features jako antipattern by bylo p\u0159\u00edli\u0161 jednoduch\u00e9. V n\u011bkter\u00fdch situac\u00edch mohou b\u00fdt rozumn\u00fdm kompromisem.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Agreguje p\u0159edv\u00eddatelnou drobnou pr\u00e1ci<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159edstavme si t\u00fdm, kter\u00fd ka\u017ed\u00fd kvart\u00e1l realizuje sadu mal\u00fdch regulatorn\u00edch \u00faprav. Jednotliv\u00e9 zm\u011bny jsou p\u0159\u00edli\u0161 mal\u00e9 pro samostatn\u00e9 Features, ale jejich realizace je povinn\u00e1 a dohromady spot\u0159ebuj\u00ed p\u0159edv\u00eddatelnou \u010d\u00e1st kapacity.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature \u201eDrobn\u00e9 regulatorn\u00ed zm\u011bny \u2013 Q4\u201c m\u016f\u017ee fungovat, pokud m\u00e1:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>jasn\u011b omezen\u00e9 obdob\u00ed,<\/li>\n<li>definovan\u00fd typ p\u0159\u00edpustn\u00e9 pr\u00e1ce,<\/li>\n<li>kapacitn\u00ed limit,<\/li>\n<li>vlastn\u00edka rozhoduj\u00edc\u00edho o vstupu,<\/li>\n<li>a samostatn\u00e9 po\u0159ad\u00ed jednotliv\u00fdch polo\u017eek.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">To, \u017ee jsou polo\u017eky ve spole\u010dn\u00e9m kontejneru, nesm\u00ed znamenat, \u017ee jsou v\u0161echny automaticky schv\u00e1len\u00e9.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Zviditel\u0148uje provozn\u00ed a \u00fadr\u017ebovou pr\u00e1ci<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud programov\u00fd reporting dlouhodob\u011b ignoruje maintenance, bezpe\u010dnostn\u00ed aktualizace nebo provozn\u00ed zm\u011bny, m\u016f\u017ee Container Feature uk\u00e1zat jejich skute\u010dn\u00fd dopad na kapacitu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Je v\u0161ak dobr\u00e9 ov\u011b\u0159it, zda by stejnou pot\u0159ebu nevy\u0159e\u0161il l\u00e9pe jin\u00fd atribut: typ pr\u00e1ce, komponenta, t\u0159\u00edda slu\u017eby, label, samostatn\u00fd swimlane nebo reportingov\u00e9 pole. Hierarchie nen\u00ed jedin\u00fd zp\u016fsob, jak pr\u00e1ci agregovat.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Je do\u010dasnou pom\u016fckou b\u011bhem zm\u011bny<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159i migraci backlogu, slu\u010dov\u00e1n\u00ed t\u00fdm\u016f nebo zav\u00e1d\u011bn\u00ed nov\u00e9ho pracovn\u00edho modelu m\u016f\u017ee b\u00fdt do\u010dasn\u00fd kontejner prakti\u010dt\u011bj\u0161\u00ed ne\u017e okam\u017eit\u00e1 rozs\u00e1hl\u00e1 zm\u011bna n\u00e1stroje.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Kl\u00ed\u010dov\u00e9 je slovo <strong>do\u010dasn\u00fd<\/strong>. M\u011bl by m\u00edt vlastn\u00edka, d\u016fvod existence a konkr\u00e9tn\u00ed datum, kdy bude odstran\u011bn nebo nahrazen vhodn\u011bj\u0161\u00edm \u0159e\u0161en\u00edm.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Kdy Container Feature zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature se st\u00e1v\u00e1 nebezpe\u010dnou ve chv\u00edli, kdy p\u0159estane pouze agregovat pr\u00e1ci a za\u010dne nahrazovat rozhodnut\u00ed, kter\u00e1 by organizace m\u011bla d\u011blat jinde.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Nem\u00e1 vlastn\u00ed v\u00fdsledek<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud dokon\u010den\u00ed Feature nic konkr\u00e9tn\u00edho nezm\u011bn\u00ed pro z\u00e1kazn\u00edka, stakeholdera, provoz nebo budouc\u00ed schopnost organizace, je t\u011b\u017ek\u00e9 ji pova\u017eovat za skute\u010dnou Feature.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">\u201eBackend improvements\u201c nen\u00ed v\u00fdsledek. \u201eZkr\u00e1cen\u00ed doby zpracov\u00e1n\u00ed objedn\u00e1vky z p\u011bti minut na m\u00e9n\u011b ne\u017e jednu minutu\u201c u\u017e v\u00fdsledkem b\u00fdt m\u016f\u017ee.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Jedin\u00fdm poj\u00edtkem je t\u00fdm nebo komponenta<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature nazvan\u00e1 \u201eFrontend Team Work\u201c pouze kop\u00edruje organiza\u010dn\u00ed strukturu. To, \u017ee stejn\u00fd t\u00fdm realizuje n\u011bkolik Stories, je\u0161t\u011b neznamen\u00e1, \u017ee maj\u00ed spole\u010dn\u00fd produktov\u00fd smysl.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159\u00edslu\u0161nost k t\u00fdmu nebo komponent\u011b je u\u017eite\u010dn\u00e1 reportingov\u00e1 informace. Nen\u00ed to ale automaticky vhodn\u00fd d\u016fvod pro vytvo\u0159en\u00ed nad\u0159azen\u00e9 backlogov\u00e9 polo\u017eky.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Z\u016fst\u00e1v\u00e1 otev\u0159en\u00e1 n\u011bkolik PI nebo kvart\u00e1l\u016f<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">N\u011bkter\u00e9 Container Features funguj\u00ed jako p\u0159edplacen\u00e1 popelnice. Poka\u017ed\u00e9, kdy\u017e se bl\u00ed\u017e\u00ed jejich dokon\u010den\u00ed, p\u0159ibydou dal\u0161\u00ed Stories.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takov\u00e1 polo\u017eka nem\u00e1 kone\u010dn\u00fd rozsah ani smysluplnou podm\u00ednku dokon\u010den\u00ed. Jej\u00ed stav nevypov\u00edd\u00e1 o v\u00fdsledku, ale pouze o administrativn\u00edm zvyku.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Ka\u017ed\u00e1 Story m\u00e1 jinou prioritu<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jestli\u017ee jedna Story \u0159e\u0161\u00ed kritickou zranitelnost, druh\u00e1 kosmetickou \u00fapravu u\u017eivatelsk\u00e9ho rozhran\u00ed a t\u0159et\u00ed po\u017eadavek jednoho lok\u00e1ln\u00edho trhu, ned\u00e1v\u00e1 smysl prioritizovat Container Feature jako celek.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Spole\u010dn\u00fd rodi\u010d v tomto p\u0159\u00edpad\u011b vytv\u00e1\u0159\u00ed pouze iluzi jednoho rozhodnut\u00ed. Ve skute\u010dnosti je pot\u0159eba ud\u011blat t\u0159i odli\u0161n\u00e1 rozhodnut\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Obch\u00e1z\u00ed prioritizaci<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jedn\u00edm z nejv\u011bt\u0161\u00edch rizik je mo\u017enost p\u0159id\u00e1vat nov\u00e9 Stories pod ji\u017e schv\u00e1lenou Feature bez op\u011btovn\u00e9ho posouzen\u00ed hodnoty a kapacity.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature pak funguje jako otev\u0159en\u00fd rozpo\u010det. Jakmile jednou projde pl\u00e1nov\u00e1n\u00edm, mohou se pod n\u00ed pr\u016fb\u011b\u017en\u011b schov\u00e1vat dal\u0161\u00ed po\u017eadavky. V\u00fdsledkem nen\u00ed flexibilita, ale nekontrolovan\u00fd p\u0159\u00edsun pr\u00e1ce.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Vytv\u00e1\u0159\u00ed fale\u0161nou transparentnost<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dashboard ukazuje, \u017ee je Feature dokon\u010dena ze sedmdes\u00e1ti procent, proto\u017ee sedm z deseti Stories je hotov\u00fdch. To ale nemus\u00ed \u0159\u00edkat v\u016fbec nic o dosa\u017een\u00e9m v\u00fdsledku.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">U skute\u010dn\u00e9 Feature m\u016f\u017eeme sledovat nejen dokon\u010den\u00e9 polo\u017eky, ale tak\u00e9 to, zda vznikla pou\u017eiteln\u00e1 funkcionalita nebo ov\u011b\u0159iteln\u00fd p\u0159\u00ednos. U n\u00e1hodn\u00e9ho kontejneru sledujeme pouze po\u010det uzav\u0159en\u00fdch ticket\u016f.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">P\u011bt test\u016f zdrav\u00e9 Container Feature<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nejd\u016fle\u017eit\u011bj\u0161\u00ed ot\u00e1zka nen\u00ed, zda pou\u017e\u00edv\u00e1te Container Features. D\u016fle\u017eit\u011bj\u0161\u00ed je, zda m\u00e1te jasn\u00e1 pravidla, podle kter\u00fdch pozn\u00e1te jejich legitimn\u00ed pou\u017eit\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">1. Test \u00fa\u010delu<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dok\u00e1\u017eeme jednou v\u011btou vysv\u011btlit, pro\u010d kontejner pot\u0159ebujeme a pro\u010d nesta\u010d\u00ed label, komponenta, typ pr\u00e1ce nebo jin\u00e9 reportingov\u00e9 pole?<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jestli\u017ee jedinou odpov\u011bd\u00ed je \u201eproto\u017ee Jira vy\u017eaduje parent Feature\u201c, \u0159e\u0161\u00edme technick\u00e9 omezen\u00ed n\u00e1stroje. To m\u016f\u017ee b\u00fdt legitimn\u00ed, ale m\u011bli bychom to otev\u0159en\u011b p\u0159iznat a nehovo\u0159it o polo\u017ece jako o skute\u010dn\u00e9 produktov\u00e9 Feature.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">2. Test hranice<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Je p\u0159edem jasn\u00e9, co do Container Feature sm\u00ed vstoupit a co u\u017e ne?<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nap\u0159\u00edklad do kontejneru \u201eSecurity updates \u2013 Q4\u201c mohou vstoupit aktualizace souvisej\u00edc\u00ed s konkr\u00e9tn\u00edm seznamem zranitelnost\u00ed. Nem\u011bl by se do n\u011bj automaticky vej\u00edt libovoln\u00fd technick\u00fd dluh jen proto, \u017ee m\u00e1 tak\u00e9 technick\u00fd charakter.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">3. Test \u010dasu<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">M\u00e1 Container Feature konkr\u00e9tn\u00ed \u010dasov\u00fd horizont a okam\u017eik uzav\u0159en\u00ed?<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jedno PI, kvart\u00e1l nebo definovan\u00e1 migra\u010dn\u00ed etapa m\u016f\u017ee b\u00fdt rozumnou hranic\u00ed. \u201eBudeme ji pou\u017e\u00edvat, dokud ji budeme pot\u0159ebovat\u201c hranic\u00ed nen\u00ed.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">4. Test kapacity<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Existuje limit, kolik kapacity sm\u00ed kontejner spot\u0159ebovat?<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Bez limitu za\u010dne drobn\u00e1 pr\u00e1ce postupn\u011b vytla\u010dovat d\u016fle\u017eit\u011bj\u0161\u00ed v\u00fdsledky. Kapacitn\u00ed limit v\u0161ak nesm\u00ed b\u00fdt automatick\u00fdm n\u00e1rokem. Vyhrazen\u00fdch deset procent neznamen\u00e1, \u017ee je nutn\u00e9 za ka\u017edou cenu deset procent spot\u0159ebovat.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">5. Test integrity priorit<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Mus\u00ed ka\u017ed\u00e1 nov\u00e1 Story proj\u00edt skute\u010dn\u00fdm rozhodnut\u00edm o priorit\u011b, nebo se pod rodi\u010dem automaticky schov\u00e1?<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud spole\u010dn\u00fd kontejner obch\u00e1z\u00ed triage, po\u0159ad\u00ed backlogu nebo rozhodnut\u00ed o kapacit\u011b, je nebezpe\u010dn\u00fd bez ohledu na to, jak dob\u0159e je pojmenovan\u00fd.<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Pokud Container Feature nem\u00e1 \u00fa\u010del, hranici, \u010dasov\u00fd horizont, kapacitn\u00ed limit a pravidlo prioritizace, nejde o pom\u016fcku. Jde o ne\u0159\u00edzen\u00fd vstupn\u00ed kan\u00e1l do backlogu.<\/p><\/blockquote>\n\n\n\n\n<h2 class=\"wp-block-heading\">Konkr\u00e9tn\u00ed p\u0159\u00edklady z praxe<\/h2>\n\n\n\n\n<h3 class=\"wp-block-heading\">Drobn\u00e9 zm\u011bny trh\u016f \u2013 PI 3<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pod jednou Feature je dvacet p\u011bt po\u017eadavk\u016f z r\u016fzn\u00fdch zem\u00ed: zm\u011bna textace, nov\u00e9 pole ve formul\u00e1\u0159i, \u00faprava notifikace, lok\u00e1ln\u00ed valida\u010dn\u00ed pravidlo a export do dal\u0161\u00edho syst\u00e9mu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jednotliv\u00e9 Stories nemaj\u00ed spole\u010dn\u00fd v\u00fdsledek ani stejnou prioritu. Container Feature zde m\u016f\u017ee do\u010dasn\u011b pomoci s agregac\u00ed, ale pouze pokud m\u00e1 kapacitn\u00ed limit a ka\u017ed\u00fd po\u017eadavek proch\u00e1z\u00ed samostatnou prioritizac\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pro dlouhodob\u00e9 \u0159e\u0161en\u00ed bude pravd\u011bpodobn\u011b vhodn\u011bj\u0161\u00ed zachytit p\u016fvod po\u017eadavku pomoc\u00ed pole \u201eMarket\u201c nebo \u201eRequest source\u201c a v\u011bt\u0161\u00ed zm\u011bny formulovat jako samostatn\u00e9 v\u00fdsledkov\u00e9 Features.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Security updates \u2013 Q4<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">P\u0159edem zn\u00e1m\u00e1 sada aktualizac\u00ed knihoven m\u00e1 odstranit konkr\u00e9tn\u00ed skupinu bezpe\u010dnostn\u00edch zranitelnost\u00ed do konce kvart\u00e1lu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Tento kontejner m\u016f\u017ee fungovat dob\u0159e. M\u00e1 jasn\u00fd typ pr\u00e1ce, vlastn\u00edka, \u010dasovou hranici a ov\u011b\u0159iteln\u00fd provozn\u00ed v\u00fdsledek. Mus\u00ed se ale zabr\u00e1nit tomu, aby se pod n\u011bj za\u010dal ukl\u00e1dat ve\u0161ker\u00fd technick\u00fd dluh.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Frontend improvements<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Feature obsahuje Stories ze \u0161esti r\u016fzn\u00fdch z\u00e1kaznick\u00fdch cest. Jedin\u00e9, co maj\u00ed spole\u010dn\u00e9, je realizace frontendov\u00fdm t\u00fdmem.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Zde kontejner zakr\u00fdv\u00e1 skute\u010dnou strukturu hodnoty. Stories by m\u011bly b\u00fdt p\u0159ipojeny k v\u00fdsledkov\u00fdm Features podle zm\u011bny, kterou pom\u00e1haj\u00ed vytvo\u0159it. Frontendovou p\u0159\u00edslu\u0161nost lze evidovat pomoc\u00ed komponenty nebo odpov\u011bdn\u00e9ho t\u00fdmu.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Maintenance \u2013 10 % kapacity<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">T\u00fdm opr\u00e1vn\u011bn\u011b pot\u0159ebuje pr\u016fb\u011b\u017en\u011b v\u011bnovat \u010d\u00e1st kapacity \u00fadr\u017eb\u011b. Container Feature tuto spot\u0159ebu zviditeln\u00ed.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Probl\u00e9m nastane, kdy\u017e se deset procent kapacity za\u010dne ch\u00e1pat jako bianco \u0161ek. I maintenance polo\u017eky pot\u0159ebuj\u00ed po\u0159ad\u00ed, vstupn\u00ed pravidla a rozhodnut\u00ed, co se nyn\u00ed d\u011blat nebude.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Co pou\u017e\u00edt m\u00edsto Container Feature<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Ne ka\u017ed\u00e9 seskupen\u00ed pr\u00e1ce pot\u0159ebuje rodi\u010dovskou backlogovou polo\u017eku. Vhodn\u00e1 alternativa z\u00e1vis\u00ed na \u00fa\u010delu.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Skute\u010dn\u00e1 Feature orientovan\u00e1 na v\u00fdsledek<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud \u010d\u00e1st Stories skute\u010dn\u011b p\u0159isp\u00edv\u00e1 ke spole\u010dn\u00e9 zm\u011bn\u011b, seskupte je podle v\u00fdsledku. Ne podle technologie nebo t\u00fdmu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nap\u0159\u00edklad m\u00edsto \u201eDatabase changes\u201c m\u016f\u017ee vzniknout Feature \u201eZkr\u00e1cen\u00ed vyhled\u00e1n\u00ed z\u00e1kazn\u00edka pod dv\u011b sekundy\u201c. Datab\u00e1zov\u00e9 zm\u011bny jsou zp\u016fsob realizace, nikoliv samotn\u00fd v\u00fdsledek.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Samostatn\u00fd typ pr\u00e1ce<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud maintenance, provozn\u00ed zm\u011bny nebo regulatorn\u00ed polo\u017eky proch\u00e1zej\u00ed z\u00e1sadn\u011b jin\u00fdm rozhodovac\u00edm procesem, m\u016f\u017ee d\u00e1vat smysl samostatn\u00fd typ pr\u00e1ce.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Nen\u00ed c\u00edlem vytvo\u0159it deset nov\u00fdch issue typ\u016f. Jde o to p\u0159iznat, \u017ee n\u011bkter\u00e1 pr\u00e1ce m\u00e1 jinou povahu a nem\u011bla by b\u00fdt um\u011ble vyd\u00e1v\u00e1na za produktovou Feature.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Label, komponenta nebo reportingov\u00e9 pole<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pot\u0159ebujete-li polo\u017eky pouze filtrovat nebo agregovat podle trhu, komponenty, t\u00fdmu \u010di typu n\u00e1klad\u016f, pou\u017eijte datov\u00fd atribut. Reportingov\u00e1 klasifikace nemus\u00ed vytv\u00e1\u0159et novou \u00farove\u0148 backlogu.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Technick\u00fd outcome nebo Enabler<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Technick\u00e1 pr\u00e1ce nemus\u00ed m\u00edt bezprost\u0159edn\u011b viditeln\u00fd z\u00e1kaznick\u00fd v\u00fdstup. To ale neznamen\u00e1, \u017ee nem\u016f\u017ee m\u00edt konkr\u00e9tn\u00ed v\u00fdsledek.<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>zkr\u00e1cen\u00ed nasazen\u00ed z dvou hodin na patn\u00e1ct minut,<\/li>\n<li>odstran\u011bn\u00ed konkr\u00e9tn\u00edho bezpe\u010dnostn\u00edho rizika,<\/li>\n<li>zv\u00fd\u0161en\u00ed dostupnosti slu\u017eby,<\/li>\n<li>sn\u00ed\u017een\u00ed n\u00e1klad\u016f na infrastrukturu,<\/li>\n<li>umo\u017en\u011bn\u00ed budouc\u00ed produktov\u00e9 zm\u011bny.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Takto formulovan\u00e1 technick\u00e1 Feature nebo Enabler je podstatn\u011b l\u00e9pe \u0159iditeln\u00e1 ne\u017e obecn\u00fd kontejner \u201eTechnical improvements\u201c.<\/p>\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>Ka\u017ed\u00e1 Story mus\u00ed m\u00edt Feature.<\/strong> Z n\u00e1strojov\u00e9 konvence se stane domn\u011bl\u00e9 agiln\u00ed pravidlo.<\/li>\n<li><strong>Feature je ch\u00e1p\u00e1na pouze jako v\u011bt\u0161\u00ed polo\u017eka.<\/strong> Velikost sama o sob\u011b nevytv\u00e1\u0159\u00ed spole\u010dn\u00fd v\u00fdsledek.<\/li>\n<li><strong>Spole\u010dn\u00fd t\u00fdm se zam\u011bn\u00ed za spole\u010dnou hodnotu.<\/strong> Organiza\u010dn\u00ed struktura za\u010dne ur\u010dovat strukturu backlogu.<\/li>\n<li><strong>Container Feature z\u016fst\u00e1v\u00e1 otev\u0159en\u00e1 n\u011bkolik obdob\u00ed.<\/strong> Nov\u00e1 pr\u00e1ce se do n\u00ed p\u0159id\u00e1v\u00e1 rychleji, ne\u017e se dokon\u010duje.<\/li>\n<li><strong>Business Value se p\u0159id\u011bl\u00ed cel\u00e9mu kontejneru.<\/strong> P\u0159itom ka\u017ed\u00e1 Story m\u016f\u017ee m\u00edt jinou hodnotu, nal\u00e9havost i riziko.<\/li>\n<li><strong>Procento dokon\u010den\u00fdch Stories se vyd\u00e1v\u00e1 za pokrok v\u00fdsledku.<\/strong> Uzav\u0159en\u00e9 tickety je\u0161t\u011b neznamenaj\u00ed dosa\u017een\u00fd outcome.<\/li>\n<li><strong>Kontejner obch\u00e1z\u00ed prioritizaci.<\/strong> Nov\u00e1 Story se pova\u017euje za schv\u00e1lenou jen proto, \u017ee se ve\u0161la pod existuj\u00edc\u00edho rodi\u010de.<\/li>\n<li><strong>Do jednoho kontejneru se sm\u00edch\u00e1 produktov\u00e1, technick\u00e1, provozn\u00ed a regulatorn\u00ed pr\u00e1ce.<\/strong> Ka\u017ed\u00fd typ p\u0159itom m\u016f\u017ee vy\u017eadovat jin\u00fd zp\u016fsob rozhodov\u00e1n\u00ed.<\/li>\n<li><strong>Do\u010dasn\u00e9 \u0159e\u0161en\u00ed nem\u00e1 datum ukon\u010den\u00ed.<\/strong> Po n\u011bkolika m\u011bs\u00edc\u00edch u\u017e nikdo nev\u00ed, pro\u010d bylo zavedeno.<\/li>\n<li><strong>Organizace nejprve m\u011bn\u00ed Jira a a\u017e potom diskutuje pravidla.<\/strong> Nov\u00e1 konfigurace pouze p\u0159esn\u011bji automatizuje p\u016fvodn\u00ed nejasnosti.<\/li>\n<\/ul>\n\n\n\n\n<h2 class=\"wp-block-heading\">Jak nastavit Container Feature, kdy\u017e ji opravdu pot\u0159ebujete<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Legitimn\u00ed Container Feature by m\u011bla m\u00edt kr\u00e1tkou a viditelnou policy. M\u016f\u017ee b\u00fdt uvedena p\u0159\u00edmo v popisu polo\u017eky nebo na spole\u010dn\u00e9 str\u00e1nce s pravidly backlogu.<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>\u00da\u010del:<\/strong> Pro\u010d kontejner existuje?<\/li>\n<li><strong>P\u0159\u00edpustn\u00fd obsah:<\/strong> Jak\u00e9 polo\u017eky do n\u011bj mohou vstoupit?<\/li>\n<li><strong>Zak\u00e1zan\u00fd obsah:<\/strong> Co do n\u011bj naopak nepat\u0159\u00ed?<\/li>\n<li><strong>\u010casov\u00fd horizont:<\/strong> Kdy bude uzav\u0159en?<\/li>\n<li><strong>Kapacitn\u00ed limit:<\/strong> Kolik pr\u00e1ce sm\u00ed spot\u0159ebovat?<\/li>\n<li><strong>Vlastn\u00edk:<\/strong> Kdo rozhoduje o p\u0159ijet\u00ed nov\u00e9 polo\u017eky?<\/li>\n<li><strong>Prioritizace:<\/strong> Jak se \u0159ad\u00ed jednotliv\u00e9 Stories?<\/li>\n<li><strong>Podm\u00ednka uzav\u0159en\u00ed:<\/strong> Co p\u0159esn\u011b znamen\u00e1 Done?<\/li>\n<li><strong>Pl\u00e1n n\u00e1hrady:<\/strong> M\u00e1 b\u00fdt kontejner v budoucnu nahrazen lep\u0161\u00edm reportingov\u00fdm \u0159e\u0161en\u00edm?<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Tento p\u0159\u00edstup odpov\u00edd\u00e1 obecn\u011bj\u0161\u00edmu principu explicitn\u00edch pravidel. Aktu\u00e1ln\u00ed <a href=\"https:\/\/kanbanguides.org\/the-kanban-guide\/\">Kanban Guide<\/a> zd\u016fraz\u0148uje pot\u0159ebu jasn\u011b definovat workflow, \u0159\u00edzen\u00ed rozpracovanosti a pravidla, podle kter\u00fdch mohou polo\u017eky syst\u00e9mem proudit.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature tedy nemus\u00ed b\u00fdt pops\u00e1na v konkr\u00e9tn\u00edm frameworku. Mus\u00ed ale b\u00fdt transparentn\u00ed a \u0159iditeln\u00e1.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Pojmenov\u00e1n\u00ed by nem\u011blo zakr\u00fdvat realitu<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jestli\u017ee jde o technick\u00fd nebo reportingov\u00fd kontejner, pojmenujte jej tak.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Lep\u0161\u00ed n\u00e1zvy:<\/strong><\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>[CONTAINER] Maintenance \u2013 Q4 2026<\/li>\n<li>[CONTAINER] Drobn\u00e9 regulatorn\u00ed zm\u011bny \u2013 PI 3<\/li>\n<li>[CONTAINER] Security updates \u2013 \u010dasov\u011b omezen\u00fd bal\u00edk<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\"><strong>Rizikov\u00e9 n\u00e1zvy:<\/strong><\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>Platform Improvements<\/li>\n<li>Customer Experience<\/li>\n<li>Technical Excellence<\/li>\n<li>Other Features<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Obecn\u00fd produktov\u011b zn\u011bj\u00edc\u00ed n\u00e1zev m\u016f\u017ee vytv\u00e1\u0159et dojem skute\u010dn\u00e9ho v\u00fdsledku, i kdy\u017e jde pouze o administrativn\u00ed ob\u00e1lku.<\/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\">Nen\u00ed pot\u0159eba okam\u017eit\u011b p\u0159ekreslovat celou hierarchii backlogu nebo m\u011bnit konfiguraci Jira. Za\u010dn\u011bte kr\u00e1tk\u00fdm auditem existuj\u00edc\u00edch Features.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Audit Container Features za 60 minut<\/h3>\n\n\n\n\n<ol class=\"wp-block-list\">\n<li>Vyberte v\u0161echny Features, kter\u00e9 byly otev\u0159en\u00e9 b\u011bhem posledn\u00edch dvou PI nebo kvart\u00e1l\u016f.<\/li>\n<li>Ozna\u010dte polo\u017eky obsahuj\u00edc\u00ed n\u00e1zvy jako \u201eimprovements\u201c, \u201etechnical\u201c, \u201esupport\u201c, \u201emaintenance\u201c, \u201eother\u201c, n\u00e1zev t\u00fdmu nebo \u010dasov\u00e9 obdob\u00ed.<\/li>\n<li>U ka\u017ed\u00e9 podez\u0159el\u00e9 Feature vyberte t\u0159i n\u00e1hodn\u00e9 Stories.<\/li>\n<li>Zkuste jednou v\u011btou formulovat jejich spole\u010dn\u00fd v\u00fdsledek.<\/li>\n<li>Ov\u011b\u0159te, zda m\u00e1 polo\u017eka alespo\u0148 jasn\u00fd \u00fa\u010del, hranici, limit a datum ukon\u010den\u00ed.<\/li>\n<li>Rozd\u011blte ji do jedn\u00e9 ze t\u0159\u00ed kategori\u00ed: skute\u010dn\u00e1 Feature, \u0159\u00edzen\u00fd kontejner, backlogov\u00fd odpadkov\u00fd ko\u0161.<\/li>\n<li>Vyberte jeden odpadkov\u00fd ko\u0161 a b\u011bhem nejbli\u017e\u0161\u00edho refinementu jej opravte.<\/li>\n<\/ol>\n\n\n\n\n<h3 class=\"wp-block-heading\">Rozd\u011blte existuj\u00edc\u00ed polo\u017eky do t\u0159\u00ed skupin<\/h3>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li><strong>Skute\u010dn\u00e9 Features:<\/strong> maj\u00ed spole\u010dn\u00fd v\u00fdsledek, hranici a lze je prioritizovat jako celek.<\/li>\n<li><strong>\u0158\u00edzen\u00e9 kontejnery:<\/strong> maj\u00ed legitimn\u00ed agrega\u010dn\u00ed \u00fa\u010del, limit, \u010dasov\u00fd horizont a explicitn\u00ed pravidla.<\/li>\n<li><strong>Odpadkov\u00e9 ko\u0161e:<\/strong> obsahuj\u00ed nesouvisej\u00edc\u00ed pr\u00e1ci, nemaj\u00ed hranici a obch\u00e1zej\u00ed prioritizaci.<\/li>\n<\/ul>\n\n\n\n\n<h3 class=\"wp-block-heading\">Opravte nejprve jedin\u00fd p\u0159\u00edpad<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Vyberte jednu Container Feature a:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>odd\u011blte Stories, kter\u00e9 tvo\u0159\u00ed skute\u010dn\u00fd spole\u010dn\u00fd v\u00fdsledek,<\/li>\n<li>vytvo\u0159te pro n\u011b v\u00fdsledkovou Feature,<\/li>\n<li>ostatn\u00ed polo\u017eky se\u0159a\u010fte podle priority,<\/li>\n<li>pro reporting pou\u017eijte vhodn\u00fd atribut,<\/li>\n<li>a nastavte jedno jednoduch\u00e9 pravidlo pro vznik dal\u0161\u00edch kontejner\u016f.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Teprve na z\u00e1klad\u011b t\u00e9to zku\u0161enosti rozhodujte, zda je pot\u0159eba m\u011bnit issue typy, workflow nebo programov\u00fd reporting.<\/p>\n\n\n\n\n<h3 class=\"wp-block-heading\">Po jednom obdob\u00ed ov\u011b\u0159te dopad<\/h3>\n\n\n\n\n<p class=\"wp-block-paragraph\">Sledujte nap\u0159\u00edklad:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>po\u010det dlouhodob\u011b otev\u0159en\u00fdch Features,<\/li>\n<li>st\u00e1\u0159\u00ed rozpracovan\u00fdch polo\u017eek,<\/li>\n<li>mno\u017estv\u00ed nov\u011b p\u0159idan\u00e9 pr\u00e1ce b\u011bhem realizace,<\/li>\n<li>po\u010det Stories bez jasn\u00e9ho v\u00fdsledku,<\/li>\n<li>objem pr\u00e1ce p\u0159ijat\u00e9 mimo b\u011b\u017enou prioritizaci,<\/li>\n<li>pod\u00edl kapacity spot\u0159ebovan\u00fd jednotliv\u00fdmi kontejnery.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">Metriky maj\u00ed pomoci s rozhodov\u00e1n\u00edm, ne pouze vytvo\u0159it hez\u010d\u00ed dashboard. Kanban Guide mezi z\u00e1kladn\u00ed flow metriky \u0159ad\u00ed nap\u0159\u00edklad rozpracovanost, throughput, st\u00e1\u0159\u00ed polo\u017eek a cycle time. Pro pr\u00e1ci s Container Features bude \u010dasto nejzaj\u00edmav\u011bj\u0161\u00ed jejich st\u00e1\u0159\u00ed a mno\u017estv\u00ed pr\u00e1ce, kter\u00e1 do nich p\u0159ib\u00fdv\u00e1 po zah\u00e1jen\u00ed. <\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Probl\u00e9m \u010dasto nen\u00ed v typu ticketu<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature b\u00fdv\u00e1 viditeln\u00fdm p\u0159\u00edznakem hlub\u0161\u00edho probl\u00e9mu. Organizace nap\u0159\u00edklad nem\u00e1 jasno:<\/p>\n\n\n\n\n<ul class=\"wp-block-list\">\n<li>jak se strategick\u00e9 priority p\u0159ekl\u00e1daj\u00ed do backlogu,<\/li>\n<li>kter\u00e1 rozhodnut\u00ed pat\u0159\u00ed na programovou a kter\u00e1 na t\u00fdmovou \u00farove\u0148,<\/li>\n<li>kdo m\u016f\u017ee p\u0159ij\u00edmat novou pr\u00e1ci,<\/li>\n<li>jak se pracuje s nepl\u00e1novan\u00fdmi po\u017eadavky,<\/li>\n<li>jak\u00fd typ pr\u00e1ce m\u00e1 p\u0159ednost p\u0159i omezen\u00e9 kapacit\u011b,<\/li>\n<li>nebo co vlastn\u011b znamen\u00e1 dokon\u010den\u00ed Feature.<\/li>\n<\/ul>\n\n\n\n\n<p class=\"wp-block-paragraph\">V takov\u00e9 situaci nepom\u016f\u017ee pouze p\u0159ejmenovat Container Feature nebo p\u0159idat nov\u00e9 povinn\u00e9 pole. Je pot\u0159eba sladit prioritizaci, role, rozhodovac\u00ed pravidla a samotnou strukturu backlogu.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud se strategie a priority p\u0159i p\u0159ekladu do pr\u00e1ce t\u00fdm\u016f pravideln\u011b ztr\u00e1cej\u00ed, m\u016f\u017ee b\u00fdt u\u017eite\u010dn\u00e9 pod\u00edvat se na p\u0159\u00edstup <a href=\"https:\/\/ab.jakub-drbohlav.cz\/produkty\/strategy-to-execution\/\">Strategy-to-Execution<\/a>. Je zam\u011b\u0159en\u00fd na propojen\u00ed strategick\u00fdch c\u00edl\u016f s prioritami, backlogy a pravidly, podle kter\u00fdch se v organizaci skute\u010dn\u011b rozhoduje.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Dal\u0161\u00ed praktick\u00e9 materi\u00e1ly, kr\u00e1tk\u00e9 kurzy a toolkity pro pr\u00e1ci s flow, p\u0159edv\u00eddatelnost\u00ed a \u0159\u00edzen\u00edm backlogu postupn\u011b p\u0159id\u00e1v\u00e1me tak\u00e9 do <a href=\"https:\/\/academy.agilebrothers.cz\/zdroje\">Agile Brothers Academy<\/a>.<\/p>\n\n\n\n\n<h2 class=\"wp-block-heading\">Shrnut\u00ed: probl\u00e9m nen\u00ed kontejner, ale rozhodnut\u00ed, kter\u00e1 nahrazuje<\/h2>\n\n\n\n\n<p class=\"wp-block-paragraph\">Container Feature nen\u00ed automaticky chyba. M\u016f\u017ee b\u00fdt u\u017eite\u010dnou pom\u016fckou pro agregaci drobn\u00e9, provozn\u00ed nebo technick\u00e9 pr\u00e1ce, zejm\u00e9na pokud sou\u010dasn\u00fd n\u00e1stroj nebo reporting neum\u00ed tuto pr\u00e1ci zachytit jinak.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Mus\u00ed v\u0161ak b\u00fdt z\u0159ejm\u00e9, \u017ee nejde o skute\u010dnou v\u00fdsledkovou Feature. Pot\u0159ebuje jasn\u00fd \u00fa\u010del, hranici, \u010dasov\u00fd horizont, kapacitn\u00ed limit, vlastn\u00edka a pravidla prioritizace.<\/p>\n\n\n\n\n<p class=\"wp-block-paragraph\">Jakmile kontejner z\u016fst\u00e1v\u00e1 otev\u0159en\u00fd n\u011bkolik obdob\u00ed, p\u0159ij\u00edm\u00e1 nesouvisej\u00edc\u00ed Stories nebo umo\u017e\u0148uje obch\u00e1zet rozhodov\u00e1n\u00ed o hodnot\u011b a kapacit\u011b, za\u010d\u00edn\u00e1 zakr\u00fdvat nefunk\u010dn\u00ed backlog.<\/p>\n\n\n\n\n<blockquote class=\"wp-block-quote is-layout-flow wp-block-quote-is-layout-flow\"><p>Backlog nen\u00ed funk\u010dn\u00ed proto, \u017ee m\u00e1 ka\u017ed\u00e1 Story rodi\u010de. Je funk\u010dn\u00ed tehdy, kdy\u017e je z n\u011bj patrn\u00e9, pro\u010d pr\u00e1ci d\u011bl\u00e1me, jak\u00fd v\u00fdsledek o\u010dek\u00e1v\u00e1me, kdo rozhodl o jej\u00ed priorit\u011b a kdy ji m\u016f\u017eeme pova\u017eovat za skute\u010dn\u011b dokon\u010denou.<\/p><\/blockquote>\n\n\n\n\n<p class=\"wp-block-paragraph\">Pokud ve sv\u00e9m backlogu nach\u00e1z\u00edte n\u011bkolik nekone\u010dn\u00fdch kontejner\u016f a nen\u00ed jasn\u00e9, kter\u00fd probl\u00e9m \u0159e\u0161it jako prvn\u00ed, m\u016f\u017eeme se spole\u010dn\u011b pod\u00edvat na konkr\u00e9tn\u00ed Features a Stories. \u010casto sta\u010d\u00ed kr\u00e1tk\u00fd pohled zven\u010d\u00ed, aby bylo mo\u017en\u00e9 odli\u0161it n\u00e1strojov\u00fd kompromis od probl\u00e9mu v prioritizaci nebo \u0159\u00edzen\u00ed pr\u00e1ce.<\/p>\n\n\n\n\n<div class=\"wp-block-buttons is-layout-flex wp-block-buttons-is-layout-flex\">\n<div class=\"wp-block-button\"><a class=\"wp-block-button__link wp-element-button\" href=\"https:\/\/ab.jakub-drbohlav.cz\/produkty\/\">Probrat n\u00e1\u0161 backlog<\/a><\/div>\n<\/div>\n\n","protected":false},"excerpt":{"rendered":"<p>Container Feature m\u016f\u017ee b\u00fdt u\u017eite\u010dnou pom\u016fckou pro \u0159\u00edzen\u00ed drobn\u00e9, technick\u00e9 nebo provozn\u00ed pr\u00e1ce. Stejn\u011b snadno se z n\u00ed ale stane nekone\u010dn\u00fd kontejner na nesouvisej\u00edc\u00ed Stories, kter\u00fd obch\u00e1z\u00ed prioritizaci a vytv\u00e1\u0159\u00ed fale\u0161n\u00fd obraz o stavu dod\u00e1vky. Jak oba p\u0159\u00edpady rozli\u0161it a jak nastavit pravidla, aby Container Feature nezakr\u00fdvala nefunk\u010dn\u00ed backlog?<\/p>\n","protected":false},"author":4,"featured_media":1326,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[101,103,111],"tags":[259,224,257,218,207,261,217,244,255,260,225,258],"class_list":["post-1325","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-flow-a-predvidatelnost","category-operating-model","category-transformation-playbook","tag-art-backlog","tag-backlog","tag-container-feature","tag-feature","tag-flow","tag-hierarchie-backlogu","tag-jira","tag-prioritizace","tag-product-owner","tag-programovy-backlog","tag-safe","tag-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>Container Feature: kdy pom\u00e1h\u00e1 a kdy zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog - Blog Agile Brothers<\/title>\n<meta name=\"description\" content=\"Kdy Container Feature pom\u00e1h\u00e1 \u0159\u00eddit drobnou pr\u00e1ci a kdy jen zakr\u00fdv\u00e1 chaos v backlogu? Praktick\u00e9 testy, p\u0159\u00edklady a pravidla pou\u017eit\u00ed.\" \/>\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\/container-feature-nefunkcni-backlog\/\" \/>\n<meta property=\"og:locale\" content=\"cs_CZ\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog\" \/>\n<meta property=\"og:description\" content=\"%\" \/>\n<meta property=\"og:url\" content=\"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/\" \/>\n<meta property=\"og:site_name\" content=\"Blog Agile Brothers\" \/>\n<meta property=\"article:published_time\" content=\"2026-07-13T10:46:43+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2026-07-13T14:11:45+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.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\\\/container-feature-nefunkcni-backlog\\\/#article\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/\"},\"author\":{\"name\":\"Milan Drbohlav\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#\\\/schema\\\/person\\\/8820a946316ac68645371e2a16fa77cb\"},\"headline\":\"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog\",\"datePublished\":\"2026-07-13T10:46:43+00:00\",\"dateModified\":\"2026-07-13T14:11:45+00:00\",\"mainEntityOfPage\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/\"},\"wordCount\":3731,\"publisher\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#organization\"},\"image\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Container-feature.png\",\"keywords\":[\"ART backlog\",\"backlog\",\"Container Feature\",\"Feature\",\"flow\",\"hierarchie backlogu\",\"Jira\",\"prioritizace\",\"Product Owner\",\"programov\u00fd backlog\",\"SAFe\",\"Story\"],\"articleSection\":[\"Flow &amp; P\u0159edv\u00eddatelnost\",\"Operating model\",\"Transformation playbook\"],\"inLanguage\":\"cs\"},{\"@type\":\"WebPage\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/\",\"name\":\"Container Feature: kdy pom\u00e1h\u00e1 a kdy zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog - Blog Agile Brothers\",\"isPartOf\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#primaryimage\"},\"image\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#primaryimage\"},\"thumbnailUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Container-feature.png\",\"datePublished\":\"2026-07-13T10:46:43+00:00\",\"dateModified\":\"2026-07-13T14:11:45+00:00\",\"description\":\"Kdy Container Feature pom\u00e1h\u00e1 \u0159\u00eddit drobnou pr\u00e1ci a kdy jen zakr\u00fdv\u00e1 chaos v backlogu? Praktick\u00e9 testy, p\u0159\u00edklady a pravidla pou\u017eit\u00ed.\",\"breadcrumb\":{\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#breadcrumb\"},\"inLanguage\":\"cs\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"cs\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#primaryimage\",\"url\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Container-feature.png\",\"contentUrl\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/wp-content\\\/uploads\\\/2026\\\/07\\\/Container-feature.png\",\"width\":1672,\"height\":941,\"caption\":\"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/container-feature-nefunkcni-backlog\\\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Dom\u016f\",\"item\":\"https:\\\/\\\/agilebrothers.cz\\\/blog\\\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog\"}]},{\"@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":"Container Feature: kdy pom\u00e1h\u00e1 a kdy zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog - Blog Agile Brothers","description":"Kdy Container Feature pom\u00e1h\u00e1 \u0159\u00eddit drobnou pr\u00e1ci a kdy jen zakr\u00fdv\u00e1 chaos v backlogu? Praktick\u00e9 testy, p\u0159\u00edklady a pravidla pou\u017eit\u00ed.","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\/container-feature-nefunkcni-backlog\/","og_locale":"cs_CZ","og_type":"article","og_title":"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog","og_description":"%","og_url":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/","og_site_name":"Blog Agile Brothers","article_published_time":"2026-07-13T10:46:43+00:00","article_modified_time":"2026-07-13T14:11:45+00:00","og_image":[{"width":1672,"height":941,"url":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.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\/container-feature-nefunkcni-backlog\/#article","isPartOf":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/"},"author":{"name":"Milan Drbohlav","@id":"https:\/\/agilebrothers.cz\/blog\/#\/schema\/person\/8820a946316ac68645371e2a16fa77cb"},"headline":"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog","datePublished":"2026-07-13T10:46:43+00:00","dateModified":"2026-07-13T14:11:45+00:00","mainEntityOfPage":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/"},"wordCount":3731,"publisher":{"@id":"https:\/\/agilebrothers.cz\/blog\/#organization"},"image":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#primaryimage"},"thumbnailUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.png","keywords":["ART backlog","backlog","Container Feature","Feature","flow","hierarchie backlogu","Jira","prioritizace","Product Owner","programov\u00fd backlog","SAFe","Story"],"articleSection":["Flow &amp; P\u0159edv\u00eddatelnost","Operating model","Transformation playbook"],"inLanguage":"cs"},{"@type":"WebPage","@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/","url":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/","name":"Container Feature: kdy pom\u00e1h\u00e1 a kdy zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog - Blog Agile Brothers","isPartOf":{"@id":"https:\/\/agilebrothers.cz\/blog\/#website"},"primaryImageOfPage":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#primaryimage"},"image":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#primaryimage"},"thumbnailUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.png","datePublished":"2026-07-13T10:46:43+00:00","dateModified":"2026-07-13T14:11:45+00:00","description":"Kdy Container Feature pom\u00e1h\u00e1 \u0159\u00eddit drobnou pr\u00e1ci a kdy jen zakr\u00fdv\u00e1 chaos v backlogu? Praktick\u00e9 testy, p\u0159\u00edklady a pravidla pou\u017eit\u00ed.","breadcrumb":{"@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#breadcrumb"},"inLanguage":"cs","potentialAction":[{"@type":"ReadAction","target":["https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/"]}]},{"@type":"ImageObject","inLanguage":"cs","@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#primaryimage","url":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.png","contentUrl":"https:\/\/agilebrothers.cz\/blog\/wp-content\/uploads\/2026\/07\/Container-feature.png","width":1672,"height":941,"caption":"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog"},{"@type":"BreadcrumbList","@id":"https:\/\/agilebrothers.cz\/blog\/container-feature-nefunkcni-backlog\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Dom\u016f","item":"https:\/\/agilebrothers.cz\/blog\/"},{"@type":"ListItem","position":2,"name":"Kdy Container Feature pom\u00e1h\u00e1 \u2013 a kdy jen zakr\u00fdv\u00e1 nefunk\u010dn\u00ed backlog"}]},{"@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\/1325","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=1325"}],"version-history":[{"count":1,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts\/1325\/revisions"}],"predecessor-version":[{"id":1327,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/posts\/1325\/revisions\/1327"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/media\/1326"}],"wp:attachment":[{"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/media?parent=1325"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/categories?post=1325"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agilebrothers.cz\/blog\/wp-json\/wp\/v2\/tags?post=1325"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}