What not to estimate: defects, spikes and (in during sprint planning): stories.
Posted by jpluimers on 2019/06/06
A few nice reads on that not to estimate and why:
- Estimating software defects impede stable velocity. If possible the effects of software defects should be tracked, quantified, and represented separately.[WayBack] Don’t Estimate Software Defects -LeadingAgile
- Should you estimate a spike? Spikes are, like defects, generally harder to estimate correctly relative to user stories. It’s best to time-box them.[WayBack] Don’t Estimate a Spike -LeadingAgile
- If we estimate stories during sprint planning we run the risk of inflating your velocity and under estimating the size of your remaining backlog.[WayBack] Don’t Estimate Stories In Sprint Planning -LeadingAgile
Related:
Via:
–jeroen






Leave a comment