{"id":282,"date":"2009-08-30T16:42:03","date_gmt":"2009-08-30T15:42:03","guid":{"rendered":"http:\/\/soch.cz\/blog\/?p=282"},"modified":"2009-08-30T16:42:03","modified_gmt":"2009-08-30T15:42:03","slug":"waterfall-rup-nebo-agile","status":"publish","type":"post","link":"https:\/\/soch.cz\/blog\/management\/waterfall-rup-nebo-agile\/","title":{"rendered":"Waterfall, RUP nebo Agile?"},"content":{"rendered":"

Za\u010d\u00edn\u00e1te projekt a nev\u00edte kterou metodu zvolit? Zkus\u00edm se pod\u00edvat na jednotliv\u00e9 metody detailn\u011bji. Tradi\u010dn\u00ed Waterfall vypad\u00e1 ide\u00e1ln\u011b. Nejprve si navrhnete, co budete d\u011blat, pak \u0159eknete jak, pak to ud\u011bl\u00e1te, otestujete. Ide\u00e1ln\u00ed. Snadn\u00e9. Jen bohu\u017eel realita je v\u017edy jin\u00e1. V\u00fdsledek uk\u00e1\u017eete z\u00e1kazn\u00edkovi, a on se zatv\u00e1\u0159\u00ed zklaman\u011b, \u0159ekne, \u017ee tohle si nep\u0159edstavoval, \u010di \u017ee tohle nikdy necht\u011bl a a\u0165 to p\u0159ed\u011bl\u00e1te. V\u00e1s pak na jedn\u00e9 stran\u011b \u010dek\u00e1 dlouh\u00fd refactoring a p\u0159ed\u011bl\u00e1v\u00e1n\u00ed, a k tomu z\u00e1kazn\u00edk, kter\u00fd je nerv\u00f3zn\u00ed \u017ee aplikaci st\u00e1le nem\u00e1. Na druh\u00e9 stran\u011b jsou dlouh\u00e9 diskuze se z\u00e1kazn\u00edkem, \u017ee v jeho p\u016fvodn\u00edch po\u017eadavc\u00edch to bylo jinak \u010di nebylo v\u016fbec. A \u017ee tento refactoring mus\u00ed zaplatit extra. Nic neobvykl\u00e9ho, a nic co by se jen bl\u00ed\u017eilo spokojenosti na obou stran\u00e1ch.<\/p>\n

Proto vznikl Rational Unified Process (RUP), kter\u00fd si uv\u011bdomuje, \u017ee nen\u00ed mo\u017en\u00e9 celou aplikaci napsat v jednom sekven\u010dn\u00edm procesu \u2013 ostatn\u011b stejn\u011b se tak nikdy v re\u00e1lu ned\u011blo \u2013 a \u017ee jednotliv\u00e9 f\u00e1ze jsou v\u00edce \u010di m\u00e9n\u011b p\u0159\u00edtomny periodicky v pr\u016fb\u011bhu cel\u00e9ho procesu. RUP se d\u00e1 v podstat\u011b pova\u017eovat za pokus p\u0159ibl\u00ed\u017eit Waterfall re\u00e1ln\u00e9mu sv\u011btu. Pokus to byl dobr\u00fd, nicm\u00e9n\u011b spokojenosti z\u00e1kazn\u00edka moc nep\u0159isp\u011bl. N\u00e1vrh vede \u010dasto k velice komplexn\u00ed a n\u00e1ro\u010dn\u00e9 architektu\u0159e, kter\u00e1 zt\u011b\u017euje p\u0159\u00edpadn\u00fd refactoring. Nav\u00edc jednotliv\u00e9 f\u00e1ze jsou extr\u00e9mn\u011b detailn\u011b specifikovan\u00e9, tedy libovoln\u00e9 zm\u011bna vy\u017eaduje i dlouh\u00fd \u010das na p\u0159eps\u00e1n\u00ed v\u0161ech model\u016f a diagram\u016f.<\/p>\n

Asi nikoho nep\u0159ekvap\u00ed, \u017ee budu na tomto m\u00edst\u011b doporu\u010dovat agiln\u00ed metody. Na rozd\u00edl od p\u0159edchoz\u00ed metody, kter\u00e1 vsadila na dobr\u00fd n\u00e1vrh, jsou agiln\u00ed metody orientov\u00e1ny na zm\u011bnu. N\u00e1vrh by m\u011bl b\u00fdt co nejjednodu\u0161\u0161\u00ed, iterace dostate\u010dn\u011b kr\u00e1tk\u00e9, aby se omezilo riziko refactoringu. Nav\u00edc z\u00e1kazn\u00edk, kter\u00fd vid\u00ed ka\u017ed\u00e9 dva t\u00fddny jednu feature a m\u016f\u017ee se k n\u00ed p\u0159\u00edmo vyj\u00e1d\u0159it, je potom v daleko hor\u0161\u00ed situaci kdy\u017e na konci projektu chce n\u011bco jinak. Agiln\u00ed metody omezuj\u00ed n\u00e1vrh a dokumentaci na nutn\u00e9 minimum, nicm\u00e9n\u011b na druh\u00e9 stran\u011b zapojuj\u00ed testov\u00e1n\u00ed hned na za\u010d\u00e1tek n\u00e1vrhu (TDD), zav\u00e1d\u00ed automatick\u00e9 testov\u00e1n\u00ed a kontinu\u00e1ln\u00ed integraci. Agiln\u00ed metody jsou nav\u00edc zalo\u017een\u00e9 na spolupr\u00e1ci, a to jak v r\u00e1mci t\u00fdmu tak i extern\u011b se z\u00e1kazn\u00edkem, co\u017e je \u010din\u00ed o dost efektivn\u011bj\u0161\u00ed.<\/p>\n

Na z\u00e1v\u011br p\u0159id\u00e1v\u00e1m kr\u00e1tkou tabulku s porovn\u00e1n\u00edm jednotliv\u00fdch metod:<\/p>\n\n\n\n\n\n\n\n\n\n\n\n
\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Waterfall <\/span><\/span><\/strong><\/p>\n<\/td>\n

\n

RUP <\/span><\/span><\/strong><\/p>\n<\/td>\n

\n

Agile <\/span><\/span><\/strong><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Sekven\u010dn\u00ed <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Inkrement\u00e1ln\u00ed <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Iterativn\u00ed <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Jasn\u011b definovan\u00e9 requirementy. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Po\u010d\u00edt\u00e1 s m\u00edrnou zm\u011bnou requirement\u016f. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Requirementy se konzultuj\u00ed se z\u00e1kazn\u00edkem v pr\u016fb\u011bhu. <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Specifikace se nem\u011bn\u00ed <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Specifikace se nem\u011bn\u00ed v r\u00e1mci inkrementu. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Specifikace se nem\u011bn\u00ed v r\u00e1mci sprintu. <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Jednotliv\u00e9 f\u00e1ze (anal\u00fdza, design, testov\u00e1n\u00ed, \u2026) jsou odd\u011blen\u00e9 a sekven\u010dn\u00ed. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Jednotliv\u00e9 f\u00e1ze (anal\u00fdza, design, testov\u00e1n\u00ed, \u2026) jsou odd\u011blen\u00e9, ale b\u011b\u017e\u00ed paraleln\u011b. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Nerozd\u011bluje projekt na jednotliv\u00e9 f\u00e1ze. Ka\u017ed\u00e1 \u00faloha obsahuje v\u0161echny f\u00e1ze (anal\u00fdza, design, testov\u00e1n\u00ed, \u2026). <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Striktn\u011b definovan\u00fd proces, kter\u00fd nepo\u010d\u00edt\u00e1 s \u017e\u00e1dnou zm\u011bnou. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Slo\u017eit\u00fd, use-case driven, architecture-centric proces.\u00a0 <\/span><\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Metodologie zalo\u017een\u00e1 na rychl\u00e9 reakci na zm\u011bnu a spolupr\u00e1ci (intern\u00ed i extern\u00ed). <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

\u00a0<\/span><\/span><\/p>\n<\/td>\n

\n

Jednotliv\u00e9 f\u00e1ze jsou zdokumentovan\u00e9 <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Snaha m\u00edt v\u0161e do detailu zdokumentovan\u00e9.\u00a0 <\/span><\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Dokumentace jen v nejnutn\u011bj\u0161\u00ed m\u00ed\u0159e, jednoduch\u00fd designe, hlavn\u00ed metrikou je spokojenost z\u00e1kazn\u00edka. <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

R<\/span><\/span><\/span><\/strong><\/p>\n

I<\/span><\/span><\/span><\/strong><\/p>\n

Z<\/span><\/span><\/span><\/strong><\/p>\n

I<\/span><\/span><\/span><\/strong><\/p>\n

K<\/span><\/span><\/span><\/strong><\/p>\n

A<\/span><\/strong><\/span><\/span><\/p>\n<\/td>\n

\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Nespokojenost z\u00e1kazn\u00edka (n\u011bco jin\u00e9ho ne\u017e cht\u011bl)<\/span><\/span><\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Dlouh\u00fd refactoring<\/span><\/span><\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Nep\u0159esn\u00e9 odhady <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>P\u0159\u00edli\u0161 slo\u017eit\u00e1 a n\u00e1ro\u010dn\u00e1 architektura<\/span><\/span><\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Dlouh\u00fd refactoring<\/span><\/span><\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Nep\u0159esn\u00e9 odhady <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>N\u00e1ro\u010dn\u00fd na komunikaci a kooperaci<\/span><\/span><\/span><\/p>\n

\u00b7<\/span>\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0\u00a0 <\/span><\/span><\/span>Mus\u00ed odpov\u00eddat firemn\u00ed kultu\u0159e <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n

\n

P<\/span><\/span><\/span><\/strong><\/p>\n

O<\/span><\/span><\/span><\/strong><\/p>\n

U<\/span><\/span><\/span><\/strong><\/p>\n

\u017d<\/span><\/span><\/span><\/strong><\/p>\n

I<\/span><\/span><\/span><\/strong><\/p>\n

T<\/span><\/span><\/span><\/strong><\/p>\n

\u00cd<\/span><\/strong><\/span><\/span><\/p>\n<\/td>\n

\n

Jasn\u011b definovan\u00fd a dob\u0159e specifikovan\u00fd projekt kdy zm\u011bna je vysoce nepravd\u011bpodobn\u00e1. Z\u00e1kazn\u00edk mus\u00ed perfektn\u011b v\u011bd\u011bt, co chce dop\u0159edu. N\u00e1ro\u010dn\u00fd na zku\u0161enosti jednotliv\u00fdch engineer\u016f. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Komplexn\u00ed syst\u00e9my vy\u017eaduj\u00edc\u00ed detailn\u00ed dokumentaci a n\u00e1ro\u010dnou architekturu. Zm\u011bna po\u017eadavk\u016f je nepravd\u011bpodobn\u00e1. N\u00e1ro\u010dn\u00fd na zku\u0161enosti jednotliv\u00fdch engineer\u016f. <\/span><\/span><\/span><\/p>\n<\/td>\n

\n

Projekt pro b\u011b\u017en\u00e9 z\u00e1kazn\u00edky co \u010dasto \u00fapln\u011b p\u0159esn\u011b nev\u011bd\u00ed, co cht\u011bj\u00ed. Po\u017eadavky se mohou m\u011bnit v r\u00e1mci projektu. C\u00edlem je spokojen\u00fd z\u00e1kazn\u00edk. St\u0159edn\u00ed n\u00e1roky na zku\u0161enosti t\u00fdmu. <\/span><\/span><\/span><\/p>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n","protected":false},"excerpt":{"rendered":"

Za\u010d\u00edn\u00e1te projekt a nev\u00edte kterou metodu zvolit? Zkus\u00edm se pod\u00edvat na jednotliv\u00e9 metody detailn\u011bji. Tradi\u010dn\u00ed Waterfall vypad\u00e1 ide\u00e1ln\u011b. Nejprve si navrhnete, co budete d\u011blat, pak \u0159eknete jak, pak to ud\u011bl\u00e1te, otestujete. Ide\u00e1ln\u00ed. Snadn\u00e9. Jen bohu\u017eel realita je v\u017edy jin\u00e1. V\u00fdsledek uk\u00e1\u017eete z\u00e1kazn\u00edkovi, a on se zatv\u00e1\u0159\u00ed zklaman\u011b, \u0159ekne, \u017ee tohle si nep\u0159edstavoval, \u010di \u017ee tohle … Continue reading “Waterfall, RUP nebo Agile?”<\/span><\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":[],"categories":[11],"tags":[272,273,45,46],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/282"}],"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=282"}],"version-history":[{"count":0,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/posts\/282\/revisions"}],"wp:attachment":[{"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/media?parent=282"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/categories?post=282"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/soch.cz\/blog\/wp-json\/wp\/v2\/tags?post=282"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}