Source: thenewstack.io
Deep Work: A Better Way to Measure Developer Velocity
Estimating developer work is more art than science. Devs typically use story points or hours for their estimations, or sometimes they’ll use a “https://www.atlassian.com/blog/platform/a-brief-overview-of-planning-poker” exercise to determine what they can accomplish in a given sprint.
One may estimate three story points for a task while the other estimates five.
Even when estimated with hours or planning poker, the velocity estimates remain subjective.
When using story points to measure velocity, you are predicting how future sprints will look based on previous trends.
One may estimate three story points for a task while the other estimates five.
Even when estimated with hours or planning poker, the velocity estimates remain subjective.
When using story points to measure velocity, you are predicting how future sprints will look based on previous trends.
Related Articles
Community Partners
DevOps Careers