Estimations are a game we play. To understand how good you are, you need to figure out what's happening with the business and understand the impact you're havin

Estimations are a game we play. To understand how good you are, you need to figure out what's happening with the business and understand the impact you're having there. For a small company, this is probably the rate at which you ship features. Good developers ship enough that there's pressure to constantly explain the improvement to sales / marketing. For a larger company, this is probably a user metric. Are this things you're doing moving the needle on logins, time on site, repeat visits? You should understand what areas of the product are high value, and which are experimental. You should spend your time converting experimental features to high value features. Polish and edge cases. For a bigco, this is probably scaling metrics, like page load time and uptime. You should have clear targets you're working against and be able to prioritize against that target. Numbers are easy to show results against. Anybody can be fast against sprint points. You need to understand what the business goal is and play to your strengths against that goal.