RELATED IDEAS
Estimate in points, but log work in time
My agile development team uses story points for estimation. Once work is in progress, I want my developers to log work in time. This helps me understand where their time is going, and to inform future estimates for planning.
| Release time frame | 6 months |
-
-
-
-
-
-
-
-
-
-
-
-
-
-
- +3
3
MERGED
Log work in time while estimating in points
Story points are predictive. We want to reflect on those predictions to compare them against real data. Our goal is to provide metrics like "on average, it takes us X time to complete 8 story points." To support this goal, we want to estimate in s...
1
Unlikely to implement
© 2025 Aha! Labs Inc.•All rights reserved
Executives need to see things reflected in money for estimates and for investment decisions. Time is a proxy for money. Executives do not understand story points. Being able to translate story points/velocity to time spent allows you to get a proxy for cost to implement a feature/story. It is critical to be able to track time in terms of time and estimate in terms of points. Logging time worked in terms of points (e.g. "I worked 3p today") doesn't make logical sense.
Additionally, we use hours for capitalization of development costs. The budgets are driven by hours worked, not be story points.