{"id":2825,"date":"2024-07-01T12:03:26","date_gmt":"2024-07-01T10:03:26","guid":{"rendered":"https:\/\/teamdeck.io\/?p=2825"},"modified":"2025-01-23T22:46:57","modified_gmt":"2025-01-23T20:46:57","slug":"how-to-estimate-projects","status":"publish","type":"post","link":"https:\/\/teamdeck.io\/lt\/projektu-valdymas\/kaip-ivertinti-projektus\/","title":{"rendered":"Planavimo pokerio vertinimo technika ir istorijos ta\u0161kai"},"content":{"rendered":"<div class=\"vc_row wpb_row vc_row-fluid redl-row-section padding-default bgv-default bgh-default halign-default\"><div class=\"wpb_column vc_column_container text-left vc_col-sm-12 padding-default bgv-default bgh-default halign-default\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\">\n\t<div class=\"wpb_text_column wpb_content_element\" >\n\t\t<div class=\"wpb_wrapper\">\n\t\t\t<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-the-challenge-of-inaccurate-estimates\">Netiksli\u0173 vertinim\u0173 problema<\/h3>\n<p class=\"has-text-align-start\">Netikslios s\u0105matos yra viena populiariausi\u0173 projekt\u0173 valdymo problem\u0173. Prad\u0117dami nauj\u0105 IT projekt\u0105 norite \u017einoti du dalykus: kiek laiko jis u\u017etruks ir kiek kainuos. Nor\u0117dami atsakyti \u012f \u0161iuos klausimus, turite \u012fvertinti ketinamus vykdyti projektus. N\u0117ra stebuklingos taisykl\u0117s, kuri sakyt\u0173, kad projektas X trunka 12 savai\u010di\u0173 ir kainuoja $150 000. Arba \u012f Y pana\u0161i\u0105 svetain\u0119 reikia sukurti per 10 savai\u010di\u0173 ir ji kainuoja $100 000.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-key-questions-answered-in-this-article\">Pagrindiniai klausimai, \u012f kuriuos atsakyta \u0161iame straipsnyje<\/h3>\n<p class=\"has-text-align-start\">K\u0105 su\u017einosite i\u0161 \u0161io straipsnio:<\/p>\n<p>- Kaip projekt\u0173 vadovai pasiruo\u0161ia s\u0105naud\u0173 vertinimui projekt\u0173 valdyme?<\/p>\n<p>- Kokie vertinimo metodai yra naudingi projekto vertinimui?<\/p>\n<p>- Kaip planuojant reikia pasiruo\u0161ti \u012fvertinti i\u0161laidas pagal formules?<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1152\" height=\"764\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134711\/Planning1.jpg\" alt=\"\" class=\"wp-image-13648\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-the-importance-of-accurate-estimation\">Tikslaus \u012fvertinimo svarba<\/h3>\n<p class=\"has-text-align-start\">Negalite \u012fvertinti projekto termin\u0173 ar s\u0105naud\u0173 be i\u0161samaus \u012fvertinimo, net jei projekto apimtis yra labai pana\u0161i \u012f anks\u010diau atlikt\u0173 darb\u0173. Ta\u010diau viskas dar blogiau: \u012fvertinimas niekada nepateiks 100% tikslaus atsakymo ir \u012f \u0161iuos klausimus. Taigi, kod\u0117l mes vertiname? Nes tai vienintelis b\u016bdas daryti prielaidas apie projekto terminus ir biud\u017eet\u0105, darbo kr\u016bv\u012f ir jam \u012fgyvendinti reikalingus i\u0161teklius.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1151\" height=\"767\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134711\/Planning2.jpg\" alt=\"\" class=\"wp-image-13651\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-benefits-of-accurate-estimation\">Tikslaus \u012fvertinimo nauda<\/h3>\n<p class=\"has-text-align-start\">\u012evertin\u0119 projekto s\u0105mat\u0105, taip pat gal\u0117site suplanuoti reikiamos patirties ir \u012fg\u016bd\u017ei\u0173 turin\u010dius darbuotojus. Tai, k\u0105 galite padaryti, tai naudoti metodikas ir b\u016bdus, kurie leis jums \u012fvertinti maksimaliai tiksliai. \u0160tai kaip naudoti \"Agile\" metodologij\u0105 ir planavimo pokerio technik\u0105, kad sukurtum\u0117te prasmingus projekto \u012fver\u010dius.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1063\" height=\"750\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134711\/Planning3.jpg\" alt=\"\" class=\"wp-image-13652\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-the-origin-of-planning-poker\">Pokerio planavimo kilm\u0117<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-where-did-scrum-planning-poker-come-from\">I\u0161 kur atsirado Scrum (planavimo) pokeris?<\/h4>\n<p class=\"has-text-align-start\">2002 m. Jamesas Grenningas suk\u016br\u0117 planavimo pokerio sesij\u0105, \u017einom\u0105 d\u0117l savo strategijos, pavadintos \"Scrum poker\". \u0160e\u0161tojo de\u0161imtme\u010dio prad\u017eioje jo taikytas vertinimo metodas \"Wide band Delphi\" u\u017e\u0117m\u0117 per daug laiko ir tur\u0117jo kit\u0173 apribojim\u0173. Grenningo atveju pokerio planas i\u0161 prad\u017ei\u0173 buvo skirtas problemai spr\u0119sti, kai \u017eaid\u0117jai buvo pernelyg entuziastingi ir pernelyg susitelk\u0119, kad laim\u0117t\u0173. Mike'as Cohnas, \"Agile alliances\" ir \"Scrum alliances\" \u012fk\u016br\u0117jas, v\u0117liau panaudojo \u0161\u012f metod\u0105 straipsnyje \"Agile Estimation and Planning\".<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1153\" height=\"767\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134710\/Planning4.jpg\" alt=\"\" class=\"wp-image-13653\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-steps-to-accurate-project-estimation\">Tikslaus projekto \u012fvertinimo \u017eingsniai<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-create-a-list-of-required-features\">Sukurkite reikiam\u0173 funkcij\u0173 s\u0105ra\u0161\u0105<\/h4>\n<p class=\"has-text-align-start\">S\u0117kmingo projekto prad\u017eia labiausiai priklauso nuo to, kaip gerai suprantate, apie k\u0105 i\u0161 tikr\u0173j\u0173 kalbama. Tai apima:<\/p>\n<p>- Kliento l\u016bkes\u010di\u0173 supratimas<\/p>\n<p>- Projekto tiksl\u0173 ir pagrindinio tikslo supratimas<\/p>\n<p>- Reikaling\u0173 funkcij\u0173 s\u0105ra\u0161o sudarymas<\/p>\n<p class=\"has-text-align-start\">I\u0161nagrin\u0117j\u0119 kliento santrauk\u0105 ir tur\u0117dami kuo daugiau informacijos apie projekto reikalavimus, galite i\u0161vardyti visas funkcijas ir perduoti jas savo komandai.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-developing-a-product-backlog\">Produkt\u0173 s\u0105ra\u0161o k\u016brimas<\/h4>\n<p>Nor\u0117dami tai padaryti, sukurkite produkto atsilikimo s\u0105ra\u0161\u0105, kur\u012f sudaro visos privalomos atlikti funkcijos. Tada gal\u0117site nustatyti j\u0173 prioritetus, \u012fvertinti j\u0173 sud\u0117tingum\u0105 ir apskai\u010diuoti, kiek laiko prireiks joms atlikti. Tinkam\u0105 produkto atsilikimo s\u0105ra\u0161\u0105 tur\u0117t\u0173 sudaryti:<\/p>\n<p>- Vartotojo istorijos - apra\u0161ykite veiksmus, kuriuos vartotojai gali atlikti kiekviename produkto naudojimo etape.<\/p>\n<p>- Pri\u0117mimo kriterijai - i\u0161vardykite elementus, kuri\u0173 reikia, kad istorija b\u016bt\u0173 u\u017ebaigta.<\/p>\n<p>- Istorijos ta\u0161kai - \u012fvertinkite darbo kiek\u012f, rizik\u0105 ir sud\u0117tingum\u0105 santykine ta\u0161k\u0173 verte.<\/p>\n<p>- Vartotojo istorij\u0173 u\u017eduotys - i\u0161vardykite u\u017eduotis, kurias reikia atlikti, kad naudotojo istorija b\u016bt\u0173 \u012fgyvendinta.<\/p>\n<p>Labai svarbu, kad kuriant ir nustatant prioritetus b\u016bt\u0173 \u012ftraukta k\u016brimo komanda, kad b\u016bt\u0173 u\u017etikrintas tikslus ir realus \u012fvertinimas.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-prioritizing-features\">Funkcij\u0173 prioritet\u0173 nustatymas<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-sort-features-by-priority\">R\u016b\u0161iuoti funkcijas pagal prioritet\u0105<\/h4>\n<p class=\"has-text-align-start\">Pareng\u0119 funkcij\u0173 s\u0105ra\u0161\u0105, kiekvienai i\u0161 j\u0173 suteikite prioritet\u0105. Galite naudoti MoSCoW analiz\u0117s metod\u0105, kad jas sur\u016b\u0161iuotum\u0117te taip:<\/p>\n<p>- Turi b\u016bti<\/p>\n<p>- Tur\u0117t\u0173 b\u016bti<\/p>\n<p>- Gal\u0117jo<\/p>\n<p>- Netur\u0117s<\/p>\n<p class=\"has-text-align-start\">Kurdami projekt\u0105, daugiausia d\u0117mesio skirkite dalykams, kuriuos pirmiausia turite pristatyti. Kurdami MVP galite patikrinti savo id\u0117jos hipotezes prie\u0161 u\u017ebaigdami vis\u0105 projekt\u0105, parodyti j\u0105 suinteresuotosioms \u0161alims arba beta naudotojams ir surinkti gr\u012f\u017etam\u0105j\u012f ry\u0161\u012f, svarb\u0173 tolesniam likusi\u0173 funkcij\u0173 k\u016brimui.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-importance-of-assigning-priority\">Prioriteto priskyrimo svarba<\/h4>\n<p class=\"has-text-align-start\">Prioritet\u0173 priskyrimas taip pat gali pad\u0117ti \u012fvertinti projekt\u0105. Sutelk\u0119 d\u0117mes\u012f \u012f pagrindines funkcijas ir tas, kurias reikia atlikti pirmiausia, gal\u0117site tiksliau numatyti numatom\u0105 j\u0173 u\u017ebaigim\u0105. \"Gal\u0117t\u0173 b\u016bti\" funkcij\u0173 atveju galite prad\u0117ti nuo apytikslio \u012fver\u010dio, nes jos yra tolimesn\u0117je k\u016brimo proceso stadijoje ir daug kas gali pasikeisti, kol j\u016bs\u0173 komanda jas prad\u0117s kurti (ir jei komanda jas prad\u0117s kurti, nes, surink\u0119 atsiliepimus apie j\u016bs\u0173 MVP, galite pakeisti ir ne\u012ftraukti vis\u0173 i\u0161 prad\u017ei\u0173 planuot\u0173 funkcij\u0173).<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-comprehensive-estimation\">I\u0161samus vertinimas<\/h4>\n<p class=\"has-text-align-start\">Ta\u010diau svarbu \u012fvertinti visas funkcijas, nepriklausomai nuo j\u0173 prioriteto (\u017einoma, i\u0161skyrus tas, kuri\u0173 \"nebus\"), nes norite i\u0161 karto ap\u017evelgti vis\u0105 projekt\u0105. Pereidami \u012f kitus projekto etapus, galite i\u0161 naujo \u012fvertinti darb\u0173 apimt\u012f, kad \u012fsitikintum\u0117te, jog j\u016bs\u0173 \u012fver\u010diai i\u0161lieka tiksl\u016bs.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1152\" height=\"763\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134710\/Planning5.jpg\" alt=\"\" class=\"wp-image-13654\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-estimation-techniques\">Vertinimo metodai<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-story-point-estimation-process\">Istorijos ta\u0161k\u0173 vertinimo procesas<\/h4>\n<p>Dabar, kai jau turite u\u017ebaigt\u0105 produkto atsilikimo s\u0105ra\u0161\u0105, laikas \u012fvertinti kiekvien\u0105 jo element\u0105. Tam naudojame istorijos ta\u0161kus. Tai vienetai, kuriuos \"Agile\" komandos naudoja, kad \u012fvertint\u0173 darb\u0105, kurio reikia kiekvienam \"backlog\" elementui u\u017ebaigti. Istorijos ta\u0161kai padeda priskirti santykin\u0119 vert\u0119 produkto atgalinio s\u0105ra\u0161o elementams. Jie nesusij\u0119 su laiku ir skirtingoms komandoms gali tur\u0117ti skirting\u0105 vert\u0119, tod\u0117l jie neturi emocin\u0117s vert\u0117s. Taigi yra tikimyb\u0117, kad komandos nariai nepadidins s\u0105mat\u0173 vien d\u0117l saugumo. Planavimo pokeris padeda programin\u0117s \u012frangos komandoms planuoti darbo eig\u0105 ir pagerinti projekto \u012fgyvendinimo spart\u0105.<\/p>\n<p>Naudodama istorijos ta\u0161kus komanda gali \u012fvertinti:<\/p>\n<ul class=\"wp-block-list\">\n<li>\nAtliekam\u0173 darb\u0173 kiekis\n<\/li>\n<li>\nRizika ir neapibr\u0117\u017etumas\n<\/li>\n<li>\nSud\u0117tingumas\n<\/li>\n<\/ul>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1164\" height=\"776\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/06\/24135020\/MeasuringUtilization.jpg\" alt=\"\" class=\"wp-image-13642\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-using-planning-poker-for-estimation\">Planavimo pokerio naudojimas vertinimui<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-negotiate-estimates-with-planning-poker\">Derybos d\u0117l s\u0105mat\u0173 su planavimo pokeriu<\/h4>\n<p>Planavimo sesija - tai vienas i\u0161 bendrojo lygio vertinimo metod\u0173, kuriame naudojama modifikuota Fibona\u010dio sekos versija: 1, 2, 3, 5, 8, 13, 20, 40, 100. Kad \u012fvertint\u0173 gaminio s\u0105ra\u0161o elementus, komandos nariai gauna tuos pa\u010dius planavimo pokerio korteli\u0173 su skai\u010diais rinkinius. Tada, produkto savininkui (kuris nebalsuoja) trumpai prista\u010dius produkto atsilikimo s\u0105ra\u0161o element\u0105 ir prad\u0117jus diskusij\u0105, jie priva\u010diai i\u0161sirenka kortel\u0119 su tokiu istorijos ta\u0161k\u0173 skai\u010diumi, kuris, j\u0173 nuomone, yra susij\u0119s su \u0161iam elementui u\u017ebaigti reikaling\u0173 darb\u0173 kiekiu, ir tuo pa\u010diu metu jas atskleid\u017eia.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-consensus-based-estimation-technique\">Konsensusu pagr\u012fstas vertinimo metodas<\/h4>\n<p>Jei skai\u010diai skiriasi, komandos nariai aptaria, kod\u0117l jie pasirinko tok\u012f istorijos ta\u0161k\u0173 skai\u010di\u0173, ir v\u0117l balsuoja. Tai yra planavimo pokerio proceso dalis - bendru sutarimu grind\u017eiamo vertinimo metodo, naudojamo \"Agile\" metodikoje siekiant \u012fvertinti naudotojo istorij\u0173 pastangas. Taip jie daro tol, kol pasiekia bendr\u0105 sutarim\u0105, ir tada pereina prie kito produkto darb\u0173 s\u0105ra\u0161o elemento. Ir jei sutartas skai\u010dius yra didelis, tarkime, 20, 40 ar daugiau, tai rei\u0161kia, kad istorijai gali prireikti per daug darbo vienam sprintui ir j\u0105 gali tekti i\u0161skaidyti \u012f ma\u017eesnes u\u017eduotis. Idealiu atveju elemento pristatymas, diskusija ir balsavimas tur\u0117t\u0173 u\u017etrukti apie dvi minutes, tod\u0117l per trump\u0105 laik\u0105 galima \u012fvertinti vis\u0105 atsilikim\u0105. Ta\u010diau kadangi \u010dia siekiama \u012fvertinti vis\u0105 atsilikim\u0105 i\u0161 karto, neskub\u0117kite ir nesijaudinkite, jei kai kurioms istorijoms \u012fvertinti prireiks \u0161iek tiek daugiau laiko.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1152\" height=\"763\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134710\/Planning6.jpg\" alt=\"\" class=\"wp-image-13655\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-evaluating-team-velocity\">Komandos grei\u010dio vertinimas<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-assess-team-velocity\">\u012evertinkite komandos greit\u012f<\/h4>\n<p>Komandos greitis rodo, koks yra projekto vystymo tempas. Jis padeda suprasti du dalykus:<\/p>\n<p>- Kiek darbo j\u016bs\u0173 komanda gali atlikti per vien\u0105 sprint\u0105<\/p>\n<p>- Kokia numatoma visos apimties u\u017ebaigimo data, darant prielaid\u0105, kad ji yra fiksuota<\/p>\n<p>Kiekvienos komandos greitis yra skirtingas. J\u012f galite \u012fvertinti po pirm\u0173j\u0173 iteracij\u0173, kai j\u016bs\u0173 komanda jau dirba su kai kuriomis funkcijomis. Pavyzd\u017eiui, jei \u012f pirm\u0105j\u0105 iteracij\u0105 \u012ftrauk\u0117te keturis produkto atgalinio s\u0105ra\u0161o elementus, kuri\u0173 bendras skai\u010dius yra 20 istorijos punkt\u0173, o komanda baig\u0117 tris i\u0161 j\u0173, kas sudaro 15 istorijos punkt\u0173, tai yra dabartinis j\u016bs\u0173 komandos greitis. Atminkite, kad skai\u010diuojami tik u\u017ebaigti elementai. Net jei pavyko prad\u0117ti ketvirt\u0105j\u012f element\u0105, bet jo nebaigti, jis neskai\u010diuojamas.<\/p>\n<p>\"Scrum\" meistras atlieka svarb\u0173 vaidmen\u012f palengvinant vertinimo proces\u0105 ir u\u017etikrinant tikslius vertinimus per \u0161ias sesijas.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-scheduling-and-budgeting\">Planavimas ir biud\u017eeto sudarymas<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-how-to-schedule-a-particular-project-on-story-points\">Kaip suplanuoti konkret\u0173 projekt\u0105 istorijos ta\u0161kuose<\/h4>\n<p class=\"has-text-align-start\">Suderinus istorijos ta\u0161kus ir \u012fvertinus komandos greit\u012f, galima nustatyti projekto tvarkara\u0161t\u012f. Nor\u0117dami tai padaryti, susumuokite trij\u0173 paskutini\u0173 iteracij\u0173 komandos greit\u012f ir padalykite j\u012f i\u0161 trij\u0173. Pavyzd\u017eiui, jei \u0161i\u0173 iteracij\u0173 greitis buvo 20, 23 ir 17, vidutinis greitis b\u016bt\u0173 lygus ma\u017edaug 20 ta\u0161k\u0173. Jei buvo apskai\u010diuota, kad bendra darb\u0173 apimtis yra 100 istorijos ta\u0161k\u0173, tai, esant vidutiniam grei\u010diui 20 ta\u0161k\u0173, projektui u\u017ebaigti prireikt\u0173 5 iteracij\u0173. Darant prielaid\u0105, kad viena iteracija trunka dvi savaites, projekt\u0105 tur\u0117tum\u0117te \u012fgyvendinti per 10 savai\u010di\u0173.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1144\" height=\"761\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134709\/Planning7.jpg\" alt=\"\" class=\"wp-image-13656\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-determining-the-budget\">Biud\u017eeto nustatymas<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-project-cost-estimation-formula\">Projekto i\u0161laid\u0173 \u012fvertinimo formul\u0117<\/h4>\n<p class=\"has-text-align-start\">Projekto biud\u017eetui nustatyti galite naudoti \u0161i\u0105 pagrindin\u0119 formul\u0119: (bendras istorijos ta\u0161k\u0173 skai\u010dius \/ greitis * komandos valandos per sprint\u0105) + su darbu nesusijusios i\u0161laidos = numatomas biud\u017eetas. Tur\u0117dami bendr\u0105 istorijos ta\u0161k\u0173 skai\u010di\u0173, padalyt\u0105 i\u0161 vidutinio grei\u010dio, padauginkite sprint\u0173 skai\u010di\u0173 i\u0161 40 valand\u0173 per savait\u0119 vienam komandos nariui, kad gautum\u0117te darbo s\u0105naudas. Tada prid\u0117kite su darbu nesusijusias i\u0161laidas, pavyzd\u017eiui, kapitalo, \u012frangos, technin\u0117s prie\u017ei\u016bros, mokymo i\u0161laidas ir t. t. Pavyzd\u017eiui, turime projekt\u0105, kurio vert\u0117 yra 100 istorijos ta\u0161k\u0173, o vidutinis komandos greitis yra 20. Projektui priskyrus 5 \u017emoni\u0173 komand\u0105 su $50 valandiniais \u012fkainiais, komandos valandos per sprint\u0105 kainuoja $20 000, o per 5 sprintus - $100 000. Su hipotetin\u0117mis $50 000 ne darbo s\u0105naudomis numatomas m\u016bs\u0173 projekto biud\u017eetas b\u016bt\u0173 $150 000. Atsi\u017evelgiant \u012f 80-120% pavyzdini\u0173 lygi\u0173 pasikliautinuosius intervalus, nurodytas m\u016bs\u0173 biud\u017eeto intervalas dabar yra nuo $120 000 iki $180 000.<\/p>\n<figure class=\"wp-block-image\"><img decoding=\"async\" src=\"https:\/\/teamdeck.io\/wp-content\/uploads\/2024\/06\/image-placeholder.png\" alt=\"\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-re-estimation-for-accuracy\">Pakartotinis \u012fvertinimas siekiant tikslumo<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-re-estimate-your-project-to-get-a-more-accurate-cost-estimate\">I\u0161 naujo \u012fvertinkite savo projekt\u0105, kad gautum\u0117te tikslesn\u0119 s\u0105mat\u0105<\/h4>\n<p class=\"has-text-align-start\">Atminkite, kad joks \u012fvertinimas n\u0117ra 100% tikslus. Geriausia kas kelias iteracijas i\u0161 naujo \u012fvertinti projekt\u0105, nes laikui b\u0117gant gali pasikeisti tokie dalykai kaip i\u0161tekli\u0173 prieinamumas, komandos greitis ar projekto apimtis. Pakartotinai vertindami \u012fsitikinate, kad j\u016bs\u0173 s\u0105mata yra aktuali. Naudodami laiko steb\u0117jimo ir i\u0161tekli\u0173 planavimo programin\u0119 \u012frang\u0105 taip pat gal\u0117site valdyti savo komandos u\u017eimtum\u0105 ir prireikus juos perskirstyti. Naudodami tinkamus metodus ir priemones, galite padidinti savo s\u0105mat\u0173 patikimum\u0105 ir geriau suplanuoti kit\u0105 projekt\u0105.<\/p>\n<figure class=\"wp-block-image size-full\"><img loading=\"lazy\" decoding=\"async\" width=\"1150\" height=\"766\" src=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2024\/07\/24134708\/Planning8.jpg\" alt=\"\" class=\"wp-image-13657\"\/><\/figure>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-conclusion\">I\u0161vada<\/h3>\n<p class=\"has-text-align-start\">S\u0117kmingam projekto valdymui labai svarbus tikslus projekto \u012fvertinimas. Suprasdami l\u016bkes\u010dius ir tikslus, sukurdami i\u0161sam\u0173 produkto darb\u0173 s\u0105ra\u0161\u0105, nustatydami funkcij\u0173 prioritetus ir naudodami tokius metodus kaip istorijos ta\u0161kai ir planavimo pokeris, galite padidinti savo s\u0105mat\u0173 tikslum\u0105. Reguliarus pakartotinis vertinimas ir laiko steb\u0117jimo bei i\u0161tekli\u0173 valdymo priemoni\u0173 naudojimas dar labiau padidina projekto termin\u0173 ir biud\u017eet\u0173 patikimum\u0105. Laikydamiesi \u0161ios praktikos, galite \u012fveikti netiksli\u0173 s\u0105mat\u0173 keliamas problemas ir u\u017etikrinti geresnius projekto rezultatus.<\/p>\n\n\t\t<\/div>\n\t<\/div>\n<\/div><\/div><\/div><\/div><div class=\"vc_row wpb_row vc_row-fluid redl-row-section feature-row vc_custom_1574416816256 vc_row-o-equal-height vc_row-o-content-middle vc_row-flex padding-medium bgv-default bgh-default halign-center\"><\/div><div class=\"vc_row wpb_row vc_row-fluid redl-row-section vc_row-o-content-middle vc_row-flex padding-default bgv-default bgh-default halign-default\"><div class=\"wpb_column vc_column_container text-center vc_col-sm-12 padding-default bgv-default bgh-default halign-center\"><div class=\"vc_column-inner\"><div class=\"wpb_wrapper\">\n\t<div class=\"wpb_text_column wpb_content_element\" >\n\t\t<div class=\"wpb_wrapper\">\n\t\t\t<p> Lengvai naudokite planavimo pokerio vertinimo metod\u0105<\/p>\n<p><strong>Su\u017einokite, kod\u0117l m\u016bs\u0173 i\u0161tekli\u0173 valdymo programin\u0119 \u012frang\u0105 renkasi \"Hill-Knowlton\" ar \"Stormind Games\" projekt\u0173 vadovai.<\/strong> <\/p>\n\n\t\t<\/div>\n\t<\/div>\n<a class=\"redl-btn   vc_custom_1596025898618 redl-btn-medium redl-btn-69e1eb22703b7 btn-icon-left redl-btn redl-btn-two vc_custom_1551260371526 redl-btn-medium redl-btn-5f2168a4adf5d btn-hover-one btn-icon-right signup-top\" href=\"https:\/\/app.teamdeck.io\/register\">Gaukite 14 dien\u0173 NEMOKAM\u0104 bandom\u0105j\u0105 versij\u0105<\/a><div class=\"vc_empty_space\"   style=\"height: 32px\" ><span class=\"vc_empty_space_inner\"><\/span><\/div>\n<\/div><\/div><\/div><\/div>","protected":false},"excerpt":{"rendered":"Netiksli\u0173 s\u0105mat\u0173 problema Netikslios s\u0105matos yra viena populiariausi\u0173 projekt\u0173 valdymo problem\u0173. Prad\u0117dami nauj\u0105 IT projekt\u0105 norite \u017einoti du dalykus: kiek laiko jis u\u017etruks ir kiek...","protected":false},"author":3,"featured_media":8515,"comment_status":"closed","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[22],"tags":[33,28,32],"class_list":["post-2825","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-project-management","tag-estimation","tag-project-manager","tag-project-planning"],"yoast_head":"<!-- This site is optimized with the Yoast SEO Premium plugin v23.8 (Yoast SEO v24.3) - https:\/\/yoast.com\/wordpress\/plugins\/seo\/ -->\n<title>Planning Poker Estimation Technique and Story Points | Teamdeck.io<\/title>\n<meta name=\"description\" content=\"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology, Planning Poker and Story Points.\" \/>\n<meta name=\"robots\" content=\"index, follow, max-snippet:-1, max-image-preview:large, max-video-preview:-1\" \/>\n<link rel=\"canonical\" href=\"https:\/\/teamdeck.io\/lt\/projektu-valdymas\/kaip-ivertinti-projektus\/\" \/>\n<meta property=\"og:locale\" content=\"lt_LT\" \/>\n<meta property=\"og:type\" content=\"article\" \/>\n<meta property=\"og:title\" content=\"Your estimates suck, but that\u2019s ok\" \/>\n<meta property=\"og:description\" content=\"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology and Planning Poker.\" \/>\n<meta property=\"og:url\" content=\"https:\/\/teamdeck.io\/lt\/projektu-valdymas\/kaip-ivertinti-projektus\/\" \/>\n<meta property=\"og:site_name\" content=\"Teamdeck\" \/>\n<meta property=\"article:publisher\" content=\"https:\/\/www.facebook.com\/helloteamdeck\" \/>\n<meta property=\"article:published_time\" content=\"2024-07-01T10:03:26+00:00\" \/>\n<meta property=\"article:modified_time\" content=\"2025-01-23T20:46:57+00:00\" \/>\n<meta property=\"og:image\" content=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/helloquence-61189.jpg\" \/>\n<meta name=\"author\" content=\"Pawe\u0142 Ha\u0142abuda\" \/>\n<meta name=\"twitter:card\" content=\"summary_large_image\" \/>\n<meta name=\"twitter:title\" content=\"Your estimates suck, but that\u2019s ok\" \/>\n<meta name=\"twitter:description\" content=\"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology and Planning Poker.\" \/>\n<meta name=\"twitter:image\" content=\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/helloquence-61189.jpg\" \/>\n<meta name=\"twitter:creator\" content=\"@helloteamdeck\" \/>\n<meta name=\"twitter:site\" content=\"@helloteamdeck\" \/>\n<meta name=\"twitter:label1\" content=\"Written by\" \/>\n\t<meta name=\"twitter:data1\" content=\"Pawe\u0142 Ha\u0142abuda\" \/>\n\t<meta name=\"twitter:label2\" content=\"Est. reading time\" \/>\n\t<meta name=\"twitter:data2\" content=\"11 minutes\" \/>\n<script type=\"application\/ld+json\" class=\"yoast-schema-graph\">{\"@context\":\"https:\/\/schema.org\",\"@graph\":[{\"@type\":\"WebPage\",\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/\",\"url\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/\",\"name\":\"Planning Poker Estimation Technique and Story Points | Teamdeck.io\",\"isPartOf\":{\"@id\":\"https:\/\/teamdeck.io\/#website\"},\"primaryImageOfPage\":{\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage\"},\"image\":{\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage\"},\"thumbnailUrl\":\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg\",\"datePublished\":\"2024-07-01T10:03:26+00:00\",\"dateModified\":\"2025-01-23T20:46:57+00:00\",\"author\":{\"@id\":\"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e\"},\"description\":\"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology, Planning Poker and Story Points.\",\"breadcrumb\":{\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#breadcrumb\"},\"inLanguage\":\"lt-LT\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"lt-LT\",\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage\",\"url\":\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg\",\"contentUrl\":\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg\",\"width\":1470,\"height\":981,\"caption\":\"Estimate Projects with Planning Poker and Story Points\"},{\"@type\":\"BreadcrumbList\",\"@id\":\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#breadcrumb\",\"itemListElement\":[{\"@type\":\"ListItem\",\"position\":1,\"name\":\"Home\",\"item\":\"https:\/\/teamdeck.io\/\"},{\"@type\":\"ListItem\",\"position\":2,\"name\":\"Planning Poker Estimation Technique and Story Points\"}]},{\"@type\":\"WebSite\",\"@id\":\"https:\/\/teamdeck.io\/#website\",\"url\":\"https:\/\/teamdeck.io\/\",\"name\":\"Teamdeck\",\"description\":\"resource scheduling + time tracking + leave management\",\"potentialAction\":[{\"@type\":\"SearchAction\",\"target\":{\"@type\":\"EntryPoint\",\"urlTemplate\":\"https:\/\/teamdeck.io\/?s={search_term_string}\"},\"query-input\":{\"@type\":\"PropertyValueSpecification\",\"valueRequired\":true,\"valueName\":\"search_term_string\"}}],\"inLanguage\":\"lt-LT\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e\",\"name\":\"Pawe\u0142 Ha\u0142abuda\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"lt-LT\",\"@id\":\"https:\/\/teamdeck.io\/#\/schema\/person\/image\/\",\"url\":\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/25113657\/s38W_LT-150x150.jpg\",\"contentUrl\":\"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/25113657\/s38W_LT-150x150.jpg\",\"caption\":\"Pawe\u0142 Ha\u0142abuda\"}}]}<\/script>\n<!-- \/ Yoast SEO Premium plugin. -->","yoast_head_json":{"title":"Planning Poker Estimation Technique and Story Points | Teamdeck.io","description":"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology, Planning Poker and Story Points.","robots":{"index":"index","follow":"follow","max-snippet":"max-snippet:-1","max-image-preview":"max-image-preview:large","max-video-preview":"max-video-preview:-1"},"canonical":"https:\/\/teamdeck.io\/lt\/projektu-valdymas\/kaip-ivertinti-projektus\/","og_locale":"lt_LT","og_type":"article","og_title":"Your estimates suck, but that\u2019s ok","og_description":"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology and Planning Poker.","og_url":"https:\/\/teamdeck.io\/lt\/projektu-valdymas\/kaip-ivertinti-projektus\/","og_site_name":"Teamdeck","article_publisher":"https:\/\/www.facebook.com\/helloteamdeck","article_published_time":"2024-07-01T10:03:26+00:00","article_modified_time":"2025-01-23T20:46:57+00:00","og_image":[{"url":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/helloquence-61189.jpg","type":"","width":"","height":""}],"author":"Pawe\u0142 Ha\u0142abuda","twitter_card":"summary_large_image","twitter_title":"Your estimates suck, but that\u2019s ok","twitter_description":"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology and Planning Poker.","twitter_image":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/helloquence-61189.jpg","twitter_creator":"@helloteamdeck","twitter_site":"@helloteamdeck","twitter_misc":{"Written by":"Pawe\u0142 Ha\u0142abuda","Est. reading time":"11 minutes"},"schema":{"@context":"https:\/\/schema.org","@graph":[{"@type":"WebPage","@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/","url":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/","name":"Planning Poker Estimation Technique and Story Points | Teamdeck.io","isPartOf":{"@id":"https:\/\/teamdeck.io\/#website"},"primaryImageOfPage":{"@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage"},"image":{"@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage"},"thumbnailUrl":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg","datePublished":"2024-07-01T10:03:26+00:00","dateModified":"2025-01-23T20:46:57+00:00","author":{"@id":"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e"},"description":"Estimating software projects is usually very tricky. Here\u2019s how to create meaningful estimates using Agile methodology, Planning Poker and Story Points.","breadcrumb":{"@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#breadcrumb"},"inLanguage":"lt-LT","potentialAction":[{"@type":"ReadAction","target":["https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/"]}]},{"@type":"ImageObject","inLanguage":"lt-LT","@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#primaryimage","url":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg","contentUrl":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/07\/17161904\/How-to-Estimate-Projects-with-Planning-Poker-and-Story-Points.jpeg","width":1470,"height":981,"caption":"Estimate Projects with Planning Poker and Story Points"},{"@type":"BreadcrumbList","@id":"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/#breadcrumb","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https:\/\/teamdeck.io\/"},{"@type":"ListItem","position":2,"name":"Planning Poker Estimation Technique and Story Points"}]},{"@type":"WebSite","@id":"https:\/\/teamdeck.io\/#website","url":"https:\/\/teamdeck.io\/","name":"Teamdeck","description":"resource scheduling + time tracking + leave management","potentialAction":[{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https:\/\/teamdeck.io\/?s={search_term_string}"},"query-input":{"@type":"PropertyValueSpecification","valueRequired":true,"valueName":"search_term_string"}}],"inLanguage":"lt-LT"},{"@type":"Person","@id":"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e","name":"Pawe\u0142 Ha\u0142abuda","image":{"@type":"ImageObject","inLanguage":"lt-LT","@id":"https:\/\/teamdeck.io\/#\/schema\/person\/image\/","url":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/25113657\/s38W_LT-150x150.jpg","contentUrl":"https:\/\/cdn.teamdeck.io\/uploads\/website\/2017\/09\/25113657\/s38W_LT-150x150.jpg","caption":"Pawe\u0142 Ha\u0142abuda"}}]}},"_links":{"self":[{"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/posts\/2825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/comments?post=2825"}],"version-history":[{"count":33,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/posts\/2825\/revisions"}],"predecessor-version":[{"id":13658,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/posts\/2825\/revisions\/13658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/media\/8515"}],"wp:attachment":[{"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/media?parent=2825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/categories?post=2825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teamdeck.io\/lt\/wp-json\/wp\/v2\/tags?post=2825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}