We have bug databases for a reason, we should also have progress databases. Why rely on your gut instinct built from experience, when you can objectively say "i

We have bug databases for a reason, we should also have progress databases. Why rely on your gut instinct built from experience, when you can objectively say "it normally takes me one week to implement foo in terms of size and complexity"? It should be possible to look at your project and see at a glance how many components there are, how long each has taken, and how long it has taken to complete components of similar metrics. I'm surprised that I haven't seen much emphasis on this in Agile, considering the very emphasis on decomposing projects into more-easily estimated components (git plugins to offer nifty visualizations categorized by class, design, cyclical complexity, etc). There is probably a huge market if you can figure out a reliable, easy way of updating your estimates in a more communicable way than relying on remembered experience