Loading Profile...
Twitter,
Facebook, or email.
I’m
thankful
How about custom point values
I'd love to be able to set different scales based on the project type. So one project might have 1-10 scale, while another would have 0-2. This would allow me to make Tracker best fit my existing processes.
Official
Response
EMPLOYEE
Promoted
Responses
-
I’m
sad
3Dear Pivotal, could we have an update on this!
This is a blocker for us. We could live without completely custom values, but to not offer values compatible with our Planning Poker decks (0, .5, 1, 2, 3, 5, 8, 13, 20, 40, 100) will make the move to Pivotal impossible. And that makes me sad, I so do want to move to Pivotal. -
3Just 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. -
7I 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. -
EMPLOYEE
3We have this feature in the Tracker backlog. Look for it early next year!
| next » « previous |
-
I’m
frustrated
Could we initially just have the fibonacci series? No need for the complex stuff yet that is delaying this. The point visual is totally unnecessary and can be replaced with a simple number. I think you will gain many more clients if you do that.
We are still currently evaluating this.Comment -
-
1lol .. custom point scales are a good idea I'm sure ... but if you just added a couple of new options you would answer 90% of the complaints I'm sure (or even just extended the existing scales) -
-
I’m
a dissapointed
We are just usings pivotaltracker within our project. Because the project has just started, we have a lot of backlog items with points > 8
It would be very helpful if de fibonacci scale would be extended (13, 20, 40, 100), just like our cards.
This would make our life a lot easier. -
-
I’m
frustrated
Adding 0.25 and 0.5 to the fibonacci scale would be great!
-
-
I’m
confused
This arbitrary cap on 8 points is definitely a showstopper for me as well, it creates so much unnecessary overhead. And the full Fibonacci series should be much simpler to implement than most other planned stories, such as integration with bug trackers.
-
-
I’m
frustrated
I was hoping to use the point scale as the estimated days to complete each animated shot on a tv show production. however without having a custom field to enter (or for my cases, 0-10 points) would be enough. but maxing out at 4 won't work for our situation unfortunately, unless you start having to do math in your head as you read the values which i would like to avoid if it all possible.
Please bring us more point options! -
-
1We have used following point scale before:
0.5, 1, 2, 3, 5, 8, 13, 20, 40
(our poker planning cards contains this scale)
The problem is now especially the missing of 0.5 and 13 point estimates. It is not possible to change our scale on existing projects.
This reply was created from a merged topic originally titled
Fibonacci point scale should contain 0.5 and 13 point estimates. -
-
I like this idea. I was about to ask for it; however, I'd like to see an additional option. Include additional option that allows the user to enter an "other" value. For example, 1,2,3,4,5,6,7,8,other. If other selected allow the user to enter a number, e.g., 22. I know this is not the agile way. This capability would be nice as we use PT for tracking projects that aren't development in nature. We use it to track other business projects where actual hours would be nice to track. Getting these folks to understand story points is nearly impossible.
-
-
I’m
unhappy
1I have a problem with applying the story points sequence (fibonacci) - it happens very often that beside the implemented sequence 0,1,2,3,5,8 also 13 & 20 occure. Is it possible to add this two numbers? This would be very helpful!
This reply was created from a merged topic originally titled
Implemented part of Fibonacci - Sequence is hard to use!. -
-
Can i change the story points options? we use 1,2,3,5 and 8 to estimate effort. Looks like currently you use only 1, 2, 3.
This reply was created from a merged topic originally titled
change/add story points value?. -
-
I’m
frustrated
i like the idea of them being custom. my main need, however, is having support for epic range (8, 13, 20, 40, 100...)
-
-
I’m
happy
Just checked out Pivotal Tracker. I'm really surprized you limit story point estimates to 1,2 or 3. This really isn't sufficient for points estimating. We use Fibbonacci numbers, usually from 2-13. Anything bigger is probably too big.
This reply was created from a merged topic originally titled
Need More Than 3 Story Points. -
-
I’m
frustrated
Our team won't use the software before custom point ranges are supported. We simply cant match out already created stories down in PivotalTracker.
-
-
I’m
sad
3Dear Pivotal, could we have an update on this!
This is a blocker for us. We could live without completely custom values, but to not offer values compatible with our Planning Poker decks (0, .5, 1, 2, 3, 5, 8, 13, 20, 40, 100) will make the move to Pivotal impossible. And that makes me sad, I so do want to move to Pivotal.-
Completely agree. We HAVE TO HAVE the epic range (13, 20, 40, 100) to use this tool. A 100 might need to be broken up, but it still needs to be trackable until it is and we have had 13 and 20 point stories in iterations. Sure we try to avoid it, but it happens and if the tool can't take the value then it can't get our velocity right.
-
-
-
-
-
I’m
frustrated
I completely agree with this. It's been three years since this ticket was filed. We're PT premium customers, but are finding that the absence of custom points a huge pain. We aren't able to adapt it to our pricing model, and might have to move away from PT if this isn't resolved.
Can somebody at PT give me a rough indication of when we can get custom points ranges? -
-
I’m
frustrated
1I agree again... and again. I don't know about other people, but I find I need these extra points to denote epics in the product backlog 'iceberg'. It's perfectly normal to start with a huge story and break it into smaller stories over time, as you move closer to starting development on it.
I'm just reiterating what everyone else has already said to see if more comments = more action. -
-
1The biggest weakness of Pivotal is the point system. You can't on one hand have the very limited options you have, then on the other leave the value of a point vaguely defined as "a relative, team-specific measure of effort to complete a feature story. It can be based on something concrete, like ideal engineering days, but over time it becomes an intuitive, relative metric" (from the FAQ). That's BS. The limited options in fact prescribe a very specific value to points, yet you don't come out and say what that value is.
The point system my team uses, which has been refined over a couple years, is an exponential scale where 4 points = ~ 1 day of work. Therefore 1 pt is equal to something how to make the point system actually fit a real-world development process. -
-
I’m
frustrated
We're trialling Pivotal right now and would like to move over completely, but the restrictions on points is the one thing that gets in the way. There's no way we can abandon all our previous estimates/velocity values to fit with Pivotal and we need to be able to give a rough (large) estimate on epics.
I want to ask Pivotal when this is happening, but it seems even if I did get an answer I would have a hard time accepting it as for three years people have been waiting for this without much joy. -
-
I’m
frustrated
Can we get an update on whether an extended scale is still on the radar? The release burndown graph is unusable until we can have 13 and 20 in our backlog
-
-
I’m
sad
When will have the ability to have stories larger than 8 points. We like to keep the whole backlog optomised with stories in the distant future often being less will defined and larger. As stories get closer to the current sprint they are refined and broken down if possible to make them 8 points or less. Though with our team of 9 we would really like to be able to have 13 point stories in the sprint
This reply was created from a merged topic originally titled
We need stories larger than 8 points. -
-
I’m
disappointed
This is critical if you'd like to be considered for 99designs (0.5, 1, 2, 3, 5, 8, 13, 20, 40, 100). We use Mountain Goat Software card decks. It's fine to be opinionated but please not on this. Your solution looks great by the way. My monthly Jira hosted subscription is up for grabs... ?
-
-
I’m
frustrated
I want to add to this.. This seems to be such a small enhancement:
just add a bunch of value to the Fibonacci scale: 1, 2, 3, 5, 8, 13, 20, 40, 100
If you do this, there is no retroactive calculation, mapping or anything, customers will readjust there stories if they need to manually. I don't see the big deal here.
I can understand that having a totally customizable point scale can be tougher than it looks but adding 4 values to the Suite seems a total no brainer.. And looking at the length of this thread you guys should set the priority pretty high for this right?
I see a lot of people saying it's a blocker, they can't fully migrate, etc.. that would help you get more customers!! -
-
-
YEaaahhhh!!!!!!
-
-
-
-
-
I’m
undecided
That's nice and all, but the request included fractional points. Our planning poker cards include the 1/2 point, which with our interpretation of the value of a point is extremely useful to have. It would be a little overkill to try to double all our estimates in order to obviate the need for a half point.-
Hi Victor,
Fractional point values will require an API version change (floating point vs. integer), but we do plan to add 0.5 as a supported point value soon. Look for it as part of the APV V4 release. -
-
-
-
-
I’m
excited
Thank you guys! We really love the update. -
-
I’m
excited
Thanks gang, this was tops o' the list for us. The planning poker decks are out and about. -
-
I’m
happy
1I'd love to see a story point sequence like Mike Cohn proposes. ?, 1/2, 1, 2, 3, 5, 8, 13, 20, 40, 100, infinity.
This reply was created from a merged topic originally titled
Another story point sequence?. -
| next » « previous |
