How about custom point values

This is not quite the same, and I know it's a complicated ask, but I would love to be able to adjust the point scale for an existing project. Our project currently uses 0-2 points, but we've come to the conclusion that we need a broader range than that. I'd be happy if we could change to the Fibonacci or exponential scale. This could be a simple mapping from the current to the new point system (0 = 1, 1 = 3, 2 = 8).

Just to make sure everyone knows, Tracker gives you the option of choosing from one of three different scales for your project:

Linear (1/2/3)
Powers of 2 (1/2/4/8)
Fibonacci (1/2/3/5/8)

As Dan says, we're also working on totally custom point scales.

The choices are cool, but be careful. At some point at the beginning (starting the first story?) your choice of point scales is locked forevermore.

I appreciate that tracker prescribes much of the process, eliminating choices that are meaningless or problematic... so I don't feel that more point choices will make us any more productive or our estimates any better...

A couple points, though:
- zero pt stories are allowed. I wrote a separate report requesting the ability not turn this off.
- It _would_ be useful support larger pt values (13/20/40 etc.) for "epics". We've had to find out some way around this. We've used a couple techniques (unsuccessfully):
(a) don't estimate these stories until we can break them up
(b) our highest pt value is "illegal" and denotes a story that needs to be re-estimated. These are both "hacks" around the tool

It would be nice to do this the right way.

In fact, we'd probably like to be able to have two levels of estimation. Yup, I know, but bear with me.

Before we get into nitty gritty detail on stories we t-shirt size everything (S,M,L,XL), and then assign broad costs to those t-shirt sizes.

An iteration or two before we start a story we'll detail cost it (drill into more functional and then ultimately technical detail).

It's useful having the t-shirt cost because that costing is done en-masse as a relative complexity costing, and so that provides the team with a means of re-adjusting overall project estimates as stories are accepted.

The detail costing exercise is really just a means of getting the team talking about detail in a group so everyone knows what's coming, though those in charge of planning like to think that the detail cost is more accurate that the t-shirt (it sometimes is), and therefore have both available.

Why does the fibonacci scale end at 8 btw? Is it a big issue to pin up a couple of more? Up to 21 for example, or is it not adviced within Agile Development?

Just to harp in on ideas here:

- I'd love to see 'longer' scales for values too. The 4 option sets are rather limiting

- I'd love to see multiple estimation levels too. With my situation in Product Management, we use the points to manage estimation for dev-time, and are jamming the 'product improvement/importance' into the comments. For example, there are some things that we want to do that take 4points of dev time, but only improve the product by 1 point; and vice versa. It would be nice to be able to track both - letting the dev team and management teams better prioritize the build cycles.

How do we set points via a text box, not a pre-defined drop-down scale?

If this doesn't exist yet, can you add this as a feature request?