{"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\/ro\/managementul-proiectelor\/cum-sa-estimati-proiectele\/","title":{"rendered":"Planificarea Poker Tehnica de estimare \u0219i Story Points"},"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\">Provocarea estim\u0103rilor inexacte<\/h3>\n<p class=\"has-text-align-start\">Estim\u0103rile inexacte se num\u0103r\u0103 printre cele mai populare provoc\u0103ri legate de gestionarea proiectelor. Atunci c\u00e2nd \u00eencepe\u021bi un nou proiect IT, dori\u021bi s\u0103 \u0219ti\u021bi dou\u0103 lucruri: c\u00e2t timp va dura \u0219i c\u00e2t va costa. Pentru a r\u0103spunde la aceste \u00eentreb\u0103ri, trebuie s\u0103 estima\u021bi proiectele pe care urmeaz\u0103 s\u0103 le derula\u021bi. Nu exist\u0103 o regul\u0103 magic\u0103 care s\u0103 spun\u0103 c\u0103 proiectul X dureaz\u0103 12 s\u0103pt\u0103m\u00e2ni \u0219i cost\u0103 $150.000. Sau un site web de tip Y are nevoie de 10 s\u0103pt\u0103m\u00e2ni pentru a fi dezvoltat \u0219i cost\u0103 $100.000.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-key-questions-answered-in-this-article\">\u00centreb\u0103ri cheie la care se r\u0103spunde \u00een acest articol<\/h3>\n<p class=\"has-text-align-start\">Ce ve\u021bi \u00eenv\u0103\u021ba din acest articol:<\/p>\n<p>- Cum se preg\u0103tesc managerii de proiect pentru estimarea costurilor \u00een managementul proiectelor?<\/p>\n<p>- Ce tehnici de estimare sunt utile pentru estimarea proiectelor?<\/p>\n<p>- C\u00e2t dureaz\u0103 planificarea pentru a v\u0103 preg\u0103ti s\u0103 estima\u021bi costurile cu ajutorul formulelor?<\/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\">Importan\u021ba estim\u0103rii exacte<\/h3>\n<p class=\"has-text-align-start\">Nu pute\u021bi evalua calendarul sau costul unui proiect f\u0103r\u0103 o estimare am\u0103nun\u021bit\u0103, chiar dac\u0103 domeniul de aplicare al proiectului este foarte similar cu ceea ce a\u021bi mai f\u0103cut. Cu toate acestea, lucrurile devin \u0219i mai grave: estimarea nu v\u0103 va oferi niciodat\u0103 un r\u0103spuns 100% precis nici la aceste \u00eentreb\u0103ri. Deci, de ce estim\u0103m? Pentru c\u0103 este singura modalitate de a formula ipoteze cu privire la calendarul \u0219i bugetul proiectului, la volumul de munc\u0103 \u0219i la resursele necesare pentru realizarea acestuia.<\/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\">Beneficiile unei estim\u0103ri precise<\/h3>\n<p class=\"has-text-align-start\">Estim\u00e2nd proiectul, pute\u021bi, de asemenea, s\u0103 programa\u021bi angaja\u021bii cu experien\u021ba \u0219i competen\u021bele potrivite. Ceea ce pute\u021bi face \u00een acest sens este s\u0103 utiliza\u021bi metodologii \u0219i tehnici care v\u0103 vor permite s\u0103 estima\u021bi cu cea mai mare acurate\u021be posibil\u0103. Iat\u0103 cum s\u0103 utiliza\u021bi metodologia Agile \u0219i tehnica Planning Poker pentru a crea estim\u0103ri semnificative ale proiectului dumneavoastr\u0103.<\/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\">Originea pokerului de planificare<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-where-did-scrum-planning-poker-come-from\">De unde a ap\u0103rut Scrum (planificare) Poker?<\/h4>\n<p class=\"has-text-align-start\">James Grenning a dezvoltat \u00een 2002 o sesiune de poker de planificare cunoscut\u0103 pentru strategia sa, numit\u0103 Scrum poker. La \u00eenceputul anilor 1950, metoda sa de estimare, Wide band Delphi, era prea consumatoare de timp \u0219i avea alte limit\u0103ri. \u00cen cazul lui Grenning, planul de poker a fost ini\u021bial despre abordarea unei probleme \u00een care juc\u0103torii erau prea entuziasma\u021bi \u0219i prea concentra\u021bi pentru a c\u00e2\u0219tiga. Mike Cohn, fondator al alian\u021belor Agile \u0219i al alian\u021belor Scrum, a utilizat ulterior aceast\u0103 tehnic\u0103 pentru un articol intitulat Agile Estimation and Planning (Estimare \u0219i planificare Agile).<\/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\">Pa\u0219i pentru o estimare precis\u0103 a proiectului<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-create-a-list-of-required-features\">Crea\u021bi o list\u0103 de caracteristici necesare<\/h4>\n<p class=\"has-text-align-start\">Demararea cu succes a unui proiect depinde \u00een principal de c\u00e2t de bine \u00een\u021belege\u021bi despre ce este vorba. Aceasta include:<\/p>\n<p>- \u00cen\u021belegerea a\u0219tept\u0103rilor clientului dvs.<\/p>\n<p>- \u00cen\u021belegerea obiectivelor proiectului \u0219i a scopului s\u0103u principal<\/p>\n<p>- Crearea unei liste de caracteristici necesare<\/p>\n<p class=\"has-text-align-start\">Odat\u0103 ce a\u021bi parcurs briefingul clientului \u0219i ave\u021bi c\u00e2t mai multe informa\u021bii despre cerin\u021bele proiectului, pute\u021bi s\u0103 enumera\u021bi toate caracteristicile \u0219i s\u0103 le transmite\u021bi echipei dvs.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-developing-a-product-backlog\">Dezvoltarea unui portofoliu de produse<\/h4>\n<p>Pentru a face acest lucru, crea\u021bi un portofoliu de produse care s\u0103 cuprind\u0103 toate caracteristicile de f\u0103cut. Pute\u021bi apoi s\u0103 le prioritiza\u021bi, s\u0103 le evalua\u021bi complexitatea \u0219i s\u0103 estima\u021bi c\u00e2t timp va fi necesar pentru a le finaliza. Un backlog de produs adecvat ar trebui s\u0103 constea din:<\/p>\n<p>- Pove\u0219tile utilizatorului - descriu ac\u021biunile pe care le pot \u00eentreprinde utilizatorii la fiecare etap\u0103 a utiliz\u0103rii produsului<\/p>\n<p>- Criterii de acceptare - lista elementelor necesare pentru ca o poveste s\u0103 fie finalizat\u0103<\/p>\n<p>- Puncte de poveste - estimarea volumului de munc\u0103, a riscurilor \u0219i a complexit\u0103\u021bii \u00een valoare relativ\u0103 \u00een puncte<\/p>\n<p>- Sarcini pentru pove\u0219tile utilizatorilor - lista\u021bi sarcinile care trebuie \u00eendeplinite pentru a realiza o poveste a utilizatorului<\/p>\n<p>Este esen\u021bial s\u0103 implica\u021bi echipa de dezvoltare \u00een crearea \u0219i prioritizarea portofoliului de produse pentru a asigura evalu\u0103ri exacte \u0219i realiste.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-prioritizing-features\">Prioritizarea caracteristicilor<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-sort-features-by-priority\">Sortare caracteristici dup\u0103 prioritate<\/h4>\n<p class=\"has-text-align-start\">Av\u00e2nd lista de caracteristici gata, acorda\u021bi prioritate fiec\u0103reia dintre ele. Pute\u021bi utiliza metoda de analiz\u0103 MoSCoW pentru a le clasifica dup\u0103 cum urmeaz\u0103:<\/p>\n<p>- Trebuie s\u0103 aib\u0103<\/p>\n<p>- Ar fi trebuit<\/p>\n<p>- Ar fi putut<\/p>\n<p>- Nu va avea<\/p>\n<p class=\"has-text-align-start\">\u00cen dezvoltarea unui proiect, concentra\u021bi-v\u0103 pe lucrurile pe care trebuie s\u0103 le livra\u021bi \u00een primul r\u00e2nd. Construirea unui MVP v\u0103 ofer\u0103 posibilitatea de a testa ipoteze cu privire la ideea dvs. \u00eenainte de a finaliza \u00eentregul proiect, de a o prezenta p\u0103r\u021bilor interesate sau utilizatorilor beta \u0219i de a colecta feedback important pentru dezvoltarea ulterioar\u0103 a restului de caracteristici.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-importance-of-assigning-priority\">Importan\u021ba atribuirii priorit\u0103\u021bii<\/h4>\n<p class=\"has-text-align-start\">Atribuirea priorit\u0103\u021bilor v\u0103 poate ajuta \u0219i la estimarea proiectului. Pe m\u0103sur\u0103 ce v\u0103 concentra\u021bi pe caracteristicile principale \u0219i pe cele pe care trebuie s\u0103 le realiza\u021bi mai \u00eent\u00e2i, pute\u021bi face ipoteze mai precise cu privire la estimarea finaliz\u0103rii lor. Pentru caracteristicile \"care ar putea fi\", pute\u021bi \u00eencepe cu o estimare aproximativ\u0103, deoarece acestea se afl\u0103 mai departe \u00een procesul de dezvoltare \u0219i multe lucruri se pot schimba p\u00e2n\u0103 c\u00e2nd echipa dvs. ajunge la ele (\u0219i dac\u0103 echipa dvs. ajunge la ele, deoarece, dup\u0103 colectarea feedback-ului cu privire la MVP-ul dvs., pute\u021bi schimba \u0219i nu pute\u021bi include toate func\u021bionalit\u0103\u021bile planificate ini\u021bial).<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-comprehensive-estimation\">Estimare cuprinz\u0103toare<\/h4>\n<p class=\"has-text-align-start\">Cu toate acestea, este important s\u0103 estima\u021bi toate caracteristicile, indiferent de prioritatea lor (cu excep\u021bia celor \"nu vor avea\", desigur), deoarece dori\u021bi s\u0103 ob\u021bine\u021bi o imagine de ansamblu a \u00eentregului proiect dintr-o dat\u0103. Iar pe m\u0103sur\u0103 ce ajunge\u021bi \u00een etapele urm\u0103toare ale proiectului, pute\u021bi reevalua domeniul de aplicare al lucr\u0103rii, pentru a v\u0103 asigura c\u0103 estim\u0103rile dvs. r\u0103m\u00e2n exacte.<\/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\">Tehnici de estimare<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-story-point-estimation-process\">Procesul de estimare a punctului de poveste<\/h4>\n<p>Acum c\u0103 a\u021bi finalizat portofoliul de produse, este timpul s\u0103 estima\u021bi fiecare dintre elementele sale. Pentru a face acest lucru, folosim puncte de poveste. Acestea sunt unit\u0103\u021bi pe care echipele Agile le folosesc pentru a evalua munca necesar\u0103 pentru a finaliza fiecare element din backlog. Story points ajut\u0103 la atribuirea unei valori relative elementelor din product backlog. Ele nu sunt legate de timp \u0219i pot purta valori diferite pentru echipe diferite, deci nu poart\u0103 valoarea emo\u021bional\u0103. Astfel, sunt \u0219anse ca membrii echipei s\u0103 nu umfle estim\u0103rile doar pentru a fi siguri. Pokerul de planificare ajut\u0103 echipele de software s\u0103 planifice fluxurile de lucru \u0219i s\u0103 \u00eembun\u0103t\u0103\u021beasc\u0103 ratele de livrare a proiectelor.<\/p>\n<p>Folosind punctele de poveste, o echip\u0103 poate estima:<\/p>\n<ul class=\"wp-block-list\">\n<li>\nCantitatea de munc\u0103 de f\u0103cut\n<\/li>\n<li>\nRiscuri \u0219i incertitudine\n<\/li>\n<li>\nComplexitate\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\">Utilizarea planific\u0103rii Poker pentru estimare<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-negotiate-estimates-with-planning-poker\">Negocierea estim\u0103rilor cu Planning Poker<\/h4>\n<p>Sesiunea de planificare este una dintre tehnicile de estimare la nivel brut, folosind o versiune modificat\u0103 a secven\u021bei Fibonacci: 1, 2, 3, 5, 8, 13, 20, 40, 100. Pentru a estima elementele din portofoliul de produse, membrii echipei primesc acelea\u0219i seturi de c\u0103r\u021bi de poker de planificare cu numere pe ele. Apoi, dup\u0103 o scurt\u0103 prezentare a elementului din portofoliul produsului de c\u0103tre proprietarul produsului (care nu voteaz\u0103) \u0219i dup\u0103 discu\u021bii, ei aleg \u00een mod privat cartea cu num\u0103rul de puncte de poveste pe care \u00eel consider\u0103 relevant pentru volumul de munc\u0103 necesar pentru finalizarea acestui element \u0219i le dezv\u0103luie \u00een acela\u0219i timp.<\/p>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-consensus-based-estimation-technique\">Tehnica de estimare bazat\u0103 pe consens<\/h4>\n<p>Dac\u0103 cifrele difer\u0103, membrii echipei discut\u0103 de ce au ales o astfel de cantitate de puncte de poveste \u0219i apoi voteaz\u0103 din nou. Aceasta face parte din procesul de poker de planificare, o metod\u0103 de estimare bazat\u0103 pe consens utilizat\u0103 \u00een Agile pentru a estima efortul pentru pove\u0219tile utilizatorilor. Ei procedeaz\u0103 astfel p\u00e2n\u0103 ajung la un consens \u0219i apoi trec la urm\u0103torul element din portofoliul de produse. Iar dac\u0103 num\u0103rul convenit este mare, s\u0103 spunem 20, 40 sau mai mare, \u00eenseamn\u0103 c\u0103 o poveste poate necesita prea mult\u0103 munc\u0103 pentru un singur sprint \u0219i poate fi nevoie s\u0103 fie \u00eemp\u0103r\u021bit\u0103 \u00een sarcini mai mici. \u00cen mod ideal, prezentarea articolului, discu\u021bia \u0219i votarea ar trebui s\u0103 dureze aproximativ dou\u0103 minute, ceea ce permite estimarea \u00eentregului backlog \u00eentr-un timp scurt. Dar, av\u00e2nd \u00een vedere c\u0103 scopul aici este de a estima \u00eentregul portofoliu dintr-o dat\u0103, nu v\u0103 gr\u0103bi\u021bi \u0219i nu v\u0103 face\u021bi griji atunci c\u00e2nd unele pove\u0219ti necesit\u0103 un pic mai mult timp pentru evaluare.<\/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\">Evaluarea vitezei echipei<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-assess-team-velocity\">Evaluarea vitezei echipei<\/h4>\n<p>Viteza echipei v\u0103 arat\u0103 care este ritmul de dezvoltare a proiectului. Aceasta ajut\u0103 la \u00een\u021belegerea a dou\u0103 lucruri:<\/p>\n<p>- Cantitatea de munc\u0103 pe care echipa dvs. o poate face \u00eentr-un sprint<\/p>\n<p>- Care este data preconizat\u0103 de finalizare a \u00eentregului domeniu de aplicare, presupun\u00e2nd c\u0103 acesta este fixat<\/p>\n<p>Viteza este diferit\u0103 pentru fiecare echip\u0103. O pute\u021bi evalua dup\u0103 itera\u021biile ini\u021biale, atunci c\u00e2nd echipa dvs. a lucrat deja la unele caracteristici. De exemplu, dac\u0103 a\u021bi inclus patru elemente ale portofoliului de produse \u00een prima itera\u021bie pentru un num\u0103r total de 20 de puncte de poveste, iar echipa a finalizat trei dintre acestea, echivalentul a 15 puncte de poveste, aceasta este viteza actual\u0103 a echipei dumneavoastr\u0103. Aminti\u021bi-v\u0103 c\u0103 doar elementele finalizate conteaz\u0103. Chiar dac\u0103 au reu\u0219it s\u0103 \u00eenceap\u0103 al patrulea element, dar nu l-au terminat, acesta nu conteaz\u0103.<\/p>\n<p>Scrum Master joac\u0103 un rol crucial \u00een facilitarea procesului de estimare \u0219i \u00een asigurarea unor evalu\u0103ri exacte \u00een timpul acestor sesiuni.<\/p>\n<h3 class=\"wp-block-heading has-text-align-left\" id=\"h-scheduling-and-budgeting\">Programarea \u0219i elaborarea bugetului<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-how-to-schedule-a-particular-project-on-story-points\">Cum s\u0103 programa\u021bi un anumit proiect pe Story Points<\/h4>\n<p class=\"has-text-align-start\">Dup\u0103 negocierea punctelor de poveste \u0219i evaluarea vitezei echipei, sunte\u021bi \u00een m\u0103sur\u0103 s\u0103 determina\u021bi calendarul proiectului. Pentru a face acest lucru, aduna\u021bi viteza echipei din ultimele trei itera\u021bii \u0219i \u00eemp\u0103r\u021bi\u021bi-o la trei. De exemplu, dac\u0103 viteza din aceste itera\u021bii a fost de 20, 23 \u0219i 17, viteza medie ar fi egal\u0103 cu aproximativ 20 de puncte. Dac\u0103 volumul total de munc\u0103 a fost estimat la 100 de puncte de poveste, atunci, cu o vitez\u0103 medie de 20 de puncte, ar fi nevoie de 5 itera\u021bii pentru a finaliza proiectul. Presupun\u00e2nd c\u0103 o itera\u021bie dureaz\u0103 dou\u0103 s\u0103pt\u0103m\u00e2ni, ar trebui s\u0103 livra\u021bi proiectul \u00een 10 s\u0103pt\u0103m\u00e2ni.<\/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\">Stabilirea bugetului<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-project-cost-estimation-formula\">Formula de estimare a costurilor proiectului<\/h4>\n<p class=\"has-text-align-start\">Pentru a determina bugetul proiectului dumneavoastr\u0103, pute\u021bi utiliza aceast\u0103 formul\u0103 de baz\u0103: (total Story Points \/ Velocity * ore de echip\u0103 pe sprint) + costuri non-munc\u0103 = buget estimat. Av\u00e2nd un num\u0103r total de puncte de poveste \u00eemp\u0103r\u021bit la viteza medie, \u00eenmul\u021bi\u021bi num\u0103rul de sprinturi cu 40 de ore pe s\u0103pt\u0103m\u00e2n\u0103 per membru al echipei pentru a ob\u021bine costul for\u021bei de munc\u0103. Ad\u0103uga\u021bi apoi costurile non-munc\u0103, cum ar fi costurile de capital, costurile echipamentelor, costurile de \u00eentre\u021binere, costurile de formare etc. De exemplu, avem un proiect estimat la 100 de story points, iar viteza medie a echipei noastre este de 20. Atribuind proiectului o echip\u0103 de 5 persoane cu rate orare de $50, orele echipei pe sprint valoreaz\u0103 $20 000 \u0219i $100 000 pentru 5 sprinturi. Cu un cost ipotetic non-munc\u0103 de $50.000, bugetul estimat pentru proiectul nostru ar fi de $150.000. Av\u00e2nd \u00een vedere intervalele de \u00eencredere privind nivelurile exemplare de 80-120%, intervalul raportat al bugetului nostru este acum cuprins \u00eentre $120.000 \u0219i $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\">Reestimare pentru acurate\u021be<\/h3>\n<h4 class=\"wp-block-heading has-text-align-left\" id=\"h-re-estimate-your-project-to-get-a-more-accurate-cost-estimate\">Re-evalua\u021bi-v\u0103 proiectul pentru a ob\u021bine o estimare mai precis\u0103 a costurilor<\/h4>\n<p class=\"has-text-align-start\">Aminti\u021bi-v\u0103 c\u0103 nicio estimare nu este 100% exact\u0103. Cel mai bine este s\u0103 v\u0103 reestima\u021bi proiectul la fiecare c\u00e2teva itera\u021bii, deoarece anumite aspecte, cum ar fi disponibilitatea resurselor, viteza echipei sau domeniul de aplicare al proiectului, se pot schimba \u00een timp. Reevalu\u00e2nd, v\u0103 asigura\u021bi c\u0103 estimarea dvs. este la zi. Utilizarea unui software de urm\u0103rire a timpului \u0219i de planificare a resurselor v\u0103 va ajuta, de asemenea, s\u0103 gestiona\u021bi disponibilitatea echipei \u0219i s\u0103 o realoca\u021bi dac\u0103 este necesar. Cu ajutorul tehnicilor \u0219i instrumentelor potrivite, v\u0103 pute\u021bi face estim\u0103rile mai fiabile \u0219i v\u0103 pute\u021bi planifica mai bine urm\u0103torul proiect.<\/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\">Concluzie<\/h3>\n<p class=\"has-text-align-start\">Estimarea precis\u0103 a proiectului este esen\u021bial\u0103 pentru gestionarea cu succes a proiectului. Prin \u00een\u021belegerea a\u0219tept\u0103rilor \u0219i a obiectivelor, crearea unui portofoliu de produse detaliat, prioritizarea caracteristicilor \u0219i utilizarea unor tehnici precum story points \u0219i Planning Poker, v\u0103 pute\u021bi \u00eembun\u0103t\u0103\u021bi acurate\u021bea estim\u0103rilor. Reestimarea periodic\u0103 \u0219i utilizarea instrumentelor de urm\u0103rire a timpului \u0219i de gestionare a resurselor sporesc \u0219i mai mult fiabilitatea termenelor \u0219i a bugetelor proiectelor dumneavoastr\u0103. Urm\u00e2nd aceste practici, pute\u021bi dep\u0103\u0219i provoc\u0103rile legate de estim\u0103rile imprecise \u0219i pute\u021bi asigura rezultate mai bune ale proiectului.<\/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> Utiliza\u021bi cu u\u0219urin\u021b\u0103 tehnica de estimare Planning Poker<\/p>\n<p><strong>Verifica\u021bi motivul pentru care software-ul nostru de gestionare a resurselor este ales de managerii de proiect de la Hill-Knowlton sau Stormind Games<\/strong> <\/p>\n\n\t\t<\/div>\n\t<\/div>\n<a class=\"redl-btn   vc_custom_1596025898618 redl-btn-medium redl-btn-69e8c71368101 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\">Ob\u021bine\u021bi o \u00eencercare GRATUIT\u0102 de 14 zile<\/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":"The Challenge of Inaccurate Estimates Inaccurate estimates are among the most popular project management challenges. When starting a new IT project, you want to know two things: how long it is going to take and how much...","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\/ro\/managementul-proiectelor\/cum-sa-estimati-proiectele\/\" \/>\n<meta property=\"og:locale\" content=\"ro_RO\" \/>\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\/ro\/managementul-proiectelor\/cum-sa-estimati-proiectele\/\" \/>\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\":\"ro-RO\",\"potentialAction\":[{\"@type\":\"ReadAction\",\"target\":[\"https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/\"]}]},{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@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\":\"ro-RO\"},{\"@type\":\"Person\",\"@id\":\"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e\",\"name\":\"Pawe\u0142 Ha\u0142abuda\",\"image\":{\"@type\":\"ImageObject\",\"inLanguage\":\"ro-RO\",\"@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\/ro\/managementul-proiectelor\/cum-sa-estimati-proiectele\/","og_locale":"ro_RO","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\/ro\/managementul-proiectelor\/cum-sa-estimati-proiectele\/","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":"ro-RO","potentialAction":[{"@type":"ReadAction","target":["https:\/\/teamdeck.io\/project-management\/how-to-estimate-projects\/"]}]},{"@type":"ImageObject","inLanguage":"ro-RO","@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":"ro-RO"},{"@type":"Person","@id":"https:\/\/teamdeck.io\/#\/schema\/person\/1073b38fa48e5b06f16eba3840da6f5e","name":"Pawe\u0142 Ha\u0142abuda","image":{"@type":"ImageObject","inLanguage":"ro-RO","@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\/ro\/wp-json\/wp\/v2\/posts\/2825","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/users\/3"}],"replies":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/comments?post=2825"}],"version-history":[{"count":33,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/posts\/2825\/revisions"}],"predecessor-version":[{"id":13658,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/posts\/2825\/revisions\/13658"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/media\/8515"}],"wp:attachment":[{"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/media?parent=2825"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/categories?post=2825"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/teamdeck.io\/ro\/wp-json\/wp\/v2\/tags?post=2825"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}