I've come across an "unadvertised feature" in the PM Gantt to compare the original time estimation, say, of a new feature and the actual time spent to implement the feature. We use this to do a bit of postmortem analysis as what's the root causes of the delay on a feature just completed.
Here is what we did: 1. We created a master ticket for a feature and recorded our original estimation in the ticket. 2. As the development was underway, more tickets were created and worked on by developers and they logged down the time they spent on their tickets. 3. In the PM Gantt, we select the "assess task risk" function. This table shows the master ticket's original estimation and the sum of "hours worked" on all sub-tickets. Immediately, we see the estimated-actual difference. 4. We also looked at tickets having bug-fixing subtype in the table. If there are too many and/or they took too much time, then it may be an indication that people were not paying enough attention to quality (do it right the first time). Corrective actions may be in order.
