Home › Hindi-English guides › Story points kaise estimate kare?

Story points kaise estimate kare?

Story points ghante nahi hote — ye relative size hai. Team har story ko doosri stories se compare karke number deti hai, aksar Fibonacci scale pe (1, 2, 3, 5, 8, 13). Points me effort, complexity aur uncertainty teeno aa jaate hain, aur inhi se velocity nikalti hai jo sprint planning ko realistic banati hai.

Ghante me estimate kyun fail hota hai

Insaan absolute estimate me kharab hai lekin comparison me theek hai. 'Ye login form se bada hai ya chhota?' ka jawab consistent aata hai; 'kitne ghante lagenge?' ka jawab hamesha optimistic aata hai. Points us uncertainty ko absorb kar lete hain — 5 ka matlab hai 'jitne baaki 5 the utna hi bada'.

Reference stories — consistency ka asli tarika

3 aisi stories chuno jo team ne already deliver ki hain aur sab ko yaad hain, aur unhe fix kar do: ye 1 hai, ye 3 hai, ye 8 hai. Ab har nayi story inhi se compare hogi. Naya banda 10 minute me calibrate ho jayega. Har quarter anchors dobara chuno, kyunki team tez hoti hai to purana 3 ab 1 lagne lagta hai.

Estimation session kaise chalayein

Story padho, sab log chup-chaap apna number socho, phir ek saath reveal karo (planning poker). Sirf outliers pe baat karo — jisne 2 bola aur jisne 8 bola, dono ko kuch alag pata hai. Ek baar dobara vote karo aur aage badho. 1 point ke liye 10 minute bahes karna us point se mehnga padta hai.

Points se date kaise batayein

Points ka ghanto me conversion mat karo. Velocity use karo: agar backlog me 40 points hain aur velocity 20 hai, to lagbhag 2 sprint. Flocci Projects me har issue pe optional story-point field hai, sprint scope karte waqt points live add hote hain, aur sprint complete hone pe velocity trend chart apne aap update ho jata hai — free plan pe.

Free board banao — card ki zaroorat nahi

Aksar puche jaane wale sawaal

1 story point kitne ghante ka hota hai?

Jaan-boojh kar koi fixed conversion nahi hai. Points team ke apne scale pe relative hote hain. Date chahiye to velocity se nikalo — 40 points backlog, velocity 20, matlab lagbhag 2 sprint.

Estimate kaun dega — manager ya team?

Jo log kaam kar rahe hain wahi. Bahar se thopa gaya estimate accuracy aur trust dono khatam kar deta hai. Manager ka kaam priority ka order decide karna hai, size nahi.

Bugs pe points lagane chahiye?

Team-to-team alag hai. Bugs pe points lagao to velocity sach batati hai ki capacity kahan ja rahi hai; na lagao to velocity sirf feature throughput dikhati hai. Ek convention chuno aur usi pe tike raho — beech me badla to purani velocity bekaar ho jaati hai.

Kya AI story points suggest kar sakta hai?

Flocci Projects ka AI backlog breakdown draft issues banata hai jinme type, priority aur story points pehle se bhare hote hain. Wo sirf starting point hai — team review karke correct karti hai, aur calibration ki asli baat-cheet team ke beech hi hoti hai.

Aur guides

English versions: agile answers · glossary.