I'm looking for a shared perspective on the following:
On a Scrum framework, where estimations are done using the Fibonacci sequence to measure complexity of each task/issue, how can we develop a sense of comparison between the complexity and the time it actually takes?
It is easy to face both tasks evaluated with a 3 (low complexity task) taking 2 months to fully complete as well as others graded with a 13 that somehow are managed in one or two sprints. Is there any way to establish a time-tracker / time comparison that helps a team to develop a better sense of commitment in the delivery and a better notion on how to estimate properly?
Also, I'm now learning more about Software Development metrics using Kanban and Scrum. Would you mind sharing your experiences?
I'm looking forward to reading from you. Saving Changes...
