Petr Kunetka <\/p>\n\n\n\n
CEO Quartex Praha <\/p>\n\n\n\n
27.8.2025 <\/p>\n\n\n\n
Projekt se nyn\u00ed rozjel jako vlak v\u202fnastaven\u00fdch kolej\u00edch. Realiza\u010dn\u00ed t\u00fdm si sedl a za\u010dal nastavovat (a do zna\u010dn\u00e9 m\u00edry i programovat, co\u017e z\u00e1kazn\u00edk ne zcela pochopil) to, co bylo naps\u00e1no v\u202fanal\u00fdze. Tak, jak je to spr\u00e1vn\u00e9, si sestavil seznam GAP\u016f a realizoval je dle sv\u00e9ho nejlep\u0161\u00edho v\u011bdom\u00ed a sv\u011bdom\u00ed, netu\u0161e, \u017ee anal\u00fdza m\u00e1 m\u00e1lo spole\u010dn\u00e9ho s\u202ft\u00edm, co z\u00e1kazn\u00edk chce nebo pot\u0159ebuje. Steering committee se pravideln\u00e9 sch\u00e1zel a z\u00e1kazn\u00edk vid\u011bl p\u011bkn\u00e9 grafy, jak se postupn\u00e9 GAPy \u0159e\u0161\u00ed a projektov\u00fd vlak jede dle cestovn\u00edho po\u0159\u00e1dku ke sv\u011btl\u00fdm z\u00edt\u0159k\u016fm. Nikde nebyly probl\u00e9my ani p\u0159ek\u00e1\u017eky, v\u0161e bylo sv\u011btl\u00e9, jak u\u017e to v\u202ft\u00e9to f\u00e1zi projektu b\u00fdv\u00e1. <\/p>\n\n\n\n
Po n\u011bjak\u00e9 dob\u011b byl prezentov\u00e1n prototyp, pot\u00e9 pokro\u010dil\u00fd prototyp, kde konzultant ke spokojenosti v\u0161ech div\u00e1k\u016f (co\u017e bylo veden\u00ed projektu a management, kter\u00fd samoz\u0159ejm\u011b tyto operace v\u202fdetailu neznal a neprov\u00e1d\u011bl) naklikal p\u0159ipraven\u00fd doklad a zpracoval jej zp\u016fsobem, kter\u00fd dle anal\u00fdzy pokl\u00e1dal za spr\u00e1vn\u00fd. Kol\u00e1\u010dov\u00e9 grafy ukazovaly st\u00e1le v\u011bt\u0161\u00ed d\u00edlky, sloupcov\u00e9 grafy st\u00e1le vy\u0161\u0161\u00ed sloupce a a Gantt\u016fv graf dal\u0161\u00ed a dal\u0161\u00ed Gapy. Samoz\u0159ejm\u011b, ob\u010das do\u0161lo k\u202fza\u0161kobrtnut\u00ed a n\u011bjak\u00fd \u00fakol se trochu zpozdil nebo z\u202fn\u011bjak\u00e9ho testu vylezla nutnost opravy, ale to v\u0161e bylo pod kontrolou. <\/p>\n\n\n\n
Snad jedin\u00fd probl\u00e9m na proz\u00e1\u0159en\u00e9 obloze byla \u010d\u00e1st projektu (komunikace s\u202fjedn\u00edm z\u202fpartner\u016f) sv\u011b\u0159en\u00e1 intern\u00edmu IT. IT velmi spr\u00e1vn\u011b usoudilo, \u017ee je projektem ohro\u017eeno, co\u017e management potvrdil t\u00edm, \u017ee je k\u202fprojektu p\u0159izval pouze s\u202f\u00fakolem zaji\u0161t\u011bn\u00ed infrastruktury. To bylo pon\u011bkud ne\u0161\u0165astn\u00e9, nebo\u0165 v\u202fre\u00e1lu IT m\u011blo velmi detailn\u00ed znalost st\u00e1vaj\u00edc\u00edho syst\u00e9mu a snad mohli zabr\u00e1nit dal\u0161\u00edmu v\u00fdvoji. I kdy\u017e sp\u00ed\u0161e ne, nebo\u0165 aktivita IT se soust\u0159e\u010fovala na chozen\u00ed po firm\u011b a vykl\u00e1d\u00e1n\u00ed, jak je st\u00e1vaj\u00edc\u00ed syst\u00e9m vlastn\u011b dobr\u00fd (co\u017e byl nesmysl) a jak dodavatel prakticky nev\u00ed, jak\u00e9 prob\u00edhaj\u00ed na pozad\u00ed procesy (co\u017e byla pravda). Nakonec, kdy\u017e p\u0159ijali fakt, \u017ee projekt se nezastav\u00ed, v\u202fobav\u00e1ch o svou budoucnost se p\u0159ihl\u00e1sili k\u202ftomu, \u017ee pomohou s\u202ftvorbou integrac\u00ed s\u202ffiremn\u00edmi partnery. Jen\u017ee tento \u00fakol byl o\u010dividn\u011b nad jejich s\u00edly a od sam\u00e9ho za\u010d\u00e1tku poskytovali dodavateli oblast, na kterou uk\u00e1zat, kdy\u017e nastane probl\u00e9m. Nicm\u00e9n\u011b to d\u00e1valo dodavateli na steering comitte n\u00e1boje kdykoliv se n\u011bkomu na stran\u011b dodavatele n\u011bco nezd\u00e1lo. <\/p>\n\n\n\n
Prvn\u00ed mr\u00e1\u010dky na obloze se za\u010daly ukazovat s\u202fnasazen\u00edm prvn\u00edch verz\u00ed k\u202ftestov\u00e1n\u00ed. Samoz\u0159ejm\u011b, sou\u010d\u00e1st\u00ed nastaven\u00ed projektu bylo, \u017ee testov\u00e1n\u00ed si prov\u00e1d\u00ed z\u00e1kazn\u00edk. Kdybych m\u011bl vyp\u00edchnout jeden bod<\/strong>, kter\u00fd obvykle zp\u016fsob\u00ed kolaps projektu, je to tento. V\u202frealit\u011b je ERP testov\u00e1n\u00ed n\u00e1ro\u010dn\u00e1, komplexn\u00ed a dosti drah\u00e1 pr\u00e1ce. Je nutno skute\u010dn\u011b detailn\u011b proj\u00edt anal\u00fdzu, ch\u00e1pat firemn\u00ed procesy, vytvo\u0159it testovac\u00ed cases\u2026 Teoreticky. V\u202fpraxi snad nepamatuji jedin\u00fd projekt, kde bych vid\u011bl, \u017ee by se tak stalo. <\/p>\n\n\n\n V\u202fr\u00e1mci sout\u011b\u017een\u00ed na cen\u011b je u n\u00e1s naprosto b\u011b\u017en\u00e1 praxe, kdy se testovac\u00ed pr\u00e1ce a odpov\u011bdnost za testovac\u00ed pr\u00e1ce pln\u011b<\/strong> p\u0159enesou na z\u00e1kazn\u00edka. Logika je jednoduch\u00e1 \u2013 nab\u00eddka t\u00edm m\u016f\u017ee b\u00fdt bratru o 20 procent ni\u017e\u0161\u00ed, co\u017e je pro management v\u011bt\u0161inou rozhoduj\u00edc\u00ed. Z\u202fpohledu z\u00e1kazn\u00edka to vypad\u00e1 naprosto logicky \u2013 stejn\u011b to mus\u00edme vyzkou\u0161et, u\u0161et\u0159\u00edme hromadu pen\u011bz \u2013 otestuj\u00ed to na\u0161i lid\u00e9 ve voln\u00e9m \u010dase, proto\u017ee jej samoz\u0159ejm\u011b maj\u00ed hromady, v\u202fkancel\u00e1\u0159\u00edch sed\u00ed cel\u00e9 hodiny bez pr\u00e1ce\u2026 A dodavateli to d\u00e1v\u00e1 naprosto nepr\u016fst\u0159eln\u00fd argument kdykoliv n\u011bco nefunguje: \u201eJe to va\u0161e chyba, proto\u017ee jste to neotestovali\u201c. Samoz\u0159ejm\u011b, jedn\u00e1 se o alibismus, ale to alibi s\u202fnad\u0161en\u00edm dodavateli poskytuje z\u00e1kazn\u00edk. <\/p>\n\n\n\n Situace se st\u00e1v\u00e1 lep\u0161\u00ed, kdy\u017e existuje dedikovan\u00fd implementa\u010dn\u00ed t\u00fdm uvnit\u0159 firmy, ale i tak osobn\u011b preferuji u projekt\u016f t\u00e9to velikosti, bez velk\u00e9ho dedikovan\u00e9ho t\u00fdmu, jako formu testu zduplikov\u00e1n\u00ed provozu za dan\u00e9 obdob\u00ed (optim\u00e1ln\u011b m\u011bs\u00edc, ale to si m\u016f\u017ee m\u00e1lokdo dovolit). <\/p>\n\n\n\n V\u202fna\u0161em p\u0159\u00edpad\u011b si t\u011bmito \u00favahami nikdo hlavu nel\u00e1mal. Dodavatel nasadil syst\u00e9m na testovac\u00ed infrastrukturu, provedl n\u011bjak\u00e9 provizorn\u00ed nastaven\u00ed a import p\u00e1r vzork\u016f dat a vyzval z\u00e1kazn\u00edka k\u202ftestu. A jak ERP testov\u00e1n\u00ed dopadlo? <\/p>\n\n\n\n Pokra\u010dov\u00e1n\u00ed:<\/em> 7. d\u00edl<\/a><\/p>\n\n\n\n V Quartexu<\/a> v\u00edme, \u017ee ERP testov\u00e1n\u00ed<\/strong> je jedn\u00edm z nejcitliv\u011bj\u0161\u00edch m\u00edst ka\u017ed\u00e9 implementace. Je to okam\u017eik, kdy se uk\u00e1\u017ee, jestli syst\u00e9m opravdu podporuje procesy, nebo jen pap\u00edrov\u00e9 p\u0159edpoklady. Proto testov\u00e1n\u00ed nikdy nenech\u00e1v\u00e1me jen na z\u00e1kazn\u00edkovi \u2013 spolupracujeme na sc\u00e9n\u00e1\u0159\u00edch, zaji\u0161\u0165ujeme dohled a pom\u00e1h\u00e1me firm\u00e1m zvl\u00e1dnout tuto kritickou f\u00e1zi.\u00a0<\/p>\n\n\n\n Firmy si n\u00e1s mohou najmout nejen jako dodavatele, ale i jako konzultanty na jejich stran\u011b. V takov\u00e9m p\u0159\u00edpad\u011b chr\u00e1n\u00edme z\u00e1jmy z\u00e1kazn\u00edka a \u0159\u00edd\u00edme testov\u00e1n\u00ed tak, aby nebylo alibistickou past\u00ed, ale cestou k re\u00e1ln\u00e9mu v\u00fdsledku. <\/p>\n\n\n\n \ud83d\udc49 P\u0159em\u00fd\u0161l\u00edte o nov\u00e9m ERP projektu?<\/a><\/p>\n\n\n\n \ud83d\udc49 M\u00e1te ji\u017e vybran\u00e9ho dodavatele a pot\u0159ebujete pomoci<\/a> na va\u0161\u00ed stran\u011b?\u00a0P\u0159\u00edpadn\u011b vyu\u017eijte n\u011bkterou z na\u0161ich aplikac\u00ed<\/a>. <\/p>\n\n\n\n <\/p>\n","protected":false},"excerpt":{"rendered":" Petr Kunetka CEO Quartex Praha 27.8.2025 Projekt jede podle pl\u00e1nu\u2026 na pap\u00ed\u0159e bez ERP testov\u00e1n\u00ed Projekt se nyn\u00ed rozjel jako vlak v\u202fnastaven\u00fdch kolej\u00edch. Realiza\u010dn\u00ed t\u00fdm si sedl a za\u010dal nastavovat (a do zna\u010dn\u00e9 m\u00edry i programovat, co\u017e z\u00e1kazn\u00edk ne zcela pochopil) to, co bylo naps\u00e1no v\u202fanal\u00fdze. Tak, jak je to spr\u00e1vn\u00e9, si sestavil seznam […]<\/p>\n","protected":false},"author":1,"featured_media":3093,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[33],"tags":[13,29,34],"class_list":["post-3092","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-30-let-s-erp","tag-business","tag-erp","tag-petr-kunetka"],"_links":{"self":[{"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/posts\/3092","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/comments?post=3092"}],"version-history":[{"count":3,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/posts\/3092\/revisions"}],"predecessor-version":[{"id":4278,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/posts\/3092\/revisions\/4278"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/media\/3093"}],"wp:attachment":[{"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/media?parent=3092"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/categories?post=3092"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/quartex.qmanapp.com\/quartex\/wp-json\/wp\/v2\/tags?post=3092"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}Quartex Praha: ERP testov\u00e1n\u00ed bez alibi<\/strong> <\/h2>\n\n\n\n