{"id":968,"date":"2019-08-24T03:53:52","date_gmt":"2019-08-24T02:53:52","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=968"},"modified":"2019-08-25T07:22:22","modified_gmt":"2019-08-25T06:22:22","slug":"jeden-produkt-jeden-product-owner","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/jeden-produkt-jeden-product-owner\/","title":{"rendered":"Jeden produkt, jeden Product Owner"},"content":{"rendered":"<p>Jeden z nej\u010dast\u011bj\u0161\u00edch dotaz\u016f je, pro\u010d m\u00e1 b\u00fdt ve Scrumu jeden Product Owner na cel\u00fd produkt, pro\u010d na ka\u017ed\u00fd syst\u00e9m nen\u00ed jin\u00fd Product Owner (tedy pro\u010d nem\u00e1me komisi Product Owner\u016f) pop\u0159\u00edpad\u011b pro\u010d ka\u017ed\u00fd t\u00fdm nem\u00e1 sv\u00e9ho Product Ownera (team PO, proxy PO). A kdy\u017e u\u017e tedy m\u00e1me jednoho PO jak to m\u016f\u017ee v\u0161echno stihnout.<\/p>\n<p>Za\u010dneme od za\u010d\u00e1tku. Jednoho PO m\u00e1me, proto\u017ee m\u00e1me jeden produkt. A ten pot\u0159ebuje pro sv\u016fj \u00fasp\u011bch jasn\u00fd sm\u011br, jasnou vizi na jej\u00edm\u017e z\u00e1klad\u011b m\u00e1 ka\u017ed\u00fd produkt jeden prioritizovan\u00fd backlog na z\u00e1klad\u011b business value. Komise je t\u011b\u017ekop\u00e1dn\u00e1, nem\u00e1 na v\u011bci jednotn\u00fd pohled a jen t\u011b\u017eko se domluv\u00ed. Obvykle kon\u010d\u00ed doporu\u010den\u00edm, \u017ee tohle v\u0161echno mus\u00edte ud\u011blat jako prioritu jedna. Tedy m\u00e1te skupinu stakeholder\u016f (nebo z\u00e1kazn\u00edk\u016f, jak je v agiln\u00edm sv\u011bt\u011b naz\u00fdv\u00e1me), ale \u017e\u00e1dn\u00e9ho Product Ownera. Konsekvence je nekvalitn\u00ed backlog, nejasn\u00e9 priority a z\u00e1kulisn\u00ed boje. T\u00fdmov\u00fd \/Proxy Product Owner je zase ne\u0161var, kter\u00fd jsme zd\u011bdili z klasick\u00e9ho vn\u00edm\u00e1n\u00ed development t\u00fdmu jako tzv. \u2018Coding monkeys\u2019 tedy cod\u00e9r\u016f, kte\u0159\u00ed tup\u011b nak\u00f3duj\u00ed co n\u011bkdo jin\u00fd naspecifikoval bez toho, ani\u017e by jakkoli p\u0159em\u00fd\u0161leli, jestli dan\u00e1 implementace vede k c\u00edli. V lep\u0161\u00edm p\u0159\u00edpad\u011b component t\u00fdm\u016f (kter\u00e9 maj\u00ed na starosti jen ur\u010ditou \u010d\u00e1st syst\u00e9mu) a nedok\u00e1\u017eou tak \u017e\u00e1dnou hodnotu dodat. Kdy\u017e t\u00fdmy nedod\u00e1vaj\u00ed end-to-end hodnotu, nem\u016f\u017eou z\u00edskat relevantn\u00ed zp\u011btnou vazbu a cel\u00e9 Sprint Review je zbyte\u010dn\u00e9. Component t\u00fdmy nemaj\u00ed dostate\u010dn\u00fd p\u0159ehled o celkov\u00e9m businessu, po\u017eadavk\u016fm ve form\u011b user story nerozum\u00ed, a tak po\u017eaduj\u00ed, aby jim n\u011bkdo napsal <a title=\"Akcepta\u010dn\u00ed krit\u00e9ria jsou ze star\u00e9ho neagiln\u00edho sv\u011bta\" href=\"http:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/akceptacni-kriteria-jsou-ze-stareho-neagilniho-sveta\/\">detailn\u00ed akcepta\u010dn\u00ed kriteria<\/a> \/specifikaci, aby v\u011bd\u011bli co se m\u00e1 v dan\u00e9 komponent\u011b ud\u011blat. A proto\u017ee businessov\u011b orientovan\u00fd PO v\u011bcem technicky nerozum\u00ed a ani na to nem\u00e1 \u010das, instaluj\u00ed asistenta, kter\u00fd jim to p\u0159ipravuje. A jsme zp\u011bt ve waterfallu. Nejd\u0159\u00edv se ud\u011bl\u00e1 specifikace, pak podle n\u00ed vyv\u00edj\u00ed produkt. Tak\u017ee tudy cesta tak\u00e9 nevede. Tedy jestli chcete z\u016fstat v tradi\u010dn\u00edm sv\u011bt\u011b, pro\u010d ne. Rozhodnut\u00ed je na v\u00e1s. Jestli ale chcete aplikovat Scrum tak jak byl zam\u00fd\u0161len\u00fd, a hlavn\u011b tak aby fungoval, odpov\u011b\u010f je snadn\u00e1.<\/p>\n<p><img loading=\"lazy\" class=\"alignleft wp-image-970\" style=\"color: #000000;\" src=\"http:\/\/soch.cz\/blog\/wp-content\/uploads\/2019\/08\/2019-08-23-21.49.25-1024x768.png\" alt=\"Backlog Refinement is about collaboration\" width=\"600\" height=\"450\" srcset=\"https:\/\/soch.cz\/blog\/wp-content\/uploads\/2019\/08\/2019-08-23-21.49.25-1024x768.png 1024w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2019\/08\/2019-08-23-21.49.25-300x225.png 300w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2019\/08\/2019-08-23-21.49.25-900x675.png 900w, https:\/\/soch.cz\/blog\/wp-content\/uploads\/2019\/08\/2019-08-23-21.49.25.png 2048w\" sizes=\"(max-width: 709px) 85vw, (max-width: 909px) 67vw, (max-width: 984px) 61vw, (max-width: 1362px) 45vw, 600px\" \/>Jeden produkt (a o tom <a title=\"Co je to produkt a co projekt\" href=\"http:\/\/soch.cz\/blog\/management\/agile\/co-je-to-produkt-a-co-projekt\/\">jak se takov\u00fd produkt definuje<\/a> u\u017e jsem tu psala) m\u00e1 jednu vizi, jeden backlog, a tedy i jednoho PO. Na produktu m\u016f\u017ee pracovat n\u011bkolik cross-functional t\u00fdm\u016f, kter\u00e9 ka\u017ed\u00fd za sebe dok\u00e1\u017eou dodat end-to-end hodnotu, tedy pln\u011b funk\u010dn\u00ed produkt. Aby to jeden PO zvl\u00e1dal, nepracuje s\u00e1m, ale v r\u00e1mci backlog refinementu mu pom\u00e1haj\u00ed ji\u017e zm\u00edn\u011bn\u00e9 t\u00fdmy, kter\u00e9 spole\u010dn\u011b s PO a z\u00e1kazn\u00edky backlog p\u0159ipravuj\u00ed a staraj\u00ed se o to, \u017ee v\u0161ichni rozum\u00ed priorit\u00e1m i jednotliv\u00fdm polo\u017ek\u00e1m backlogu. Asi nej\u010dast\u011bj\u0161\u00ed chybou, kter\u00e1 k v\u00fd\u0161e zm\u00edn\u011bn\u00e9mu \u2018fake PO\u2019 vede je p\u0159edstava, \u017ee Product Owner p\u00ed\u0161e polo\u017eky backlogu, kter\u00e9 kdy\u017e jsou ready p\u0159ed\u00e1v\u00e1 t\u00fdmu a ten je podle jeho po\u017eadavk\u016f naimplemetuje. Tak to ale ve Scrumu b\u00fdt nem\u00e1 a nikdy b\u00fdt nem\u011blo. Refinement je t\u00fdmov\u00e1 pr\u00e1ce a pod\u00edl\u00ed se na n\u00ed v\u0161ichni. Z\u00e1kazn\u00edci, stakeholde\u0159i, u\u017eivatel\u00e9, cross-functional t\u00fdmy, a Product Owner a polo\u017eky backlogu definuj\u00ed spole\u010dn\u011b.<\/p>\n<p>Kdy\u017e to cel\u00e9 zjednodu\u0161\u00edm. Scrum je o t\u00fdmov\u00e9 spolupr\u00e1ci (nejen v r\u00e1mci Scrum t\u00fdmu ale i se z\u00e1kazn\u00edky), jasn\u00fdch priorit\u00e1ch (proto m\u00e1me jednu hlavu, jednoho Product Ownera) a dod\u00e1v\u00e1n\u00ed hodnoty (cross-functional t\u00fdmy).<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Jeden z nej\u010dast\u011bj\u0161\u00edch dotaz\u016f je, pro\u010d m\u00e1 b\u00fdt ve Scrumu jeden Product Owner na cel\u00fd produkt, pro\u010d na ka\u017ed\u00fd syst\u00e9m nen\u00ed jin\u00fd Product Owner (tedy pro\u010d nem\u00e1me komisi Product Owner\u016f) pop\u0159\u00edpad\u011b pro\u010d ka\u017ed\u00fd t\u00fdm nem\u00e1 sv\u00e9ho Product Ownera (team PO, proxy PO). A kdy\u017e u\u017e tedy m\u00e1me jednoho PO jak to m\u016f\u017ee v\u0161echno stihnout. Za\u010dneme &hellip; <a href=\"https:\/\/soch.cz\/blog\/management\/agile\/scrum-management\/jeden-produkt-jeden-product-owner\/\" class=\"more-link\">Continue reading<span class=\"screen-reader-text\"> &#8220;Jeden produkt, jeden Product Owner&#8221;<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[12],"tags":[272,167,57,96,7],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/968"}],"collection":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/comments?post=968"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/968\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=968"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=968"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=968"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}