Rank 1
http://screencast.com/t/MDQyYzI1
4 Answers, 1 is accepted
Thanks for the feedback. This feature has been requested a few times and is in our backlog with a fairly high priority. However, we are pretty busy with TFS sync, so I am not sure if this summation feature will make it into our Q3 release.
I like the implementation you suggest and we will consider it for when we add this feature.
Ryan
the Telerik team
Rank 1
glad to hear that you will implement such feature, I understand that it takes time to make good software :)
Rank 1
Question: Would that just break the current concept that there is NO semantic asociated with the Story estimate??
IMHO , each project should define it's own "metric" for Story estimation.
In my case, I use DAYS for stories , so in the example there should be a basic conversion / round to 1 day.
Or it can be defined as "best practice" that the estimated Story estimation must match with the tasks (still again for doing this you need to have semantic on the estimation property (are they hs / days , etc) )
We prefer to keep the Story estimate field flexible. Some teams like to estimate in hours, some in days, some in weeks and others use a more abstract point system. That being said, we have some plans to implement a system where the user can choose what units they wish to estimate stories in. For example, if the user picked 'Days' for a particular project then the word 'Days' would appear next to the estimate field of every story in that project.
As for what to do about it matching the Task's estimation units, we may need to have an additional estimation field on a story that is simply a summation of the Task estimates.
These ideas are not fully mature and are still in the discussion phases. But, would an implementation similar to this work for you? Do you have any other suggestions?
Ryan
the Telerik team