{"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\/et\/projektijuhtimine\/kuidas-hinnata-projekte\/","title":{"rendered":"Planeerimise pokkerite hindamise tehnika ja jutupunktid"},"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\">Ebat\u00e4psete hinnangute v\u00e4ljakutse<\/h3>\n<p class=\"has-text-align-start\">Ebat\u00e4psed hinnangud on \u00fcks populaarsemaid projektijuhtimise probleeme. Uue IT-projekti alustamisel soovite teada kahte asja: kui kaua see kestab ja kui palju see maksab. Nendele k\u00fcsimustele vastamiseks tuleb teil hinnata projekte, mida te kavatsete k\u00e4ivitada. Ei ole olemas maagilist reeglit, mis \u00fctleb, et projekt X v\u00f5tab aega 12 n\u00e4dalat ja maksab $150 000. V\u00f5i Y-taolise veebisaidi arendamiseks kulub 10 n\u00e4dalat ja see maksab $100 000.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-key-questions-answered-in-this-article\">Selles artiklis vastatud p\u00f5hik\u00fcsimused<\/h3>\n<p class=\"has-text-align-start\">Mida te sellest artiklist saate teada:<\/p>\n<p>- Kuidas valmistuvad projektijuhid projektijuhtimise kulude hindamiseks?<\/p>\n<p>- Millised hindamismeetodid on kasulikud projekti hindamiseks?<\/p>\n<p>- Kuidas v\u00f5tab planeerimine aega, et valmistada end ette kulude hindamiseks valemitega?<\/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\">T\u00e4pse hindamise t\u00e4htsus<\/h3>\n<p class=\"has-text-align-start\">Te ei saa hinnata projekti ajakava v\u00f5i kulusid ilma p\u00f5hjaliku hinnanguta, isegi kui projekti ulatus on v\u00e4ga sarnane sellega, mida olete varem teinud. Kuid asi l\u00e4heb veel hullemaks: hindamine ei anna teile kunagi 100% t\u00e4pset vastust ka nendele k\u00fcsimustele. Miks me siis hindame? Sest see on ainus v\u00f5imalus teha eeldusi projekti ajakava ja eelarve, t\u00f6\u00f6koormuse ja projekti elluviimiseks vajalike ressursside kohta.<\/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\">T\u00e4pse hindamise eelised<\/h3>\n<p class=\"has-text-align-start\">Projekti hinnates saate ka \u00f5ige kogemuse ja oskustega t\u00f6\u00f6tajad planeerida. Mida saate teha, on kasutada metoodikaid ja tehnikaid, mis v\u00f5imaldavad teil hinnata v\u00f5imalikult t\u00e4pselt. Siin on, kuidas kasutada agiilset metoodikat ja planeerimispokkeri tehnikat, et koostada oma projekti kohta sisukaid hinnanguid.<\/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\">Pokkeri planeerimise p\u00e4ritolu<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-where-did-scrum-planning-poker-come-from\">Kust tuli Scrumi (planeerimise) pokker?<\/h4>\n<p class=\"has-text-align-start\">James Grenning t\u00f6\u00f6tas 2002. aastal v\u00e4lja oma strateegia poolest tuntud planeerimispokkeri, mida nimetatakse Scrum pokkeriks. 1950ndate alguses oli tema hindamismeetod, Wide band Delphi, liiga aegan\u00f5udev ja tal olid muud piirangud. Grenningi puhul k\u00e4sitles pokker algselt probleemi lahendamist, kus m\u00e4ngijad olid liiga entusiastlikud ja liiga keskendunud, et v\u00f5ita. Mike Cohn, agiilsete liitude ja Scrumi liitude asutaja, kasutas seda tehnikat hiljem artiklis 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\">Projekti t\u00e4pse hindamise sammud<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-create-a-list-of-required-features\">Looge n\u00f5utavate funktsioonide nimekiri<\/h4>\n<p class=\"has-text-align-start\">Eduka projekti k\u00e4ivitamine s\u00f5ltub peamiselt sellest, kui h\u00e4sti te m\u00f5istate, millega see tegelikult seotud on. See h\u00f5lmab j\u00e4rgmist:<\/p>\n<p>- Kliendi ootuste m\u00f5istmine<\/p>\n<p>- Projekti eesm\u00e4rkide ja peamise eesm\u00e4rgi m\u00f5istmine<\/p>\n<p>- N\u00f5utavate funktsioonide loetelu koostamine<\/p>\n<p class=\"has-text-align-start\">Kui olete saanud kliendi l\u00fchikirjelduse l\u00e4bi ja teil on v\u00f5imalikult palju teavet projekti n\u00f5uete kohta, saate loetleda k\u00f5ik funktsioonid ja edastada need oma meeskonnale.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-developing-a-product-backlog\">Toote tagavaraportfelli v\u00e4ljat\u00f6\u00f6tamine<\/h4>\n<p>Selleks looge toote tagavaraplaan, mis koosneb k\u00f5igist tegemata funktsioonidest. Seej\u00e4rel saate need t\u00e4htsuse j\u00e4rjekorda seada, hinnata nende keerukust ja hinnata, kui kaua nende l\u00f5puleviimiseks kulub aega. Korralik toote backlog peaks koosnema j\u00e4rgmistest elementidest:<\/p>\n<p>- Kasutaja lood - kirjeldavad tegevusi, mida kasutajad saavad teha toote kasutamise igal etapil.<\/p>\n<p>- Vastuv\u00f5tukriteeriumid - loe \u00fcles, mida on vaja loo l\u00f5petamiseks.<\/p>\n<p>- Loo punktid - hinnata t\u00f6\u00f6mahtu, riske ja keerukust suhtelises punktiv\u00e4\u00e4rtuses<\/p>\n<p>- Kasutaja lugude \u00fclesanded - loendage \u00fclesanded, mida on vaja teha kasutaja loo elluviimiseks.<\/p>\n<p>T\u00e4pse ja realistliku hinnangu tagamiseks on v\u00e4ga oluline kaasata arendusmeeskond tooteprojekti koostamisse ja prioriteetide seadmisse.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-prioritizing-features\">Prioriteedi seadmine funktsioonidele<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-sort-features-by-priority\">Sorteeri omadused prioriteedi j\u00e4rgi<\/h4>\n<p class=\"has-text-align-start\">Kui funktsioonide nimekiri on valmis, m\u00e4\u00e4rake iga\u00fchele neist prioriteet. V\u00f5ite kasutada MoSCoW anal\u00fc\u00fcsimeetodit, et neid sorteerida j\u00e4rgmiselt:<\/p>\n<p>- Peab olema<\/p>\n<p>- Peaks olema<\/p>\n<p>- Oleks v\u00f5inud<\/p>\n<p>- Ei ole<\/p>\n<p class=\"has-text-align-start\">Projekti arendamisel keskenduge asjadele, mida peate esmaj\u00e4rjekorras t\u00e4itma. MVP ehitamine annab teile v\u00f5imaluse testida h\u00fcpoteese oma idee kohta enne kogu projekti l\u00f5puleviimist, n\u00e4idata seda sidusr\u00fchmadele v\u00f5i beetakasutajatele ning koguda tagasisidet, mis on oluline \u00fclej\u00e4\u00e4nud funktsioonide edasiseks arendamiseks.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-importance-of-assigning-priority\">Prioriteedi m\u00e4\u00e4ramise t\u00e4htsus<\/h4>\n<p class=\"has-text-align-start\">Prioriteedi m\u00e4\u00e4ramine aitab teil ka projekti hindamisel. Kui keskendute peamistele funktsioonidele ja nendele, mida on vaja teha esimesena, saate teha t\u00e4psemaid oletusi nende eeldatava valmimise kohta. \"V\u00f5iks olla\" funktsioonide puhul v\u00f5ite alustada ligikaudse hinnanguga, kuna need on arendusprotsessis kaugemal ja palju v\u00f5ib muutuda selleks ajaks, kui teie meeskond nende juurde j\u00f5uab (ja kui teie meeskond j\u00f5uab nende juurde, sest p\u00e4rast tagasiside kogumist oma MVP kohta v\u00f5ite muuta ja mitte lisada k\u00f5iki algselt kavandatud funktsioone).<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-comprehensive-estimation\">P\u00f5hjalik hindamine<\/h4>\n<p class=\"has-text-align-start\">Oluline on siiski hinnata k\u00f5iki funktsioone, s\u00f5ltumata nende prioriteetsusest (v\u00e4lja arvatud muidugi need, mida \"ei ole\"), sest te soovite saada korraga \u00fclevaate kogu projektist. Ja kui j\u00f5uate projekti j\u00e4rgmistesse etappidesse, saate t\u00f6\u00f6de mahtu uuesti hinnata, et teie hinnangud j\u00e4\u00e4ksid t\u00e4pseks.<\/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\">Hindamistehnikad<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-story-point-estimation-process\">Loo punkti hindamise protsess<\/h4>\n<p>N\u00fc\u00fcd, kui teil on oma tooteprojektide nimekiri valmis, on aeg hinnata iga \u00fcksikut selle punkti. Selleks kasutame jutupunkte. Need on \u00fcksused, mida agiilsed meeskonnad kasutavad iga backlogi elemendi l\u00f5petamiseks vajaliku t\u00f6\u00f6 hindamiseks. Story points aitavad m\u00e4\u00e4rata toote backlogi objektidele suhtelist v\u00e4\u00e4rtust. Need ei ole seotud ajaga ja v\u00f5ivad erinevatele meeskondadele kanda erinevat v\u00e4\u00e4rtust, seega ei kanna nad emotsionaalset v\u00e4\u00e4rtust. Seega on t\u00f5en\u00e4oline, et meeskonnaliikmed ei paisuta hinnanguid vaid kindluse m\u00f5ttes. Planeerimispokker aitab tarkvarameeskondadel kavandada t\u00f6\u00f6vooge ja parandada projekti valmiduskiirust.<\/p>\n<p>Kasutades jutupunkte, saab meeskond hinnata:<\/p>\n<ul class=\"wp-block-list\">\n<li>\nTehtava t\u00f6\u00f6 hulk\n<\/li>\n<li>\nRiskid ja ebakindlus\n<\/li>\n<li>\nKeerukus\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\">Planeerimispokkeri kasutamine hindamiseks<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-negotiate-estimates-with-planning-poker\">L\u00e4bir\u00e4\u00e4kimised hinnangute \u00fcle planeerimispokkeriga<\/h4>\n<p>Planeerimise sessioon on \u00fcks brutotasandi hindamismeetoditest, mille puhul kasutatakse Fibonacci jada modifitseeritud versiooni: 1, 2, 3, 5, 8, 13, 20, 40, 100. Toote tagavaraportfelli elementide hindamiseks saavad meeskonnaliikmed samad planeerimispokkeri kaardid, millel on numbrid. Seej\u00e4rel valivad nad p\u00e4rast toote omaniku (kes ei h\u00e4\u00e4leta) poolt toote tagavaralogi punkti l\u00fchitutvustust ja arutelu eraviisiliselt v\u00e4lja kaardi, millel on nende arvates selle punkti t\u00e4itmiseks vajaliku t\u00f6\u00f6mahu suhtes asjakohane loo punktide arv, ja paljastavad need korraga.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-consensus-based-estimation-technique\">Konsensusp\u00f5hine hindamistehnika<\/h4>\n<p>Kui arvud erinevad, arutavad meeskonnaliikmed, miks nad sellise arvu loosipunkte valisid, ja h\u00e4\u00e4letavad seej\u00e4rel uuesti. See on osa planeerimispokkeri protsessist, mis on konsensusp\u00f5hine hindamismeetod, mida kasutatakse Agile'is kasutajate lugude t\u00f6\u00f6mahu hindamiseks. Nad teevad seda seni, kuni j\u00f5uavad konsensusele, ja seej\u00e4rel liiguvad edasi j\u00e4rgmise toote tagavaraprogrammi punkti juurde. Ja kui kokkulepitud arv on suur, \u00fctleme 20, 40 v\u00f5i suurem, t\u00e4hendab see, et lugu v\u00f5ib n\u00f5uda \u00fche sprindi jaoks liiga palju t\u00f6\u00f6d ja seda v\u00f5ib olla vaja jagada v\u00e4iksemateks \u00fclesanneteks. Ideaalis peaks kirje tutvustamine, arutelu ja h\u00e4\u00e4letamine kestma umbes kaks minutit, mis v\u00f5imaldab kogu backlogi l\u00fchikese ajaga hinnata. Kuid kuna eesm\u00e4rk on hinnata kogu backlogi korraga, v\u00f5tke aega ja \u00e4rge muretsege, kui m\u00f5ne loo hindamine v\u00f5tab veidi kauem aega.<\/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\">Meeskonna kiiruse hindamine<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-assess-team-velocity\">Hinnake meeskonna kiirust<\/h4>\n<p>Meeskonna kiirus n\u00e4itab, milline on projekti arengu tempo. See aitab m\u00f5ista kahte asja:<\/p>\n<p>- Millise t\u00f6\u00f6mahu suudab teie meeskond \u00fche sprindi jooksul \u00e4ra teha.<\/p>\n<p>- Milline on prognoositav kuup\u00e4ev, millal kogu rakendusala l\u00f5petatakse, eeldades, et see on fikseeritud.<\/p>\n<p>Kiirus on iga meeskonna puhul erinev. Seda saab hinnata p\u00e4rast esimesi iteratsioone, kui teie meeskond on juba t\u00f6\u00f6tanud m\u00f5ne funktsiooni kallal. N\u00e4iteks kui te olete esimesse iteratsiooni lisanud neli tooteprotokolli punkti, mis teeb kokku 20 loo punkti, ja meeskond on neist kolm l\u00f5petanud, mis teeb 15 loo punkti, siis on see teie meeskonna praegune kiirus (velocity). Pidage meeles, et arvesse l\u00e4hevad ainult l\u00f5petatud elemendid. Isegi kui nad oleksid suutnud alustada neljandat punkti, kuid ei ole seda l\u00f5petanud, ei loe see.<\/p>\n<p>Scrum master m\u00e4ngib olulist rolli hindamisprotsessi h\u00f5lbustamisel ja t\u00e4psete hinnangute tagamisel nende seansside ajal.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-scheduling-and-budgeting\">Planeerimine ja eelarvestamine<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-how-to-schedule-a-particular-project-on-story-points\">Kuidas planeerida konkreetne projekt Story Points'ile<\/h4>\n<p class=\"has-text-align-start\">P\u00e4rast l\u00e4bir\u00e4\u00e4kimiste pidamist loo punktide \u00fcle ja meeskonna kiiruse hindamist saate m\u00e4\u00e4rata projekti ajakava. Selleks liita kokku meeskonna kiirus viimasest kolmest iteratsioonist ja jaga see kolmega. N\u00e4iteks kui nende iteratsioonide kiirus oli 20, 23 ja 17, siis keskmine kiirus oleks ligikaudu 20 punkti. Kui kogu t\u00f6\u00f6 maht oli hinnanguliselt 100 jutupunkti, siis keskmise kiiruse 20 punkti puhul kuluks projekti l\u00f5puleviimiseks 5 iteratsiooni. Eeldades, et \u00fcks iteratsioon v\u00f5tab aega kaks n\u00e4dalat, peaksite projekti valmis saama 10 n\u00e4dalaga.<\/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\">Eelarve kindlaksm\u00e4\u00e4ramine<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-project-cost-estimation-formula\">Projekti kulude hindamise valem<\/h4>\n<p class=\"has-text-align-start\">Oma projekti eelarve m\u00e4\u00e4ramiseks v\u00f5ite kasutada j\u00e4rgmist p\u00f5hivalemit: (Story Points kokku \/ Velocity * meeskonnatunnid sprindi kohta) + mittet\u00f6\u00f6j\u00f5ukulud = hinnanguline eelarve. Kui teil on loo punktide koguarv jagatuna keskmise kiirusega, korrutage sprintide arv 40 tunniga n\u00e4dalas meeskonnaliikme kohta, et saada t\u00f6\u00f6j\u00f5ukulud. Seej\u00e4rel lisage mittet\u00f6\u00f6j\u00f5ukulud, nagu kapitalikulud, seadmete kulud, hoolduskulud, koolituskulud jne. N\u00e4iteks on meil projekti hinnanguline maht 100 jutupunkti ja meie meeskonna keskmine kiirus on 20. M\u00e4\u00e4rates projektile 5-liikmelise meeskonna $50 tunnitasuga, on meeskonna tundide v\u00e4\u00e4rtus \u00fche sprindi kohta $20 000 ja 5 sprindi puhul $100 000. Kui h\u00fcpoteetiline mittet\u00f6\u00f6j\u00f5ukulu on $50,000, oleks meie projekti hinnanguline eelarve $150,000. V\u00f5ttes arvesse usaldusvahemikke 80-120%, on meie eelarve teatatud vahemik n\u00fc\u00fcd $120,000 kuni $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\">Uuesti hindamine t\u00e4psuse tagamiseks<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-re-estimate-your-project-to-get-a-more-accurate-cost-estimate\">Hinnake oma projekti uuesti, et saada t\u00e4psem kulude kalkulatsioon<\/h4>\n<p class=\"has-text-align-start\">Pidage meeles, et \u00fckski hinnang ei ole 100% t\u00e4pne. Parem on oma projekti iga paari iteratsiooni j\u00e4rel uuesti hinnata, sest asjad, nagu ressursside k\u00e4ttesaadavus, meeskonna kiirus v\u00f5i projekti ulatus, v\u00f5ivad aja jooksul muutuda. Uuesti hinnates veendute, et teie hinnang on ajakohane. Aja j\u00e4lgimise ja ressursside planeerimise tarkvara kasutamine aitab teil ka juhtida oma meeskonna k\u00e4ttesaadavust ja vajadusel neid \u00fcmber paigutada. \u00d5igete tehnikate ja t\u00f6\u00f6riistade abil saate muuta oma hinnangud usaldusv\u00e4\u00e4rsemaks ja paremini planeerida oma j\u00e4rgmist projekti.<\/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\">Kokkuv\u00f5te<\/h3>\n<p class=\"has-text-align-start\">T\u00e4pne projektihindamine on eduka projektijuhtimise jaoks \u00fclioluline. Kui m\u00f5istate ootusi ja eesm\u00e4rke, koostate \u00fcksikasjaliku tooteprojekti, seate funktsioonid t\u00e4htsuse j\u00e4rjekorda ning kasutate selliseid tehnikaid nagu story points ja Planning Poker, saate parandada oma hinnangute t\u00e4psust. Regulaarne \u00fcmberhindamine ning aja j\u00e4lgimise ja ressursside haldamise vahendite kasutamine suurendavad veelgi teie projekti ajakava ja eelarve usaldusv\u00e4\u00e4rsust. Neid tavasid j\u00e4rgides saate \u00fcletada ebat\u00e4psetest hinnangutest tulenevad probleemid ja tagada paremad projektitulemused.<\/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> Kasutage h\u00f5lpsasti planeerimispokkeri hindamistehnikat<\/p>\n<p><strong>Vaata, miks meie ressursihaldustarkvara valivad projektijuhid Hill-Knowltonist v\u00f5i Stormind Gamesist<\/strong> <\/p>\n\n\t\t<\/div>\n\t<\/div>\n<a class=\"redl-btn   vc_custom_1596025898618 redl-btn-medium redl-btn-69d02e7237e26 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\">Hankige 14-p\u00e4evane TASUTA prooviperiood<\/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":"Ebat\u00e4psete hinnangute probleem Ebat\u00e4psed hinnangud on \u00fcks populaarsemaid projektijuhtimise probleeme. Uue IT-projekti alustamisel soovite teada kahte asja: kui kaua see kestab ja kui palju...","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\/et\/projektijuhtimine\/kuidas-hinnata-projekte\/\" \/>\n<meta property=\"og:locale\" content=\"et_EE\" \/>\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\/et\/projektijuhtimine\/kuidas-hinnata-projekte\/\" \/>\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\":\"et\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"et\",\"@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\":\"et\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e\",\"name\":\"Pawe\u0142 Ha\u0142abuda\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"et\",\"@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\/et\/projektijuhtimine\/kuidas-hinnata-projekte\/","og_locale":"et_EE","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\/et\/projektijuhtimine\/kuidas-hinnata-projekte\/","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":"et","potentialAction":[{"@type":"ReadAction","target":["https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/"]}]},{"@type":"ImageObject","inLanguage":"et","@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":"et"},{"@type":"Person","@id":"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e","name":"Pawe\u0142 Ha\u0142abuda","image":{"@type":"ImageObject","inLanguage":"et","@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\/et\/wp-json\/wp\/v2\/posts\/2825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/comments?post=2825"}],"version-history":[{"count":33,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/posts\/2825\/revisions"}],"predecessor-version":[{"id":13658,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/posts\/2825\/revisions\/13658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/media\/8515"}],"wp:attachment":[{"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/media?parent=2825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/categories?post=2825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teamdeck.io\/et\/wp-json\/wp\/v2\/tags?post=2825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}