I would like to share an excellent write-up by the JIRA Agile Product Manager from Atlassian Shawn Clowes . This was written a while ago, but the depth and detail present in this reply from Shawn for one of the questions in the Answers site still amazes us. This was his explanation about time estimates and story points in the agile context. Here it goes: I'd like to provide a full explanation of why we we've offered 'Original Time Estimate' as an 'Estimate' value and not 'Remaining Estimate'. Some of my discussion refers to agile concepts that anyone reading probably knows well but I've included it because the context is important. Note that the discussion refers to the best practices we've implemented as the main path in GreenHopper, you can choose not to use this approach if you feel it's really not suitable. Estimation is separate from Tracking In Scrum there is a distinction between estimation and tracking. Estimation is typically perform...