Uploaded image for project: 'Jira Software Data Center'
  1. Jira Software Data Center
  2. JSWSERVER-1288

As a project manager, I would like to be able to view a burndown chart that clearly communicates changes in scope.

XMLWordPrintable

    • Icon: Suggestion Suggestion
    • Resolution: Fixed
    • 6.0.1
    • 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.

      Burndown charts don't do a good job of showing when scope gets added to a project. There are q number of good charting techniques for doing this. See possible examples in fugs 3-23 to 3-26 here:

      http://alistair.cockburn.us/Earned-value+and+burn+charts

      Either add a vertical spike when new stories are added or old stories are re-estimated – or convey the same thing by having the bottom line step down below zero (This is nice because you can get a sense of the total scope addition over time).

        1. Screen shot 2011-08-30 at 11.15.37 .png
          27 kB
          Tanel Tenso
        2. Screen shot 2011-08-30 at 16.52.43.png
          50 kB
          Tanel Tenso

            [JSWSERVER-1288] As a project manager, I would like to be able to view a burndown chart that clearly communicates changes in scope.

            Katherine Yabut made changes -
            Workflow Original: JAC Suggestion Workflow [ 3065843 ] New: JAC Suggestion Workflow 3 [ 3660937 ]
            Status Original: RESOLVED [ 5 ] New: Closed [ 6 ]
            Owen made changes -
            Workflow Original: Confluence Workflow - Public Facing v4 [ 2624392 ] New: JAC Suggestion Workflow [ 3065843 ]
            Rachel Lin (Inactive) made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2326231 ] New: Confluence Workflow - Public Facing v4 [ 2624392 ]
            Status Original: Closed [ 6 ] New: Resolved [ 5 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 2043026 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2326231 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 - TEMP [ 2031110 ] New: JIRA PM Feature Request Workflow v2 [ 2043026 ]
            Katherine Yabut made changes -
            Workflow Original: JIRA PM Feature Request Workflow v2 [ 738798 ] New: JIRA PM Feature Request Workflow v2 - TEMP [ 2031110 ]
            Martin (Inactive) made changes -
            Backlog Order (Obsolete) Original: 570000000
            Workflow Original: GreenHopper Kanban Workflow v2 [ 300432 ] New: JIRA PM Feature Request Workflow v2 [ 738798 ]
            Issue Type Original: Story [ 16 ] New: Suggestion [ 10000 ]
            Priority Original: Major [ 3 ]
            Status Original: Resolved [ 5 ] New: Closed [ 6 ]
            Shaun Clowes (Inactive) made changes -
            Fix Version/s New: 6.0.1 [ 27805 ]
            Resolution New: Fixed [ 1 ]
            Status Original: Open [ 1 ] New: Resolved [ 5 ]

            Shaun Clowes (Inactive) added a comment -

            The burndown chart in the new GreenHopper boards now display scope change (and explicitly call out scope change in the table below the chart).

            Thanks,
            Shaun

            Shaun Clowes (Inactive) added a comment - The burndown chart in the new GreenHopper boards now display scope change (and explicitly call out scope change in the table below the chart). Thanks, Shaun
            Shaun Clowes (Inactive) made changes -
            Rank New: Ranked higher

              Unassigned Unassigned
              77658968547c Steve Lane
              Votes:
              34 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: