Tip #3: Choose a meaningful story points scale for estimating user stories.
The MSF Agile 5.0 template uses story points as the estimation unit for items on the product backlog (User Stories). The field itself is a double and supports different number formats, however teams that use story points successfully agree upfront on a scale that they apply across all stories on their backlog.
Before choosing a scale for your team, it’s important to be comfortable with what story points are. Story points are simply an abstract unit of size (or complexity) assigned to each story on your backlog. They’re not hours, days, weeks, or any other scale that has an absolute measurement. They’re simply “points”. I recommend walking through Mike Cohn’s presentation on Agile Estimating and Planning that goes into specifics on story points and how to use them. They three key advantages he lays out in his presentation are:
In short, story points provide a relative size for each story on your product backlog that can be used to plan iterations and determine the team’s velocity (amount of work planned or completed in an iteration).
The Fibonacci sequence (1, 2, 3, 5, 8, 13, etc) seems to be the most popular scale being used by Agile teams. It’s well known, non-linear, and provides nicely sized “buckets” that people are comfortable using. Whatever scale your team chooses, be sure that everyone on the team understands it and is committed to using it – you’ll find success with story points easier to come by when your agree on the scale up front.
At SSW we use t-shirt sizes as a way to stop the develoeprs thinking of the number as hours.
I've used t-shirt sizes as well and agree that they REALLY help avoiding the hours conversation. The downside IMHO is that you can't add them together to determine total size. How do you determine velocity with t-shirt sizes?
Small = 1
Medium = 2
Large = 3
XL = 5
XXL = 8
XXXL = 13