I'm with Jay on this one. Fibonnaci numbers work well for sorting out the relative effort of a story - you don't have an argument about whether it is a 5 or a 6, instead it's a question of "is it a 5 or an 8?".
One way to start is to select a user story that the team is fairly confident about how much effort is involved. Estimate this using fibonnaci and call it a 3 or a 5, for instance, then you can proceed with estimating other stories using that issue as an indication.
We use the somewhat typical X-small, Small, Medium, Large, X-Large, ??? approach during the estimation game. Then I translate that to 2,4,8,16,32. 32 is too big for us to get into a sprint, we do 1 week sprints, so we break it down. 16 we usually break down as well. Anything over 32 is an epic and needs to be broken down.
Hey Atlassian Community! Today we are launching a bunch of customer stories about the amazing work teams, like Dropbox and Twilio, are doing with Jira. You can check out the stories here. The thi...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG