0.5 is not part of Fibonacci numbers, never seen in any scrum tool ? about trelloscrum HOT 9 CLOSED

Really ? There is no 0.5 in my company card deck, and never seen this in scrum tools.

If you want to count hours or day, it can be usefull, I grant you that. But if you are counting story points, I do not see the value of having 0.5 whereas all other numbers are integers from the Fibonacci numbers. Anyway if you display Fibonacci numbers I believe you should not display 0.5. Nothing prevents some users to put 0.5 if they want to.

I just think it is "cleaner" not to display it.

Again it is just my opinion :)

from trelloscrum.

Although .5 doesn't follow the Fib seq .5 is present on all scrum estimation card decks and tools that scrum teams usually use to estimate story points.

from trelloscrum.

@koici , it's not only your opinion 😉

I wince every time I see it. I thought of sending a PR for a ½ instead, but the problem is more than visual. It seems to confuse points with hours. Points are arbitrary units. If you need a finer grain estimation than your 1 point, then just make your one point count for less.

Especially when the project says #35 is an edge case and wouldn't want to push that change on users, I argue this one should be reverted.

from trelloscrum.

Yes, the JIRA deck is the most wide spread example http://www.jiraplanningpoker.com/jira-planning-poker-extension-from-spartez-start-page.html as it plugs directly into the Atlasssian suite .

We use it mostly with the very senior engineer teams they routinely slice stories thinly and they tend to use it a lot.

from trelloscrum.

@kitglen, I agree with turadg, I would advise you to start counting at 1 instead of 0.5 and make adjustments in the way you translate that value into whatever system you use to produce stats with it.

Otherwise why not using 0.25 or 4 or any other number ?

My scrum experience is that tasks tend to be smaller when people get used to scrum and when the project becomes more mature. I believe it is good to re-evaluate your scoring policy at that time. Otherwise all tasks/stories tend to count for 1,2,3 or max 5 and there is not really any difference between them.

from trelloscrum.

Yeah, I agree w. you on that. The point recalibration meeting is always a rowdy one, haha.
The alignment with some of the popular decks and plugins is more the driving factor here. There are two schools of thought on it, pretty divided :-)
Adding it was 100% backwards compatible and brought the picker into alignment with some card decks and scrum poker virtual tools.
I think that since its showing up in decks etc there isn't a downside to adding it. But I guess if it is driving people crazy or breaking things then it could come out again...

from trelloscrum.

It is not an important issue, I am just getting to know the product before trying to submit some modifications. I guess this can be left like this.

from trelloscrum.

Thanks for helping out. That's pretty great.

from trelloscrum.

You can use custom points (i.e. 4, 0.25) if you type them manually in the card title. We received some questions regarding adding 0.5 to the default list, so we did just that.

from trelloscrum.