The three-point scale is the general way we assign points in Mashup Garage projects. It starts with the mantra of "3 points by default," where stories are most often given 3 points.
Always start with 3
points. Don't overthink it, it's called an "estimate" for a reason. Adjust if needed:
3
(Medium) points by default.2
(Small) points if they're a bit smaller.5
(Large) if they're bigger.On a typical day, you're expected to do one 3
-pointer, or two 2
-pointers. Possibly more on good days!
In very productive days, it may be common to do two or three 3-pointers. This is especially true if some items turn out to be easier than some.
There's also a 1
-pointer, which is the same as a 2-pointer that you're sure isn't going to need any feedback.
If it takes more than a day, it's a 5
-pointer.
There are also 8
-pointer items for those too big to estimate. These are typically items that need to be broken down into smaller items.
Points | Size | Duration |
---|---|---|
1 point | Extra Small | Too short to think about |
2 points | Small | 1 to 2 hours (half-day average) |
3 points | Medium | 3 to 6 hours (1 day average) |
5 points | Large | 2 days or more |
8 points | Extra Large | Too long to think about |
Same as a 2-pointer, but you're very confident that there won't be any revisions from your code-reviewers and your stakeholders. Try to avoid this, since the cost of doing one item (PR + review + CI + etc) has a fixed cost anyway—so only use 1 point if you're sure there won't be any back-and-forth.
Duration:
Examples:
Could be a 3, but feels a little too easy compared to other 3's.
Duration:
Examples:
The default. Use 3 points by default.
Duration:
Examples:
Features that would make you step back and think twice. These are typically things that would need a bit of architecture, or some deep refactoring.
Duration:
Examples:
Features too big that they need to be broken down into other stories.
Duration:
Examples: