• Icon: Suggestion Suggestion
    • Resolution: Answered
    • 5.6
    • None
    • None
    • We collect Jira feedback from various sources, and we evaluate what we've collected when planning our product roadmap. To understand how this piece of feedback will be reviewed, see our Implementation of New Features Policy.

      Is it possible to add such a field, and have Burndown Charts use that value?

      Or is this a violation of "how Scrum works"?

      Related to this is logging of work. Normally you log work in time units. But we would like to log work as "story points worth of work". Basically, we're after the same functionality for Story Points as we already have for time (Estimate, Spent, Remaining).

          Form Name

            [JSWSERVER-2647] "Remaining Story Points" field for individual Stories

            danielpid added a comment -

            I don't understand why you don't want to implement this. We are only asking for the possibility of using this, if some teams find useful this feature, why don't you want to make it available and increase the satisfaction?

            danielpid added a comment - I don't understand why you don't want to implement this. We are only asking for the possibility of using this, if some teams find useful this feature, why don't you want to make it available and increase the satisfaction?

            Partial done would be useful in certain situations, I think it makes sense to account for the progress already done when planning the next sprint

            Tamás Hegedűs added a comment - Partial done would be useful in certain situations, I think it makes sense to account for the progress already done when planning the next sprint

            Man, I really did not understand what is the matter about implement "partial Done". Microsoft offers this feature and it's really great. On Jira, I have to do both estimations (story points and hours). I really can't see the real problem. 

            Fernando Gonçalves added a comment - Man, I really did not understand what is the matter about implement "partial Done". Microsoft offers this feature and it's really great. On Jira, I have to do both estimations (story points and hours). I really can't see the real problem. 

            Please note that while this issue has been resolved in 5.6.0 the status will let you know whether it has been Fixed, Answered, Obsolete or Won't Fix.

            Nicholas Muldoon [Atlassian] added a comment - Please note that while this issue has been resolved in 5.6.0 the status will let you know whether it has been Fixed, Answered, Obsolete or Won't Fix.

            Hi Christoffer,

            Thanks for confirming that, I will close this issue as 'Answered'.

            The GreenHopper team, by way of example, first estimates stories using story points (Fibonacci). Once we have completed that estimation the team breaks the stories into individual sub-tasks for each story, these cover the tasks that will be completed as part of the story work. Usually, a story with a story point estimate of five may have between 4 and 10 sub-tasks. We then estimate each of these sub-tasks in hours to give us a (quite) granular look at the upcoming sprint.

            Time spent is then logged against these sub-tasks as work progresses and this provides our hour burndown chart.

            There is not a simple conversion of story points to hours. Perhaps your team may wish to start with estimating in hours only, and then introduce story points at a later date.

            Thank you Christoffer.

            Regards,
            Nicholas

            Nicholas Muldoon [Atlassian] added a comment - Hi Christoffer, Thanks for confirming that, I will close this issue as 'Answered'. The GreenHopper team, by way of example, first estimates stories using story points (Fibonacci). Once we have completed that estimation the team breaks the stories into individual sub-tasks for each story, these cover the tasks that will be completed as part of the story work. Usually, a story with a story point estimate of five may have between 4 and 10 sub-tasks. We then estimate each of these sub-tasks in hours to give us a (quite) granular look at the upcoming sprint. Time spent is then logged against these sub-tasks as work progresses and this provides our hour burndown chart. There is not a simple conversion of story points to hours. Perhaps your team may wish to start with estimating in hours only, and then introduce story points at a later date. Thank you Christoffer. Regards, Nicholas

            Hi Nicholas,

            I got the answer I anticipated, and I totally understand your reasoning.

            So, I'm thinking of ways around this "predicament". Is it possible to "convert" story points to a time value (Original estimate)? If you know your velocity, this might be a better way.

            Thanks,

            • Christoffer Lette

            Christoffer Lette added a comment - Hi Nicholas, I got the answer I anticipated, and I totally understand your reasoning. So, I'm thinking of ways around this "predicament". Is it possible to "convert" story points to a time value (Original estimate)? If you know your velocity, this might be a better way. Thanks, Christoffer Lette

            Hi Christoffer,

            When we talk about the story points burndown we believe that there is no partial 'done'. A story is done when it is complete and as such all story points will be 'burned' once done, but not before.

            While I can see that it is technically possible to provide this functionality I do not believe it provides value for GreenHopper customers.

            If you have no objection I will close this as 'Won't Fix'.

            Thank you Christoffer.

            Regards,
            Nicholas Muldoon

            Nicholas Muldoon [Atlassian] added a comment - Hi Christoffer, When we talk about the story points burndown we believe that there is no partial 'done'. A story is done when it is complete and as such all story points will be 'burned' once done, but not before. While I can see that it is technically possible to provide this functionality I do not believe it provides value for GreenHopper customers. If you have no objection I will close this as 'Won't Fix'. Thank you Christoffer. Regards, Nicholas Muldoon

              Unassigned Unassigned
              1f1966539af2 Christoffer Lette
              Votes:
              0 Vote for this issue
              Watchers:
              10 Start watching this issue

                Created:
                Updated:
                Resolved: