Can you recommend an appropriate method for sizing our cards and why?

Waffle supports estimating cards using story point sizing. Waffle supports sizing using Fibonacci-like numbers 1-100 based off of the commonly-used "Planning Poker" method.

Story points are used as a comparison of complexity/effort/doubt between cards --they do not equal hours. If a card has 3 points, it should be three times as difficult as a 1 point card.

If you run into a card that is sized larger (ex. 13) than your team’s normal size (ex. 3), it generally means one of two things:

A) The card is not well enough defined

B) The card should be broken down further into multiple cards

Getting started with story estimation

Pick a few “common” cards and assign them 3 points. As you estimate cards, compare them to the 3 point cards.  Are they more or less complex?  If they’re less complex, they’re probably a 1 or 2 point card.  If they’re more complex, they’re probably a 5, 8, etc. point card.  Don’t worry too much about accuracy when getting started.  Just spend a minute or two sizing each card and keep going.  In fact, a quick way to size is to read a card, size it, and then have additional discussion if all team members didn’t pick a similar size.

After a few weeks of estimating using story point sizing, you can use Waffle’s Throughput Graph to determine how many points you finish each week, and can use this information in the future to determine how many points to plan in coming weeks. This is often called your historical velocity, which determines your future capacity. If you keep your team together over time this velocity number stabilizes. If your velocity has been about 15 in the past, you can predict that if the team stays the same, you will get 15 done each iteration moving forward.  Also if you often have interrupt work, you might not want to plant to 100% of your capacity, leaving some room for unplanned work.  

Some teams choose to not estimate cards using story point sizing, rather trying to make each card a similar amount of complexity.  Teams that use this approach count the number of cards they complete each week as their historical velocity.  Waffle’s Throughput Graph also supports reporting by card count instead of point size.

Estimating cards also helps track progress towards a milestone.  Waffle’s Milestone Burndown Graph provides the ability to see how many points have been completed and are still remaining, and also shows an ideally trend line of progress to complete the milestone by the desired date.

Below is a segment from CA Technologies' guide to sizing and estimating user stories (if you're having trouble or want to learn more, we highly suggest checking this out).

Links to related articles:

Did this answer your question?