{"id":242,"date":"2010-01-21T17:28:31","date_gmt":"2010-01-21T16:28:31","guid":{"rendered":"http:\/\/agile.sk\/?p=242"},"modified":"2010-01-21T17:28:31","modified_gmt":"2010-01-21T16:28:31","slug":"rola-scrummaster","status":"publish","type":"post","link":"https:\/\/agile.sk\/?p=242","title":{"rendered":"Rola: ScrumMaster"},"content":{"rendered":"<p>ScrumMaster je jeden z najd\u00f4le\u017eitej\u0161\u00e1ch prvkov Scrumu, ak chceme by\u0165 \u00faspe\u0161n\u00ed.<\/p>\n<p>Prv\u00fd k\u013e\u00fa\u010dov\u00fd bod a z\u00e1rove\u0148 naj\u010dastej\u0161ie nepochopenie tejto role &#8211; <strong>ScrumMaster nie je mana\u017e\u00e9r T\u00edmu, neriadi ho<\/strong>. Vypl\u00fdva to u\u017e z n\u00e1zvu tejto role &#8211; &#8220;ten kto ovl\u00e1da Scrum&#8221;. ScrumMaster teda T\u00edm podporuje, sl\u00fa\u017ei mu, ochra\u0148uje ho pred vonkaj\u0161\u00edmi vplyvmi a usmer\u0148uje ho, aby bol Scrum pochopen\u00fd a spr\u00e1vne aplikovan\u00fd. Prechod na agiln\u00e9 princ\u00edpy nie je jednoduch\u00fd, od sam\u00e9ho za\u010diatku zvidite\u013e\u0148uje skryt\u00e9 prek\u00e1\u017eky v organiz\u00e1cii &#8211; pr\u00e1ve po\u010das t\u00fdchto n\u00e1ro\u010dn\u00fdch zmien je potrebn\u00e1 \u00faloha ScrumMastera.<\/p>\n<p>Rola ScrumMastera teda zah\u0155\u0148a n\u00e1sledovn\u00e9 zodpovednosti:<\/p>\n<ul>\n<li><strong>ochra\u0148uje <\/strong>T\u00edm pred vonkaj\u0161\u00edmi vplyvmi, ktor\u00e9 by mohli jeho pr\u00e1cu nar\u00fa\u0161a\u0165<\/li>\n<li>odstra\u0148uje ka\u017edodenn\u00e9 prek\u00e1\u017eky, ktor\u00e9 by mohli zn\u00ed\u017ei\u0165 efektivitu pr\u00e1ce T\u00edmu<\/li>\n<li><strong>kou\u010duje <\/strong>T\u00edm, Product Ownera a celkovo organiz\u00e1ciu, aby dodr\u017eiavali pravidl\u00e1 Scrumu a integrovali agiln\u00e9 praktiky, sleduj\u00fac pritom cie\u013e &#8211; \u00faspe\u0161n\u00e9 a efekt\u00edvne nasadenie Scrumu<\/li>\n<li>kou\u010duje T\u00edm, aby spr\u00e1vne nasadil a pou\u017e\u00edval vhodn\u00e9 XP praktiky<\/li>\n<li>kou\u010duje Product Ownera, aby pracoval efekt\u00edvne s Product Backlogom, s po\u017eiadavkami na produkt, aby maximalizoval n\u00e1vratnos\u0165 invest\u00edci\u00ed<\/li>\n<li><strong>podporuje <\/strong>dosiahnutie zhody medzi o\u010dak\u00e1vaniami Product Ownera a pr\u00eds\u013eubom T\u00edmu &#8211; medi\u00e1tor v ich komunik\u00e1cii<\/li>\n<li>organizuje a pom\u00e1ha vies\u0165 porady predp\u00edsan\u00e9 Scrumom<\/li>\n<\/ul>\n<p>Zo za\u010diatku sa na t\u00fato rolu odpor\u00fa\u010da priradi\u0165 osobu na pln\u00fd \u00fav\u00e4zok. \u010clenovia T\u00edmu sa e\u0161te len zoznamuj\u00fa so Scrumom v ich ka\u017edodennom \u017eivote, mana\u017ement h\u013ead\u00e1 mo\u017enosti, ako zasahova\u0165 do iter\u00e1ci\u00ed,\u00a0 v\u00fdvojov\u00e9 prostredie a testovacie n\u00e1stroje nie s\u00fa pripraven\u00e9 na agiln\u00e9 procesy&#8230; toto v\u0161etko predpoved\u00e1, \u017ee ScrumMaster bude ma\u0165 pln\u00e9 ruky pr\u00e1ce.\u00a0 Nesk\u00f4r, ako sa Scrum a agiln\u00e9 my\u0161lienky st\u00e1vaj\u00fa samozrejmos\u0165ou, n\u00e1stroje s\u00fa automatizovan\u00e9 a XP praktiky sa plnohodnotne vyu\u017e\u00edvaj\u00fa, v\u00fdznam dedikovan\u00e9ho ScrumMastera kles\u00e1 a jeho kapacita sa m\u00f4\u017ee postupne pres\u00fava\u0165 na \u010dlenov T\u00edmu, napr\u00edklad rotovan\u00edm tejto role.<\/p>\n<p><strong>Koho do role ScrumMastera dosadi\u0165 ?<\/strong> V prvom rade tak\u00fa osobu, ktor\u00e1 u\u017e m\u00e1 sk\u00fasenosti s agiln\u00fdmi princ\u00edpmi a v\u00fdvojom, je do Scrumu za\u0161kolen\u00e1 a ver\u00ed v agiln\u00e9 princ\u00edpy. Tieto predpoklady netreba podceni\u0165, medzi agiln\u00fdmi projektami a chaosom je relat\u00edvne tenk\u00e1 l\u00ednia, tak\u017ee nesk\u00fasen\u00fd ScrumMaster m\u00f4\u017ee narobi\u0165 viac \u0161kody ako \u00fa\u017eitku. Je to teda ten, kto vie o Scrume najviac a je ochotn\u00fd a schopn\u00fd tieto vedomosti \u0161\u00edri\u0165 \u010falej a presadzova\u0165 ich nielen v T\u00edme ale aj v celej organiz\u00e1cii. Je tie\u017e u\u017eito\u010dn\u00e9, ak m\u00e1 ScrumMaster z\u00e1rove\u0148 praktick\u00e9 znalosti z projektov\u00e9ho mana\u017ementu, dizajnu, k\u00f3dovania a testovania, tak\u017ee sa \u013eahko stoto\u017en\u00ed so vznikaj\u00facimi probl\u00e9mami a vie ich promptne rie\u0161i\u0165. Ak v\u0161ak bol ScrumMaster pred prechodom na Scrum ved\u00facim t\u00edmu \/ projektov\u00fdm mana\u017e\u00e9rom, jeho zmena myslenia m\u00f4\u017ee by\u0165 ve\u013emi \u0165a\u017ek\u00e1 &#8211; mus\u00ed v sebe potla\u010di\u0165 tendenciu prikazova\u0165 \u010dlenom \u010do a ako robi\u0165, pl\u00e1nova\u0165, rozhodova\u0165 za nich o rie\u0161eniach alebo pride\u013eova\u0165 konkr\u00e9tne \u00falohy. Samoriadenie T\u00edmu ako n\u00e1stroj na zv\u00fd\u0161enie efektivity potom nezafunguje.<\/p>\n<p>Ako u\u017e bolo spomenut\u00e9, \u010dasom sa m\u00f4\u017ee rola ScrumMastera obsadi\u0165 \u010dlenom T\u00edmu. Neplat\u00ed to v\u0161ak v pr\u00edpade kombin\u00e1cie ScrumMaster-Product Owner. Tieto roly s\u00fa \u010dasto vo vz\u00e1jomnom rozpore a \u010dlovek na dvoch tak\u00fdchto stoli\u010dk\u00e1ch m\u00e1 \u0165a\u017ek\u00e9 sa rozhodn\u00fa\u0165, koho rolu m\u00e1 v ktorej situ\u00e1cii hra\u0165. Napr\u00edklad Product Owner je pod tlakom prior\u00edt v po\u017eiadavk\u00e1ch a ak v sebe potla\u010d\u00ed zodpovednos\u0165 ScrumMastera, tak m\u00f4\u017ee urobi\u0165 tak\u00fa zasadn\u00fa chybu ako meni\u0165 T\u00edmu \u00falohy po\u010das Sprintu. Bez druhej osoby mu ch\u00fdba jasn\u00fd protiklad, ktor\u00fd by ho upozor\u0148oval na potencion\u00e1lne chyby a rizik\u00e1 a nasadenie Scrumu by sa minulo \u00fa\u010dinkom.<\/p>\n\n<!-- Facebook Like Button v1.9.6 BEGIN [http:\/\/blog.bottomlessinc.com] -->\n<iframe src=\"http:\/\/www.facebook.com\/plugins\/like.php?href=https%3A%2F%2Fagile.sk%2F%3Fp%3D242&amp;layout=standard&amp;show_faces=false&amp;width=450&amp;action=like&amp;colorscheme=light\" scrolling=\"no\" frameborder=\"0\" allowTransparency=\"true\" style=\"border:none; overflow:hidden; width:450px; height: 30px; align: left; margin: 20px 0px 2px 0px\"><\/iframe>\n<!-- Facebook Like Button END -->\n","protected":false},"excerpt":{"rendered":"<p>ScrumMaster je jeden z najd\u00f4le\u017eitej\u0161\u00e1ch prvkov Scrumu, ak chceme by\u0165 \u00faspe\u0161n\u00ed. Prv\u00fd k\u013e\u00fa\u010dov\u00fd bod a z\u00e1rove\u0148 naj\u010dastej\u0161ie nepochopenie tejto role &#8211; ScrumMaster nie je mana\u017e\u00e9r T\u00edmu, neriadi ho. Vypl\u00fdva to u\u017e z n\u00e1zvu tejto role &#8211; &#8220;ten kto ovl\u00e1da Scrum&#8221;. ScrumMaster teda T\u00edm podporuje, sl\u00fa\u017ei mu, ochra\u0148uje ho pred vonkaj\u0161\u00edmi vplyvmi a usmer\u0148uje ho, aby [&hellip;]<\/p>\n","protected":false},"author":4,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[49],"tags":[6],"_links":{"self":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/242"}],"collection":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/users\/4"}],"replies":[{"embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcomments&post=242"}],"version-history":[{"count":5,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/242\/revisions"}],"predecessor-version":[{"id":247,"href":"https:\/\/agile.sk\/index.php?rest_route=\/wp\/v2\/posts\/242\/revisions\/247"}],"wp:attachment":[{"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fmedia&parent=242"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Fcategories&post=242"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/agile.sk\/index.php?rest_route=%2Fwp%2Fv2%2Ftags&post=242"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}