{"id":547,"date":"2013-11-19T07:36:00","date_gmt":"2013-11-19T06:36:00","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=547"},"modified":"2013-11-19T14:07:40","modified_gmt":"2013-11-19T13:07:40","slug":"role-testera-v-agilnim-tymu","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/agile\/role-testera-v-agilnim-tymu\/","title":{"rendered":"Role testera v agiln\u00edm t\u00fdmu"},"content":{"rendered":"

Jedn\u00edm z nej\u010dast\u011bj\u0161\u00edch probl\u00e9m\u016f, na kter\u00e9 t\u00fdmy p\u0159i agiln\u00ed transformaci naraz\u00ed, je rozd\u00edln\u00e9 vn\u00edm\u00e1n\u00ed rol\u00ed. V tradi\u010dn\u00edm sv\u011bt\u011b analytik d\u011bl\u00e1 dop\u0159edu anal\u00fdzu, v\u00fdvoj\u00e1\u0159 to podle n\u00ed nak\u00f3duje a tester n\u00e1sledn\u011b hled\u00e1 chyby. O tom, \u017ee anal\u00fdzy dop\u0159edu nepot\u0159ebujeme, nebo\u0165 m\u016f\u017eou vznikat klidn\u011b za b\u011bhu, se mluv\u00ed \u010dasto. O tom, \u017ee v\u00fdvoj\u00e1\u0159i mohou pomoci s testov\u00e1n\u00edm taky, a\u010d tato praktika ji\u017e obvykle nen\u00ed p\u0159ij\u00edm\u00e1na s takov\u00fdm nad\u0161en\u00edm a sl\u00fdch\u00e1me k n\u00ed spousty v\u00fdmluv typu v\u00fdvoj\u00e1\u0159i to nem\u016f\u017eou testovat proto\u017ee to neum\u00ed. No proto tak\u00e9 \u0159\u00edk\u00e1me, \u017ee tester\u016fm s testov\u00e1n\u00edm mohou pomoct. Ne \u017ee je maj\u00ed nahradit. Hned druh\u00e1 v\u00fdmluva v po\u0159ad\u00ed je, \u017ee berou v\u011bt\u0161\u00ed plat ne\u017e teste\u0159i a tak \u017ee by se to nevyplatilo. A tak n\u00e1m tato spolupr\u00e1ce obvykle zpo\u010d\u00e1tku trochu sk\u0159\u00edpe.<\/p>\n

D\u0159\u00edve nebo pozd\u011bji tak t\u00fdmy dojdou do stavu, kdy teste\u0159i na za\u010d\u00e1tku Sprintu nemaj\u00ed co d\u011blat a na konci nest\u00edhaj\u00ed. User Stories jsou hotov\u00e9 – tedy nak\u00f3dovan\u00e9 – a p\u0159esto je nesm\u00edme uznat jako v\u00fdsledek Sprintu. Chyb\u00ed p\u0159eci testy. T\u00fdmy v takov\u00e9 situaci p\u0159ich\u00e1z\u00ed s r\u016fzn\u00fdmi legra\u010dn\u00edmi n\u00e1pady jako nap\u0159. \u017ee by bylo pot\u0159eba testery od t\u00fdmu odd\u011blit a ud\u011blat jim separ\u00e1tn\u00ed posunut\u00fd Sprint. Tedy to, co v\u00fdvoj\u00e1\u0159i v jednom Sprintu nap\u00ed\u0161ou, teste\u0159i v druhem Sprintu otestuj\u00ed a je to. Ale to jsme po\u0159\u00e1d ment\u00e1ln\u011b ve waterfallu. Nikam bl\u00ed\u017ee k agiln\u00edmu Scrum t\u00fdmu jsme se v pochopen\u00ed ani implementaci neposunuli. Bez ohledu na to, jestli m\u00e1me tabuli a d\u011bl\u00e1me standupy.<\/p>\n

Jak by tedy takov\u00e1 spolupr\u00e1ce m\u011bla vypadat? Analytik, v\u00fdvoj\u00e1\u0159 a tester si vezmou User Story, a za\u010dnou si o n\u00ed pov\u00eddat. Analytik vym\u00fd\u0161l\u00ed, jak by se dan\u00e1 funkcionalita m\u011bla chovat, v\u00fdvoj\u00e1\u0159 to hned implementuje a tester upozor\u0148uje, na co v\u0161e si mus\u00ed d\u00e1t pozor. Co ud\u011bl\u00e1te kdy\u017e nep\u0159ijdou data? Co kdy\u017e nebudou validn\u00ed? Nezapome\u0148te, \u017ee v akcepta\u010dn\u00edch kriteri\u00edch je i to \u010di ono. A v neposledn\u00ed \u0159ad\u011b p\u0159ipom\u00edn\u00e1 business value (pro\u010d) definovanou v posledn\u00ed \u010d\u00e1sti formule User Story, abychom v pln\u00e9m zapojen\u00ed do implementace funkcionality nezapomn\u011bli, pro\u010d to vlastn\u011b cel\u00e9 d\u011bl\u00e1me a v n\u00e1vrhu to zohlednili. Tedy v podstat\u011b m\u00edsto aby chyby chytal na konci (kdy u\u017e je pozd\u011b), chceme aby chyb\u00e1m p\u0159edch\u00e1zel. Chceme, aby chyby v\u016fbec nevznikaly a v\u00fdvoj\u00e1\u0159 se tedy nemusel k ji\u017e ‘hotov\u00e9mu’ k\u00f3du vracet. Spolu s t\u00edm, \u017ee testera zapoj\u00edme do n\u00e1vrhu \u0159e\u0161en\u00ed funkcionalit, chceme, aby v\u00fdvoj\u00e1\u0159\u016fm pom\u00e1hal ji\u017e v pr\u016fb\u011bhu a testoval jednotliv\u00e9 \u010d\u00e1sti. V n\u011bkter\u00fdch p\u0159\u00edpadech pak klidn\u011b pracuj\u00ed v p\u00e1ru, jinde jde jen o \u00fazkou spolupr\u00e1ci. Hon\u00ed-li se v\u00e1m hlavou, \u017ee to nebude efektivn\u00ed, proto\u017ee tester to mus\u00ed testovat po\u0159\u00e1d dokola, nen\u00ed tomu tak. Opravy chyb se tak\u00e9 testuj\u00ed dokola a k tomu tam m\u00e1me je\u0161t\u011b multitasking v\u00fdvoj\u00e1\u0159\u016f a jejich \u010das str\u00e1ven\u00fd opravou ji\u017e hotov\u00fdch funk\u010dnost\u00ed. A \u0159\u00edk\u00e1te-li si, \u017ee to va\u0161i teste\u0159i nezvl\u00e1dnou, proto\u017ee co maj\u00ed testovat pochop\u00ed a\u017e z hotov\u00e9 funkcionality, zkuste se pod\u00edvat na to, jak dob\u0159e definovan\u00e9 User Story m\u00e1te. Jestli dob\u0159e, v\u010detn\u011b akcepta\u010dn\u00edch kriteri\u00ed, je to snadn\u00e9. Kdy\u017e ne, nen\u00ed to chyba tester\u016f, ale pravd\u011bpodobn\u011b tomu nerozum\u00ed ani ostatn\u00ed \u010dlenov\u00e9 t\u00fdmu.<\/p>\n

Tak\u017ee summary na z\u00e1v\u011br. \u00dakolem testera nen\u00ed chyby hledat, ale p\u0159edch\u00e1zet jim. Dobr\u00fd tester v agiln\u00edm t\u00fdmu dos\u00e1hne toho, \u017ee ve fin\u00e1ln\u00edm testov\u00e1n\u00ed User Story se \u017e\u00e1dn\u00e9 chyby nenajdou. A t\u00edm jen tak mimochodem u\u0161et\u0159\u00ed firm\u011b spousty \u010dasu pota\u017emo pen\u011bz. Dobr\u00fd tester rozum\u00ed z\u00e1kazn\u00edkovi a funkcionalit\u011b a pom\u00e1h\u00e1 s n\u00e1vrhem \u0159e\u0161en\u00ed. Um\u00ed se na User Story pod\u00edvat o\u010dima u\u017eivatele. Je to plnopr\u00e1vn\u00fd \u010dlen t\u00fdmu, kter\u00fd je pro jeho \u00fasp\u011bch kl\u00ed\u010dov\u00fd. A ot\u00e1zka na z\u00e1v\u011br… Opravdu si mysl\u00edte, \u017ee takov\u00fd \u010dlen t\u00fdmu m\u00e1 m\u00edt men\u0161\u00ed plat jen kv\u016fli n\u00e1zvu jeho pozice?<\/p>\n

Edited with BlogPad Pro<\/span>\"\"<\/a><\/div>\n","protected":false},"excerpt":{"rendered":"

Jedn\u00edm z nej\u010dast\u011bj\u0161\u00edch probl\u00e9m\u016f, na kter\u00e9 t\u00fdmy p\u0159i agiln\u00ed transformaci naraz\u00ed, je rozd\u00edln\u00e9 vn\u00edm\u00e1n\u00ed rol\u00ed. V tradi\u010dn\u00edm sv\u011bt\u011b analytik d\u011bl\u00e1 dop\u0159edu anal\u00fdzu, v\u00fdvoj\u00e1\u0159 to podle n\u00ed nak\u00f3duje a tester n\u00e1sledn\u011b hled\u00e1 chyby. O tom, \u017ee anal\u00fdzy dop\u0159edu nepot\u0159ebujeme, nebo\u0165 m\u016f\u017eou vznikat klidn\u011b za b\u011bhu, se mluv\u00ed \u010dasto. O tom, \u017ee v\u00fdvoj\u00e1\u0159i mohou pomoci s testov\u00e1n\u00edm … Continue reading “Role testera v agiln\u00edm t\u00fdmu”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[6],"tags":[272,77,106,105,48,10,82],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/547"}],"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=547"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/547\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=547"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=547"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=547"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}