{"id":1210,"date":"2013-06-30T10:47:58","date_gmt":"2013-06-30T08:47:58","guid":{"rendered":"http:\/\/agile.sk\/?p=1210"},"modified":"2013-06-30T10:47:58","modified_gmt":"2013-06-30T08:47:58","slug":"daily-stand-up-dobre-iv-scrum-master-a","status":"publish","type":"post","link":"https:\/\/agile.sk\/?p=1210","title":{"rendered":"Daily stand-up dobre IV – scrum master. A?"},"content":{"rendered":"

\"Batman\"<\/a>Scrum master pe\u010die denn\u00fd chlieb t\u00edmu na dennom stretnut\u00ed.<\/p>\n

Pr\u00e1ve po\u010das tohto stretnutia sa prejavuj\u00fa schopnosti scrum mastra. Nie\u010do o scrum mastershipe sa s\u00edce dozviete po\u010das certifika\u010dn\u00fdch a in\u00fdch \u0161kolen\u00ed, no iba prax v\u00e1s nau\u010d\u00ed.<\/p>\n

T\u00edm dobr\u00e9ho scrum mastra nem\u00e1 probl\u00e9m so samoorganiz\u00e1ciou \u00faloh, s komunik\u00e1ciou a ani v\u00fdrazn\u00e9 probl\u00e9my so stavom \u00faloh. Navy\u0161e v takom t\u00edme je vysok\u00e1 miera sebadiscipl\u00edny a zodpovednosti.<\/p>\n

Disciplinovan\u00fd scrum master<\/strong>\u00a0pred samotn\u00fdm daily m\u00edtingom :<\/p>\n

    \n
  1. prever\u00ed\u00a0stav nahl\u00e1sen\u00fdch probl\u00e9mov<\/strong>\u00a0a zaktualizuje ich zoznam, resp. \u010das\u0165 tabule s probl\u00e9mami,<\/li>\n
  2. skontroluje\u00a0aktu\u00e1lnos\u0165 stavu<\/strong>\u00a0implementa\u010dn\u00fdch\u00a0\u00faloh<\/strong>\u00a0na Kanban tabuli,<\/li>\n
  3. skontroluje, \u010di \u00falohy maj\u00fa aktualizovan\u00fd\u00a0zost\u00e1vaj\u00facu \u010das<\/strong>\u00a0implement\u00e1cie,<\/li>\n
  4. skontroluje, \u010di\u00a0tok<\/strong>\u00a0(flow) \u00faloh je v poriadku,<\/li>\n
  5. prever\u00ed, \u010di \u010dlenovia t\u00edmu sa sna\u017eia\u00a0uzatv\u00e1ra\u0165 user stories<\/strong>\u00a0a nie otv\u00e1ra\u0165 \u010fal\u0161ie \u00falohy,<\/li>\n
  6. identifkuje\u00a0novopridan\u00e9 \u00falohy<\/strong>, ktor\u00e9 by moli zmeni\u0165 z\u00e1v\u00e4zok t\u00edmu dan\u00fd na za\u010diatku sprintu,<\/li>\n
  7. prever\u00ed si\u00a0vy\u0165a\u017eenie<\/strong>\u00a0\u010dlenov t\u00edmu tak, aby ich naviedol pri samoorganiz\u00e1cii po\u010das m\u00edtingu,<\/li>\n
  8. over\u00ed dohodnut\u00e9\u00a0WIP limity<\/strong>,<\/li>\n
  9. spolu s produktov\u00fdm vlastn\u00edkom preveria, \u010di nie s\u00fa nutn\u00e9\u00a0zmeny v backlogu sprintu<\/strong>,<\/li>\n
  10. spolu s in\u00fdmi scrum mastrami over\u00ed\u00a0stav z\u00e1visl\u00fdch pr\u00e1c<\/strong>, pr\u00edpadne potreby in\u00fdch t\u00edmov,<\/li>\n
  11. prever\u00ed, \u010di\u00a0mana\u017ement<\/strong>\u00a0nem\u00e1 nie\u010do d\u00f4le\u017eit\u00e9 z poh\u013eadu organiz\u00e1cie, \u010do je potrebn\u00e9 odkomunikova\u0165,<\/li>\n
  12. skontroluje priebeh\u00a0burn-down grafu<\/strong>\u00a0a identifikuje ot\u00e1zne hodnoty, ktor\u00e9 m\u00e1 s t\u00edmom prediskutova\u0165,<\/li>\n
  13. pr\u00edprav\u00ed\u00a0priestor<\/strong>\u00a0pre denn\u00e9 stretnutie,<\/li>\n
  14. priprav\u00ed\u00a0n\u00e1stroje<\/strong>\u00a0(napr. zobraz\u00ed elektronick\u00fa kanban tabu\u013eu),<\/li>\n
  15. a \u00a0v neposlednom rade vymysl\u00ed ako otvor\u00ed stretnutie tak, aby sa t\u00edm\u00a0pozit\u00edvne<\/strong>\u00a0naladil.<\/li>\n<\/ol>\n

    \u010co zmen\u00edte na svojom scrum mastershipe zajtra?<\/p>\n

    Odkazy:<\/p>\n